View Source

Overview

This page gives an overview of all the enterprise structure objects in Syensqo.

Numbering Rules

Overview

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.

Recommendation

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

Impact

One time mapping / cleansing required in upstream / downstream systems/applications that use the old enterprise structure

Finance Enterprise Structure

This section will detail the Finance Enterprise Structure objects and the proposed design along with the Rational for the same.

Stream	Enterprise Structure Object	Proposed Design	Aligned with As-Is Enterprise Structure	Aligned with Best Practise	Options Considered	Detailed evaluation required	Design decision rational	Requirement to differentiate GBU?	GBU Differentiation method
Finance	Controlling Area	One Controlling Area for Syensqo	No	Yes	No	No	Provides consistent approach to cost capturing, inventory valuation and reporting and analysis of its costs	No
	Operating Concern	One Operating concern per controlling area	No	Yes	No	No	Provides global profitability analysis by enabling group wide consistent treatment of transactions and flow of values captured against common characteristics	No
	Company	One company per each Syensqo legal entity	No	Yes	No	No	Setting up companies for every entity enables the consolidation process/ I/C eliminations	No
	Company Code	One company code per operational legal entity (Consolidated)/ JV operated by Syensqo	No	Yes	Yes	Yes	Company Code	Yes	Profit center Group and Segments
	Credit Control Area	One Credit control area for Syensqo	Yes	Yes	Yes	Yes		No
	Segment	One Segment per Operational GBU	No	No	Yes	Yes		No
	Standard Profit Centre Hierarchy	Profit center hierarchy groups aligned with GBU	No	No	Yes	No	Reform Finance Master Data KDD
	Standard Cost Centre Hierarchy						Reform Finance Master Data KDD
	Chart of Accounts						Reform Finance Master Data KDD
	Chart of Depreciation	One chart of depreciation shall be created for each country					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.

This section describes the applications and modules that the finance enterprise structure objects are

test

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

Sales Enterprise Structure

Stream	Enterprise Structure Object	Proposed Design	Aligned with As-Is Enterprise Structure	Aligned with Best Practise	Options Considered	Detailed evaluation required	Design decision rational	Requirement to differentiate GBU?	GBU Differentiation method	Additional Information
Sales	Sales Organisation	One Sales Org per company code and GBU	No	No	Yes	Yes	Sales Organisation Approach KDD
	Distribution Channel	One distribution channel per external sale channel One Intercompany Sales Channel	No	No	No	No
	Division	To be determined during the detailed design based on the product grouping	No	No	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
	Sales Area
	Sales Office
	Sales Groups

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
	Sales organization	CX*	Sales organization
	Sales Area		Sales Area
	Sales Office		Sales Office
	Sales Group		Sales Group

Supply Chain Enterprise Structure

Stream	Enterprise Structure Object	Proposed Design	Aligned with As-Is Enterprise Structure	Aligned with Best Practise	Options Considered	Detailed evaluation required	Design decision rational	Requirement to differentiate GBU?	GBU Differentiation method	Additional Information
Supply Chain	Plant
	Maintenance Plant
	Planning Plant
	Quality management Plant
	Storage Location
	Warehouse numbers
	Shipping Points / Goods Receiving Points
	Transportation Planning Points

Source system / application / Module	Enterprise Structure Object	Target system / Application / Module	Enterprise Structure Object	Comments
SAP S/4HANA	Plant	Ariba	Plant
SAP S/4HANA	Plant	GTS	Legal Unit
SAP S/4HANA	Storage Location	GTS	Legal Unit
SAP S/4HANA	Warehouse Number	SAP EWM	Warehouse number

Procurement Enterprise Structure

Stream	Enterprise Structure Object	Proposed Design	Aligned with As-Is Enterprise Structure	Aligned with Best Practise	Options Considered	Detailed evaluation required	Design decision rational	Requirement to differentiate GBU?	GBU Differentiation method	Additional Information
Purchasing	Purchasing Org
Purchasing	Purchasing Group

Source system / Application / Module	Enterprise Structure Object	Target system / Application / Module	Enterprise Structure Object	Comments
SAP S/4 HANA	Purchasing organization	Ariba	Purchasing organization
SAP S/4 HANA	Purchasing Group	Ariba	Purchasing Group