| Status | Approved |
|---|---|
| Owner | |
| Stakeholders |
Purpose
This document outlines the approach for converting Material Listing and Exclusion data into SAP S/4HANA.
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:
- Material/Destination Country/Region
- Sales Organization/Departure Country
- Sales Organization/Material/Destination Country
- Material/Destination Country
- Destination Country/Region/Material
- Destination Country/Material Group
- Material/Plant/Sold-to Party
- Material/Plant/Ship-to Party
- Sales Organization/Destination Country
(Note: Pending confirmation via MDS)
The objective of this conversion is to migrate active and relevant Material Listing and Exclusion records from the current ECC system to S/4HANA. This will be achieved using transformation logic within the Syniti platform, which supports data migration and transformation processes. The finalized data will then be loaded into the S/4HANA system using standard SAP methods such as Data Migration Cockpit, IDOCs, BAPIs, or direct table loads, depending on what is most appropriate.
Conversion Scope
The scope of this document covers the approach for converting active Material Listing and Exclusions from Legacy Source Systems into S/4HANA following the Material Listing and Exclusions Master Data Design Standard.
From the current system landscape, Material Master data exists separately in the legacy systems (PF2 and WP2), with potential discrepancies in both systems. Harmonization and validation are required to ensure accurate and consolidated data in S/4HANA. While PF2 and WP2 serve as source systems, extensive 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: Final relevancy rule pending MDS
- All active Material Listing or Material Exclusions, where "valid from date up to 1 year after S/4HANA Go-Live date" AND "valid to date is after valid from date AND beyond S/4HANA Go-Live date" AND each of the below as per table combination:
- 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 in scope for S/4HANA
- Distribution Channel (pending MDS if this will be in-scope for Material Listing and Exclusions and how to map/ map to which field in S/4HANA)
- Plant in scope of S/4HANA
- Material Group in scope of S/4HANA
- Country in scope of S/4HANA (pending MDS, e.g. XK - Kosovo available in WP2 but not in Sandpit)
- Region in scope of S/4HANA (pending MDS, if all Region in used will be configured in S/4HANA)
The data from legacy system excludes:
- Invalid Material Listing or Material Exclusions; none of the above
List of source systems and approximate number of records (Not including table with 0 records. Pending MDS for table in scope)
| 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 | 50 | S/4 HANA | 50 |
WP2 | ZA01 - RCS Inclusion | Table: KOTG004 Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material - Valid to - Valid From | 20 | S/4 HANA | 20 |
WP2 | ZB01 - RCS Exclusion | Table: KOTG906 Listing/exclusion type - Sales Organization - Customer - Material - Valid to - Valid From | 100,000 | S/4 HANA | 100,000 |
WP2 | ZB01 - RCS Exclusion | Table: KOTG908 Listing/exclusion type - Sales Organization - Departure country - Valid to - Valid From | 20 | S/4 HANA | 20 |
WP2 | ZB01 - RCS Exclusion | Table: KOTG909 Listing/exclusion type - Material - Destination Country - Region - Valid to - Valid From | 2,500 | S/4 HANA | 2,500 |
WP2 | ZB01 - RCS Exclusion | Table: KOTG913 Listing/exclusion type - Sales Organization - Material - Customer - Valid to - Valid From | 300 | S/4 HANA | 300 |
WP2 | ZREA - REACH Exclusion | Table: KOTG962 Listing/exclusion type - Material - Destination Country - Valid to - Valid From | 200 | S/4 HANA | 200 |
WP2 | ZREA - REACH Exclusion | Table: KOTG964 Listing/exclusion type - Sales Organization - Material - Destination Country - Valid to - Valid From | 70,000 | S/4 HANA | 70,000 |
PF2 | EXCL - Exclusion ERP | Table: KOTG501 Listing/exclusion type - Destination Country - Material Group - Valid to - Valid From | 15,500 | S/4 HANA | 15,500 |
PF2 | EXCL - Exclusion ERP | Table: KOTG521 Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From | 15 | S/4 HANA | 15 |
PF2 | ZEXC - Exclusion ERP | Table: KOTG521 Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From | 15 | S/4 HANA | 15 |
PF2 | EXCL - Exclusion ERP | Table: KOTG903 List/excl. - Material - Plant - Ship-To Party - Valid to - Valid From | 10 | S/4 HANA | 10 |
PF2 | EXCL - Exclusion ERP | Table: KOTG904 List/excl. - Material - Plant - Sold-To Party - Valid to - Valid From | 10 | S/4 HANA | 10 |
PF2 | EXCL - Exclusion ERP | Table: KOTG906 Sales org. - Destination Country - Valid to - Valid From | 75 | S/4 HANA | 75 |
Additional Information
Multi-language Requirement
Not applicable
Document Management
None identified. The conversion scope is limited to the migration of Material Listing and Exclusions condition data records. No document attachments, images, or supporting files are included.
Legal Requirement
As per US Department of Defence (DOD) a Cybersecurity Maturity Model Certification/ CMMC 2.0 is a mandatory certification for all contractors handling Controlled Unclassified Information (CUI) and Federal Contract Information (FCI). CUI includes sensitive technical data (e.g., design specs, system info) related to U.S. military and space applications. The Composites Business handles CUI and is therefore within CMMC scope. Without certification, the business risks disqualification from existing and future DoD programs.
It is mandatory to implement CMMC-compliant systems and processes to for all the organizations that are dealing with CUI. Therefore, there will be one SAP instance specifically for CUI related entities.
Special Requirements
Due to legal and compliance requirement, there will be one SAP instance for Rest Of the World (ROW), one for China and one for CUI.
- To identify the record is for SAP China, CUI or ROW Instance, it will use below logic (pending MDS & CR0081 approval).
- 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.
One Sales Organization per GBU
As elaborated in KDD060 - Sales Enterprise Structure, in the S/4Hana design, one sales organization will be mapped to one GBU. Therefore, it is possible that one sales organization in legacy system is mapped to multiple sales organization in the S/4HANA. When such scenario happens, one record of material listing and exclusions will be split into multiple records based on the mapping (pending MDS - if table fields cannot be used to determine the GBU then will be created for both split sales organization).
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. (pending MDS).
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KOTG001_WP2 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG001_WP2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG004_WP2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG906_WP2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG908_WP2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG909_WP2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG913_WP2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG962_WP2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG964_WP2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG501_PF2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG521_PF2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG903_PF2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG904_PF2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | MANDT | MANDT | Client | CLNT | 3 | Internal |
| KOTG906_PF2 | KAPPL | KAPPL | Application | CHAR | 2 | Internal |
| 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 | C-1 | Remove obsolete customer | Customer in table KOTG001, KOTG004, KOTG903, KOTG904, KOTG906, KOTG913 AND Customer in the sales organization in scope Where it has flagged for deletion at General OR Sales view | List of customer obsolete record for Data cleanser to set valid to date to before S/4HANA go-live date | PF2/ WP2 |
| 2001-002 | C-1 | Remove obsolete material | Material in table KOTG001, KOTG004, KOTG521, KOTG903, KOTG904, KOTG906, KOTG909, KOTG913, KOTG962, KOTG964 AND Material in the sales organization in scope Where it has flagged for deletion at Basic OR Sales view | List of material obsolete record for Data cleanser to set valid to date to before S/4HANA go-live date | PF2/ WP2 |
| 2001-003 |
|
|
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 (i.e. WP2/PF2) periodically. 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. Check Data Migration Cockpit and decide the load type and update the diagram below.
Data Privacy and Sensitivity
Not applicable.Extraction
Extract data from a source 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 |
|---|---|---|
| Extraction Scope Definition | - Identify the source systems and databases involved. - Define the data objects (tables, fields, records) to be extracted. - Establish business rules for data selection. | Syniti / LTC Data team |
| Extraction Methodology | - Specify the extraction approach (full, incremental, or delta extraction). - Determine the tools and technologies used. - Define data filtering criteria to exclude irrelevant records. | Syniti |
| Extraction Execution Plan | - Establish execution timelines and batch processing schedules. - Assign responsibilities for extraction monitoring. - Document dependencies on other migration tasks. | Syniti |
| Data Quality and Validation | - Define error handling mechanisms for extraction failures. | Syniti |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Not applicable | ||||
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 |
|---|---|---|
| Pending MDS and number of data in source system | ||
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 |
| 7 | Data cleansing of legacy Material Listing and Exclusions must be completed. If standardization within the DCT begins using relevant data from PF2 and WP2 before the cleansing is finalized, it is understood that the business will take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT. | Business |
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 | Transformation Scope Definition - Identify the source and target data structures. - Define business rules for data standardization. - Establish data cleansing requirements to remove inconsistencies. | Data Team |
2 | Data Mapping and Standardization - Align source fields with target fields. - Ensure unit consistency (e.g., currency, measurement units) | Data Team |
3 | Business Rule Application - Implement data enrichment/collection if applicable - Apply conditional transformations based on predefined logic/business rules | Data Team |
4 | Transformation Execution Plan - Define batch processing schedules. - Assign responsibilities for monitoring execution. - Establish error-handling mechanisms | Syniti |
Transformation Rules
| Rule # | Source System | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 2001-001 | WP2 | KOTG001, KOTG004, KOTG906, KOTG913 | KUNNR | Customer | S/4HANA | KUNNR | Customer | Value Mapping: Customer Number | |
| 2001-002 | WP2 | KOTG908 | ALAND | Departure country | S/4HANA | ALAND | Departure country | Value Mapping: Country Key | |
| 2001-003 | PF2/ WP2 | KOTG501, KOTG521, KOTG906, KOTG909, KOTG962, KOTG964 | LAND1 | Destination Country | S/4HANA | LAND1 | Destination Country | Value Mapping: Country Key | |
| 2001-004 | WP2 | KOTG004 | VTWEG | Distribution Channel | S/4HANA | VTWEG | Distribution Channel | Value Mapping: Distribution Channel Pending MDS: with mapping table OR without mapping table and use logic: if has distribution channel (1 or x) - change/ update with Domestic and Export only. | |
| 2001-005 | PF2/ WP2 | KOTG001, KOTG004, KOTG501, KOTG521, KOTG903, KOTG904, KOTG906, KOTG908, KOTG909, KOTG913, KOTG962, KOTG964 | KSCHL | Listing/exclusion type | S/4HANA | KSCHL | Listing/ Exclusion type | Value Mapping: TBD As SD pricing, tax, cross selling, material substitution, etc. are using the same field (KSCHL) | |
| 2001-006 | PF2/ WP2 | KOTG001, KOTG004, KOTG521, KOTG903, KOTG904, KOTG906, KOTG909, KOTG913, KOTG962, KOTG964 | MATNR | Material | S/4HANA | MATNR | Material | Value Mapping: Material Master | |
| 2001-007 | PF2 | KOTG501 | MATKL | Material Group | S/4HANA | MATKL | Material Group | Value Mapping: Material Group | |
| 2001-008 | PF2 | KOTG903, KOTG904 | WERKS | Plant | S/4HANA | WERKS | Plant | Value Mapping: Plant | |
| 2001-009 | PF2/ WP2 | KOTG521, KOTG909 | REGIO | Region | S/4HANA | REGIO | Region | Value Mapping: Region | |
| 2001-010 | PF2/ WP2 | KOTG004, KOTG906, KOTG908, KOTG913, KOTG964 | VKORG | Sales Organization | S/4HANA | VKORG | Sales Organization | Value Mapping: Sales Organization | |
| 2001-011 | PF2 | KOTG903 | KUNWE | Ship-to Party | S/4HANA | KUNWE | Ship-to Party | Value Mapping: Customer Number (AND have partner function = SH) | |
| 2001-012 | PF2 | KOTG904 | KUNAG | Sold-to Party | S/4HANA | KUNAG | Sold-to Party | Value Mapping: Customer Number (AND have partner function = SP) | |
| 2001-013 | PF2/ WP2 | KOTG001, KOTG004, KOTG501, KOTG521, KOTG903, KOTG904, KOTG906, KOTG908, KOTG909, KOTG913, KOTG962, KOTG964 | DATAB | Valid From | S/4HANA | DATAB | Valid From | Direct Mapping | |
| 2001-014 | PF2/ WP2 | KOTG001, KOTG004, KOTG501, KOTG521, KOTG903, KOTG904, KOTG906, KOTG908, KOTG909, KOTG913, KOTG962, KOTG964 | DATBI | Valid to | S/4HANA | DATBI | Valid to | Direct Mapping |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
| Customer Number | KUNNR: Old to New Customer No. For ALL Customers, incl.: KUNNR Customer, KUNAG Sold-to and KUNWE Ship-to |
| Country Key | LAND1: Old Country Code to New Country code For ALAND Departure Country and LAND1 Destination Country |
| Distribution Channel | VTWEG: Old to New Distribution Channel Pending MDS: with mapping table OR without mapping table and use logic: if has distribution channel (1 or x) - change/ update with Domestic and Export only. |
| Listing/ Exclusion Type | TBD As SD pricing, tax, cross selling, material substitution, etc. are using the same field (KSCHL) |
| Material Master | MATNR: Old to New Material No. |
| Material Group | MATKL: Old Material Group to New Material Group |
| Plant | Enterprise Structure of Old Plant to New Plant |
| Region | REGIO: Old to New Region |
| Sales Organization | VKORG: Old to New Sales Organization |
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 |
|
Validate the mandatory fields | Validate there is value for all the mandatory fields |
Validate Primary Keys and Unique Constraints |
|
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 |
|
Business
The following pre-load validations will be performed by the Business.Completeness
| Task | Action |
|---|---|
Compare Data Count |
|
| 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
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 |
|
Configuration | There is mandatory field XXX missing |
|
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 |
|
Accuracy
| Task | Action |
|---|---|
Execute Sample Queries and Reports |
|
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 |
|
| 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.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||