Status	Revision under Review
Owner	Soumen Laru
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

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	Target System
PF2	Activity Type	S4HANA
WP2	Activity Type	S4HANA
PI2	Activity Type	S4HANA

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

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

Data Cleansing

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:

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

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

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

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

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
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	CEPC	KOKRS	Controlling Area* The controlling area is the highest organizational unit in Controlling. Type: Text Length: 80	S/4HANA	CEPC	KOKRS	Controlling Area* The controlling area is the highest organizational unit in Controlling. Type: Text Length: 80	Default to Controlling Area XXXX
2	ECC	CEPC	PRCTR	Profit Center* Key which together with the controlling area uniquely identifies a profit center. Use You can make an organizational assignment of a profit center to a controlling object (an order, cost center,…). The system posts automatically on the profit center when you make a posting on controlling object (an order, cost center,…). Type: Text Length: 80	S/4HANA	CEPC	PRCTR	Profit Center* Key which together with the controlling area uniquely identifies a profit center. Use You can make an organizational assignment of a profit center to a controlling object (an order, cost center,…). The system posts automatically on the profit center when you make a posting on controlling object (an order, cost center,…). Type: Text Length: 80	Read from Activity Type Mapping File with new number
3	ECC	CEPC	DATAB	Valid From* When you create an object, the beginning date to which object is valid is defined here. Type: Date	S/4HANA	CEPC	DATAB	Valid From* When you create an object, the beginning date to which object is valid is defined here. Type: Date	Copy as is
4	ECC	CEPC	DATBI	Valid To* When you create an object, you use the ending date to define as of when the object is valid. Type: Date	S/4HANA	CEPC	DATBI	Valid To* When you create an object, you use the ending date to define as of when the object is valid. Type: Date	Copy as is
5	ECC	CEPC	LANGU	Language in Which Texts Are Saved Language in which profit center texts are saved. If the language is not filled, logon language is used as default to save the profit center text. Type: Text Length: 80	S/4HANA	CEPC	LANGU	Language in Which Texts Are Saved Language in which profit center texts are saved. If the language is not filled, logon language is used as default to save the profit center text. Type: Text Length: 80	Copy as is
6	ECC	CEPC	KTEXT	Profit Center Name* General description of the object. The profit center name is used for online displays and evaluations that do not have enough space for the profit center description. Type: Text Length: 20	S/4HANA	CEPC	KTEXT	Profit Center Name* General description of the object. The profit center name is used for online displays and evaluations that do not have enough space for the profit center description. Type: Text Length: 20	Copy as is
7	ECC	CEPC	LTEXT	Description A text that describes the profit center to which it refers in greater detail. Type: Text Length: 40	S/4HANA	CEPC	LTEXT	Description A text that describes the profit center to which it refers in greater detail. Type: Text Length: 40	Copy as is
8	ECC	CEPC	VERAK	Person Responsible* Name of the person in charge of the profit center. Type: Text Length: 20	S/4HANA	CEPC	VERAK	Person Responsible* Name of the person in charge of the profit center. Type: Text Length: 20	Map to new person Responsible based on Person / Position Mapping from HR Employee Number
9	ECC	CEPC	VERAK_USER	User Responsible In this field, you can enter the user ID of the person responsible for the profit center. This user ID is stored in the SAP user master record. Type: Text Length: 80	S/4HANA	CEPC	VERAK_USER	User Responsible In this field, you can enter the user ID of the person responsible for the profit center. This user ID is stored in the SAP user master record. Type: Text Length: 80	Map Old to new User ID Based on User ID Mapping
10	ECC	CEPC	KHINR	Standard Hierarchy Node/Profit Cntr Grp* Each profit center must be assigned to a node in the standard hierarchy for its controlling area. This ensures that the standard hierarchy contains all the profit centers in the controlling area. Type: Text Length: 12	S/4HANA	CEPC	KHINR	Standard Hierarchy Node/Activity Type Grp* Each profit center must be assigned to a node in the standard hierarchy for its controlling area. This ensures that the standard hierarchy contains all the profit centers in the controlling area. Type: Text Length: 12	Read new Activity Type Hierarchy value based on Activity Type Mapping ( and Enrichment File )
11	ECC	CEPC	ABTEI	Department This field contains the name of the department to which the profit center belongs. Type: Text Length: 12	S/4HANA	CEPC	ABTEI	Department This field contains the name of the department to which the profit center belongs. Type: Text Length: 12	Copy as is
12	ECC	CEPC	SEGMENT	Segment Segment for Segmental Reporting. Note: Field Segment must be filled with leading zeros if it is numeric data. Example: if the segment value is 9999, enter 0000009999 in the XML file. Type: Text Length: 10	S/4HANA	CEPC	SEGMENT	Segment Segment for Segmental Reporting. Note: Field Segment must be filled with leading zeros if it is numeric data. Example: if the segment value is 9999, enter 0000009999 in the XML file. Type: Text Length: 10	Read From Activity Type Mapping File where Segment Enrichment is given
13	ECC	CEPC	ANRED	Title Title for Address data. Type: Text Length: 15	S/4HANA	CEPC	ANRED	Title Title for Address data. Type: Text Length: 15	Not used
14	ECC	CEPC	NAME1	Name 1 Name 1 of the customer/supplier address. Type: Text Length: 35	S/4HANA	CEPC	NAME1	Name 1 Name 1 of the customer/supplier address. Type: Text Length: 35	Copy as is
15	ECC	CEPC	NAME2	Name 2 Name 2 of the customer/supplier address. Type: Text Length: 35	S/4HANA	CEPC	NAME2	Name 2 Name 2 of the customer/supplier address. Type: Text Length: 35	Copy as is
16	ECC	CEPC	NAME3	Name 3 Name 3 of the customer/supplier address. Type: Text Length: 35	S/4HANA	CEPC	NAME3	Name 3 Name 3 of the customer/supplier address. Type: Text Length: 35	Copy as is
17	ECC	CEPC	NAME4	Name 4 Name 4 of the customer/supplier address. Type: Text Length: 35	S/4HANA	CEPC	NAME4	Name 4 Name 4 of the customer/supplier address. Type: Text Length: 35	Copy as is
18	ECC	CEPC	STRAS	Street Street and house number as part of the address. Type: Text Length: 35	S/4HANA	CEPC	STRAS	Street Street and house number as part of the address. Type: Text Length: 35	Copy as is
19	ECC	CEPC	ORT01	City Name of the city as a part of the address. Type: Text Length: 35	S/4HANA	CEPC	ORT01	City Name of the city as a part of the address. Type: Text Length: 35	Copy as is
20	ECC	CEPC	ORT02	District Supplement to city name or district. Use The entry is appended to the city name with a hyphen by the automatic address formatting function. (Exceptions: Germany, United Kingdom/Ireland and Japan) Type: Text Length: 35	S/4HANA	CEPC	ORT02	District Supplement to city name or district. Use The entry is appended to the city name with a hyphen by the automatic address formatting function. (Exceptions: Germany, United Kingdom/Ireland and Japan) Type: Text Length: 35	Copy as is
21	ECC	CEPC	LAND1	Country/Region The country/region key contains information which the system uses to check entries such as the length of the postal code or bank account number. The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used. Type: Text Length: 80	S/4HANA	CEPC	LAND1	Country/Region The country/region key contains information which the system uses to check entries such as the length of the postal code or bank account number. The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used. Type: Text Length: 80	Copy as is
22	ECC	CEPC	TELBX	Telebox Number Number of telebox for electronic mail. Type: Text Length: 15	S/4HANA	CEPC	TELBX	Telebox Number Number of telebox for electronic mail. Type: Text Length: 15	Copy as is
23	ECC	CEPC	TELF1	Telephone Number First telephone number Type: Text Length: 16	S/4HANA	CEPC	TELF1	Telephone Number First telephone number Type: Text Length: 16	Copy as is
24	ECC	CEPC	TELF2	Second Telephone Number Second telephone number for communication. Type: Text Length: 16	S/4HANA	CEPC	TELF2	Second Telephone Number Second telephone number for communication. Type: Text Length: 16	Copy as is
25	ECC	CEPC	TELFX	Fax Number under which a business partner's telefax machine can be reached. Use The number is used by the system if you send a message by telefax to your business partner from within an SAP transaction. Type: Text Length: 31	S/4HANA	CEPC	TELFX	Fax Number under which a business partner's telefax machine can be reached. Use The number is used by the system if you send a message by telefax to your business partner from within an SAP transaction. Type: Text Length: 31	Copy as is
26	ECC	CEPC	TELTX	Teletex Number Number under which a business partner's teletex machine can be reached. Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater. Use The number is determined by the SAP system if you send a teletex message to your business partner from within an SAP transaction. Type: Text Length: 30	S/4HANA	CEPC	TELTX	Teletex Number Number under which a business partner's teletex machine can be reached. Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater. Use The number is determined by the SAP system if you send a teletex message to your business partner from within an SAP transaction. Type: Text Length: 30	Copy as is
27	ECC	CEPC	TELX1	Telex Number Number under which the telex machine can be reached. Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater. Type: Text Length: 30	S/4HANA	CEPC	TELX1	Telex Number Number under which the telex machine can be reached. Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater. Type: Text Length: 30	Copy as is
28	ECC	CEPC	DATLT	Data Line Data communication line no. Line number (telephone line). Dialing this number enables you to establish a link with another computer at a different location. Type: Text Length: 14	S/4HANA	CEPC	DATLT	Data Line Data communication line no. Line number (telephone line). Dialing this number enables you to establish a link with another computer at a different location. Type: Text Length: 14	Not used
29	ECC	CEPC	DRNAM	Printer Printer name for profit center Type: Text Length: 4	S/4HANA	CEPC	DRNAM	Printer Printer name for profit center Type: Text Length: 4	Not used
30	ECC	CEPC	TXJCD	Tax Jurisdiction Max. length of input must not exceed 15 digits. The tax jurisdiction is used for determining the tax rate. It defines to which tax authorities you must pay your taxes. It is always the city to which the goods are supplied. If Vertex is activated (esp. on US installations) the tax jurisdiction code will be determined by the business object's address. If the given postal code/Zip code is not accurate as possible, Vertex will determine more than one tax jurisdiction code for one record, the migration of this record will fail. You will then get the error message "No unique jurisdiction code can be determined". Type: Text Length: 15	S/4HANA	CEPC	TXJCD	Tax Jurisdiction Max. length of input must not exceed 15 digits. The tax jurisdiction is used for determining the tax rate. It defines to which tax authorities you must pay your taxes. It is always the city to which the goods are supplied. If Vertex is activated (esp. on US installations) the tax jurisdiction code will be determined by the business object's address. If the given postal code/Zip code is not accurate as possible, Vertex will determine more than one tax jurisdiction code for one record, the migration of this record will fail. You will then get the error message "No unique jurisdiction code can be determined". Type: Text Length: 15	Not used
31	ECC	CEPC	PFACH	PO Box PO Box for address. Type: Text Length: 10	S/4HANA	CEPC	PFACH	PO Box PO Box for address. Type: Text Length: 10	Copy as is
32	ECC	CEPC	PSTLZ	Postal Code This field contains the postal (zip) code for the house address (street and city). Type: Text Length: 10	S/4HANA	CEPC	PSTLZ	Postal Code This field contains the postal (zip) code for the house address (street and city). Type: Text Length: 10	Copy as is
33	ECC	CEPC	PSTL2	P.O. Box Postal Code Postal code needed to allocate the P.O. Box. Use This field is used for a country/region where: - the postal code (zip code) used to send letters to a customer's/vendor's P.O. Box is different to that used to send letters to a customer's/vendor's company address. - large companies have their own postal code and no P.O. Box. Type: Text Length: 10	S/4HANA	CEPC	PSTL2	P.O. Box Postal Code Postal code needed to allocate the P.O. Box. Use This field is used for a country/region where: - the postal code (zip code) used to send letters to a customer's/vendor's P.O. Box is different to that used to send letters to a customer's/vendor's company address. - large companies have their own postal code and no P.O. Box. Type: Text Length: 10	Copy as is
34	ECC	CEPC	REGIO	Region In some countries/regions, the region forms part of the address. The meaning depends on the country/region. Type: Text Length: 80	S/4HANA	CEPC	REGIO	Region In some countries/regions, the region forms part of the address. The meaning depends on the country/region. Type: Text Length: 80	Copy as is
35	ECC	CEPC	LOCK_IND	Indicator: Profit Center Locked You can use the lock indicator to lock a profit center for postings. The lock only applies to the selected time interval. If the profit center is assigned to an object that receives a posting, the system displays an error message and the data is not posted. This is an indicator field. If the criterion is met, enter X. If not, leave the field empty. Type: Text Length: 1	S/4HANA	CEPC	LOCK_IND	Indicator: Profit Center Locked You can use the lock indicator to lock a profit center for postings. The lock only applies to the selected time interval. If the profit center is assigned to an object that receives a posting, the system displays an error message and the data is not posted. This is an indicator field. If the criterion is met, enter X. If not, leave the field empty. Type: Text Length: 1	Copy as is
36	ECC	CEPC	PCA_TEMPLATE	Planning Template Template for Formula Planning in Profit Centers Contains functions, which are used to find plan values using formula planning. A template is assigned to the profit centers for which it is to be valid, in master data maintenance. It can be used for more than one profit center. Type: Text Length: 10	S/4HANA	CEPC	PCA_TEMPLATE	Planning Template Template for Formula Planning in Profit Centers Contains functions, which are used to find plan values using formula planning. A template is assigned to the profit centers for which it is to be valid, in master data maintenance. It can be used for more than one profit center. Type: Text Length: 10	Not used

Transformation Mapping

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

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

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 CEPC to confirm copied fields are accurately copied.

If any of the sum is different, raise defect and flag the relevant record as error.

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 Activity Type.
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

Configuration

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

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

Completeness

Task

Action

Reconciliation of Record Count

Total number of records loaded for TB Balance ( PY ) will be generated in the Post-load reports in tool based on the target table and fields mentioned in section 3.

The reconciliation needs to be executed on the total number of ‘valid’ records and currency amount per company code in the source compared to total number of records and currency amount in S/4HANA

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

Check Amount in Document Currency and Local Currency

Check on line item level that the sum of the amount in Document Currency and Local Currency in the load file is the same as posted in S/4HANA. If any of the sum is different, flag the record as error.

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

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 FS10N – Vendor Line Item Display or equivalent report in Fiori App to display loaded TB Balance ( PY ) in S/4HANA and compare results against the pre-load reports generated from tool.

Accuracy

Task	Action
Open items totals	Check business partner open item totals by Business partner, Company code, Activity Type. Totals should be checked in Document, Local and Group currency.
Spot check	Business should choose some business partners and perform comprehensive check of open items, payment terms etc Such partners should have huge number of open items or be critical for payment runs in S4 or have certain complexity in conversion.

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

Version	Published	Changed By
CURRENT (v. 2)	Feb 23, 2026 10:11	PARA-ext, Anil
v. 41	Nov 20, 2025 11:44	PARA-ext, Anil
v. 40	Oct 28, 2025 13:26	PILLAY-ext, Lawrence
v. 39	Oct 20, 2025 12:16	PARA-ext, Anil
v. 38	Oct 08, 2025 08:05	PILLAY-ext, Lawrence
v. 37	Oct 02, 2025 10:27	PARA-ext, Anil
v. 36	Sept 30, 2025 11:43	PARA-ext, Anil
v. 35	Sept 29, 2025 09:27	GARCIA-ext, Angel Luis
v. 34	Sept 23, 2025 18:55	PARA-ext, Anil
v. 33	Sept 23, 2025 15:56	PARA-ext, Anil

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

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

CNV-1071 Activity Types

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction 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

Business

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