Status	Approved
Owner	LIU-ext, Ekawati
Stakeholders	CIRULE, Anita

Purpose

The purpose of this document is to define the data conversion approach to create Material Listing and Exclusions in S/4 HANA.

Material Listing and Exclusion functionality in SAP enables control over which materials a customer is permitted or restricted from purchasing. A listing defines materials that a specific customer is allowed to buy, whereas an exclusion specifies materials they are not permitted to purchase. This functionality is essential for enforcing customer-specific sales restrictions.

In SAP S/4HANA, the structure and usage of Material Listing and Exclusion remains consistent with the ECC system, primarily based on combinations such as customer/ material or sales organization/ distribution channel/ customer/ material.

However, in SAP ECC, additional table combinations exist beyond the standard structures. Examples include:

Destination Country/Material Group
Destination Country/Region/Material
Material/Plant/Ship-to Party
Material/Plant/Sold-to Party
Sales Organization/ Customer/ Material
Sales Organization/Destination Country
Sales Organization/Departure Country
Material/Destination Country/Region
Sales Organization/ Material/ Customer
Material/Destination Country
Sales Organization/Material/Destination Country

This conversion aims to migrate active and relevant Material Listing and Exclusion records from existing ECC systems into S/4HANA by applying required transformation logic using Syniti as the data migration and transformation platform. The converted records will be loaded into the target S/4HANA system using standard SAP mechanisms such as IDOCs, BAPIs, or direct table loads where applicable.

Conversion Scope

The scope of this document covers the approach for converting active Material Listing and Exclusions records from Legacy Source Systems into S/4HANA following the Material Listing and Exclusions Master Data Design Standard: DD-FUN-050 Master Data Standard_2001-Material Listing and Exclusions.

From the current system landscape, Material Listing and Exclusions exist in the both legacy systems - PF2 and WP2. Harmonization and validation are required to ensure the accurate and consolidated data in S/4HANA. While PF2 and WP2 serve as source systems, a mapping and transformation logic will be necessary to produce properly formatted load templates in line with the target design.

The data from legacy system includes:

All active Material Listing or Material Exclusions records, where "valid to date is beyond S/4HANA Go-Live date" AND must meet one or more of the applicable table combination criteria below:
1. Customer/ Sold-to/ Ship-to sales view migrated as per CNV-3003 Business Partners - Customer (Sales and Service) - FLCU01
2. Material sales view migrated as per CNV-2003 Materials - Sales view with sales long text.
3. Sales organization is in scope of S/4HANA
4. Plant is in scope of S/4HANA
5. Material Group is in scope of S/4HANA
6. Country (Departure/ Destination) must be within S/4HANA scope
7. Region must be within S/4HANA scope

The data from legacy system excludes:

Invalid Material Listing or Material Exclusions, e.g. table KOTG905 - PF2 (Material/ Sales Organization) or KOTG905 - WP2 (Sales Organization/ Sales Document Type/ Item Category Group).

List of source systems and approximate number of records

Source	Condition Type	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WP2	ZA01 - RCS Inclusion	Table: KOTG001 Listing/exclusion type - Customer - Material - Valid to - Valid From	30	S/4HANA	30
WP2	ZA01 - RCS Inclusion	Table: KOTG004 Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material - Valid to - Valid From *As at 28-Oct-2025: all customer has flag for deletion.	10	S/4HANA	10
WP2	ZB01 - RCS Exclusion	Table: KOTG906 Listing/exclusion type - Sales Organization - Customer - Material - Valid to - Valid From	20,000	S/4HANA	20,000
WP2	ZB01 - RCS Exclusion	Table: KOTG908 Listing/exclusion type - Sales Organization - Departure country - Valid to - Valid From	20	S/4HANA	20
WP2	ZB01 - RCS Exclusion	Table: KOTG909 Listing/exclusion type - Material - Destination Country - Region - Valid to - Valid From	5,000	S/4HANA	5,000
WP2	ZB01 - RCS Exclusion	Table: KOTG913 Listing/exclusion type - Sales Organization - Material - Customer - Valid to - Valid From	50	S/4HANA	50
WP2	ZREA - REACH Exclusion	Table: KOTG962 Listing/exclusion type - Material - Destination Country - Valid to - Valid From	20	S/4HANA	20
WP2	ZREA - REACH Exclusion	Table: KOTG964 Listing/exclusion type - Sales Organization - Material - Destination Country - Valid to - Valid From	10,000	S/4HANA	10,000
PF2	EXCL - Exclusion ERP	Table: KOTG501 Listing/exclusion type - Destination Country - Material Group - Valid to - Valid From	15,500	S/4HANA	15,500
PF2	EXCL - Exclusion ERP	Table: KOTG521 Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From *As at 28-Oct-2025: all material has flag for deletion.	10	S/4HANA	10
PF2	ZEXC - Exclusion ERP	Table: KOTG521 Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From *As at 28-Oct-2025: all material has flag for deletion.	10	S/4HANA	10
PF2	EXCL - Exclusion ERP	Table: KOTG903 List/excl. - Material - Plant - Ship-To Party - Valid to - Valid From	10	S/4HANA	10
PF2	EXCL - Exclusion ERP	Table: KOTG904 List/excl. - Material - Plant - Sold-To Party - Valid to - Valid From *As at 28-Oct-2025: all material has flag for deletion.	10	S/4HANA	10
PF2	EXCL - Exclusion ERP	Table: KOTG906 Sales org. - Destination Country - Valid to - Valid From	75	S/4HANA	75

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

Due to compliance requirement, there will be one SAP instance for Rest of the World (ROW), one for China and one for CUI. For Material Listing and Exclusions table with sales organization the records will be migrated to respective SAP instances. For Material Listing and Exclusions table without sales organization the records will be migrated to all instances.

Target Design

Material Listing and Exclusions Data strictly adheres to the Master Data Standard. The complete information of the tables and key fields that hold the Material Listing and Exclusions information follows the Master Data Standard document.

The technical design of the target for this conversion approach.

Table Pending configuration - TBC	Field	Data Element	Field Description	Data Type	Length	Requirement
KOTG001_WP2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG001_WP2	KUNNR	KUNNR_V	Customer	CHAR	10	Mandatory
KOTG001_WP2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG001_WP2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG001_WP2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG004_WP2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG004_WP2	VKORG	VKORG	Sales Organization	CHAR	4	Mandatory
KOTG004_WP2	VTWEG	VTWEG	Distribution Channel	CHAR	2	Mandatory
KOTG004_WP2	KUNNR	KUNNR_V	Customer	CHAR	10	Mandatory
KOTG004_WP2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG004_WP2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG004_WP2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG906_WP2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG906_WP2	VKORG	VKORG	Sales Organization	CHAR	4	Mandatory
KOTG906_WP2	KUNNR	KUNNR_V	Customer	CHAR	10	Mandatory
KOTG906_WP2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG906_WP2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG906_WP2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG908_WP2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG908_WP2	VKORG	VKORG	Sales Organization	CHAR	4	Mandatory
KOTG908_WP2	ALAND	ALAND	Departure country	CHAR	3	Mandatory
KOTG908_WP2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG908_WP2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG909_WP2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG909_WP2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG909_WP2	LAND1	LLAND	Destination Country	CHAR	3	Mandatory
KOTG909_WP2	REGIO	REGIO	Region	CHAR	3	Mandatory
KOTG909_WP2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG909_WP2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG913_WP2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG913_WP2	VKORG	VKORG	Sales Organization	CHAR	4	Mandatory
KOTG913_WP2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG913_WP2	KUNNR	KUNNR_V	Customer	CHAR	10	Mandatory
KOTG913_WP2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG913_WP2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG962_WP2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG962_WP2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG962_WP2	LAND1	LLAND	Destination Country	CHAR	3	Mandatory
KOTG962_WP2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG962_WP2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG964_WP2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG964_WP2	VKORG	VKORG	Sales Organization	CHAR	4	Mandatory
KOTG964_WP2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG964_WP2	LAND1	LLAND	Destination Country	CHAR	3	Mandatory
KOTG964_WP2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG964_WP2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG501_PF2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG501_PF2	LAND1	LLAND	Destination Country	CHAR	3	Mandatory
KOTG501_PF2	MATKL	MATKL	Material Group	CHAR	9	Mandatory
KOTG501_PF2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG501_PF2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG521_PF2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG521_PF2	LAND1	LLAND	Destination Country	CHAR	3	Mandatory
KOTG521_PF2	REGIO	REGIO	Region	CHAR	3	Mandatory
KOTG521_PF2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG521_PF2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG521_PF2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG903_PF2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG903_PF2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG903_PF2	WERKS	WERKS_D	Plant	CHAR	4	Mandatory
KOTG903_PF2	KUNWE	KUNWE	Ship-to Party	CHAR	10	Mandatory
KOTG903_PF2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG903_PF2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG904_PF2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG904_PF2	MATNR	MATNR	Material	CHAR	18	Mandatory
KOTG904_PF2	WERKS	WERKS_D	Plant	CHAR	4	Mandatory
KOTG904_PF2	KUNAG	KUNAG	Sold-to Party	CHAR	10	Mandatory
KOTG904_PF2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG904_PF2	DATAB	KODATAB	Valid From	DATS	8	Mandatory
KOTG906_PF2	KSCHL	KSCHG	Listing/exclusion type	CHAR	4	Mandatory
KOTG906_PF2	VKORG	VKORG	Sales Organization	CHAR	4	Mandatory
KOTG906_PF2	LAND1	LLAND	Destination Country	CHAR	3	Mandatory
KOTG906_PF2	DATBI	KODATBI	Valid to	DATS	8	Mandatory
KOTG906_PF2	DATAB	KODATAB	Valid From	DATS	8	Mandatory

Data Cleansing

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

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
2001-001	C1	Customer with flag for deletion	Flag for deletion for all area (KNA1-LOEVM) OR flag for deletion at company code level (KNB1-LOEVM) OR flag for deletion at sales area level (KNVV-LOEVM) is 'X' - Yes For WP2 - table: KOTG001, KOTG004, KOTG906 and KOTG913 For PF2 - table: KOTG903 and KOTG904 Company code: IF KOTGxxx has VKORG, get TVKO-BUKRS, where TVKO-VKORG = KOTGxxx-VKORG IF KOTGxxx does not have VKORG, get TVKO-BUKRS, where TVKO-VKORG = KNVV-VKORG (for all sales organization in scope) *Sales organization: IF KOTGxxx does not have VKORG, get KNVV-VKORG for all sales organization in scope.	Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer No. (KUNNR, KUNAG, KUNWE)/ Customer Name/ Country/ Company Code/ Company Code Name/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Division/ Division Name/ Plant/ Plant Name/ Flag for deletion for all area level/ Flag for deletion at company code level/ Flag for deletion at sales area level/ Material No./ Material Description	PF2/ WP2
2001-002	C1	Customer with posting block	Posting block for all company code (KNA1-SPERR) OR posting block at company code level (KNB1-SPERR) is "X" - Yes For WP2 - table: KOTG001, KOTG004, KOTG906 and KOTG913 For PF2 - table: KOTG903 and KOTG904 Company code: IF KOTGxxx has VKORG, get TVKO-BUKRS, where TVKO-VKORG = KOTGxxx-VKORG IF KOTGxxx does not have VKORG, get TVKO-BUKRS, where TVKO-VKORG = KNVV-VKORG (for all sales organization in scope) *Sales organization: IF KOTGxxx does not have VKORG, get KNVV-VKORG for all sales organization in scope.	Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer No. (KUNNR, KUNAG, KUNWE)/ Customer Name/ Country/ Company Code/ Company Code Name/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Division/ Division Name/ Plant/ Plant Name/ Posting block for all company code/ Posting block at company code level/ Material No./ Material Description	PF2/ WP2
2001-003	C1	Customer with sales block	Sales block for all sales area (KNA1-CASSD) OR sales block at sales area level (KNVV-CASSD) is "X" - Yes For WP2 - table: KOTG001, KOTG004, KOTG906 and KOTG913 For PF2 - table: KOTG903 and KOTG904 **Sales organization: IF KOTGxxx does not have VKORG, get KNVV-VKORG for all sales organization in scope.	Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer No. (KUNNR, KUNAG, KUNWE)/ Customer Name/ Country/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Division/ Division Name/ Plant/ Plant Name/ Sales block for all sales area/ Sales block at sales area level/ Material No./ Material Description	PF2/ WP2
2001-004	C1	Customer with order block, delivery block or billing block	Order block for all sales area (KNA1-AUFSD) OR order block at sales area level (KNVV-AUFSD) OR delivery block for all sales area (KNA1-LIFSD) OR delivery block at sales area level (KNVV-LIFSD) OR billing block for all sales area (KNA1-FAKSD) OR billing block at sales area level (KNVV-FAKSD) is NOT BLANK. For WP2 - table: KOTG001, KOTG004, KOTG906 and KOTG913 For PF2 - table: KOTG903 and KOTG904 **Sales organization: IF KOTGxxx does not have VKORG, get KNVV-VKORG for all sales organization in scope.	Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer No. (KUNNR, KUNAG, KUNWE)/ Customer Name/ Country/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Division/ Division Name/ Plant/ Plant Name/ Order block for all sales area (code + description)/ Order block at sales area level (code + description)/ Delivery block for all sales area (code + description)/ Delivery block at sales area level (code + description)/ Billing block for all sales area (code + description)/ Billing block at sales area level (code + description)/ Material No./ Material Description	PF2/ WP2
2001-005	C1	Material with flag for deletion	Flag for deletion at client level (MARA-LVORM) OR flag for deletion at distribution chain level (MVKE-LVORM) is 'X' - Yes For WP2 - table: KOTG001, KOTG004, KOTG906, KOTG909, KOTG913, KOTG962 and KOTG964 For PF2 - table: KOTG521, KOTG903 and KOTG904 **Sales organization: IF KOTGxxx does not have VKORG, get MVKE-VKORG for all sales organization in scope.	Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material No./ Material Description/ Customer No. (KUNNR, KUNAG, KUNWE)/ Customer Name/ Country/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Plant/ Plant Name/ Destination Country Code/ Destination Country Description/ Region Code/ Region Description/ Flag for deletion at client level/ Flag for deletion at distribution chain level	PF2/ WP2
2001-006	C1	Material with distribution-chain material status	Cross-distribution-chain material status (MARA-MSTAV) OR Distribution-chain-specific material status (MVKE-VMSTA) is NOT BLANK For WP2 - table: KOTG001, KOTG004, KOTG906, KOTG909, KOTG913, KOTG962 and KOTG964 For PF2 - table: KOTG521, KOTG903 and KOTG904 **Sales organization: IF KOTGxxx does not have VKORG, get MVKE-VKORG for all sales organization in scope.	Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material No./ Material Description/ Customer No. (KUNNR, KUNAG, KUNWE)/ Customer Name/ Country/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Plant/ Plant Name/ Destination Country Code/ Destination Country Description/ Region Code/ Region Description/ Cross-distribution-chain material status code and the description/ Distribution-chain-specific material status code and the description	PF2/ WP2
2001-007	C1	Duplicate Material Listing and Exclusions records by distribution channel	Only for Table: KOTG004 with the same sales organization, same customer and same material but different distribution channel	Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Customer No./ Customer Name/ Country/ Material No./ Material Description	PF2/ WP2

How to clean: Header data invalid - Data cleanser to delete all item data in the Material Listing and Exclusions, Item data invalid - Data cleanser to delete the invalid item data only.

Conversion Process

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

The ETL (Extract, Transform, Load) process is a structured approach to data migration and management, ensuring high-quality data is seamlessly transferred across systems. Here’s a breakdown of its key components:

1. Extraction
The process begins with extracting metadata and raw data from source systems, such as Syensqo ECC system WP2 and PF2. The extracted data is then staged for transformation.

2. Transformation
Once extracted, the data undergoes cleansing, consolidation, and governance. This step ensures data integrity, consistency, and compliance with business rules. The transformation process includes:
- Data validation to remove inconsistencies.
- Standardization to align formats across datasets.
- Business rule application to refine data for operational use.

3. Loading
The transformed data is then loaded into the target S/4HANA system.

Data Privacy and Sensitivity

N/A

Extraction

Extract data from a SAP ECC WP2 and PF2 into Syniti Migrate for S/4HANA. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 2 possibilities:

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.
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
2001-001	- Identify the source systems (WP2 and PF2) and databases involved. - Define the data objects (tables such as KOTGxxx) to be extracted. - Establish business rules for data selection.	Syniti / LTC Data team
2001-002	- Specify the extraction approach (full, incremental, or delta extraction). - Determine the tools and technologies used. - Define data filtering criteria to exclude irrelevant records.	Syniti
2001-003	- Establish execution timelines and batch processing schedules. - Assign responsibilities for extraction monitoring. - Document dependencies on other migration tasks.	Syniti
2001-004	- Define error handling mechanisms for extraction failures.	Syniti

Selection Screen

Parameter Name	Selection Type	Requirement	Value to be entered/set
Valid To Date	Single	Select Data that are valid from this (Valid to) date	Date
Listing/ Exclusions Table	Multiple	Valid listing/ exclusions table for extraction	Table
Sales Organization	Multiple	Valid sales organization for extraction	In-scope Sales Organization
Plant	Multiple	Valid plant for extraction	In-scope Plant

Data Collection Template (DCT)

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

DCT Rules

Field Name	Field Description	Rule
N/A

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Source System Availability Ensure that the source database or application is accessible. Confirm that necessary credentials and permissions are granted	Syensqo IT
2	Data Structure Identify relationships between tables, views, and stored procedures.	Syniti
3	Referential Integrity Ensure dependent records are extracted together.	Syniti
4	Extraction Methodology Define whether extraction is full, incremental, or delta-based. Establish batch processing schedules for large datasets.	Syniti
5	Performance and Scalability Considerations Optimize extraction queries to prevent system overload. Ensure network bandwidth supports data transfer volumes.	Syniti
6	Security and Compliance Adhere to regulatory standards for sensitive information if applicable	Syniti

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

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in Syniti Migrate
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	Identify target S/4HANA fields and determine applicable legacy source fields from ECC system (PF2/ WP2).	Functional Team (L2C) + Data Team (L2C)
2	Map legacy field values to S/4HANA target values (including field-level mapping and technical names)	Data Team (L2C), Data Team (Syniti)
3	Define value mapping rules for fields requiring standardization or harmonization across the source systems	Functional Team (L2C) + Data Team (L2C)
4	Identify and agree on default values where legacy data is incomplete or inconsistent	Business Team + Functional Team (L2C)
5	Configure transformation rules in Syniti Migrate	Data Team (Syniti)
6	Review transformation logic and mappings with Business for confirmation	Business Team + Functional Team (L2C)
7	Perform initial transformation run and generate draft target-ready dataset	Data Team (Syniti)
8	Review draft target-ready data for structure and completeness	Data Team (L2C), Functional Team (L2C)
9	Share transformed data with Business for Pre-load Validation	Business Team
10	Incorporate feedback from Business and refine mappings or transformation logic as needed	Data Team (L2C)
11	Finalize and approve transformed data as Target Ready Load File	Business + Functional (L2C) + Data Team (L2C)
12	Handover final file to Load Team or trigger the load via Syniti Load Workbench	Data Team (Syniti), Data Load Team

Transformation Rules

Rule #	Source System	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Mapping Table	Transformation Logic
Material Listing and Exclusions
Data Extraction Logic for Material Listing and Exclusions 1. Identify Relevant Listing/ Exclusions Types All Listing/ Exclusions type in the mapping table will be in-scope for extraction. There are multiple Listing/ Exclusions type used in ECC, e.g. ZB01 - RCS Exclusions (WP2), ZREA - REACH Exclusion (WP2), EXCL - Exclusion ERP (PF2). 2. Process by Source System Perform the extraction steps from source system, i.e. WP2 and PF2. 3. Extract data from all tables below. Extract Customer, Departure Country, Destination Country, Distribution Channel, Listing/ Exclusions Type, Material, Material Group, Plant, Region, Sales Organization, Ship-to Party, Sold-to Party, Valid From and Valid To with the following: Filter #1: - Validity Date (DATBI): include only records with validity greater than the cut-off date defined for the current conversion cycle (as specified on the selection screen). - Sales Organization (VKORG): include only records for in-scope Sales Organizations provided in the parameter list. From WP2 - table: KOTG004, KOTG906,KOTG908, KOTG913 and KOTG964 From PF2 - table: KOTG906 Filter #2: - Validity Date (DATBI): include only records with validity greater than the cut-off date defined for the current conversion cycle (as specified on the selection screen). - Plant (WERKS): include only records for in-scope Plants provided in the parameter list. From PF2 - table: KOTG903 and KOTG904 Filter #3: - Validity Date (DATBI): include only records with validity greater than the cut-off date defined for the current conversion cycle (as specified on the selection screen). From WP2 - table: KOTG001, KOTG909 and KOTG962 From PF2 - table: KOTG501 and KOTG521 4. For fields related to Customer/ Sold-to Party/ Ship-to Party, Material Master, Departure/ Destination Country, Listing/ Exclusions Type, Material Group and Region, include records only if the corresponding migrated target value exists in the target system.
2001-001	WP2	KOTG001	KSCHL	Listing/exclusion type	S/4HANA	KOTG001	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-002	WP2	KOTG001	KUNNR	Customer	S/4HANA	KOTG001	KUNNR	Customer	MAP_KUNNR	Mapping
2001-003	WP2	KOTG001	MATNR	Material	S/4HANA	KOTG001	MATNR	Material	MAP_MATNR	Mapping
2001-004	WP2	KOTG001	DATBI	Valid to	S/4HANA	KOTG001	DATBI	Valid to		Copy
2001-005	WP2	KOTG001	DATAB	Valid From	S/4HANA	KOTG001	DATAB	Valid From		Copy
2001-006	WP2	KOTG004	KSCHL	Listing/exclusion type	S/4HANA	KOTG004	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-007	WP2	KOTG004	VKORG	Sales Organization	S/4HANA	KOTG004	VKORG	Sales Organization	MAP_VKORG	Mapping
2001-008	WP2	KOTG004	VTWEG	Distribution Channel	S/4HANA	KOTG004	VTWEG	Distribution Channel	Rule	RULE: 1. Get ALL sales documents for the last 4 years for sales organization in scope and document category/ VBAK-VBTYP = C - Order. 2. Get valid sales documents for Material Listing and Exclusions; VBPA-VBELN = VBAK-VBELN, where VBPA-KUNNR = KOTG004-KUNNR (ignore the partner function) 3. From the valid sales document (point #2), get the Ship-to Party country; VBPA-LAND1, where VBPA-PARVW = SH/ Ship-to party 4. From the valid sales document (point #2), get the Plant; VBAP-WERKS, where VBAP-VBELN = VBPA-VBELN and VBAP-MATNR = KOTG004-MATNR. 5. Get the Plant country; T001W-LAND1, where T001W-WERKS = VBAP-WERKS 6. Select sales document for each Material Listing and Exclusions records, where VBAK-VKORG = KOTG004-VKORG and VBAK-VTWEG = KOTG004-VTWEG and VBPA-KUNNR = KOTG004-KUNNR (ignore the partner function) and VBAP-MATNR = KOTG004-MATNR: - IF Plant Country = Ship-to Party Country: map to S/4HANA distribution channel = 20 Domestic - IF Plant Country <> Ship-to Party Country: map to S/4HANA distribution channel = 10 Export IF the sales order created for both 10 Export and 20 Domestic; then create 2 Material Listing and Exclusions Records as per distribution channel.
2001-009	WP2	KOTG004	KUNNR	Customer	S/4HANA	KOTG004	KUNNR	Customer	MAP_KUNNR	Mapping
2001-010	WP2	KOTG004	MATNR	Material	S/4HANA	KOTG004	MATNR	Material	MAP_MATNR	Mapping
2001-011	WP2	KOTG004	DATBI	Valid to	S/4HANA	KOTG004	DATBI	Valid to		Copy
2001-012	WP2	KOTG004	DATAB	Valid From	S/4HANA	KOTG004	DATAB	Valid From		Copy
2001-013	WP2	KOTG906	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-014	WP2	KOTG906	VKORG	Sales Organization	S/4HANA	TBC	VKORG	Sales Organization	MAP_VKORG	Mapping
2001-015	WP2	KOTG906	KUNNR	Customer	S/4HANA	TBC	KUNNR	Customer	MAP_KUNNR	Mapping
2001-016	WP2	KOTG906	MATNR	Material	S/4HANA	TBC	MATNR	Material	MAP_MATNR	Mapping
2001-017	WP2	KOTG906	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-018	WP2	KOTG906	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-019	WP2	KOTG908	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-020	WP2	KOTG908	VKORG	Sales Organization	S/4HANA	TBC	VKORG	Sales Organization	MAP_VKORG	Mapping
2001-021	WP2	KOTG908	ALAND	Departure country	S/4HANA	TBC	ALAND	Departure country		Copy
2001-022	WP2	KOTG908	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-023	WP2	KOTG908	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-024	WP2	KOTG909	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-025	WP2	KOTG909	MATNR	Material	S/4HANA	TBC	MATNR	Material	MAP_MATNR	Mapping
2001-026	WP2	KOTG909	LAND1	Destination Country	S/4HANA	TBC	LAND1	Destination Country		Copy
2001-027	WP2	KOTG909	REGIO	Region	S/4HANA	TBC	REGIO	Region	MAP_REGION	Mapping
2001-028	WP2	KOTG909	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-029	WP2	KOTG909	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-030	WP2	KOTG913	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-031	WP2	KOTG913	VKORG	Sales Organization	S/4HANA	TBC	VKORG	Sales Organization	MAP_VKORG	Mapping
2001-032	WP2	KOTG913	MATNR	Material	S/4HANA	TBC	MATNR	Material	MAP_MATNR	Mapping
2001-033	WP2	KOTG913	KUNNR	Customer	S/4HANA	TBC	KUNNR	Customer	MAP_KUNNR	Mapping
2001-034	WP2	KOTG913	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-035	WP2	KOTG913	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-036	WP2	KOTG962	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-037	WP2	KOTG962	MATNR	Material	S/4HANA	TBC	MATNR	Material	MAP_MATNR	Mapping
2001-038	WP2	KOTG962	LAND1	Destination Country	S/4HANA	TBC	LAND1	Destination Country		Copy
2001-039	WP2	KOTG962	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-040	WP2	KOTG962	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-041	WP2	KOTG964	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-042	WP2	KOTG964	VKORG	Sales Organization	S/4HANA	TBC	VKORG	Sales Organization	MAP_VKORG	Mapping
2001-043	WP2	KOTG964	MATNR	Material	S/4HANA	TBC	MATNR	Material	MAP_MATNR	Mapping
2001-044	WP2	KOTG964	LAND1	Destination Country	S/4HANA	TBC	LAND1	Destination Country		Copy Pending MDS if country XK - Kosovo will be configured in S/4HANA with the same code or not. Note: no customer with country code XK in KNA1
2001-045	WP2	KOTG964	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-046	WP2	KOTG964	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-047	PF2	KOTG501	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-048	PF2	KOTG501	LAND1	Destination Country	S/4HANA	TBC	LAND1	Destination Country		Copy Pending MDS if country AN - Netherl. Antil., CS - Serbia&Mont.D, TP - Replaced by TL, YU - Yugoslavia D, ZR - Ex-Zaire and ZZ (unspecified) will be configured in S/4HANA with the same code or not. Note: - no customer with country code YU and ZR in KNA1 - TP has 1 customer: 888820229 - Prospective TP - ZZ has 1 customer: 888820000 - Prospective ZZ - AN has 2 customer: 888820016 - Prospective AN and 888830012 - Ship-to for NETHERL. ANTIL. - CS has 2 customer: 888820241 - Prospective CS. and 888830056 - Ship-to for SERBIA MONTEN. - 888820241 - Prospective CS has order block ZZ (customer blocked)
2001-049	PF2	KOTG501	MATKL	Material Group	S/4HANA	TBC	MATKL	Material Group	MAP_MATKL	Mapping
2001-050	PF2	KOTG501	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-051	PF2	KOTG501	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-052	PF2	KOTG521	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-053	PF2	KOTG521	LAND1	Destination Country	S/4HANA	TBC	LAND1	Destination Country		Copy
2001-054	PF2	KOTG521	REGIO	Region	S/4HANA	TBC	REGIO	Region	MAP_REGION	Mapping
2001-055	PF2	KOTG521	MATNR	Material	S/4HANA	TBC	MATNR	Material	MAP_MATNR	Mapping
2001-056	PF2	KOTG521	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-057	PF2	KOTG521	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-058	PF2	KOTG903	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-059	PF2	KOTG903	MATNR	Material	S/4HANA	TBC	MATNR	Material	MAP_MATNR	Mapping
2001-060	PF2	KOTG903	WERKS	Plant	S/4HANA	TBC	WERKS	Plant	MAP_WERKS	Mapping
2001-061	PF2	KOTG903	KUNWE	Ship-to Party	S/4HANA	TBC	KUNWE	Ship-to Party	MAP_KUNNR	Mapping
2001-062	PF2	KOTG903	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-063	PF2	KOTG903	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-064	PF2	KOTG904	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-065	PF2	KOTG904	MATNR	Material	S/4HANA	TBC	MATNR	Material	MAP_MATNR	Mapping
2001-066	PF2	KOTG904	WERKS	Plant	S/4HANA	TBC	WERKS	Plant	MAP_WERKS	Mapping
2001-067	PF2	KOTG904	KUNAG	Sold-to Party	S/4HANA	TBC	KUNAG	Sold-to Party	MAP_KUNNR	Mapping
2001-068	PF2	KOTG904	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-069	PF2	KOTG904	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy
2001-070	PF2	KOTG906	KSCHL	Listing/exclusion type	S/4HANA	TBC	KSCHL	Listing/exclusion type	MAP_KSCHL_KOTG-V	Mapping
2001-071	PF2	KOTG906	VKORG	Sales Organization	S/4HANA	TBC	VKORG	Sales Organization	MAP_VKORG	Mapping
2001-072	PF2	KOTG906	LAND1	Destination Country	S/4HANA	TBC	LAND1	Destination Country		Copy
2001-073	PF2	KOTG906	DATBI	Valid to	S/4HANA	TBC	DATBI	Valid to		Copy
2001-074	PF2	KOTG906	DATAB	Valid From	S/4HANA	TBC	DATAB	Valid From		Copy

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Mapping Table Name	Mapping Table Description
MAP_KSCHL_KOTG-V	ECC (PF2/ WP2) to S/4AHANA Listing/ Exclusions Type Mapping Table
MAP_VKORG	ECC (PF2/ WP2) to S/4AHANA Sales Organization Mapping Table
MAP_KUNNR	ECC (PF2/ WP2) to S/4AHANA Customer No. Mapping Table
MAP_MATNR	ECC (PF2/ WP2) to S/4AHANA Material No. Mapping Table
MAP_WERKS	ECC (PF2/ WP2) to S/4AHANA Plant Mapping Table
MAP_MATKL	ECC (PF2/ WP2) to S/4AHANA Material Group Mapping Table
MAP_REGION	ECC (PF2/ WP2) to S/4AHANA Region Code Mapping Table
MAP_LAND1	ECC (PF2/ WP2) to S/4AHANA Country Code Mapping Table Pending missing country configuration.

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Source Data Integrity - Ensure extracted data is complete, accurate, and consistent. - Validate that data types and formats align with transformation requirements.	Syniti
2	Referential Integrity - Ensure dependent records are transformed together or in advance	Syniti
3	Transformation Logic and Mapping - Define data mapping rules between source and target schemas.	Data Team
4	Performance and Scalability Considerations - Optimize transformation processes for large datasets. - Ensure system resources can handle transformation workloads	Syniti
5	Logging and Error Handling - Maintain detailed logs of transformation activities. - Define error-handling procedures for failed transformations	Syniti

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Compare Data Counts	Verify row counts between source and target databases. Identify missing or duplicated records.
Validate the mandatory fields	Validate there is value for all the mandatory fields
Validate Primary Keys and Unique Constraints	Check for duplicate or missing primary key values. Ensure unique constraints are maintained.
Test Referential Integrity	Confirm dependent records exist in related tables

Accuracy

Task	Action
Validate the transformation	Validate the fields which require transformation have the value after transformation instead of the original field value
Check Data Consistency	Compare field values across systems Validate data formats and structures

Business

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

Completeness

Task	Action
Compare Data Count	Verify row counts between source and target databases. Identify missing or duplicated records.
Review populated templates for missing or incorrect values	Use checklists to verify completeness and correctness before submission

Accuracy

Task	Action
Conversion Accuracy	Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/ mapping rules (and signed-off DCT data).

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

To identify the record is for SAP China, CUI or ROW Instance, it will use below logic.

The Material Listing and Material Exclusions have sales organizations in-scope as per link HERE - sheet: MAP_VKORG (link to be updated once confirm)
The Material Listing and Material Exclusions have Plants in-scope as per this link HERE - sheet: MAP_WERKS (mapping table owned by S2P, link to be updated once confirm)
If the Material Listing and Material Exclusions do not used sales organization or plant in the table in-scope, e.g. Customer/Material OR Destination Country/Material Group OR Destination Country/Region/Material OR Material/Destination Country; then it will be migrated to all 3 instances (ROW, CUI and China). To check if the customer/ material are only in specific sales organization, sales transaction by sales organization to the destination country and material group and other combination in scope, etc. May need Syniti report or transformation logic to decide which sales organization the listing/ exclusions to be extended to.

PREPARE FILE MAPPING SALES ORGANIZATION & S/4 INSTANCE BASED ON COMPANY CODE IN ENTERPRISE STRUCTURE FILE.

PREPARE FILE MAPPING PLANT & S/4 INSTANCE BASED ON COMPANY CODE IN ENTERPRISE STRUCTURE FILE.

Load Run Sheet

Item #	Step Description	Team Responsible
1	Load Scope Definition - Identify the target system and database structure. - Define data objects (tables, fields, records) to be loaded. - Establish business rules for data validation.	Data team
2	Load Methodology - Specify the loading tools and technologies (Migration Cockpit, LSMW, custom loading program).	Syniti
3	Data Quality and Validation - Ensure data integrity checks (null values, duplicates, format validation). - Perform pre-load validations to verify completeness. - Define error handling mechanisms for load failures	Syniti
4	Load Execution Plan - Establish execution timelines and batch processing schedules. - Assign responsibilities for monitoring execution. - Document dependencies on other migration tasks	Syniti
5	Logging and Reporting - Maintain detailed logs of loading activities. - Generate summary reports on loaded data volume and quality. - Define escalation procedures for errors	Syniti

Load Phase and Dependencies

The Material Listing and Exclusions will be loaded in the pre-cutover period.

Before loading, it will have dependency on the following configuration and data objects in the S/4 HANA.

Configuration

Item #	Configuration Item
1	Listing/ Exclusion Table
2	Listing/ Exclusion Access Sequence
3	Listing/ Exclusion Type
4	Listing/ Exclusion Procedure
5	Country Code (Departure and Destination Country)
6	Region
7	Material Group
8	Sales Organization
9	Distribution Channel
10	Plant

Conversion Objects

Object #	Preceding Object Conversion Approach
3003	Business Partners - Customer (Sales and Service) - FLCU01
2003	Materials - Sales view with sales long text

Error Handling

Error Type	Error Description	Action Taken
Configuration / Data Transformation	The value XXX for field XXX doesn't exist	Check the mapping/ conversion is done properly in the loading file Validate the target value is configured/ transported in the target system Reach out to function team to validate the configuration
Configuration	There is mandatory field XXX missing	Validate MDS if the fields are set as mandatory Validate if there is value in the pre-loading file Validate if the configuration for the mandatory fields are done properly

Post-Load Validation

Project Team

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

Completeness

Task	Action
Validate Record count in the backend	Validate all tables with prefix “KOTG” has the same records as the loading file
Display Records	Pick up a few random Material Listing or Material Exclusions, and run t-code: VB03 to validate the Material Listing and Exclusions can be displayed without any error.
Perform Source-to-Target Comparisons	Validate that migrated data matches source records. Check for discrepancies in numerical values, text fields, and timestamps

Accuracy

Task	Action
Execute Sample Queries and Reports	Run queries to validate business logic. Generate reports to compare expected vs. actual results
Conduct Post-Migration Reconciliation	Generate reports comparing pre- and post-migration data.

Business

Post-load validation is a critical step in data migration, ensuring that transferred data is accurate, complete, and functional within the target system.

1. Ensuring Data Integrity
After migration, data must be consistent with its original structure. Post-load validation checks for missing records, incorrect mappings, and formatting errors to prevent discrepancies.
2. Business Continuity
Faulty data can disrupt operations, leading to financial losses and inefficiencies. Validating post-load data ensures that applications function as expected, preventing downtime.
3. Error Detection and Resolution
By validating data post-migration, businesses can detect anomalies early, reducing the cost and effort required for corrections

Completeness

Task	Action
Perform Source-to-Target Comparisons	Validate that migrated data matches source records. Check for discrepancies in numerical values, text fields, and timestamps
Conduct Post-Migration Reconciliation	Go through reports comparing pre- and post-migration data.

Accuracy

Task	Action
Perform Manual Testing	Conduct manual spot-checks for additional assurance.

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
Material Listing and Exclusions is in scope based on data design and any exception requested by business.
There will be 3 SAP instances, one for ROW, one for China and one for CUI only.
For S/4HANA CUI instance, the migration activity will be handled by US based data consultant.

Change log

Version	Published	Changed By
CURRENT (v. 32)	Apr 20, 2026 08:01	LIU-ext, Ekawati
v. 51	Mar 03, 2026 13:55	LIU-ext, Ekawati
v. 50	Feb 27, 2026 07:42	LIU-ext, Ekawati
v. 49	Feb 04, 2026 12:27	LIU-ext, Ekawati
v. 48	Feb 02, 2026 17:41	LIU-ext, Ekawati
v. 47	Feb 02, 2026 08:46	LIU-ext, Ekawati
v. 46	Feb 02, 2026 07:52	LIU-ext, Ekawati
v. 45	Jan 19, 2026 09:57	LIU-ext, Ekawati
v. 44	Dec 11, 2025 16:07	LIU-ext, Ekawati
v. 43	Dec 09, 2025 07:17	LIU-ext, Ekawati

Go to Page History

Workflow history

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

Apr 21, 2026	Actor	Type	Activity	Version
Approved	TAMRAKAR-ext, Pooja	State	changed state to Approved at 6:35 am	v52
Revision under Review	TAMRAKAR-ext, Pooja	State	gave Minor change approval at 6:35 am CR0455- DC logic change
Apr 20, 2026
	LIU-ext, Ekawati	State	changed state to Revision under Review at 8:02 am Updated as per CR0455 - L2C CNV-3003 Distribution channel logic enhancement	v52
Revision in Progress	LIU-ext, Ekawati	State	changed state to Revision in Progress at 8:01 am	v52
From Mar 03, 2026 to Apr 20, 2026
Approved	LIU-ext, Ekawati	Edit	updated the page at 1:55 pm

Workflow history

Space shortcuts

Page tree

CNV-2001 Material Listing and Exclusions

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

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

See also

Change log

Workflow history