| Status |
| |
|---|---|---|
| Owner | ||
| Stakeholders |
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:
- Customer/ Sold-to/ Ship-to sales view migrated as per CNV-3003 Business Partners - Customer (Sales and Service) - FLCU01
- Material sales view migrated as per CNV-2003 Materials - Sales view with sales long text.
- Sales organization is in scope of S/4HANA
- Plant is in scope of S/4HANA
- Material Group is in scope of S/4HANA
- Country (Departure/ Destination) must be within S/4HANA scope
- 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).
20260227-Eka: Refer to CR0279 - Update Conversion Specs to remove mention of CUI System
List of source systems and approximate number of records
20251208 - MDS updated with following:
- Source table: KOTG001 - Customer/ Material and KOTG913 - Sales Organization/ Material/ Customer will not be included for migration (Deleted).
- Source table: KOTG004 - Sales Organization/ Distribution Channel/ Customer/ Material will not be included for migration and replaced with KOTG946 (New table for eCommerce).
- Mapping for source table: KOTG962 - Material/ Destination Country updated from S/4HANA KOTG910 to KOTG907.
- Mapping for source table: KOTG521 - Destination Country/ Region/ Material updated from S/4HANA KOTG902 to KOTG909. Note: the sequence in table PF2 - KOTG521 and S/4HANA - KOTG909 are not the same.
- KOTG521-LAND1 (seq #2) transform to KOTG909-LAND1 (seq #3)
- KOTG521-REGIO (seq #3) transform to KOTG909-REGIO (seq #4)
- KOTG521-MATNR (seq #4) transform to KOTG909-MATNR (seq #2)
- New source table: KOTG945 - Sales Organization/ Distribution Channel/ Material mapped to S/4HANA table KOTG902.
| Source System | Listing/ Exclusions - Condition Type | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records | ||
|---|---|---|---|---|---|---|---|
| WP2 | ZA01 ZB01 - RCS InclusionExclusion | Table: KOTG001KOTG906 Listing/exclusion type - Sales Organization - Customer - Material - Valid to - Valid From | 20,000 | S/4HANA ROW | 20,000 | ||
| WP2 | ZA01 ZB01 - RCS InclusionExclusion | Table: KOTG001KOTG906 Listing/exclusion type - Sales Organization - Customer - Material - Valid to - Valid From | S/4HANA China | ||||
| WP2 | ZA01 ZB01 - RCS InclusionExclusion | Table: KOTG001KOTG908 Listing/exclusion type - Customer Sales Organization - Material Departure country - Valid to - Valid From | 20 | S/4HANA CUIROW | 20 | ||
| WP2 | ZA01 ZB01 - RCS InclusionExclusion | Table: KOTG004KOTG908 Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material Departure country - Valid to - Valid From | S/4HANA ROWChina | ||||
| WP2 | ZA01 ZB01 - RCS InclusionExclusion | Table: KOTG004KOTG909 Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material - Material - Destination Country - Region - Valid to - Valid From | S/4HANA ChinaROW | ||||
| WP2 | ZA01 ZB01 - RCS InclusionExclusion | Table: KOTG004KOTG909 Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material Material - Destination Country - Region - Valid to - Valid From | S/4HANA CUIChina | ||||
| WP2 | ZB01 ZREA - RCS REACH Exclusion | Table: KOTG906KOTG962 Listing/exclusion type - Sales Organization Material - Customer Destination Country - Material - Valid to - Valid From | 20,000 | S/4HANA ROW | 20,000 | ||
| WP2 | ZB01 ZREA - RCS REACH Exclusion | Table: KOTG906KOTG962 Listing/exclusion type - Sales Organization - Customer - Material Material - Destination Country - Valid to - Valid From | 020 | S/4HANA China | 020 | ||
| WP2 | ZB01 ZREA - RCS REACH Exclusion | Table: KOTG906KOTG964 Listing/exclusion type - Sales Organization - Customer Material - Material Destination Country - Valid to - Valid From | S/4HANA CUIROW | ||||
| WP2 | ZB01 ZREA - RCS REACH Exclusion | Table: KOTG908KOTG964 Listing/exclusion type - Sales Organization - Material - Departure country Destination Country - Valid to - Valid From | 200 | S/4HANA ROWChina | 200 | ||
| WP2ZB01 | - RCS ExclusionZE03 - eComm Material/ Customer | Table: KOTG908KOTG945 Listing/exclusion type - Sales Organization - Departure country Distribution Channel - Material - Valid to - Valid From *As at 8-De-2025: only 1 sales organization has data = FRAZ | 7500 | S/4HANA ChinaROW | 0750 | ||
| WP2 | ZE03 - eComm Material/ Customer | Table: KOTG908KOTG945 Listing/exclusion type - Sales Organization - Departure country Distribution Channel - Material - Valid to - Valid From *As at 8-De-2025: only 1 sales organization has data = FRAZ | 0 | S/4HANA CUIChina | 0 | ||
| WP2ZB01 | - RCS ExclusionZE03 - eComm Material/ Customer | Table: KOTG909KOTG946 Listing/exclusion type - Sales Organization - Material Distribution Channel - Destination Country Customer - Region Material - Valid to - Valid From *As at 8-De-2025: only 5 sales organization has data = FRAZ, GB34, IT07, NL05, US05 | 5,000 | S/4HANA ROW | 5,000 | ||
| WP2ZB01 | - RCS ExclusionZE03 - eComm Material/ Customer | Table: KOTG909KOTG946 Listing/exclusion type - Sales Organization - Material Distribution Channel - Destination Country Customer - Region Material - Valid to - Valid From | 5,000 | *As at 8-De-2025: only 5 sales organization has data = FRAZ, GB34, IT07, NL05, US05 | 0 | S/4HANA China | 5,0000 |
| ZB01 EXCL - RCS Exclusion ERP | Table: KOTG909KOTG501 Listing/exclusion type - Material - Destination Country - Region Material Group - Valid to - Valid From | 515,000 | S/4HANA CUIROW | 515,000 | |||
| ZB01 EXCL - RCS Exclusion ERP | Table: KOTG913KOTG501 Listing/exclusion type - Sales Organization Destination Country - Material - Customer Group - Valid to - Valid From | S/4HANA ROWChina | |||||
| ZB01 EXCL - RCS Exclusion ERP | Table: KOTG913KOTG521 Listing/exclusion type - Destination Country - Sales Organization Region - Material - Customer - Valid to - Valid From | S/4HANA ChinaROW | |||||
| ZB01 EXCL - RCS Exclusion ERP | Table: KOTG913KOTG521 Listing/exclusion type - Destination Country - Sales Organization Region - Material - Customer - Valid to - Valid From | S/4HANA CUIChina | |||||
| WP2PF2 | ZREA ZEXC - REACH Exclusion ERP | Table: KOTG962KOTG521 Listing/exclusion type - Material - Destination Country - Region - Material - Valid to - Valid From | 2010 | S/4HANA ROW | 2010 | ||
| WP2PF2 | ZREA ZEXC - REACH Exclusion ERP | Table: KOTG962KOTG521 Listing/exclusion type - Material - Destination Country - Region - Material - Valid to - Valid From | 2010 | S/4HANA China | 2010 | ||
| ZREA EXCL - REACH Exclusion ERP | Table: KOTG962KOTG903 ListingList/exclusion type excl. - Material - Destination Country - Plant - Ship-To Party - Valid to - Valid From | S/4HANA CUIROW | |||||
| WP2PF2 | ZREA EXCL - REACH Exclusion ERP | Table: KOTG964KOTG903 Listing/exclusion type - Sales Organization - Material - Destination Country List/excl. - Material - Plant - Ship-To Party - Valid to - Valid From | 10,000 | S/4HANA ROWChina | 10,000 | ||
| WP2PF2 | ZREA EXCL - REACH Exclusion ERP | Table: KOTG964KOTG904 ListingList/exclusion type - Sales Organization - Material - Destination Country excl. - Material - Plant - Sold-To Party - Valid to - Valid From | 010 | S/4HANA ChinaROW | 010 | ||
| ZREA EXCL - REACH Exclusion ERP | Table: KOTG964KOTG904 Listing/exclusion type - Sales Organization - Material - Destination Country List/excl. - Material - Plant - Sold-To Party - Valid to - Valid From | S/4HANA CUIChina | |||||
| WP2PF2 | ZE03 - eComm Material/ CustomerEXCL - Exclusion ERP | Table: KOTG945KOTG906 Listing/exclusion type - Sales Organization - Distribution Channel - Material - Sales org. - Destination Country - Valid to - Valid From*As at 8-De-2025: only 1 sales organization has data = FRAZ | 75075 | S/4HANA ROW | 75075 | ||
| WP2PF2 | ZE03 - eComm Material/ CustomerEXCL - Exclusion ERP | Table: KOTG945KOTG906 Listing/exclusion type - Sales Organization - Distribution Channel - Material Sales org. - Destination Country - Valid to - Valid From*As at 8-De-2025: only 1 sales organization has data = FRAZ | 020 | S/4HANA China | 020 |
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 S/4HANA instance for Rest of the World (ROW) and one for China and one for CUI.
Following logic to identify the record is for SAP China, CUI or ROW Instance:
- Material Listing and Exclusions with sales organizations in the table in-scope; to be migrated to respective S/4HANA instance.
- Material Listing and Exclusions without sales organization in the table in-scope, e.g. Destination Country/Material Group; to be migrated to all 2 instances (ROW
, CUIand China).
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 | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KOTG004 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory |
| KOTG004 | VKORG | VKORG | Sales Organization | CHAR | 4 | Mandatory |
| KOTG004 | VTWEG | VTWEG | Distribution Channel | CHAR | 2 | Mandatory |
| KOTG004 | KUNNR | KUNNR_V | Customer | CHAR | 10 | Mandatory |
| KOTG004 | MATNR | MATNR | Material | CHAR | 18 | Mandatory |
| KOTG004 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory |
| KOTG004 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory |
| KOTG900 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory |
| KOTG900 | VKORG | VKORG | Sales Organization | CHAR | 4 | Mandatory |
| KOTG900 | KUNNR | KUNNR_V | Customer | CHAR | 10 | Mandatory |
| KOTG900 | MATNR | MATNR | Material | CHAR | 18 | Mandatory |
| KOTG900 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory |
| KOTG900 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory |
| KOTG908 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory |
| KOTG908 | VKORG | VKORG | Sales Organization | CHAR | 4 | Mandatory |
| KOTG908 | ALAND | ALAND | Departure country | CHAR | 3 | Mandatory |
| KOTG908 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory |
| KOTG908 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory |
| KOTG909 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory |
| KOTG909 | MATNR | MATNR | Material | CHAR | 18 | Mandatory |
| KOTG909 | LAND1 | LLAND | Destination Country | CHAR | 3 | Mandatory |
| KOTG909 | REGIO | REGIO | Region | CHAR | 3 | Mandatory |
| KOTG909 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory |
| KOTG909 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory |
KOTG907 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory |
KOTG907 | MATNR | MATNR | Material | CHAR | 18 | Mandatory |
KOTG907 | LAND1 | LLAND | Destination Country | CHAR | 3 | Mandatory |
KOTG907 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory |
KOTG907 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory |
| KOTG905 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory |
| KOTG905 | VKORG | VKORG | Sales Organization | CHAR | 4 | Mandatory |
| KOTG905 | MATNR | MATNR | Material | CHAR | 18 | Mandatory |
| KOTG905 | LAND1 | LLAND | Destination Country | CHAR | 3 | Mandatory |
| KOTG905 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory |
| KOTG905 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory |
| KOTG901 | KSCHL |
Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material - Valid to - Valid From
*As at 8-De-2025: only 5 sales organization has data = FRAZ, GB34, IT07, NL05, US05
Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material - Valid to - Valid From
*As at 8-De-2025: only 5 sales organization has data = FRAZ, GB34, IT07, NL05, US05
Listing/exclusion type - Destination Country - Material Group - Valid to - Valid From
Listing/exclusion type - Destination Country - Material Group - Valid to - Valid From
Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From
Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From
Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From
Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From
List/excl. - Material - Plant - Ship-To Party - Valid to - Valid From
List/excl. - Material - Plant - Ship-To Party - Valid to - Valid From
List/excl. - Material - Plant - Sold-To Party - Valid to - Valid From
List/excl. - Material - Plant - Sold-To Party - Valid to - Valid From
Sales org. - Destination Country - Valid to - Valid From
Sales org. - Destination Country - Valid to - Valid From
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 S/4HANA instance for Rest of the World (ROW) and one for China and one for CUI.
Following logic to identify the record is for SAP China, CUI or ROW Instance:
- Material Listing and Exclusions with sales organizations in the table in-scope; to be migrated to respective S/4HANA instance.
- Material Listing and Exclusions without sales organization in the table in-scope, e.g. Destination Country/Material Group; to be migrated to all 2 instances (ROW
, CUIand China).
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 | Field | Data Element | Field Description | Data Type | Length | Requirement | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||||
| LLAND | Destination Country | CHAR | Mandatory | |||||||
| MATKL | Material Group | CHAR | Mandatory | |||||||
| DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | |||||
| DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | |||||
| KOTG004KOTG902 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | MandatoryKOTG004 | ||||
| KOTG902 |
VKORG | VKORG | Sales Organization | CHAR | 4 | Mandatory | ||||
| KOTG902KOTG004 |
VTWEG | VTWEG | Distribution Channel | CHAR | 2 | Mandatory | ||||
| KOTG004 | KUNNR | KUNNR_V | Customer | CHAR | 10 | Mandatory | ||||
| KOTG902 | KOTG004 | MATNR | MATNR | Material | CHAR | 18 | Mandatory | |||
| KOTG004KOTG902 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG004KOTG902 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG900KOTG903 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG900KOTG903 | VKORGMATNRVKORG | MATNR | Sales OrganizationMaterial | CHAR | 418 | Mandatory | ||||
| KOTG900KOTG903 | KUNNRWERKSKUNNR | WERKS_VD | CustomerPlant | CHAR | 104 | Mandatory | ||||
| KOTG900KOTG903 | MATNRKUNWE | MATNR | KUNWE | Ship-to PartyMaterial | CHAR | 1810 | Mandatory | |||
| KOTG900KOTG903 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG900KOTG903 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG908KOTG904 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG904 | MATNR | MATNR | Material | CHAR | 18 | Mandatory | ||||
| KOTG904 | WERKS | WERKS_D | Plant | KOTG908 | VKORG | VKORG | Sales Organization | CHAR | 4 | Mandatory |
| KOTG908KOTG904 | ALANDKUNAG | ALAND | KUNAG | Sold-to PartyDeparture country | CHAR | 310 | Mandatory | |||
| KOTG908KOTG904 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG908KOTG904 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG909KOTG906 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG909KOTG906 | MATNRVKORGMATNR | VKORGMaterial | Sales Organization | CHAR | 184 | Mandatory | ||||
| KOTG909KOTG906 | LAND1 | LLAND | Destination Country | CHAR | 3 | Mandatory | ||||
| KOTG909 | REGIO | REGIO | Region | CHAR | 3 | Mandatory | ||||
| KOTG906 | KOTG909 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | |||
| KOTG909KOTG906 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
KOTG907 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
KOTG907 | MATNR | MATNR | Material | CHAR | 18 | Mandatory | ||||
KOTG907 | LAND1 | LLAND | Destination Country | CHAR | 3 | Mandatory | ||||
KOTG907 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
KOTG907 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG905 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG905 | VKORG | VKORG | Sales Organization | CHAR | 4 | Mandatory | ||||
| KOTG905 | MATNR | MATNR | Material | CHAR | 18 | Mandatory | ||||
| KOTG905 | LAND1 | LLAND | Destination Country | CHAR | 3 | Mandatory | ||||
| KOTG905 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG905 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG901 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG901 | LAND1 | LLAND | Destination Country | CHAR | 3 | Mandatory | ||||
| KOTG901 | MATKL | MATKL | Material Group | CHAR | 9 | Mandatory | ||||
| KOTG901 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG901 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG902 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG902 |
VKORG |
VKORG |
Sales Organization | CHAR |
4 | Mandatory | ||||
| KOTG902 |
VTWEG |
VTWEG |
Distribution Channel | CHAR |
2 | Mandatory | ||||
| KOTG902 | MATNR | MATNR | Material | CHAR | 18 | Mandatory | ||||
| KOTG902 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG902 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG903 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG903 | MATNR | MATNR | Material | CHAR | 18 | Mandatory | ||||
| KOTG903 | WERKS | WERKS_D | Plant | CHAR | 4 | Mandatory | ||||
| KOTG903 | KUNWE | KUNWE | Ship-to Party | CHAR | 10 | Mandatory | ||||
| KOTG903 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG903 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG904 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG904 | MATNR | MATNR | Material | CHAR | 18 | Mandatory | ||||
| KOTG904 | WERKS | WERKS_D | Plant | CHAR | 4 | Mandatory | ||||
| KOTG904 | KUNAG | KUNAG | Sold-to Party | CHAR | 10 | Mandatory | ||||
| KOTG904 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG904 | DATAB | KODATAB | Valid From | DATS | 8 | Mandatory | ||||
| KOTG906 | KSCHL | KSCHG | Listing/exclusion type | CHAR | 4 | Mandatory | ||||
| KOTG906 | VKORG | VKORG | Sales Organization | CHAR | 4 | Mandatory | ||||
| KOTG906 | LAND1 | LLAND | Destination Country | CHAR | 3 | Mandatory | ||||
| KOTG906 | DATBI | KODATBI | Valid to | DATS | 8 | Mandatory | ||||
| KOTG906 | 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.
Cleansing reports should include/ consider the relevancy rule.
20260202 - Output update based on the Table.
| 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 IF KOTGxxx does not have VKORG, only get flag for deletion at general data (KNA1-LOEVM). | PF2 - KOTG903 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Ship-to Party/ Ship-to Party Name/ Ship-to Party Country/ Flag for deletion at general data level PF2 - KOTG904 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Sold-to Party/ Sold-to Party Name/ Sold-to Party Country/ Flag for deletion at general data level WP2 - KOTG906 and KOTG946 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer/ Customer Name/ Customer Country/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Division/ Division Description/ Company Code/ Company Code Description/ Flag for deletion at general data level/ Flag for deletion at sales area level/ Flag for deletion at company code level/ Customer availability in sales area/ Customer availability in company code | 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 IF KOTGxxx does not have VKORG, only get posting block at general data (KNA1-SPERR). | PF2 - KOTG903 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Ship-to Party/ Ship-to Party Name/ Ship-to Party Country/ Posting block at general data level PF2 - KOTG904 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Sold-to Party/ Sold-to Party Name/ Sold-to Party Country/ Posting block at general data level WP2 - KOTG906 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer/ Customer Name/ Customer Country/ Sales Organization/ Sales Organization Description/ Company Code/ Company Code Description/ Posting block at general data level/ Posting block at company code level/ Customer availability in company code WP2 - KOTG946 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer/ Customer Name/ Customer Country/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Company Code/ Company Code Description/ Posting block at general data level/ Posting block at company code level/ Customer availability in company code | 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: KOTG906 and KOTG946 For PF2 - table: KOTG903 and KOTG904 **Sales organization: IF KOTGxxx does not have VKORG, only get sales block at general data (KNA1-CASSD). | PF2 - KOTG903 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Ship-to Party/ Ship-to Party Name/ Ship-to Party Country/ Sales block at general data level PF2 - KOTG904 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Sold-to Party/ Sold-to Party Name/ Sold-to Party Country/ Sales block at general data level WP2 - KOTG906 and KOTG946 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer/ Customer Name/ Customer Country/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Division/ Division Description/ Sales block at general data level/ Sales block at sales area level/Customer availability in sales area | 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. |
Data Cleansing
All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.
Cleansing reports should include/ consider the relevancy rule.
20260202 - Output update based on the Table.
| 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: KOTG906 and KOTG946 For PF2 - table: KOTG903 and KOTG904 **Company codeSales organization: IF KOTGxxx has does not have VKORG, get TVKO-BUKRS, where TVKO-VKORG = KOTGxxx-VKORGIF KOTGxxx does not have VKORG, only get flag for deletion only get order block at general data (KNA1-AUFSD) OR delivery block at general data (KNA1-LIFSD) OR billing block at general data (KNA1-LOEVMFAKSD). | PF2 - KOTG903 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Ship-to Party/ Ship-to Party Name/ Ship-to Party Country/ Flag for deletion / Order block at general data level/ Order block at general data level description/ Delivery block at general data level/ Delivery block at general data level description/ Billing block at general data level/ Billing block at general data level description PF2 - KOTG904 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Sold-to Party/ Sold-to Party Name/ Sold-to Party Country/ Flag for deletion Order block at general data level WP2 - KOTG906 and KOTG946 / Order block at general data level description/ Delivery block at general data level/ Delivery block at general data level description/ Billing block at general data level/ Billing block at general data level description WP2 - KOTG906 and KOTG946 Source System/ Table/ Table Description/ Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer/ Customer Name/ Customer Country/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Division/ Division Description/ Company Code/ Company Code Description/ Flag for deletion / Order block at general data level/ Order block at general data level description/ Delivery block at general data level/ Delivery block at general data level description/ Billing block at general data level/ Billing block at general data level description/ Flag for deletion Order block at sales area level/ Flag for deletion at company code level/ Customer availability in sales area/ Customer availability in company codeOrder block at sales area level description/ Delivery block at sales area level/ Delivery block at sales area level description/ Billing block at sales area level/ Billing block at sales area level description/ Customer availability in sales area | PF2/ WP2 | ||||||||||||||
| 2001-002005 | C1 | Customer with posting block | 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' Posting block for all company code (KNA1-SPERR) OR posting block at company code level (KNB1-SPERR) is "X" - Yes
For PF2 - table: KOTG903 and KOTG904 | PF2 - KOTG521 PF2 - KOTG903 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ MaterialDestination Country/ Material Destination Country Description/ PlantRegion/ Plant Region Description/ Ship-to Party/ Ship-to Party Name/ Ship-to Party Country/ Posting block at general data levelMaterial/ Material Description/ Flag for Deletion at General Data Level PF2 - KOTG903 and KOTG904 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Sold-to Party/ Sold-to Party Name/ Sold-to Party Country/ Posting block at general data levelFlag for Deletion at General Data Level/ Flag for Deletion at Plant Data Level/ Material Availability in Plant WP2 - KOTG906 and KOTG946WP2 - KOTG906 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Customer/ Customer Name/ Customer Country/ Sales OrganizationMaterial/ Sales Organization Material Description/ Company Code/ Company Code Description/ Posting block at general data level/ Posting block at company code level/ Customer availability in company codeFlag for Deletion at General Data level/ Flag for Deletion at Sales Data Level/ Material availability in Sales Area WP2 - KOTG909 and KOTG962WP2 - KOTG946 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ CustomerMaterial/ Customer Name/ Customer Country/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Company Code/ Company Code Description/ Posting block at general data level/ Posting block at company code level/ Customer availability in company codeMaterial Description/ Flag for Deletion at General Data Level WP2 - KOTG945 and KOTG964 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Material/ Material Description/ Flag for Deletion at General Data level/ Flag for Deletion at Sales Data Level/ Material availability in Sales Area | PF2/ WP2 | |||||||||||||
| 2001-003006 | C1 | Customer with sales block | Material with distribution-chain material status | Cross-distribution-chain material status (MARA-MSTAV) OR Distribution-chain-specific material status (MVKE-VMSTA) is NOT BLANK Sales block for all sales area (KNA1-CASSD) OR sales block at sales area level (KNVV-CASSD) is "X" - Yes
KOTG906, KOTG909, KOTG945, KOTG946, KOTG962 and KOTG964 For PF2 - table: KOTG903 and KOTG904KOTG521 Cross-distribution-chain material status (MARA-MSTAV) For PF2 - table: KOTG903 and KOTG904 20260303-Eka: KNVV table needs to be joined to check corresponding customer, sales organization and distribution channel against material sales area for KOTG906 and KOTG946 | PF2 - KOTG521 PF2 - KOTG903 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ MaterialDestination Country/ Material Destination Country Description/ PlantRegion/ Plant Region Description/ Ship-to Party/ Ship-to Party Name/ Ship-to Party Country/ Sales block at general data level/ Material/ Material Description/ Cross Distribution Chain Material Status/ Cross Distribution Chain Material Status Description/ Cross Distribution Chain Material Status Valid From PF2 - KOTG903 and PF2 - KOTG904 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Cross Distribution Chain Material Status/ Cross Distribution Chain Material Status Description/ Cross Distribution Chain Material Status Valid From/ Cross Plant Material Status/ Cross Plant Material Status Description/ Sold-to Party/ Sold-to Party Name/ Sold-to Party Country/ Sales block at general data level/ Cross Plant Material Status Valid From/ Plant Specific Material Status/ Plant Specific Material Status Description/ Plant Specific Material Status Valid From/ Material Availability in Plant WP2 - KOTG906 and KOTG946 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer/ Customer Name/ Customer Country/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Division/ Division Description/ Sales block at general data level/ Sales block at sales area level/Customer availability in sales area | PF2/ WP2 | 2001-004 | C1 | Customer with order block, delivery block or billing block | Customer/ Customer Name/ Customer Country/ Material/ Material Description/ Cross Distribution Chain Material Status/ Cross Distribution Chain Material Status Description/ Cross Distribution Chain Material Status Valid From/ Distribution Chain Specific Material Status/ Distribution Chain Specific Material Status Description/ Distribution Chain Specific Material Status Valid From/ Material availability in Sales Area WP2 - KOTG909 and KOTG962 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Cross Distribution Chain Material Status/ Cross Distribution Chain Material Status Description/ Cross Distribution Chain Material Status Valid From WP2 - KOTG945 and KOTG964 Source System | 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: KOTG906 and KOTG946 For PF2 - table: KOTG903 and KOTG904 **Sales organization: IF KOTGxxx does not have VKORG, only get order block at general data (KNA1-AUFSD) OR delivery block at general data (KNA1-LIFSD) OR billing block at general data (KNA1-FAKSD) | PF2 - KOTG903 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Material/ Material Description/ Plant/ Plant Description/ Ship-to Party/ Ship-to Party Name/ Ship-to Party Country/ Order block at general data level/ Order block at general data level description/ Delivery block at general data level/ Delivery block at general data level description/ Billing block at general data level/ Billing block at general data level descriptionCross Distribution Chain Material Status/ Cross Distribution Chain Material Status Description/ Cross Distribution Chain Material Status Valid From/ Distribution Chain Specific Material Status/ Distribution Chain Specific Material Status Description/ Distribution Chain Specific Material Status Valid From/ Material availability in Sales Area | PF2/ WP2 | ||||||
| 2001-007 | C1 | Duplicate Material Listing and Exclusions records by distribution channel | Table: KOTG945 with the same sales organization and same material but different distribution channel and KOTG946 with the same sales organization, same customer and same material but different distribution channel (re: transformation rule) | KOTG945PF2 - KOTG904 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ MaterialSales Organization/ Material Sales Organization Description/ PlantDistribution Channel/ Plant Distribution Channel Description/ Sold-to Party/ Sold-to Party Name/ Sold-to Party Country/ Order block at general data level/ Order block at general data level description/ Delivery block at general data level/ Delivery block at general data level description/ Billing block at general data level/ Billing block at general data level descriptionMaterial/ Material Description/ Valid From/ Valid To WP2 - KOTG906 and KOTG946 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Customer/ Customer Name/ Customer Country/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Division/ Division Description/ Order block at general data level/ Order block at general data level description/ Delivery block at general data level/ Delivery block at general data level description/ Billing block at general data level/ Billing block at general data level description/ Order block at sales area level/ Order block at sales area level description/ Delivery block at sales area level/ Delivery block at sales area level description/ Billing block at sales area level/ Billing block at sales area level description/ Customer availability in sales area | PF2/ WP2 | Customer/ Customer Name/ Customer Country/ Material/ Material Description/ Valid From/ Valid To | WP2 | ||||||||||||
| 2001-008 | C1 | Customer in Listing and Exclusions without sales view | Table: KOTG903 and KOTG904 Customer does not have sales view for sales organization assigned to plant in Listing and Exclusions table: KNVV-KUNNR = KOTG903/ KOTG904-KUNNR and KNVV-VKORG = TVKWZ-VKORG (sales organization in scope), where TVKWZ-WERKS = KOTG903/ KOTG904-WERKS but not found. | KOTG903 | 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: KOTG906, KOTG909, KOTG945, KOTG946, KOTG962 and KOTG964For PF2 - table: KOTG521 **Sales organization: IF KOTGxxx does not have VKORG, only get flag for deletion at client level (MARA-LVORM) For PF2 - table: KOTG903 and KOTG904 PF2 - KOTG521 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Destination CountryMaterial/ Destination Country Material Description/ RegionPlant/ Region Plant Description/ Material/ Material Description/ Flag for Deletion at General Data LevelShip-to Party/ Ship-to Party Name/ Ship-to Party Country PF2 - KOTG903 and KOTG904 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description/ Flag for Deletion at General Data Level/ Flag for Deletion at Plant Data Level/ Material Availability in PlantWP2 - KOTG906 and KOTG946Sold-to Party/ Sold-to Party Name/ Sold-to Party Country | PF2 | ||||||||||
| 2001-009 | C1 | Material in Listing and Exclusions without sales view | Table: KOTG903 and KOTG904 Material does not have sales view for sales organization assigned to plant in Listing and Exclusions table: MVKE-MATNR = KOTG903/ KOTG904-MATNR and MVKE-VKORG = TVKWZ-VKORG (sales organization in scope), where TVKWZ-WERKS = KOTG903/ KOTG904-WERKS but not found. | Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Customer/ Customer Name/ Customer Country/ Material/ Material Description/ Flag for Deletion at General Data level/ Flag for Deletion at Sales Data Level/ Material availability in Sales AreaPlant/ Plant Description | PF2 | ||||||||||||||
| 2001-010 | C1 | Data in listing and exclusions but NO sales document | KOTG903
KOTG904
| Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Flag for Deletion at General Data Level WP2 - KOTG945 and KOTG964 Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Sales Organization/ Sales Organization Description/ Distribution Channel/ Distribution Channel Description/ Material/ Material Description/ Flag for Deletion at General Data level/ Flag for Deletion at Sales Data Level/ Material availability in Sales Area | PF2/ WP2 | 2001-006 | C1 | Material with distribution-chain material status | PF2/ WP2 | 2001-007 | C1 | Duplicate Material Listing and Exclusions records by distribution channel | Table: KOTG945 with the same sales organization and same material but different distribution channel and KOTG946 with the same sales organization, same customer and same material but different distribution channel (re: transformation rule) | WP2 | 2001-008 | C1 | Customer in Listing and Exclusions without sales view | Table: KOTG903 and KOTG904 Customer does not have sales view for sales organization assigned to plant in Listing and Exclusions table: KNVV-KUNNR = KOTG903/ KOTG904-KUNNR and KNVV-VKORG = TVKWZ-VKORG (sales organization in scope), where TVKWZ-WERKS = KOTG903/ KOTG904-WERKS but not found. | PF2 |
| 2001-009 | C1 | Material in Listing and Exclusions without sales view | Table: KOTG903 and KOTG904 Material does not have sales view for sales organization assigned to plant in Listing and Exclusions table: MVKE-MATNR = KOTG903/ KOTG904-MATNR and MVKE-VKORG = TVKWZ-VKORG (sales organization in scope), where TVKWZ-WERKS = KOTG903/ KOTG904-WERKS but not found. | Source System/ Table/ Table Description/ Material Listing or Exclusion Type/ Material Listing or Exclusion Type Description/ Material/ Material Description/ Plant/ Plant Description | PF2 | ||||||||||||||
| 2001-010 | C1 | Data in listing and exclusions but NO sales document | KOTG903
KOTG904
| ALL fields for each table. | PF2 |
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.
| Plant/ Plant Description/ Sold-to Party or Ship-to Party/ Sold-to Party or Ship-to Party Name/ Sold-to Party or Ship-to Party Country/ Valid From/ Valid To | PF2 |
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/AExtraction
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:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- 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. | 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
| Selection Ref 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)
DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| N/A | ||
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Source System Availability
| Syensqo IT |
| 2 | Data Structure
| Syniti |
| 3 | Referential Integrity
| Syniti |
| 4 | Extraction Methodology
| Syniti |
| 5 | Performance and Scalability Considerations
| Syniti |
| 6 | Security and Compliance
| 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.
- 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 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 2. Process by Source System 3. Extract data from all tables below. Filter #2: Filter #3: 4. For fields related to Customer/ Sold-to Party/ Ship-to Party, Material Master, Departure/ Destination Country, Listing/ Exclusions Type, Sales Organization, Distribution Channel, Plant Material Group and Region, include records only if the corresponding migrated target value exists in the target system. | ||||||||||
| 2001-006 | WP2 | KOTG946 | KSCHL | Listing/exclusion type | S/4HANA | KOTG004 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping |
| 2001-007 | WP2 | KOTG946 | VKORG | Sales Organization | S/4HANA | KOTG004 | VKORG | Sales Organization | MAP_VKORG | Mapping |
| 2001-008 | WP2 | KOTG946 | VTWEG | Distribution Channel | S/4HANA | KOTG004 | VTWEG | Distribution Channel | Rule | RULE: => Listing & Exclusions table should have records for all distribution channel for the migrated customer. 2. IF Listing and Exclusions table have Material: get the migrated Material Distribution Channel for respective Sales Organization (CNV-2003). => Listing & Exclusions table should have records for all distribution channel for the migrated material. 3. IF Listing and Exclusions table have Customer and Material: get the Customer (CNV-3003) and Material (CNV-2003) Distribution Channel for respective Sales Organization. A. Customer created for distribution channel = 10 and 20; and Material only distribution channel = 10. Listing and Exclusions table should have records for distribution channel 10 only. B. Customer created for distribution channel = 10 and 20; and Material also created for distribution channel = 10 and 20. Listing and Exclusions table should have records for distribution channel 10 and 20. C. Customer created for distribution channel = 20; and Material created for distribution channel = 10 and 20. Listing and Exclusions table should have records for distribution channel 20 only. |
| 2001-009 | WP2 | KOTG946 | KUNNR | Customer | S/4HANA | KOTG004 | ||||
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.
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/AExtraction
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:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- 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
- Define the data objects (tables such as KOTGxxx) to be extracted.
- Establish business rules for data selection.
- Determine the tools and technologies used.
- Define data filtering criteria to exclude irrelevant records.
- Assign responsibilities for extraction monitoring.
- Document dependencies on other migration tasks.
Selection Screen
Data Collection Template (DCT)
DCT Rules
Extraction Dependencies
Source System Availability
- Ensure that the source database or application is accessible.
- Confirm that necessary credentials and permissions are granted
Syensqo IT
Data Structure
- Identify relationships between tables, views, and stored procedures.
Syniti
Referential Integrity
- Ensure dependent records are extracted together.
Syniti
Extraction Methodology
- Define whether extraction is full, incremental, or delta-based.
- Establish batch processing schedules for large datasets.
Syniti
Performance and Scalability Considerations
- Optimize extraction queries to prevent system overload.
- Ensure network bandwidth supports data transfer volumes.
Syniti
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.
- 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 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
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 | ||||||||||||||||||||||
| 2001-006 | WP2 |
KOTG946 | KSCHL | Listing/exclusion type | S/4HANA | KOTG004 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-007 | WP2 |
KOTG946 | VKORG | Sales Organization | S/4HANA | KOTG004 | VKORG | Sales Organization | MAP_VKORG | Mapping | 2001-008 | WP2 |
KOTG946 | VTWEG | Distribution Channel | S/4HANA | KOTG004 | VTWEG | Distribution Channel | Rule | RULE:||
| 2001-009 | WP2 |
KOTG946 | KUNNR | Customer | S/4HANA | KOTG004 | KUNNR | Customer | MAP_KUNNR | Mapping | ||||||||||||
| 2001-010 | WP2 |
KOTG946 | MATNR | Material | S/4HANA | KOTG004 | MATNR | Material | MAP_MATNR | Mapping | 2001-011 | WP2 |
KOTG946 | DATBI | Valid to | S/4HANA | KOTG004 | DATBI | Valid to | Copy | 2001-012 | WP2 |
KOTG946 | DATAB | Valid From | S/4HANA | KOTG004 | DATAB | Valid From | Copy |
| 2001-013 | WP2 | KOTG906 | KSCHL | Listing/exclusion type | S/4HANA | KOTG900 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-014 | WP2 | KOTG906 | VKORG | Sales Organization | S/4HANA | KOTG900 | VKORG | Sales Organization | MAP_VKORG | Mapping | ||||||||||||
| 2001-015 | WP2 | KOTG906 | KUNNR | Customer | S/4HANA | KOTG900 | KUNNR | Customer | MAP_KUNNR | Mapping | ||||||||||||
| 2001-016010 | WP2 | KOTG906 KOTG946 | MATNR | Material | S/4HANA | KOTG900KOTG004 | MATNR | Material | MAP_MATNR | Mapping | ||||||||||||
| 2001-017011 | WP2 | KOTG906 KOTG946 | DATBI | Valid to | S/4HANA | KOTG900KOTG004 | DATBI | Valid to | Copy | |||||||||||||
| 2001-018012 | WP2 | KOTG906 KOTG946 | DATAB | Valid From | S/4HANA | KOTG900KOTG004 | DATAB | Valid From | Copy | |||||||||||||
| 2001-019013 | WP2 | KOTG908KOTG906 | KSCHL | Listing/exclusion type | S/4HANA | KOTG908KOTG900 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-020014 | WP2 | KOTG908KOTG906 | VKORG | Sales Organization | S/4HANA | KOTG908KOTG900 | VKORG | Sales Organization | MAP_VKORG | Mapping | ||||||||||||
| 2001-015 | WP2 | KOTG906 | KUNNR | Customer | S/4HANA | KOTG900 | KUNNR | Customer | MAP_KUNNR | Mapping | ||||||||||||
| 2001-016021 | WP2 | KOTG908KOTG906 | ALANDMATNR | Departure countryMaterial | S/4HANA | KOTG900 | MATNRKOTG908 | ALAND | Departure country | Material | MAP_MATNR | MappingCopy | ||||||||||
| 2001-022017 | WP2 | KOTG908KOTG906 | DATBI | Valid to | S/4HANA | KOTG908KOTG900 | DATBI | Valid to | Copy | |||||||||||||
| 2001-023018 | WP2 | KOTG908KOTG906 | DATAB | Valid From | S/4HANA | KOTG908KOTG900 | DATAB | Valid From | Copy | |||||||||||||
| 2001-024019 | WP2 | KOTG909KOTG908 | KSCHL | Listing/exclusion type | S/4HANA | KOTG909KOTG908 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-025020 | WP2 | KOTG909KOTG908 | MATNRVKORG | MaterialSales Organization | S/4HANA | KOTG909KOTG908 | MATNRVKORG | MaterialSales Organization | MAP_MATNRVKORG | Mapping | ||||||||||||
| 2001-026021 | WP2 | KOTG909KOTG908 | LAND1ALAND | Destination CountryDeparture country | S/4HANA | KOTG909KOTG908 | LAND1ALAND | Destination CountryDeparture country | Copy | |||||||||||||
| 2001-027022 | WP2 | KOTG909 | REGIO | Region | S/4HANA | KOTG909 | REGIO | Region | MAP_REGION | Mapping | KOTG908 | 2001-028 | WP2 | KOTG909 | DATBI | Valid to | S/4HANA | KOTG909KOTG908 | DATBI | Valid to | Copy | |
| 2001-029023 | WP2 | KOTG909KOTG908 | DATAB | Valid From | S/4HANA | KOTG909KOTG908 | DATAB | Valid From | Copy | |||||||||||||
| 2001-030024 | WP2 | KSCHL | Listing/exclusion type | S/4HANA | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||||
| 2001-031025 | WP2 | S/4HANA | MAP_VKORGMATNR | Mapping | ||||||||||||||||||
| 2001-032026 | WP2 | S/4HANA | Destination Country | Copy | ||||||||||||||||||
| 2001-033027 | WP2 | S/4HANA | MAP_KUNNRREGION | Mapping | ||||||||||||||||||
| 2001-034028 | WP2 | DATBI | Valid to | S/4HANA | DATBI | Valid to | Copy | |||||||||||||||
| 2001-035029 | WP2 | DATAB | Valid From | S/4HANA | DATAB | Valid From | Copy | |||||||||||||||
| 2001-036 | WP2 | KOTG962 | KSCHL | Listing/exclusion type | S/4HANA | KOTG907 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-037 | WP2 | KOTG962 | MATNR | Material | S/4HANA | KOTG907 | MATNR | Material | MAP_MATNR | Mapping | ||||||||||||
| 2001-038 | WP2 | KOTG962 | LAND1 | Destination Country | S/4HANA |
KOTG907 | LAND1 | Destination Country | Copy | |||||||||||||
| 2001-039 | WP2 | KOTG962 | DATBI | Valid to | S/4HANA | KOTG907 | DATBI | Valid to | Copy | |||||||||||||
| 2001-040 | WP2 | KOTG962 | DATAB | Valid From | S/4HANA | KOTG907 | DATAB | Valid From | Copy | |||||||||||||
| 2001-041 | WP2 | KOTG964 | KSCHL | Listing/exclusion type | S/4HANA | KOTG905 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-042 | WP2 | KOTG964 | VKORG | Sales Organization | S/4HANA | KOTG905 | VKORG | Sales Organization | MAP_VKORG | Mapping | ||||||||||||
| 2001-043 | WP2 | KOTG964 | MATNR | Material | S/4HANA | KOTG905 | MATNR | Material | MAP_MATNR | Mapping | ||||||||||||
| 2001-044 | WP2 | KOTG964 | LAND1 | Destination Country | S/4HANA | KOTG905 | LAND1 | Destination Country | Copy | |||||||||||||
| 2001-045 | WP2 | KOTG964 | DATBI | Valid to | S/4HANA | KOTG905 | DATBI | Valid to | Copy | |||||||||||||
| 2001-046 | WP2 | KOTG964 | DATAB | Valid From | S/4HANA | KOTG905 | DATAB | Valid From | Copy | |||||||||||||
| 2001-047 | PF2 | KOTG501 | KSCHL | Listing/exclusion type | S/4HANA | KOTG901 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-048 | PF2 | KOTG501 | LAND1 | Destination Country | S/4HANA | KOTG901 | LAND1 | Destination Country | Copy | |||||||||||||
| 2001-049 | PF2 | KOTG501 | MATKL | Material Group | S/4HANA | KOTG901 | MATKL | Material Group | MAP_MATKL | Mapping | ||||||||||||
| 2001-050 | PF2 | KOTG501 | DATBI | Valid to | S/4HANA | KOTG901 | DATBI | Valid to | Copy | |||||||||||||
| 2001-051 | PF2 | KOTG501 | DATAB | Valid From | S/4HANA | KOTG901 | DATAB | Valid From | Copy | |||||||||||||
| 2001-052 | WP2 | KOTG945 | KSCHL | Listing/exclusion type | S/4HANA | KOTG902 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-053 | WP2 |
KOTG945 | VKORG |
Sales Organization | S/4HANA | KOTG902 |
VKORG |
Sales Organization | MAP_VKORG | Mapping | ||||||||||||
| 2001-054 | WP2 | KOTG945 |
VTWEG |
Distribution Channel | S/4HANA | KOTG902 | VTWEG |
Distribution Channel |
|
| Rule for Distribution Channel, as per #2001-008 above. | |||||||||||
| 2001-055 |
WP2 | KOTG945 | MATNR | Material | S/4HANA | KOTG902 | MATNR | Material | MAP_MATNR | Mapping | ||||||||||||
| 2001-056 | WP2 |
KOTG945 | DATBI | Valid to | S/4HANA | KOTG902 | DATBI | Valid to | Copy | |||||||||||||
| 2001-057 | WP2 | KOTG945 | DATAB | Valid From | S/4HANA | KOTG902 | DATAB | Valid From | Copy | |||||||||||||
| 2001-058 | PF2 | KOTG903 | KSCHL | Listing/exclusion type | S/4HANA | KOTG903 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-059 | PF2 | KOTG903 | MATNR | Material | S/4HANA | KOTG903 | MATNR | Material | MAP_MATNR | Mapping | ||||||||||||
| 2001-060 | PF2 | KOTG903 | WERKS | Plant | S/4HANA | KOTG903 | WERKS | Plant | MAP_WERKS | Mapping | ||||||||||||
| 2001-061 | PF2 | KOTG903 | KUNWE | Ship-to Party | S/4HANA | KOTG903 | KUNWE | Ship-to Party | MAP_KUNNR | Mapping | ||||||||||||
| 2001-062 | PF2 | KOTG903 | DATBI | Valid to | S/4HANA | KOTG903 | DATBI | Valid to | Copy | |||||||||||||
| 2001-063 | PF2 | KOTG903 | DATAB | Valid From | S/4HANA | KOTG903 | DATAB | Valid From | Copy | |||||||||||||
| 2001-064 | PF2 | KOTG904 | KSCHL | Listing/exclusion type | S/4HANA | KOTG904 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-065 | PF2 | KOTG904 | MATNR | Material | S/4HANA | KOTG904 | MATNR | Material | MAP_MATNR | Mapping | ||||||||||||
| 2001-066 | PF2 | KOTG904 | WERKS | Plant | S/4HANA | KOTG904 | WERKS | Plant | MAP_WERKS | Mapping | ||||||||||||
| 2001-067 | PF2 | KOTG904 | KUNAG | Sold-to Party | S/4HANA | KOTG904 | KUNAG | Sold-to Party | MAP_KUNNR | Mapping | ||||||||||||
| 2001-068 | PF2 | KOTG904 | DATBI | Valid to | S/4HANA | KOTG904 | DATBI | Valid to | Copy | |||||||||||||
| 2001-069 | PF2 | KOTG904 | DATAB | Valid From | S/4HANA | KOTG904 | DATAB | Valid From | Copy | |||||||||||||
| 2001-070 | PF2 | KOTG906 | KSCHL | Listing/exclusion type | S/4HANA | KOTG906 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-071 | PF2 | KOTG906 | VKORG | Sales Organization | S/4HANA | KOTG906 | VKORG | Sales Organization | MAP_VKORG | Mapping | ||||||||||||
| 2001-072 | PF2 | KOTG906 | LAND1 | Destination Country | S/4HANA | KOTG906 | LAND1 | Destination Country | Copy | |||||||||||||
| 2001-073 | PF2 | KOTG906 | DATBI | Valid to | S/4HANA | KOTG906 | DATBI | Valid to | Copy | |||||||||||||
| 2001-074 | PF2 | KOTG906 | DATAB | Valid From | S/4HANA | KOTG906 | DATAB | Valid From | Copy | |||||||||||||
| 2001-075 | PF2 | KOTG521 | KSCHL | Listing/exclusion type | S/4HANA | KOTG909 | KSCHL | Listing/exclusion type | MAP_KSCHL_KOTG-V | Mapping | ||||||||||||
| 2001-076 | PF2 | KOTG521 | LAND1 | Destination Country | S/4HANA | KOTG909 | LAND1 | Destination Country | Copy Sequence in table PF2 - KOTG521 and S/4HANA - KOTG909 are not the same. KOTG521-LAND1 (seq #2) transform to KOTG909-LAND1 (seq #3) KOTG521-REGIO (seq #3) transform to KOTG909-REGIO (seq #4) KOTG521-MATNR (seq #4) transform to KOTG909-MATNR (seq #2) | |||||||||||||
| 2001-077 | PF2 | KOTG521 | REGIO | Region | S/4HANA | KOTG909 | REGIO | Region | MAP_REGION | Mapping Sequence in table PF2 - KOTG521 and S/4HANA - KOTG909 are not the same. KOTG521-LAND1 (seq #2) transform to KOTG909-LAND1 (seq #3) KOTG521-REGIO (seq #3) transform to KOTG909-REGIO (seq #4) KOTG521-MATNR (seq #4) transform to KOTG909-MATNR (seq #2) | ||||||||||||
| 2001-078 | PF2 | KOTG521 | MATNR | Material | S/4HANA | KOTG909 | MATNR | Material | MAP_MATNR | Mapping Sequence in table PF2 - KOTG521 and S/4HANA - KOTG909 are not the same. KOTG521-LAND1 (seq #2) transform to KOTG909-LAND1 (seq #3) KOTG521-REGIO (seq #3) transform to KOTG909-REGIO (seq #4) KOTG521-MATNR (seq #4) transform to KOTG909-MATNR (seq #2) | ||||||||||||
| 2001-079 | PF2 | KOTG521 | DATBI | Valid to | S/4HANA | KOTG909 | DATBI | Valid to | Copy | |||||||||||||
| 2001-080 | PF2 | KOTG521 | DATAB | Valid From | S/4HANA | KOTG909 | 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 |
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 | 1. Verify row counts in the source databases. 2. Identify missing or duplicated records. |
| Validate the mandatory fields | Validate there is value for all the mandatory fields |
| Validate Primary Keys and Unique Constraints | 1. Check for duplicate or missing primary key values, i.e. if there is same sales organization, distribution channel, customer number and material number. 2. Ensure unique constraints are maintained. |
| Test Referential Integrity | Confirm dependent records exist in related tables, such as customer master, material master, plant, etc. S/4HANA. |
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 | 1. Compare field values across systems 2. Validate data formats and structures |
Business
The following pre-load validations will be performed by the Business.Completeness
| Task | Action |
|---|---|
| Compare Data Counts | 1. Verify row counts in the source databases. 2. 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:
1. Execute the automated data load into target system using load tool or produce the load file as per format in Transformation Rule section if the load must be done manually.
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Confirm readiness of final approved data sets for each ECC source system WP2 and PF2 | Business / Functional Team |
| 2 | Validate transformation rules and mappings in Syniti tool | Data Team (L2C-Data) |
| 3 | Generate target-ready load files based on S/4HANA material listing and exclusions table format | Data Team (Syniti) |
| 4 | Review and approve load files before execution | Business / Functional Team |
| 5 | Execute the upload program in the S/4HANA system | Data Load Team |
| 6 | Monitor load progress and capture load statistics (records loaded, errors, duplicates, etc.) | Data Team (Syniti) / Technical Team |
| 7 | Extract loaded data from S/4HANA for post-load validation | Data Team (Syniti) |
| 8 | Perform post-load data validation (compare target data with source/ approved files) for all loaded material listing and exclusions | Data Team (L2C-Data) |
| 9 | Log and resolve any data load errors or mismatches identified during validation | Data Team (Syniti and L2C-Data) + Functional Team |
| 10 | Obtain business sign-off on successful load and validation | Business Team |
| 11 | Archive load logs, error reports, and validation results for audit/compliance | Data Team (L2C-Data) / Data Team (Syniti) / PMO |
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 configuration and data objects in the S/4 HANA. The configuration needs to be transported into the respective system first.
Configuration
| Item # | Configuration Item |
|---|---|
1 | Sales Organization |
2 | Distribution Channel |
3 | Plant |
4 | Listing/ Exclusion Table |
5 | Listing/ Exclusion Access Sequence |
6 | Listing/ Exclusion Type |
7 | Listing/ Exclusion Procedure |
8 | Sales Document Type |
9 | Activate Listing/ Exclusion by Sales Document Type |
10 | Material Group |
11 | Country Code (Departure and Destination Country) |
| 12 | Region |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
3003 | Business Partners - Customer (Sales and Service) - FLCU01 |
2003 | Materials - Sales view with sales long text |
| 2010 | Materials - General Plant Data / S.Loc Data |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
| Configuration/ Data Transformation | The value XXX for field XXX doesn't exist | 1. Check the mapping/ conversion is done properly in the loading file 2. Validate the target value is configured/ transported in the target system 3. Reach out to functional team to validate the configuration |
| Data Error | The Customer Master or Material Master were not defined | Validate the Customer Master or Material Master relevancy rule and sales area extension for the newly mapped distribution channel; maintain the customer master or material master if it is in migration scope. For Material Master if the Plant are maintained in the Material Listing/ Exclusions table; also validate if the Material Master Plant view are created. |
Post-Load Validation
Project Team
The following post-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| Validate Record count | Validate all tables has the same records as the loading file |
| Perform Source-to-Target Comparisons | 1. Validate that migrated data matches source records count. 2. Check for discrepancies in numerical values, text fields, and timestamps. |
Accuracy
| Task | Action |
|---|---|
| Conduct Post-Migration Reconciliation | Generate reports comparing pre- and post-migration data; and the field value are identical. |
| Perform Manual Testing | Pick up a few random sample for each table, e.g. Sales Organization, Distribution Channel, Customer, Material, Country, Region, Material Group, Plant and run t-code: VB03 to validate the Material Listing/ Exclusions were migrated correctly and can be displayed without any errors. |
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 count. |
| Conduct Post-Migration Reconciliation | Go through post-load validation reports comparing pre- and post-migration data. |
Accuracy
| Task | Action |
|---|---|
| Perform Manual Testing | Conduct manual spot-checks for additional assurance. |
Key Assumptions
- Material Listing and Exclusions 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 2 SAP instances, one for ROW and one for China
and one for CUI only.
See also
Change log
| Change History | ||
|---|---|---|
|
Workflow history
| Workflow Report | ||||||
|---|---|---|---|---|---|---|
|
