| Status | Pending Stakeholder Review |
| Owner | |
| Stakeholders |
Issue
Syensqo has two systems which have very different rules for defining the Sales Org.
Recommendation
Background & Context
Syensqo has multiple business units that are independent and separate organizations operating in legal entities that are shared across more than 1 GBU (Refer to the picture below for the same). Following are some of the requirements at the GBU level
1) Operational segregation of information and access to the users in the system based on the GBU they belong to (ie. a salse person in one GBU can't see master data or transactional data from another GBU even if they are in the same legal entity)
2) Operational and Management Reporting by GBU. This means that both transactional level reports as well as summarized management reports must both be able to be segregated and secured by GBU.
Currently a combination of methods are used to represent these GBU requirements, i.e. Separate Sales Org per GBU for some entities and GBU's and a combination of Division and Distribution Channel for the other GBU's and entities. This non-standard way of representation creates a lot of overhead / inconsistencies while reporting and also pose a significant challenge when the GBU's are restructured.
Assumptions
Constraints
Impacts
Business Rules
Options considered
Option A: Sales Organization
Option B: Division
Option C: Profit Center
Option D: Next Labs DAM and DAE
Evaluation
Option A | Option B | Option C | Option D | |
|---|---|---|---|---|
| Criterion 1 |
|
|
|
|
| Criterion 2 |
|  Con |
|
|
| Criterion 3 |  Pro | Con | Con | Pro |
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||