This page gives an overview of all the enterprise structure objects in Syensqo.
Currently, there are varied and disjointed numbering rules across multiple enterprise structure objects within the two existing ECC/SAP systems. This inconsistency poses a significant challenge when migrating to the S/4HANA system, as the differing number ranges and numbering rules in each of these systems complicate the use of consistent numbering. The migration process becomes cumbersome due to the need to reconcile these discrepancies and ensure that the new system maintains data integrity and coherence. However, with the ERP Rebuild Hub program, there is an opportunity to align and standardize the enterprise structure definition and numbering. This program can facilitate the harmonization of number ranges and rules, making the transition to S/4HANA smoother and more efficient. Standardization not only addresses the immediate challenges of migration but also simplifies future system maintenance and scalability, promoting overall operational efficiency and ensuring that all enterprise structure objects are accurately and uniformly numbered in the new environment.
Align and standardize the enterprise structure definition and numbering (old numbers will be referenced for searching purposes). A list of the enterprise structure numbering rules can be found here
One time mapping / cleansing required in upstream / downstream systems/applications that use the old enterprise structure
This section will detail the Finance Enterprise Structure objects and the proposed design along with the Rational for the same.
| Enterprise Structure Object | Proposed Design | Options Considered | Detailed evaluation required | Design decision rational | Requirement to differentiate GBU? | GBU Differentiation method | Additional Information |
|---|---|---|---|---|---|---|---|
| One Controlling Area for Syensqo | No | No | Provides consistent approach to cost capturing, inventory valuation and reporting and analysis of its costs | No | ||
| One Operating concern per controlling area | No | No | Provides global profitability analysis by enabling group wide consistent treatment of transactions and flow of values captured against common characteristics | No | ||
| One company per each Syensqo legal entity | No | No | Setting up companies for every entity enables the consolidation process/ I/C eliminations | No | ||
| One company code per operational legal entity (Consolidated)/ JV operated by Syensqo | Yes | Yes | Company Code | Yes | Profit center Group and Segments | |
| One Credit control area for Syensqo | Yes | Yes | No | |||
| One Segment per Operational GBU | Yes | Yes | No | |||
| To be decided during the detailed design (Profit center hierarchy groups aligned with GBU) | Yes | No | Reform Finance Master Data KDD | No | ||
| To be decided during the detailed design | Yes | Yes | Reform Finance Master Data KDD | No | ||
| To be decided during the detailed design | Yes | Yes | Reform Finance Master Data KDD | No | ||
| One chart of depreciation shall be created for each country | No | No | Fixed Asset valuation principles are defined in the respective accounting principles a company needs to follow, these can be group policies following IFRS rules and guidelines as leading accounting principles for listed companies up to local GAAP and tax accounting requirements which are stipulated by regulatory bodies within each country’s legislation. | No |
This section describes the applications and modules that the finance enterprise structure objects are mapped to.
Target system / application / Module | Enterprise Structure Object | Source system / Application / Module | Enterprise Structure Object | Comments |
S/4 HANA | Company Code | S/4 HANA Project Portfolio Management | Area Code | |
Ariba | Company Code | |||
SAP TM | Company organization | |||
SAP GTS | Company Code | |||
SAP SF | Legal Entity | |||
SAP Concur | Company |
This section will detail the Sales Enterprise Structure objects and the proposed design along with the Rational for the same.
| Enterprise Structure Object | Proposed Design | Options Considered | Detailed evaluation required | Design decision rational | Requirement to differentiate GBU? | GBU Differentiation method | Additional Information |
|---|---|---|---|---|---|---|---|
| One Sales Org per company code and GBU | Yes | Yes | Sales Organisation Approach KDD | Yes | Sales Org | |
| One distribution channel per external sale channel One Intercompany Sales Channel | No | No | No | No | ||
| To be determined during the detailed design based on the product grouping | No | No | No | No | Division is considered as a option to achieve the GBU differentiation. Please refer to Sales Organisation Approach KDD for more details | |
| The Sales Office will represent Syensqo’s sales territories and geographic locations - The actual values will be determined during the detailed design | No | No | No | No | ||
| A sales group will be a group of people (or an individual) who are (is) responsible for selling certain products or services - | No | No | No | No |
This section describes the applications and modules that the Sales enterprise structure objects are mapped to.
Source system / application / Module | Enterprise Structure Object | Target system / Application / Module | Enterprise Structure Object | Comments |
SAP S/4 HANA | Sales organization | SAP TM | Sales organization | |
CX* | Sales organization | |||
Sales Area | Sales Area | |||
Sales Office | Sales Office | |||
Sales Group | Sales Group |
This section will detail the Supply Chain Enterprise Structure objects and the proposed design along with the Rational for the same.
| Enterprise Structure Object | Proposed Design | Options Considered | Detailed evaluation required | Design decision rational | Requirement to differentiate GBU? | GBU Differentiation method | Additional Information |
|---|---|---|---|---|---|---|---|
| To set-up as a plant, after evaluating the steps in the decision tree for managing plant. | Yes | Yes | Plants Approach | Yes - Inventory | Plant Hierarchy has some elements to differentiate the GBU in case valuation is different. Profit Center Allocation if more than one GBU exists in the same plant | |
| A Maintenance Plant will be established for each Logistics Plant where asset maintenance management activities are carried out | No | No | No | |||
| One planning plant for manufacturing centers and one for the rest of the plants in the company code (if maintenance activities exist in the company code) | No | No | No | |||
| A storage location is created to represent the physical stock. There are exception scenarios where partner storage locations are created ex: Unpacking for a HU location | No | No | No | |||
| To set-up as a Warehouse, after evaluating the steps in the decision tree for managing Warehouse. | ||||||
| At least one shipping point per plant. A new shipping point in a plant if new address or when pre-defined loading or pick/pack times are different (e.g. Export shipping point vs domestic shipping point.as Export shipping point might load into containers and domestic only loads into truck. | No | No | No |
This section describes the applications and modules that the Supply Chain enterprise structure objects are mapped to.
Source system / application / Module | Enterprise Structure Object | Target system / Application / Module | Enterprise Structure Object | Comments |
SAP S/4HANA | Plant | Ariba | Plant | |
GTS | Legal Unit | |||
SAP S/4HANA | Storage Location | GTS | Legal Unit | |
SAP S/4HANA | Warehouse Number | SAP EWM | Warehouse number |
This section will detail the Procurement Enterprise Structure objects and the proposed design along with the Rational for the same.
| Enterprise Structure Object | Proposed Design | Options Considered | Detailed evaluation required | Design decision rational | Requirement to differentiate GBU? | GBU Differentiation method | Additional Information |
|---|---|---|---|---|---|---|---|
| One purchasing org per country + One global purchasing org | Yes | Yes | Enterprise Structure Approach - Procurement - ERP Rebuild - Syensqo - Wiki knowledge base | No | ||
| To be decided after detailed design | No | No | No |
This section describes the applications and modules that the Procurement enterprise structure objects are mapped to.
Source system / Application / Module | Enterprise Structure Object | Target system / Application / Module | Enterprise Structure Object | Comments |
SAP S/4 HANA | Purchasing organization | Ariba | Purchasing organization | |
Purchasing organization | TM | Purchasing organization | ||
SAP S/4 HANA | Purchasing Group | Ariba | Purchasing Group |