Status
Owner	Anil Para
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach of activity types into S4HANA

The document details out the field list, extraction criteria, scoping, mapping of activity type object

Conversion Scope

Activity Types 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 

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Activity Type		S4HANA
WP2	Activity Type		S4HANA

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach. 

Table	Field	Data Element	Field Description	Data Type	Length (Decimals)	Requirement
CSLA	KOKRS	KOKRS	Controlling Area	CHAR	80
CSLA	LSTAR	LSTAR	Activity Type	CHAR	80
CSLA	DATAB	DATAB	Valid-from Date	Date
CSLA	DATBI	DATBI	Valid-to Date	Date
CSLA	LANGU	LANGU	Language in Which Texts Are Saved	CHAR	80
CSLA	NAME	NAME	Name	CHAR	20
CSLA	LTEXT	LTEXT	Description	CHAR	40
CSLA	LEINH_ISO	LEINH_ISO	Activity Unit (ISO Format)	CHAR	3
CSLA	LATYP	LATYP	Activity Type Category	CHAR	80
CSLA	LATYPI	LATYPI	Variant Activity Type Category	CHAR	80
CSLA	KSTTY	KSTTY	Valid Cost Center Categories	CHAR	8
CSLA	AUSEH_ISO	AUSEH_ISO	Output Unit (ISO Format)	CHAR	3
CSLA	AUSFK	AUSFK	Output Factor	Number	5
CSLA	VKSTA	VKSTA	Allocation Cost Element	CHAR	10
CSLA	SPRKZ	SPRKZ	Lock Indicator	CHAR	1
CSLA	FIXVO	FIXVO	Redistribution of Fixed Costs	CHAR	1
CSLA	TARKZ	TARKZ	Price Indicator	CHAR	3
CSLA	YRATE	YRATE	Price Calc. w. Period-Based Avg. Prices	CHAR	1
CSLA	TARKZ_I	TARKZ_I	Actual Price Indicator	CHAR	3
CSLA	MANIST	MANIST	Actual Quantity Set	CHAR	1
CSLA	MANPLAN	MANPLAN	Plan Quantity Set	CHAR	1

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1.	Can load, but business process will fail	Lock any Activity Type not being used for last 5 years	TBD	Report	PF2 / PI2 / WP2

Conversion Process 

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

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

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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 Activity Types 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

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

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

Data Collection Template (DCT)

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

<Object> DCT Rules

Field Name	Field description	Rule
CEPC-PRCTR	Activity Type	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

List the steps that need to occur before extraction can commence

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 ECC 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 Syniti Migrate to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. ECC values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in Syniti Migrate
2. 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	ECC	CSSL	KOKRS	Controlling Area	S4HANA	CSSL	KOKRS	Controlling Area
2	ECC	CSSL	LSTAR	Activity Type	S4HANA	CSSL	LSTAR	Activity Type
3	ECC	CSSL	DATAB	Valid-from Date	S4HANA	CSSL	DATAB	Valid-from Date
4	ECC	CSSL	DATBI	Valid-to Date	S4HANA	CSSL	DATBI	Valid-to Date
5	ECC	CSSL	LANGU	Language in Which Texts Are Saved	S4HANA	CSSL	LANGU	Language in Which Texts Are Saved
6	ECC	CSSL	NAME	Name	S4HANA	CSSL	NAME	Name
7	ECC	CSSL	LTEXT	Description	S4HANA	CSSL	LTEXT	Description
8	ECC	CSSL	LEINH_ISO	Activity Unit (ISO Format)	S4HANA	CSSL	LEINH_ISO	Activity Unit (ISO Format)
9	ECC	CSSL	LATYP	Activity Type Category	S4HANA	CSSL	LATYP	Activity Type Category
10	ECC	CSSL	LATYPI	Variant Activity Type Category	S4HANA	CSSL	LATYPI	Variant Activity Type Category
11	ECC	CSSL	KSTTY	Valid Cost Center Categories	S4HANA	CSSL	KSTTY	Valid Cost Center Categories
12	ECC	CSSL	AUSEH_ISO	Output Unit (ISO Format)	S4HANA	CSSL	AUSEH_ISO	Output Unit (ISO Format)
13	ECC	CSSL	AUSFK	Output Factor	S4HANA	CSSL	AUSFK	Output Factor
14	ECC	CSSL	VKSTA	Allocation Cost Element	S4HANA	CSSL	VKSTA	Allocation Cost Element
15	ECC	CSSL	SPRKZ	Lock Indicator	S4HANA	CSSL	SPRKZ	Lock Indicator
16	ECC	CSSL	FIXVO	Redistribution of Fixed Costs	S4HANA	CSSL	FIXVO	Redistribution of Fixed Costs
17	ECC	CSSL	TARKZ	Price Indicator	S4HANA	CSSL	TARKZ	Price Indicator
18	ECC	CSSL	YRATE	Price Calc. w. Period-Based Avg. Prices	S4HANA	CSSL	YRATE	Price Calc. w. Period-Based Avg. Prices
19	ECC	CSSL	TARKZ_I	Actual Price Indicator	S4HANA	CSSL	TARKZ_I	Actual Price Indicator
20	ECC	CSSL	MANIST	Actual Quantity Set	S4HANA	CSSL	MANIST	Actual Quantity Set
21	ECC	CSSL	MANPLAN	Plan Quantity Set	S4HANA	CSSL	MANPLAN	Plan Quantity Set

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
Activity Type	Mapping of ECC Profit Center to target system value
Person Responsible	Mapping of ECC Person Responsible to New Person Responsible
User ID	Mapping of ECC User ID
Hierarchy Group	Mapping of ECC 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.	Data Team
2	Ensure Activity Type hierarchies are loaded into target S/4HANA	Data Team

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
Generation of Pre-load reports	Mandatory field check. Activity Types are mapped to new values Activity Type Hierarchy Mapped to new values Person Responsible / HR positions mapped to new values
	Record Count Confirm the record counts in preload summary report Total Records:  Valid Records: Invalid Records:

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

The following pre-load validations will be performed by the 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 list of Activity Types mapped from old to new )

Accuracy

Task	Action
Conversion accuracy	Verify Activity Types are transformed accurately as per endorsed transformation/mapping rules. Review error reports in tool for any mismatch or missing transformed values. In ECC system, execute ECC tcode SE16N to display table to confirm copied fields are accurately copied.  If any of the sum is different, raise defect and flag the relevant record as error.

Load

Loading of the activity types will be done using migration cockpit object for activity type

The load process includes:

1. 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 Activity Type. 
2. 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_ECC, XXXX_S4HANA, 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) 

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 Activity Type Object using Migration Cockpit Object for Activity Type 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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence 

Item #	Configuration item
1.	Controlling Area
2.	Standard Hierarchy is Maintained
3.	Currencies (currency keys, decimal places in currencies)

 Conversion Objects

Object #	Preceding Object Conversion Approach
N/A

Error Handling

The table below depicts some possible system errors for this data object during data load.  All data load error is to be logged as defect and managed within the Defect Management

Error type	Error description	Action taken
P	Posting period is blocked for posting	Review project / cutover plan and ensure posting periods can be opened for postings
Activity Type does not exist	Activity Type does not exist in company code	Ensure the Activity Type mapping is correct and or create the Activity Type if it is valid

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
Reconciliation of Record Count	Record Count Check the sum of record count of the open items in the load file is the same as S/4HANA. The record count for TB Balance ( PY )  will be done on the group basis. The fields in the group are consist of: Company Code, Vendor Account

Accuracy

Task

Action

Check values in key fields for accuracy

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation. Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the ECC values side-by-side to allow for 100% check of all these fields in the shortest possible time. Any mismatch will be reported under the Post Load - Error report.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
Record Count Check	Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations

Accuracy

Task	Action
Spot check	Business should choose some Activity Type and perform comprehensive check of the fields in S4

Key Assumptions

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

Any additional key assumptions.

Change log

Workflow history