Status

pagestatus

Percentage Progress | Vectors (Formerly: SP Percentage progress bar)

backgroundColor	0052CC
percentage	100

Owner

Soumen Laru

Stakeholders

PILLAY-ext, Lawrence WELENSKY-ext, Dave GARCIA-ext, Angel Luis SAKTHIVEL-ext, Navaneetha

Purpose

The purpose of this document is to define the conversion approach of Profit Centres into S/4 HANA. Profit Centres

The document details out the field list, extraction criteria, scoping, mapping of cost centre object

Profit Centres will be constructed based on the target design and a DCT(Constructed data based on Data Collection Template) will be provided to Syniti for subsequent processing. Along with the DCT, a mapping file of legacy(ECC) to target(S4) will be provided for dependent master and transaction objects.Cost Centres will be extracted from Source and based on the list of cost centres from the cost centre mapping sheet, target cost centre data file will be

Conversion Scope

Profit Centres which will be listed as part of scope list with new numbering will be in scope of migration.

List of source systems and approximate number of records

Note: All the Profit Centres to be migrated will be collected. Therefore, Profit Centres are not going to be extracted from source and details given below is given for information purpose only.

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Profit Centre	6,423	S4HANA	TBD
WP2	Profit Centre	5,768	S4HANA	TBD

Additional Information

Multi-language Requirement

In the Syensqo Profit Centres, the following four language keys must be maintained:
- English (EN)
- French (FR)
- Italian (IT)
- Chinese (ZN)
Note: For certain countries it may be required to also maintain account descriptions for certain Profit Centres in local language as per regulatory requirement (e.g. Japanese) in the respective country. Such requests must be backed by supporting evidence of the underlying regulatory requirement.
Such data will be collected as part of DCT for the translation texts for Profit Centres.

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Label	Data Type	Length	Requirement	Syensqo Requirement R = Required : Mandatory field. O = Optional: Not mandatory. If a value is entered it doesn't impact Business Process. C = Conditional: Not mandatory. If a value is entered it impacts Business Process or Reporting. S = System: System generates the value. NU = Not Used
CEPC	PRCTR	PRCTR	Profit Center	CHAR	10	Organizational unit in controlling used for internal reporting and responsibility accounting. The Profit center represents in syensqo context either a Plant or a GBS 'non Plant'. The Syensqo PC codification must follow the naming convention. "1 + 4 "" Digit #1 = GBU Indicator S=SPEC. POLYMERS or C=COMPOSITE MATERIALS or N=NOVECARE or T=TECHNOLOGY SOLUTIONS or B=CBS From digit 2 to 5 : 4 char. Company Code OR Plant Code. Illustration : S1001	R
CEPC	DATBI	DATBI	Valid To Date	DATS	8	Date until which the Profit Center is valid.	R
CEPC	KOKRS	KOKRS	Controlling Area	CHAR	4	Identifies a self-contained organizational structure for which costs and revenues can be managed. Only 1 controlling used for all legal entities. Same value across all systems (same in 3 boxes : Global instance + Composites + China).	R
CEPC	DATAB	DATAB	Valid-From Date	DATS	8	Date from which the Profit Center is valid.	R
CEPC	VERAK	VERAPC	Person Responsible for Profit Center	CHAR	20	Name or ID of the person responsible for managing the Profit Center.

R

NU
CEPC	VERAK_USER	VERAPC_USER	User Responsible for the Profit Center	CHAR	12	SAP user ID of the responsible person.

C

NU
CEPC	WAERS	WAERS	Currency Key	CUKY	5	Currency used in the Profit Center. Will follow the legal entity one.

R

NU
CEPC	LAND1	LAND1	Country Key	CHAR	3	Country code related to the Profit Center's location.

O

C
CEPC	NAME1	NAME1_GP	Name 1	CHAR	35	First line of the name or company name of the Profit Center. Description of the Profit center.

R

NU
CEPC	NAME2	NAME2_GP	Name 2	CHAR	35	Second line of the name or company name.

O

NU
CEPC	NAME3	NAME3_GP	Name 3	CHAR	35	Third line of the name or additional details.

O

NU
CEPC	NAME4	NAME4_GP	Name 4	CHAR	35	Fourth line of the name or additional details.

O

NU
CEPC	ORT01	ORT01_GP	City	CHAR	35	City name in the Profit Center address.

O

C
CEPC	ORT02	ORT02_GP	District	CHAR	35	District or region in the address.

O

C
CEPC	STRAS	STRAS_GP	Street and House Number	CHAR	35	Street name and house number of the Profit Center location.

O

NU
CEPC	PFACH	PFACH	PO Box	CHAR	10	PO Box address.

O

NU
CEPC	PSTLZ	PSTLZ	Postal Code	CHAR	10	Postal code for the street address.

O

NU
CEPC	PSTL2	PSTL2	P.O. Box Postal Code	CHAR	10	Postal code associated with the PO Box.

O

NU
CEPC	SPRAS	SPRAS	Language Key	LANG	1	Language key used in texts and descriptions.

O

R
CEPC	TELBX	TELBX	Telebox number	CHAR	15	Telebox number (rarely used).

O

NU
CEPC	TELF1	TELF1	First telephone number	CHAR	16	Primary contact phone number.

O

NU
CEPC	TELF2	TELF2	Second telephone number	CHAR	16	Secondary contact phone number.

O

NU
CEPC	TELFX	TELFX	Fax Number	CHAR	31	Fax number.

O

NU
CEPC	TELTX	TELTX	Teletex number	CHAR	30	Teletex number (obsolete).

O

NU
CEPC	TELX1	TELX1	Telex number	CHAR	30	Telex number (obsolete).

O

	NU
CEPC	KHINR	PHINR	Profit center area	CHAR	12	Profit center area	NU
CEPC	BUKRS	BUKRS	Company Code	CHAR	4	Associated company code for reporting.

O

NU
CEPC	TXJCD	TXJCD	Tax Jurisdiction	CHAR	15	Tax jurisdiction code used for tax reporting.

C

NU
CEPC	REGIO	REGIO	Region (State, Province, County)	CHAR	3	State or regional subdivision (used in address).

O

NU
CEPC	LOCK_IND	LOCK_IND	Lock indicator	CHAR	1	Indicates if the Profit Center is locked for processing. If locked : no posting possible.	C
CEPCT

CEPCCEPCTKTEXTKTEXTName#N/A

KTEXT

PCA_TEMPLATEPCA_TEMPLATETemplate for Formula Planning in Profit CentersCHAR10Reference template used for planning purposes in Profit Centers.C

KTEXT

Name

CHAR

20	Profit Center Name	R
CEPCT	LTEXT	LTEXT	Long Text

#N/A

CHAR	40	Profit Center Long Text	R
CEPCT	MCTXT	MCTXT	Profit Center Text

#N/A

CHAR

20

Profit Center Text

O

R

Data Cleansing

Note: Cleansing is applicable only for business and as the data for this object is collected, cleansing is not relevant for data conversion. It just helps business to reduce the mapping requirements.

Criticality

Report

ID

Error Message/Report Description

Rule

ID

Criticality

Error Message/Report Description

Rule

Output

Source System

1.

Can load, but business process will fail

Lock any Profit Centre not being used for last 5 years

TBD

PF2 / WP2

Note: Cleansing mau not be necessary as the ex

N/A

Conversion Process

The high-level

Conversion Process

The high-level process is represented by the diagram below:

Note: When Data Source denotes DCT, no relevancy and extract rules to be applied in Syniti tool. DCT records will be collected by business Data Consultant.

Data Privacy and Sensitivity

Extraction

Extract data from a source into . There are 2 possibilities:

The data exists. connects to the source and loads the data into . There are 3 methods:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #

Requirement description

Team responsible

1.

Ensure source tables CEPC and CEPCT are extracted in tool according to the agreed cut-off date in the project plan

Ensure DCT is collected for the Profit Centres based on the collection template

Data team

2.

Perform preliminary completeness check documented in section 5.2.8.1.1

Data team

3.

Raise issues as defects if Req # 1 to 2 are not met

Data team

4.

Repeat Req # 1 to 3 if required

Data team

5.

Report extraction result to person in charge of APOI conversion

Data team

Extraction Run Sheet

Req #	Requirement description	Team responsible
1.	Ensure DCT is collected for the Profit Centres based on the collection template	Data team

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules and will be used by the data collectors.

Note: Constructed data will be imported into ADM Data Construction page.

There will be two pages -

1. Main page to contain the Profit Centre details with EN Language key Description

2. Detailed Page will contain descriptions in various languages as they are collected.

Table Name	Field Name	Field description	Rule
CEPC	PRCTR	Profit Center	This field must be 5 digits. It must follow the naming convention described in governance rules applied
CEPC	DATBI	Valid To Date	31.12.9999 by default. If a PC has a end date : this field can be updated with the accurate values. Select Last day of a month period at least (not a date during a period).
CEPC	KOKRS	Controlling Area	1 unique value for all PC.
CEPC	DATAB	Valid-From Date	Date of the creation of the Prof.center during the run. Date of the go live for the ones Mass loaded as part of the Syway cut over
CEPC	LAND1	Country Key	Collected as required
CEPC	ORT01	City	Collected as required
CEPC	ORT02	District	Collected as required
CEPC	SPRAS	Language Key	Collected as required
CEPC	KHINR	Profit center area	Collected as required
CEPC	LOCK_IND	Lock indicator	Case to tick if a Profit center must be blocked for posting : obsolete PC or PC created by mistake.

Descriptions will be collected on multiple languages and therefore a detail page to created and linked to the main page

Table Name	Field Name	Field description	Rule
CEPC	KOKRS	Controlling Area	1 unique value for all PC.
CEPC	PRCTR	Profit Center	This field must be 5 digits. It must follow the naming convention described in governance rules applied
CEPCT	DATBI	Valid To Date
CEPCT	SPRAS	Language Key	In the Syensqo Profit centers, the following four language keys must be maintained: - English (EN) - French (FR) - Italian (IT) - Chinese (ZN) Additionally, fill in the name and description for the language key;
CEPCT	KTEXT	Name	Max Length: 20
CEPCT	LTEXT	Long Text	Max Length: 40
CEPCT	MCTXT	Profit Center Text	Max Length: 20

Extraction Dependencies

Item #	Step description	Team responsible
1.	N/A

Transformation

The Target fields are mapped to the applicable DCT field that will be its source.

Note: as this object is DCT, the mapping rule for all the fields is 'Copy' as described in the transform rule section. However, some reports are to be created and executed to ensure integrity in the data collected in DCT as described in 'Pre-load Data Validation' section.

This step identifies the transformation activity required to allow to make the data Target ready:

Prepare target-ready data in the target structure and format that is required for loading via prescribed Load Tool in the load section.
Produce the preload reports as requested in the 'Preload Data Validation' section.

Transformation Run Sheet

Item #	Step description	Team responsible
1.	Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into toolMigrate.	Data team
2.	In tool, select the Trial Balance object PY.	Data team
3.	Go to Process Area Launch and Process the Object - Trial Balance object - R4 Trial Balance PY.	Data team
4.	Launch the Objects to execute transformation.	Data team
5.	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
6.	Generate Pre-Load reports .	Data team
7.	Generate data load count.	Data team
8.	Log errors as defects, if any and address resolutions. Close defects.	Data team
9.	Re-transform and re-validate the Pre-load reports if necessary.	Data team
10.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
11.	Analyse and resolve any pre-load defects logged by business.	Data team
12.	Repeat steps 6 to 11 if necessary	Data team
13.	Proceed to pre-load validations	Data team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source description	Target system	Target Table	Target Field	Target description	Transformation logic
1	DCT/ECC	CEPC	PRCTR	Profit Center	S/4HANA	CEPC	PRCTR	Profit Center	Copy From DCT as-is
2	DCT/ECC	CEPC	DATBI	Valid To Date	S/4HANA	CEPC	DATBI	Valid To Date	Copy From DCT as-is
3	DCT/ECC	CEPC	KOKRS	Controlling Area	S/4HANA	CEPC	KOKRS	Controlling Area	Copy From DCT as-is
4	DCT/ECC	CEPC	DATAB	Valid-From Date	S/4HANA	CEPC	DATAB	Valid-From Date	Copy From DCT as-is
8	DCT/ECC	CEPC	LAND1	Country Key	S/4HANA	CEPC	LAND1	Country Key	Copy From DCT as-is
13	DCT/ECC	CEPC	ORT01	City	S/4HANA	CEPC	ORT01	City	Copy From DCT as-is
14	DCT/ECC	CEPC	ORT02	District	S/4HANA	CEPC	ORT02	District	Copy From DCT as-is
19	DCT/ECC	CEPC	SPRAS	Language Key	S/4HANA	CEPC	SPRAS	Language Key	Copy From DCT as-is
27	DCT/ECC	CEPC	KHINR	Profit center area	S/4HANA	CEPC	KHINR	Profit center area	Copy From DCT as-is
30	DCT/ECC	CEPC	LOCK_IND	Lock indicator	S/4HANA	CEPC	LOCK_IND	Lock indicator

Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field Name	Field description	Rule
CEPC-PRCTR	Profit Centre	Business to enter content as per data type and length permitted

Suggestion to add:

Decimal validation - Check table TCURX for the document currency key and if Decimals (TCURX-CURRDEC) is ‘0’, validate that no decimal value is populated.

Extraction Dependencies

Item #	Step description	Team responsible
1.	Any period / year end close activities have been fully completed	Business
2.	Reconciliation for intercompany payables have been completed, and adjustment made in legacy SAP system	Business
3.	Reconciliation of migrated Purchase Order is completed before the extraction of Accounts Payable Open Items	Business and Data

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in
Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step description	Team responsible
1.	Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into toolMigrate.	Data team
2.	In tool, select the Trial Balance object PY.	Data team
3.	Go to Process Area Launch and Process the Object - Trial Balance object - R4 Trial Balance PY.	Data team
4.	Launch the Objects to execute transformation.	Data team
5.	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
6.	Generate Pre-Load reports .	Data team
7.	Generate data load count.	Data team
8.	Log errors as defects, if any and address resolutions. Close defects.	Data team
9.	Re-transform and re-validate the Pre-load reports if necessary.	Data team
10.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
11.	Analyse and resolve any pre-load defects logged by business.	Data team
12.	Repeat steps 6 to 11 if necessary	Data team
13.	Proceed to pre-load validations	Data team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source description	Target system	Target Table	Target Field	Target description	Transformation logic
1	DCT/ECC	CEPC	PRCTR	Profit Center	S/4HANA	CEPC	PRCTR	Profit Center	Copy From DCT as-is
2	DCT/ECC	CEPC	DATBI	Valid To Date	S/4HANA	CEPC	DATBI	Valid To Date	Copy From DCT as-is
3	DCT/ECC	CEPC	KOKRS	Controlling Area	S/4HANA	CEPC	KOKRS	Controlling Area	Copy From DCT as-is
4	DCT/ECC	CEPC	DATAB	Valid-From Date	S/4HANA	CEPC	DATAB	Valid-From Date	Copy From DCT as-is
5	DCT/ECC	CEPC	VERAK	Person Responsible for Profit Center	S/4HANA	CEPC	VERAK	Person Responsible for Profit Center	Apply Mapping of Employee
6	DCT/ECC	CEPC	VERAK_USER	User Responsible for the Profit Center	S/4HANA	CEPC	VERAK_USER	User Responsible for the Profit Center	Copy From DCT as-is
7	DCT/ECC	CEPC	WAERS	Currency Key	S/4HANA	CEPC	WAERS	Currency Key	Copy From DCT as-is
8	DCT/ECC	CEPC	LAND1	Country Key	S/4HANA	CEPC	LAND1	Country Key	Copy From DCT as-is
9	DCT/ECC	CEPC	NAME1	Name 1	S/4HANA	CEPC	NAME1	Name 1	Copy From DCT as-is
10	DCT/ECC	CEPC	NAME2	Name 2	S/4HANA	CEPC	NAME2	Name 2	Copy From DCT as-is
11	DCT/ECC	CEPC	NAME3	Name 3	S/4HANA	CEPC	NAME3	Name 3	Copy From DCT as-is
12	DCT/ECC	CEPC	NAME4	Name 4	S/4HANA	CEPC	NAME4	Name 4	Copy From DCT as-is
13	DCT/ECC	CEPC	ORT01	City	S/4HANA	CEPC	ORT01	City	Copy From DCT as-is
14	DCT/ECC	CEPC	ORT02	District	S/4HANA	CEPC	ORT02	District	Copy From DCT as-is
15	DCT/ECC	CEPC	STRAS	Street and House Number	S/4HANA	CEPC	STRAS	Street and House Number	Copy From DCT as-is
16	DCT/ECC	CEPC	PFACH	PO Box	S/4HANA	CEPC	PFACH	PO Box	Copy From DCT as-is
17	DCT/ECC	CEPC	PSTLZ	Postal Code	S/4HANA	CEPC	PSTLZ	Postal Code	Copy From DCT as-is
18	DCT/ECC	CEPC	PSTL2	P.O. Box Postal Code	S/4HANA	CEPC	PSTL2	P.O. Box Postal Code	Copy From DCT as-is
19	DCT/ECC	CEPC	SPRAS	Language Key	S/4HANA	CEPC	SPRAS	Language Key	Copy From DCT as-is
20	DCT/ECC	CEPC	TELBX	Telebox number	S/4HANA	CEPC	TELBX	Telebox number	Copy From DCT as-is
21	DCT/ECC	CEPC	TELF1	First telephone number	S/4HANA	CEPC	TELF1	First telephone number	Copy From DCT as-is
22	DCT/ECC	CEPC	TELF2	Second telephone number	S/4HANA	CEPC	TELF2	Second telephone number	Copy From DCT as-is
23	DCT/ECC	CEPC	TELFX	Fax Number	S/4HANA	CEPC	TELFX	Fax Number	Copy From DCT as-is
24	DCT/ECC	CEPC	TELTX	Teletex number	S/4HANA	CEPC	TELTX	Teletex number	Copy From DCT as-is
25	DCT/ECC	CEPC	TELX1	Telex number	S/4HANA	CEPC	TELX1	Telex number	Copy From DCT as-is
26	DCT/ECC	CEPC	BUKRS	Company Code	S/4HANA	CEPC	BUKRS	Company Code	Company Code Mapping File to be used
27	DCT/ECC	CEPC	TXJCD	Tax Jurisdiction	S/4HANA	CEPC	TXJCD	Tax Jurisdiction	Copy From DCT as-is
28	DCT/ECC	CEPC	REGIO	Region (State, Province, County)	S/4HANA	CEPC	REGIO	Region (State, Province, County)	Copy From DCT as-is
29	DCT/ECC	CEPC	LOCK_IND	Lock indicator	S/4HANA	CEPC	LOCK_IND	Lock indicator	Copy From DCT as-is
30	DCT/ECC	CEPC	PCA_TEMPLATE	Template for Formula Planning in Profit Centers	S/4HANA	CEPC	PCA_TEMPLATE	Template for Formula Planning in Profit Centers	Copy From DCT as-is
31	DCT/ECC	CEPCT	KTEXT	Name	S/4HANA	CEPCT	KTEXT	Name	Copy From DCT as-is
32	DCT/ECC	CEPCT	LTEXT	Long Text	S/4HANA	CEPCT	LTEXT	Long Long Text	Copy From DCT as-is
33	DCT/ECC	CEPCT	MCTXT	Profit Center Text	S/4HANA	CEPCT	MCTXT	Profit Center Text	Copy From DCT as-is

Transformation Mapping

Note: No Mapping applicable here as this data object is a collect object.

Mapping Table Name

Mapping Table Description

Profit Centre

Mapping of legacy Profit Center to target system value

Person Responsible

Mapping of legacy Person Responsible to New Person Responsible

User ID

Mapping of legacy User ID

Hierarchy Group

N/A

Mapping of Legacy Hierarchy Group to Hierarchy Group

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool.and values are imported into ADM Construction page correctly	Data Team
2	Ensure Profit Centre hierarchies are loaded into target S/4HANA	Data Team

Pre-Load Validation

Project Team

Completeness

Task

Action

Generation of
Pre-load reports

Mandatory field check.

Profit Centres are mapped to new valuesnot blank
Profit Centre Hierarchy Mapped to new valuesnot blank
Person Responsible / HR positions mapped to new valuesCompany Code is mapped based on Company Code Mappingnot blank

Record Count

Record Count

Confirm the record counts in preload summary report
- Total Records: To be Filled in Summary Report
- Valid Records: To be Filled in Summary Report
- Invalid Records: To be Filled in Summary Report

Accuracy

Task	Action
Mandatory field mapping and transformation	Review the data report to ensure mapping value is not missing in tool. Capture errors in the Data Error report

Total Records: To be Filled in Summary Report

Valid Records: To be Filled in Summary Report

Invalid Records: To be Filled in Summary Report

.

Business

Completeness

Task	Action
Verify record count in Pre-load reports by region	Confirm the Preload File contains all the records in scope of migration based on the DCT (Data Construction Template)

Accuracy

Task	Action

Mandatory field mapping and transformation

Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.
Review the data report to ensure mapping value is not missing in tool.
Capture errors in the Data Error report.

Business

Completeness

TaskActionVerify record count in Pre-load reports by region

Confirm the Preload File contains all the records in scope of migration based on the DCT (Data Construction Template)

Accuracy

TaskActionConversion accuracy

Verify Profit Centres are transformed accurately as per endorsed transformation/mapping rules.

Review error reports in tool for any mismatch or missing transformed values.

In legacy system, execute ECC tcode SE16N to display table CEPC to confirm copied fields are accurately copied. ( If applicable)

Conversion accuracy

Verify Profit Centres are transformed accurately as per endorsed transformation/mapping rules.

Review error reports in tool for any mismatch or missing transformed values.

Load

Loading will be done through migration cockpit and therefore, data from the transformation export view to be exported into the load file format.

export views to be prepared based on the field list from the load template attached.

View file

name	Source data for CO - Profit center (2).xml
height	250

View file

name	Source data for CO - Profit center.xlsx
height	250

Load

The load process includes:

Execute the automated data load into target system using load tool or produce the load file if the loading of records to be done using LTMC cockpit object of Profit Centre.
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECCDCT, XXXX_S4HANA, XXXX_MATCH XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE)

Additional export view for the descriptions in additional languages to be created as is from detail page DCT

Note: Description translation will be loaded using tcode SE63. LSMW will be created based on the tcode SE63 to enable mass upload of this data. However, further checks will be done to check if some Fiori App could be used for uploading.

Load Run Sheet

Item	Step description	Team responsible
1	Ensure the load tools are transported into the correct tool instance.	Data team
2	Ensure DCTs and all required mappings are submitted and complete	Data team
3	Ensure Pre-load sign-offs are obtained.	Data team
4	Execute upload of Profit Centre Object using Migration Cockpit Object for Profit Centre Upload	Data team
5	Generate the post load reports in tool.	Data team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
8	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
9	Repeat steps 5 to 7 if necessary.	Data team

Load Phase and Dependencies

Configuration

Item #	Configuration item
1.	Controlling Area
2.	Standard Hierarchy is Maintained

Conversion Objects

Object #	Preceding Object Conversion Approach
1068	Profit Centre Group (Alt, Std Hierarchy)

Error Handling

Error type	Error description	Action taken

Post-Load Validation

Project Team

Completeness

Task

Action

Reconciliation of Record Count

Check Record count between DCT, Preload file and target extracted data from tables CEPC and CEPCT.

A Summary report to be added in the post-load report

Accuracy

Task	Action
Check values in key fields for accuracy	Refer to the post-load file and Manual check of the Loaded data using KE53 and SE16N

Business

Completeness

Task	Action
Record Count Check	Business to check Post-Load File and Summary report in post-load

Accuracy

Task	Action

Open items totalsCheck business partner open item totals by Business partner, Company code, profit centre. Totals should be checked in Document, Local and Group currency.


Spot check	Spot check some sample records from the post-load report to be picked for checking in SAP transaction code KE53 to verify accuracy of the data.

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
is in scope based on data design and any exception requested by business.

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Mar 24, 2026	Actor	Type	Activity	Version
Approved	GARCIA-ext, Angel Luis	State	changed state to Approved at 2:57 pm	v52
Revision under Review	GARCIA-ext, Angel Luis	State	gave Minor change approval at 2:57 pm
Revision under Review	GARCIA-ext, Angel Luis	State	changed state to Revision under Review at 2:57 pm	v52
Mar 18, 2026
Revision in Progress	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:43 pm	v52
Mar 16, 2026
Edited following Approval	SAKTHIVEL-ext, Navaneetha	Comment	commented 1:11 pm LARU-ext, Soumen can you please update CNV as per new changes in Jira
Mar 13, 2026
	LARU-ext, Soumen	Comment	commented 1:39 am PILLAY-ext, Lawrence GARCIA-ext, Angel Luis SAKTHIVEL-ext, Navaneetha Please check the update from profit Centre conversion specs where some fields are taken out of scope. It will need change in the DCT page and build as well. Jira ticket : https://syensqo.atlassian.net/browse/PDM-1402

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 9

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Completeness

Completeness

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

Change log

Workflow history