Status

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

backgroundColor	0052CC
percentage	100

Owner

GANESAN-ext, Shivkumar

Stakeholders

PILLAY-ext, Lawrence PARA-ext, Anil GARCIA-ext, Angel Luis SAKTHIVEL-ext, Navaneetha

Purpose

The purpose of this document is to define the conversion approach to create conversion for Object 9107 – Activity Rates in S/4 HANA.

Activity Rates are the current active rates for different activities performed either for production, plant maintenance, HR etc. The activity rates capture the planned cost for a certain activity over a period of time. E.g. Factory overhead is charged to production orders via relevant activity types maintained for absorbing factory overheads. The activity rates are maintained for a combination of activity types and cost centre combination.

The document details out the field list, extraction criteria, scoping, mapping, transformation logic, generation of the pre-load file and loading of the same with respect to the object 9107- Activity Rate.

The requirement is to migrate planned activity rates. The actual activity rates would be performed within the S4 system as a part of the month end activity.

The activity rates will be provided by the business in a Data Collection Template (hereinafter referred to as DCT) and transformed as applicable for S4HANA in Syniti and then loaded using the excel upload option.

Conversion Scope

The scope of this document covers the approach for migration of planned activity prices.

The data from legacy system needs to be confirmed by the business.

List of source systems and approximate number of records <number of company codes to be confirmed relevant for activity rates needs to be confirmed>. The data will be provided by the business in the DCT page. The data will not be extracted and transformed in Syniti. The source of data is DCT and not PF2 and WP2.

Additional Information

Multi-language Requirement

None

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The Target design of the object 9107 – Activity rates is as below

TKF001TKFXXXFixed Activity Price MandatoryTKF002TKFXXXFixed Activity Price MandatoryTKF003TKFXXXFixed Activity Price MandatoryTKF004TKFXXXFixed Activity Price MandatoryTKF005TKFXXXFixed Activity Price MandatoryTKF006TKFXXXFixed Activity Price MandatoryTKF007TKFXXXFixed Activity Price MandatoryTKF008TKFXXXFixed Activity Price MandatoryTKF009TKFXXXFixed Activity Price MandatoryTKF010TKFXXXFixed Activity Price MandatoryTKF011TKFXXXFixed Activity Price MandatoryTKF012TKFXXXFixed Activity Price Mandatory

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
COEJT	KOKRS	KOKRS	Controlling area	CHAR	4	Mandatory
COEJT	BELNR	CO_BELNR	Document Number	CHAR	10	System Generated
COEJT	BUZEI	CO_BUZEI	Posting Row	NUMC	3	System Generated
COEJT	PERBL	PERBL	Period Block	NUMC	3	Mandatory
COEJT
TKG001
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG002
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG003
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG004
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG005
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG006
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG007
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG008
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG009
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG010
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG011
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT
TKG012
TKGXXX
Total Price per
Unit of Measure in CO Area Currency	CURR	Length:23 and 2 Decimals
System Generated
COEJT	TKE001TKF001	TKEXXXTKFXXX	Fixed Price Unit per Activity Price in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	MandatoryCOEJT
COEJT	TKE002TKF002	TKEXXXTKFXXX	Fixed Price per Activity Price Unit in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE003TKF003	TKEXXXTKFXXX	Fixed Price per Activity Price Unit in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE004TKF004	TKEXXXTKFXXX	Fixed Price per Activity Price Unit in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE005TKF005	TKEXXXTKFXXX	Fixed Price per Activity Price Unit in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE006TKF006	TKEXXXTKFXXX	Fixed Price Unit per Activity Price in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE007TKF007	TKEXXXTKFXXX	Fixed Price per Activity Price Unit in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE008TKF008	TKEXXXTKFXXX	Fixed Price Unit per Activity Price in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE009TKF009	TKEXXXTKFXXX	Fixed Price per Activity Price Unit in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKF010	TKFXXX	Fixed Price per Activity Price in CO Area Currency	CURR	Length:23 and 2 Decimals	Mandatory
COEJT	TKF011	TKFXXX	Fixed Price per Activity Price	TKE010	TKEXXX	Price Unit in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE011TKF012	TKEXXXTKFXXX	Fixed Price per Activity Price Unit in CO Area Currency	NUMC	CURR	Length:23 and 2 Decimals5	Mandatory
COEJT	TKE012TKE001	TKEXXX	Price Unit in CO Area Currency	NUMC	5	Mandatory
COEJT	LEDNRTKE002	LEDNR	Ledger for Controlling Objects	CHAR	2	TKEXXX	Price Unit in CO Area Currency	NUMC	5	MandatoryOptional
COEJT	OBJNRTKE003	J_OBJNR	Object Number	CHAR	22	TKEXXX	Price Unit in CO Area Currency	NUMC	5	MandatorySystem Generated
COEJT	GJAHRTKE004	GJAHR	TKEXXX	Price Unit in CO Area CurrencyFiscal Year	NUMC	45	Mandatory
COEJT	VERSNTKE005	VERSN	Version	CHAR	TKEXXX	Price Unit in CO Area Currency	NUMC	53	Mandatory
COEJT	VRGNG	CO_VORGANG	CO Business Transaction	CHAR	4	System Generated
COEJT	REFBZ	CO_REFBZ	Posting Row of Reference Document	NUMC	3	System Generated

Data Cleansing

For the purpose of the Object 9107- Activity rates, the data cleansing is not applicable. It is expected that relevant records will be provided in DCT by business.

Conversion Process

For activity rates the data will be collected in the DCT page. The conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business. This DCT will be used for transformation and generation of the pre-load file. The activity prices will be uploaded via excel upload option in KP26. The conversion and transformation for activity rates will not happen via Syniti as the data will be provided by business in the DCT page.

Data Privacy and Sensitivity

None

TKE006	TKEXXX	Price Unit in CO Area Currency	NUMC	5	Mandatory
COEJT	TKE007	TKEXXX	Price Unit in CO Area Currency	NUMC	5	Mandatory
COEJT	TKE008	TKEXXX	Price Unit in CO Area Currency	NUMC	5	Mandatory
COEJT	TKE009	TKEXXX	Price Unit in CO Area Currency	NUMC	5	Mandatory
COEJT	TKE010	TKEXXX	Price Unit in CO Area Currency	NUMC	5	Mandatory
COEJT	TKE011	TKEXXX	Price Unit in CO Area Currency	NUMC	5	Mandatory
COEJT	TKE012	TKEXXX	Price Unit in CO Area Currency	NUMC	5	Mandatory
COEJT	LEDNR	LEDNR	Ledger for Controlling Objects	CHAR	2	Optional
COEJT	OBJNR	J_OBJNR	Object Number	CHAR	22	System Generated
COEJT	GJAHR	GJAHR	Fiscal Year	NUMC	4	Mandatory
COEJT	VERSN	VERSN	Version	CHAR	3	Mandatory
COEJT	VRGNG	CO_VORGANG	CO Business Transaction	CHAR	4	System Generated
COEJT	REFBZ	CO_REFBZ	Posting Row of Reference Document	NUMC	3	System Generated

Note: Generally the activity prices in KP26 are entered as fixed prices. The variable price (i.e. plan price) is derived by the system when cost planning is used. However, the upload template provided by SAP has fields for both fixed price and variable price. The COST or COEJT tables do not have a field for variable price. The variable price is derived by deducting the fixed price from the total price i.e. Variable price = Total Price - Fixed Price.

Data Cleansing

For the purpose of the Object 9107- Activity rates, the data cleansing is not applicable. It is expected that relevant records will be provided in DCT by business.

Conversion Process

For activity rates the data will be collected in the DCT page. The conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business. This DCT will be used for transformation and generation of the pre-load file. The activity prices will be uploaded via excel upload option in KP26. The conversion and transformation for activity rates will not happen via Syniti as the data will be provided by business in the DCT page.

Data Privacy and Sensitivity

None

Extraction

For object 9107 – Activity rates, the extraction is not applicable as this will be a DCT provided by business.

Selection Screen

Not Applicable

Data Collection Template (DCT)

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

9107 – Activity Rates - DCT Rules

Field Name	Field Description	Rule
KOKRS	Controlling area	This is a Mandatory field Enter the controlling area for which the rates belong.
GJAHR	Fiscal Year	This is mandatory. Enter the Fiscal year for which the rates are being entered.
PERBL	From Period	This is a Mandatory field Enter the from period
PERBL	To Period	This is a Mandatory field Enter the To period
VERSN	Version	This is mandatory Enter “0”
KOSTL	Cost Centre	This is a Mandatory field Enter the cost centre for which the activity price is being maintained
LSTAR	Activity Type	This is a Mandatory field Enter the Activity type for which the activity price is being maintained
LSTXX	Activity Quantity	This is a Mandatory field Enter “1”
SPRED	Distribution Key	This is a Mandatory field Enter “1”
TKFXXX	Fixed Price	This field is optional Enter the fixed price if the activity price is based on fixed price basis
SPRED	Distribution Key Fixed Price	This is a Mandatory field Enter “1”
TKVXXX	Variable Price	This field is optional This field is generally used for planned prices entered in KP06. Enter the Variable price if the activity price is based on variable price basis.
SPRED	Distribution Key Variable Price

Extraction

For object 9107 – Activity rates, the extraction is not applicable as this will be a DCT provided by business.

Selection Screen

Not Applicable

Data Collection Template (DCT)

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

9107 – Activity Rates - DCT Rules

Field Name	Field Description	Rule
KOKRS	Controlling area	This is a Mandatory field Enter the controlling area for which the rates belong.
GJAHR	Fiscal Year	This is mandatory. Enter the Fiscal year for which the rates are being entered.
PERBL	From Period	This is a Mandatory field Enter the from period“1”
PERBLTKEXXX	To PeriodPrice Unit	This is a Mandatory field Enter the To period
VERSN	Version	This is mandatory Enter “0”
price unit for which the price is being maintained e.g. "1", "1000" etc.
WAERS	Currency	KOSTL	Cost Centre	This is a Mandatory field Enter the cost centre for currency in which the activity price is being rates are to be maintained
LSTARSPREDActivity	Distribution Key Plan Activity	This is a Mandatory field Enter “1”
VKSTA	Allocation Cost Element Type	This is a Mandatory field Enter the Activity type for which the activity price is being maintained
LSTXX	Activity Quantity	This is a Mandatory field Enter “1”
SPRED	Distribution Key	This is a Mandatory field Enter “1”
TKFXXX	Fixed Price	This field is optional Enter the fixed price if the activity price is based on fixed price basis
SPRED	Distribution Key Fixed Price	This is a Mandatory field Enter “1”
TKVXXX	Variable Price	This field is optional This field is generally used for planned prices entered in KP06. Enter the Variable price if the activity price is based on variable price basis.
SPRED	Distribution Key Variable Price	This is a Mandatory field Enter “1”
TKEXXX	Price Unit	This is a Mandatory field Enter the price unit for which the price is being maintained e.g. "1", "1000" etc.
WAERS	Currency	This is a Mandatory field Enter the currency in which the activity rates are to be maintained
SPRED	Distribution Key Plan Activity	This is a Mandatory field Enter “1”
VKSTA	Allocation Cost Element	This is a Mandatory field Enter the allocation cost element to be used for uploading the prices

Extraction Dependencies

For object 9107 – Activity Rates, no extraction dependencies are applicable as this is a DCT.

allocation cost element to be used for uploading the prices

Extraction Dependencies

For object 9107 – Activity Rates, no extraction dependencies are applicable as this is a DCT.

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

Perform value mapping and data transformation rules.

Legacy values are mapped to the to-be values (this could include a default value)
Values are transformed according to the rules defined in Syniti

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 Syniti	Data team
2	Ensure that signed off value mappings have been maintained in the Syniti	Syniti team
3	Confirm the value mappings are maintained in Syniti	Data team
4	Ensure that the relevancy rules for extraction are signed off by all relevant business stakeholders. If a DCT page is to be used then, ensure that Signed off DCT from business has been received and maintained in Syniti	Syniti/Data team
5	Execute transformation for the object	Syniti team
6	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Syniti/Data team
7.	Generate Pre-Load reports.	Syniti team
8.	Generate data load count.	Syniti team
9.	Log errors as defects, if any and address resolutions. Close defects.	Syniti/Data team
10.	Re-transform and re-validate the Pre-load reports if necessary.	Syniti/Data team
11.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
12.	Analyse and resolve any pre-load defects logged by business.	Syniti/Data team
13.	Repeat steps 5 to 11 if necessary	Syniti/Data team
14.	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
01	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	KOKRS	Controlling Area	As per DCT
02	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	GJAHR	Fiscal Year	As per DCT
03	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	PEBRL	From Period	As per DCT
04

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

Perform value mapping and data transformation rules.

Legacy values are mapped to the to-be values (this could include a default value)
Values are transformed according to the rules defined in Syniti

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 Syniti	Data team
2	Ensure that signed off value mappings have been maintained in the Syniti	Syniti team
3	Confirm the value mappings are maintained in Syniti	Data team
4	Ensure that the relevancy rules for extraction are signed off by all relevant business stakeholders. If a DCT page is to be used then, ensure that Signed off DCT from business has been received and maintained in Syniti	Syniti/Data team
5	Execute transformation for the object	Syniti team
6	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Syniti/Data team
7.	Generate Pre-Load reports.	Syniti team
8.	Generate data load count.	Syniti team
9.	Log errors as defects, if any and address resolutions. Close defects.	Syniti/Data team
10.	Re-transform and re-validate the Pre-load reports if necessary.	Syniti/Data team
11.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
12.	Analyse and resolve any pre-load defects logged by business.	Syniti/Data team
13.	Repeat steps 5 to 11 if necessary	Syniti/Data team
14.	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
01	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	KOKRSPEBRL	Controlling AreaTo Period	As per DCT
0205	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	GJAHRVERSN	Fiscal YearVersion	As per DCT
0306	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	PEBRLKOSTL	From PeriodCost Centre	As per DCT
0407	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	PEBRLLSTAR	To PeriodActivity Type	As per DCT
0508	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	VERSNLSTXX	VersionActivity Quantity	As per DCT
0609	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	KOSTLSPRED	Cost CentreDistribution Key	As per DCT
0710	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	LSTARTKFXXX	Activity TypeFixed Price	As per DCT
0811	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	LSTXX	SPRED	Distribution Key Fixed PriceActivity Quantity	As per DCT
0912	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	SPREDTKVXXX	Distribution KeyVariable Price	As per DCT
1013	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	TKFXXXSPRED	Fixed Distribution Key Variable Price	As per DCT
1114	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	SPREDTKEXXX	Distribution Key Fixed Price Unit	As per DCT
1215	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	TKVXXXWAERS	Variable PriceCurrency	As per DCT
1316	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	SPRED	Distribution Key Variable PricePlan Activity	As per DCT
1417	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	TKEXXX	VKSTA	Allocation Cost ElementPrice Unit	As per DCT
15	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	WAERS	Currency	As per DCT
16	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	SPRED	Distribution Key Plan Activity	As per DCT
17	DCT	NA	NA	CONSTRUCT	S4HANA	COEJT	VKSTA	Allocation Cost Element	As per DCT

Transformation Mapping

Below value mapping tables should be constructed in Syniti

Mapping Table Name	Mapping Table Description
Controlling Area	Controlling area should be configured and be available in value mapping or as default if only one controlling area is being used
Ledger	Ledger(s) should be configured and should be available.
Version	Version should be configured and should be available.

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 latest signed-off mapping files imported into Syniti	Data team
2	Ensure that signed off value mappings have been maintained in the Syniti	Syniti team
3	Confirm the value mappings as maintained in the Syniti	Data team
4	Ensure that Signed off DCT from business has been received and maintained in Syniti	Syniti/Data team
5	Confirm on the extracted values	Syniti, Data and business

Transformation Mapping

Below value mapping tables should be constructed in Syniti

Mapping Table Name	Mapping Table Description
Controlling Area	Controlling area should be configured and be available in value mapping or as default if only one controlling area is being used
Ledger	Ledger(s) should be configured and should be available.
Version	Version should be configured and should be available.

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 latest signed-off mapping files imported into Syniti	Data team
2	Ensure that signed off value mappings have been maintained in the Syniti	Syniti team
3	Confirm the value mappings as maintained in the Syniti	Data team
4	Ensure that Signed off DCT from business has been received and maintained in Syniti	Syniti/Data team
5	Confirm on the extracted values	Syniti, Data and business

Pre-Load Validation

Project Team

The Pre Load validations are performed by Project Team

Completeness

Task	Action
Generation of Pre-load reports	Mandatory field check. Check if the fiscal year and period is correctly maintained Check if the version is correct Check if the activity types and corresponding cost centre are correct. Check the Price unit Check the controlling area Enter correct prices corresponding to the price unit.
Record Count	Record Count Confirm the record counts in preload summary report Total Records: Valid Records: Invalid Records:
Business Confirmation	Data team after the initial validation of Pre-Load validation based on the pre agreed validation checklist To send the Pre-Load file to the Business Representatives for all plants/valuation area in scope for conversion Business Representatives to validate the pre-load file Agree with data team on the next steps for erroneous 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. Mandatory field check. Check if the fiscal year and period is correctly maintained Check if the version is correct Check if the activity types and corresponding cost centre are correct. Check the Price unit Check the controlling area
Business Value Checks	The total values as per the relevancy /DCT and pre-load value are matching for the fields containing the limit amounts
Records in Errors	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 data.

Business

The following pre-load validations will be performed by business.

Completeness

Task	Action
Check Data load register count	Business Data Owner/s to verify that the total number of relevant records to be converted as per relevancy / DCT is equal to the total number of records in the Preload file.

Accuracy

Task	Action
Conversion accuracy	To check and validate the load files with all the transformation and mapping rules, to be signed off.

Note: Generally the activity prices in KP26 are entered as fixed prices. The variable price (i.e. plan price) is derived by the system when cost planning is used. However, the upload template provided by SAP has fields for both fixed price and variable price. The COST or COEJT tables do not have a field for variable price. The variable price is derived by deducting the fixed price from the total price i.e. Variable price = Total Price - Fixed Price

Pre-Load Validation

Project Team

The Pre Load validations are performed by Project Team

Completeness

Task	Action
Generation of Pre-load reports	Mandatory field check. Check if the fiscal year and period is correctly maintained Check if the version is correct Check if the activity types and corresponding cost centre are correct. Check the Price unit Check the controlling area Enter correct prices corresponding to the price unit.
Record Count	Record Count Confirm the record counts in preload summary report Total Records: Valid Records: Invalid Records:
Business Confirmation	Data team after the initial validation of Pre-Load validation based on the pre agreed validation checklist To send the Pre-Load file to the Business Representatives for all plants/valuation area in scope for conversion Business Representatives to validate the pre-load file Agree with data team on the next steps for erroneous 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. Mandatory field check. Check if the fiscal year and period is correctly maintained Check if the version is correct Check if the activity types and corresponding cost centre are correct. Check the Price unit Check the controlling area
Business Value Checks	The total values as per the relevancy /DCT and pre-load value are matching for the fields containing the limit amounts
Records in Errors	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 data.

Business

The following pre-load validations will be performed by business.

Completeness

Task	Action
Check Data load register count	Business Data Owner/s to verify that the total number of relevant records to be converted as per relevancy / DCT is equal to the total number of records in the Preload file.

Accuracy

Task

Action

Conversion accuracy

To check and validate the load files with all the transformation and mapping rules, to be signed off

.

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 via a custom program <TBC>, as LTMC for this object is not available as of now.
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 Template for activity rates
View file
name Activity Price Template SY.xlsx
height 250

Load Run Sheet

Item #	Step Description	Team Responsible
1	Go to load file and pick 5 data records, load manually without any tool. See what happens. If all okay, proceed with the next step.	Data team
2	Go to load file and pick 10 records and load them with the tool. No action if the previous step has fallen. If not, then continue to load 10 records with the tool. Check if everything went okay.	Data team
3	Proceed with the full load if steps one and two were succeed else fix the issue with records	Data team
4	Validate few records loaded by accessing standard transactions from S/4HNA e.g. KP27 to check the activity prices.	Data team
5	Generate post load report if step 5 is validated	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 1 to 5 if necessary.	Data team

Load Phase and Dependencies

The load phase for this object is ideally relevant for pre-cutover Phase 4

Configuration

Below configurations must exist to facilitate the conversion of this object.

Item #	Configuration Item
01	Controlling Area (Check Table: TKA01)
02	Company code (Check Table: T001)
03	Activity types (Master Data)
04	Version (Check Table: TKA09)
05	Price Indicatory (Check Table: TKA10)

Conversion Objects

Object #	Preceding Object Conversion Approach
CNV-1074	Cost Centre(s)
CNV-1071	Activity types
CNV-1072	Exchange Rates

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
Activity price	Activity price wrong conversion with regards to price unit	Ensure that the price unit is correctly picked
Fiscal Year	Enter correct fiscal year	Correct fiscal year
Activity type	Cost centre and activity type combination does not match	Ensure to maintain the correct cost centre and activity type match.

Post-Load Validation

Project Team

The following post load validations will be done by Project Team

Completeness

Task

Action

Reconciliation of Record Count

Record Count - Count and check how many records were loaded vs. Records in the load file (Each mock has its own data record count)

Check for logs from Load and fix erroneous records, if any.

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 legacy 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 done by 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

Business may also run transaction code KP27 to cross check the Activity Prices

Accuracy

Task

Action

Field Checks

Check the fields to ensure that Activity Prices have been properly maintained

Value Check

Check the activity prices against activity types and corresponding cost centres

be done by 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

Business may also run transaction code KP27 to cross check the Activity Prices

Accuracy

Task	Action
Field Checks	Check the fields to ensure that Activity Prices have been properly maintained
Value Check	Check the activity prices against activity types and corresponding cost centres.

Note: Generally the activity prices in KP26 are entered as fixed prices. The variable price (i.e. plan price) is derived by the system when cost planning is used. However, the upload template provided by SAP has fields for both fixed price and variable price. The COST or COEJT tables do not have a field for variable price. The variable price is derived by deducting the fixed price from the total price i.e. Variable price = Total Price - Fixed Price.

Key Assumptions

Relevancy rules has been thoroughly validated and signed off by business.
Activity types and cost centre combination has been validated.

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Feb 23, 2026	Actor	Type	Activity	Version
Approved	TAN-ext, Charmaine	State	changed state to Approved at 3:25 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v16
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 3:25 pm [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Jan 13, 2026
	GANESAN-ext, Shivkumar	Edit	updated the page at 10:12 am
	GARCIA-ext, Angel Luis	State	changed expiry date to '20 Jan, 2026 09:15 am' at 9:15 am
	GARCIA-ext, Angel Luis	State	changed state to Lead Approval at 9:15 am	v16
Tech Review	GARCIA-ext, Angel Luis	State	gave Syniti Team Review approval at 9:15 am

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 15

New Version Current

Key

Purpose

Conversion Scope

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Cleansing

Conversion Process

Extraction

Selection Screen

Extraction

Selection Screen

Transformation

Transformation Run Sheet

Transformation

Transformation Run Sheet

Transformation Dependencies

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Business

Completeness

Accuracy

Pre-Load Validation

Project Team

Completeness

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Accuracy

Business

The following post load validations will be done by business.

Completeness

be done by business.

Completeness

Key Assumptions

Change log

Workflow history