Status

pagestatus

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

backgroundColor	0052CC
percentage	100

Owner

Soumen Laru

PARA-ext, Anil

Stakeholders

PILLAY-ext, Lawrence GARCIA-ext, Angel Luis KUMAR-ext, Rajib NAIDU-ext, Prasad

Stakeholders

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

. Activity types describe the activity produced in a cost centre within a controlling area. At SyWay, activity types are used to quantify the cost of the services that a department provides to other areas or to production orders, projects or activities in manufacturing, research and development, IT projects etc.

The scope of this conversion spec refers to the migration of Activity types into S/4HANA system.

Conversion Scope

The scope of this document covers the approach for creating a new Activity Types into S/4HANA following the MDS DD-FUN-050 Master Data Standard_1071-Activity Types,

Conversion Scope

Activity Types which will be listed as part of scope list with new numbering will be in scope of migration. . This object's conversion from source to target is an approved DCT document. Therefore, relevancy rules are not applicable for this object as it uses DCT approach with full construct design.

List of source systems and approximate number

of records

of records. Note: Target records are expected to be lower after finalization of the design.

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Activity

TypeS4HANA

Types	8994	S/4HANA	~ 2570 ~
WP2	Activity

Type

Types

S4HANA

1099

PI2Activity Type

S/4HANA

~ 350 ~

S4HANA

Additional Information

Multi-language Requirement

Activity Types will primarily be managed in English. However, according to KDD055, this master data standard will be implemented in 4 core languages.

- English (EN)
- French (FR)
- Italian (IT)
- Chinese (ZN)

Note: Other language requirements were not finalized while developing this document, refer to Jira ID # PDM 604.

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length

(Decimals)

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.

CSLA

KOKRS

Requirement

KOKRS

Controlling Area

CHAR

	4	R
CSLA	LSTAR

80

LSTAR

Activity Type

CHAR

	6	R
CSLA	DATAB

80

DATAB

Valid-from Date

Date

	DATE	8	R
CSLA	DATBI	DATBI	Valid-to Date

Date

	DATE	8	R
CSLA	LANGU	LANGU	Language in Which Texts Are Saved	CHAR	80

NAME

	O
CSLT	KTEXT	KTEXT	Name	CHAR	20	R
CSLT	LTEXT	LTEXT	Description	CHAR	40	R
CSLA	LEINH	LEINH

_ISO

Activity Unit (ISO Format)

CHAR

UNIT	3	R
CSLA	LATYP	LATYP	Activity Type Category	CHAR

	1	R
CSLA	LATYPI

80

LATYPI

Variant Activity Type Category

CHAR

	1	O
CSLA	KSTTY

80

KSTTY

Valid Cost

Center

Centre Categories

CHAR

8

AUSEH_ISO

R
CSLA	AUSEH	AUSEH	Output Unit (ISO Format)

CHAR

UNIT	3	O
CSLA	AUSFK	AUSFK	Output Factor

Number

DEC	5	O
CSLA	VKSTA	VKSTA	Allocation Cost Element	CHAR	10	C
CSLA	SPRKZ	SPRKZ	Lock Indicator	CHAR	1	O
CSLA	FIXVO	FIXVO

Redistribution

Predistribution of Fixed Costs	CHAR	1	O
CSLA	TARKZ	TARKZ	Price Indicator	CHAR	3	O
CSLA	YRATE	YRATE	Price Calc. w. Period-Based Avg. Prices	CHAR	1	O
CSLA	TARKZ_I	CO_TARKZ_I	Actual Price Indicator	CHAR	3	O
CSLA	MANIST	CO_MANIST	Actual Quantity Set	CHAR	1	O
CSLA	MANPLAN	CO_MANPLAN	Plan Quantity Set	CHAR	1	O

Data Cleansing

Data Cleansing is not relevant for this object because the entire Activity types will be afresh designed in S/4HANA. If any cleansing is deemed necessary, it will be performed outside of the system, as a result, the cleansed Activity Types will be populated directly in the Data Collection Template (DCT).

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 / WP2N/A

Conversion Process

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

Image RemovedAlthough source extraction is planned, no relevancy or extraction rules are implemented. The Data team will collect the new Activity Types manually in the DCT to support the To-Be design, and an ETL process will be followed to the Target loads.

Data Privacy and Sensitivity

N/A

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:

Perform full data extraction from relevant tables in the source

system(s).

Perform extraction through the application layer.

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 systems into Syniti Migrate. There will be no relevancy criteria is applied to the extracted records to identify the records that are , The DCT is applicable for the Target loads.

Syniti Migrate connects to the sources.
An initial extract of the relevant Activity Types will be made available to assist business with any standardization.

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

The new Activity Types will be collected using the Data Collection Template (DCT)

R2R 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 Activity Types with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules- 1 for Activity Types with English language

Table & Field Name	Field description	Rule


CSLA - KOKRS	Controlling Area	Defaults to 'XXXX' (XXXX will be finalized after config item)
CSLA - LSTAR	Activity Types
CSLA - DATAB	Valid-from Date	First Day of fiscal period when the activity type is created
CSLA - DATBI	Valid-to Date	Set to be '31.12.9999'
CSLA - LANGU	Language in Which Texts Are Saved
CSLT - KTEXT	Name
CSLT - LTEXT	Description
CSLA - LEINH	Activity Unit (ISO Format)
CSLA - LATYP	Activity Type Category	Set to be '3'
CSLA - LATYPI	Variant Activity Type Category	Set to be '2'
CSLA - KSTTY	Valid Cost Centre Categories
CSLA - AUSEH	Output Unit (ISO Format)
CSLA - AUSFK	Output Factor
CSLA - VKSTA	Allocation Cost Element	Choose an appropriate secondary cost element, there will be a relationship of 1:1 in between the activity type and the secondary cost element
CSLA - SPRKZ	Lock Indicator
CSLA - FIXVO	Predistribution of Fixed Costs
CSLA - TARKZ	Price Indicator	Set to be '1'
CSLA - YRATE	Price Calc. w. Period-Based Avg. Prices
CSLA - TARKZ_I	Actual Price Indicator	Set to be '5'
CSLA - MANIST	Actual Quantity Set
CSLA - MANPLAN	Plan Quantity Set

DCT - 2 for Activity Types that use a language other than English. Activity types with Descriptions will be collected in multiple languages, hence a separate DCT will be used

Field Name	Field description	Rule
CSLT-KOKRS	Controlling Area	Defaults to 'XXXX' (XXXX will be finalized after config item)
CSLT - LSTAR	Activity Types
CSLT - SPRAS	Language Key	Input Language Key, ex: If Chinese, CN
CSLT-DATBI	Valid to	Set to be '31.12.9999'
CSLT - KTEXT	Name	Enter

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.


CSLT - LTEXT	Description	Enter content as per data type and length permitted

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
N/A

Transformation

To prepare the data for Target, the

Transformation

The Target fields are mapped to the applicable ECC field that corresponding Legacy field (DCT will be its the 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:for this object)

Perform value mapping and data transformation rules.
1. ECC Legacy values are mapped to the to-be values (this could include a default value)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 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.	Obtain DCT Sign-off from Business	R2R Data TeamData 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
Generate Load Files	R2R Data Team
3.5.	Monitor the transformation progress and ensure that performance and completion is are within the allowed timeframetimelines	R2R Data teamTeam
64.	Generate Pre-Load reports .	Data team
7.	Generate data load count.	Data team
Review and Validate Error and Preload Reports	R2R Data Team
5.8.	Log errors as defects , if for any kind of errors and address resolutions. Close defects.resolution	R2R Data teamTeam
96.	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
files, validate and ready for load (This step is applicable If step 5 is active, else No)	R2R Data Team
7.	Proceed for final loads	R2R 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

DCT

CEPC

CSLA

KOKRS

Controlling Area

*
The controlling area is the highest organizational unit in Controlling.
Type: Text
Length: 80S/4HANACEPCKOKRSControlling Area*
The controlling area is the highest organizational unit in Controlling.
Type: Text
Length: 80Default to Controlling Area XXXX

Transformation Mapping

	S/4HANA	CSLA	KOKRS	Controlling Area	Default to 'XXXX'
2	DCT	CSLA	LSTAR	Activity Type	S/4HANA	CSLA	LSTAR	Activity Type	Direct mapping from DCT
3	DCT	CSLA	DATAB	Valid-from Date	S/4HANA	CSLA	DATAB	Valid-from Date	Direct mapping from DCT
4	DCT	CSLA	DATBI	Valid-to Date	S/4HANA	CSLA	DATBI	Valid-to Date	Set to '31.12.9999'
5	DCT	CSLA	LANGU	Language in Which Texts Are Saved	S/4HANA	CSLA	LANGU	Language in Which Texts Are Saved	Direct mapping from DCT
6	DCT	CSLT	KTEXT	Name	S/4HANA	CSLT	NAME	Name	Direct mapping from DCT
7	DCT	CSLT	LTEXT	Description	S/4HANA	CSLT	LTEXT	Description	Direct mapping from DCT
8	DCT	CSLA	LEINH	Activity Unit (ISO Format)	S/4HANA	CSLA	LEINH	Activity Unit (ISO Format)	Direct mapping from DCT
9	DCT	CSLA	LATYP	Activity Type Category	S/4HANA	CSLA	LATYP	Activity Type Category	Direct mapping from DCT
10	DCT	CSLA	LATYPI	Variant Activity Type Category	S/4HANA	CSLA	LATYPI	Variant Activity Type Category	Direct mapping from DCT
11	DCT	CSLA	KSTTY	Valid Cost Center Categories	S/4HANA	CSLA	KSTTY	Valid Cost Center Categories	Direct mapping from DCT
12	DCT	CSLA	AUSEH	Output Unit (ISO Format)	S/4HANA	CSLA	AUSEH	Output Unit (ISO Format)	Direct mapping from DCT
13	DCT	CSLA	AUSFK	Output Factor	S/4HANA	CSLA	AUSFK	Output Factor	Direct mapping from DCT
14	DCT	CSLA	VKSTA	Allocation Cost Element	S/4HANA	CSLA	VKSTA	Allocation Cost Element	Direct mapping from DCT
15	DCT	CSLA	SPRKZ	Lock Indicator	S/4HANA	CSLA	SPRKZ	Lock Indicator	Direct mapping from DCT
16	DCT	CSLA	FIXVO	Redistribution of Fixed Costs	S/4HANA	CSLA	FIXVO	Redistribution of Fixed Costs	Direct mapping from DCT
17	DCT	CSLA	TARKZ	Price Indicator	S/4HANA	CSLA	TARKZ	Price Indicator	Direct mapping from DCT
18	DCT	CSLA	YRATE	Price Calc. w. Period-Based Avg. Prices	S/4HANA	CSLA	YRATE	Price Calc. w. Period-Based Avg. Prices	Direct mapping from DCT
19	DCT	CSLA	TARKZ_I	Actual Price Indicator	S/4HANA	CSLA	TARKZ_I	Actual Price Indicator	Direct mapping from DCT
20	DCT	CSLA	MANIST	Actual Quantity Set	S/4HANA	CSLA	MANIST	Actual Quantity Set	Direct mapping from DCT
21	DCT	CSLA	MANPLAN	Plan Quantity Set	S/4HANA	CSLA	MANPLAN	Plan Quantity Set	Direct mapping from DCT

Transformation Mapping

Mapping Table Name	Mapping Table Description
Activity Types	Old to New Activity Types
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.DCT completeness	R2R Data Team
2	Ensure Activity Type hierarchies are loaded into target Value Mappings are according to the target design in S/4HANA	R2R Data Team

Pre-Load Validation

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


Verify Record Count	R2R Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task

Action

Conversion Accuracy

R2R Data Team to ensure that all fields listed below pass the checks:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks
Filed Length Checks

Review Error Reports

Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source DCT

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

Task	Action
Verify

record count in Pre-load reports by regionConfirm the Preload File contains all the records in scope of migration ( Based on list of Activity Types mapped from old to new )

Record Count

Business Data Owner/s to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion

accuracy

Accuracy

Business Data Owner/s to verify that all the data in the load table/file is accurate

Verify Activity Types are transformed accurately

as per endorsed transformation / mapping rules (and signed-off DCT data).

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

Activity types will be migrated using the SAP tool 'Migration Cockpit', Object: Activity Type used for this specific import. Migration template is attached as a reference.

1071_Source data for CO - Activity type.xml

View file

name	1071_Source data for CO - Activity type.xml
height	250

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 Activity Typei.e., SAP Migration Cockpit.
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) Validation

Load Run Sheet

.2Resolve defects by reupload and re-generate reports if necessary.

Item	Step description	Team responsible
1	Ensure Pre-load sign-offs are obtained	R2R Data team
2	Ensure the load tools are transported into the correct tool instance
	R2R Data team

Ensure DCTs and all required mappings are submitted and complete	Data team
3	Go to <Load tool>	R2R
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
Load 1 or 2 records for "Activity Types" to validate if data is loaded successfully without errors	R2R Data team
5
Generate the post load reports in tool.
Proceed with full load if step 4 is successful and validated	R2R Data team
6
Log errors as defects, if any and address resolutions. Close defects.
Validate few records loaded by accessing standard transactions or tables from S/4HNA E.g. KL03 or FIORI: Manage Activity Types	R2R Data team
7
Generate post load
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
report if step 4 is validated	R2R Data team

Load Phase and Dependencies

Pre-Cut over

Configuration

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

Conversion Objects

Object #	Preceding Object Conversion Approach
1067	GL Account Operational COA (Incl. Secondary CE)N/A

Error Handling

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


Configuration	Invalid Secondary Cost Element System provides opportunity to review the incorrectly populated data and these need to be analysed and corrected	Consult Functional team to expedite and fix the error in the system
Configuration	Invalid Cost Centre Categories System provides opportunity to review the incorrectly populated data and these need to be analysed and corrected	Consult Functional team to expedite and fix the error in the system
Configuration	Invalid Activity Type Categories System provides opportunity to review the incorrectly populated data and these need to be analysed and corrected	Consult Functional team to expedite and fix the error in the system

Ensure the Activity Type mapping is correct and or create the Activity Type if it is valid

Post-Load Validation

Project Team

Completeness

Task	Action

Reconciliation of Record

Verify 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

R2R Data Team to verify the record count created in target S/4 HANA by accessing post load reports using standard reports from S/4 HANA.
Verify Logs	Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).

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

Conversion Accuracy

Verify that the Activity Types in target S/4 HANA are loaded correctly via load program and validate post load reports using standard t.code KL03 / KL13 or database tables CSLA from S/4 HANA.

Business

Completeness

Task	Action

Record

Verify Count

CheckReview

Download Post Load Reports from load program and verify that 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

loaded in the target S/4 HANA is the same count as of the approved load file.

Accuracy

Task	Action
Spot

check

checks

Business should choose some Activity

Type

Types and perform comprehensive check of the fields

in S4

in S/4 HANA
Conversion Accuracy	Verify that the Activity Types in target S/4 HANA are loaded correctly via load program and validate post load reports using standard t.code KL03 / KL13 or database tables CSLA / CSLT from S/4 HANA.

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.
Data values in DCT are target ready data unless a specific transformation rule is stated for that field in the transformation rules
Basic required configuration to be completed prior to this conversation

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Mar 20, 2026	Actor	Type	Activity	Version
Revision under Review	GARCIA-ext, Angel Luis	State	changed state to Revision under Review at 3:17 pm	v42
Mar 18, 2026
Revision in Progress	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:43 pm	v42
From Nov 20, 2025 to Feb 23, 2026
Edited following Approval	PARA-ext, Anil	Edit	updated the page at 11:44 am
	PARA-ext, Anil	State	changed state to Edited following Approval at 10:44 am	v41
Nov 03, 2025
Approved	MUTHUSAMY-ext, Kunalan	State	changed state to Approved at 10:17 am (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v40

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 4

New Version Current

Key

Purpose

Conversion Scope

Conversion Scope

Additional Information

Multi-language Requirement

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Extraction

Transformation

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Completeness

Accuracy

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