You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Status

  Approved

Owner

LIU-ext, Ekawati 

Stakeholders

Purpose

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

Material Listing and Exclusion allows you to control which materials a customer can or cannot buy. You can create a list of materials that a specific customer is allowed to purchase (listing), or a list of materials that a customer is not allowed to purchase (exclusion). This feature helps manage sales restrictions based on customer-specific requirements. 

In SAP S/4HANA, the structure and usage of material listing and exclusions are remain consistent with combination of customer/ material or sales organization/ distribution channel/ customer material.

In SAP ECC, aside from material listing and exclusions standard structure of customer/ material or sales organization/ distribution channel/ customer material; there are few additional table combination available, e.g. 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, etc. (pending MDS)

This conversion aims to migrate active and relevant material listing and exclusions 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 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

  1. 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:
    1. Customer/ Sold-to/ Ship-to sales view migrated as per CNV-3003 Business Partners - Customer (Sales and Service) - FLCU01 
    2. Material sales view migrated as per CNV-2003 Materials - Sales view with sales long text.
    3. Sales organization in scope for S/4HANA
    4. 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)
    5. Plant in scope of S/4HANA
    6. Material Group in scope of S/4HANA
    7. Country in scope of S/4HANA (pending MDS, e.g. XK - Kosovo available in WP2 but not in Sandpit)
    8. 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:

  1. 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)

SourceCondition TypeScope

Source Approx No. of Records

Target SystemTarget 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). 

  1. The Material Listing and Material Exclusions have sales organizations in-scope as per link HERE - sheet: MAP_VKORG (link to be updated once confirm)
  2. 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)
  3. 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). 


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

TableFieldData ElementField DescriptionData TypeLengthRequirement
KOTG001_WP2MANDTMANDTClientCLNT3Internal
KOTG001_WP2KAPPLKAPPLApplicationCHAR2Internal
KOTG001_WP2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG001_WP2KUNNRKUNNR_VCustomerCHAR10Mandatory
KOTG001_WP2MATNRMATNRMaterialCHAR18Mandatory
KOTG001_WP2DATBIKODATBIValid toDATS8Mandatory
KOTG001_WP2DATABKODATABValid FromDATS8Mandatory
KOTG004_WP2MANDTMANDTClientCLNT3Internal
KOTG004_WP2KAPPLKAPPLApplicationCHAR2Internal
KOTG004_WP2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG004_WP2VKORGVKORGSales OrganizationCHAR4Mandatory
KOTG004_WP2VTWEGVTWEGDistribution ChannelCHAR2Mandatory
KOTG004_WP2KUNNRKUNNR_VCustomerCHAR10Mandatory
KOTG004_WP2MATNRMATNRMaterialCHAR18Mandatory
KOTG004_WP2DATBIKODATBIValid toDATS8Mandatory
KOTG004_WP2DATABKODATABValid FromDATS8Mandatory
KOTG906_WP2MANDTMANDTClientCLNT3Internal
KOTG906_WP2KAPPLKAPPLApplicationCHAR2Internal
KOTG906_WP2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG906_WP2VKORGVKORGSales OrganizationCHAR4Mandatory
KOTG906_WP2KUNNRKUNNR_VCustomerCHAR10Mandatory
KOTG906_WP2MATNRMATNRMaterialCHAR18Mandatory
KOTG906_WP2DATBIKODATBIValid toDATS8Mandatory
KOTG906_WP2DATABKODATABValid FromDATS8Mandatory
KOTG908_WP2MANDTMANDTClientCLNT3Internal
KOTG908_WP2KAPPLKAPPLApplicationCHAR2Internal
KOTG908_WP2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG908_WP2VKORGVKORGSales OrganizationCHAR4Mandatory
KOTG908_WP2ALANDALANDDeparture countryCHAR3Mandatory
KOTG908_WP2DATBIKODATBIValid toDATS8Mandatory
KOTG908_WP2DATABKODATABValid FromDATS8Mandatory
KOTG909_WP2MANDTMANDTClientCLNT3Internal
KOTG909_WP2KAPPLKAPPLApplicationCHAR2Internal
KOTG909_WP2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG909_WP2MATNRMATNRMaterialCHAR18Mandatory
KOTG909_WP2LAND1LLANDDestination CountryCHAR3Mandatory
KOTG909_WP2REGIOREGIORegionCHAR3Mandatory
KOTG909_WP2DATBIKODATBIValid toDATS8Mandatory
KOTG909_WP2DATABKODATABValid FromDATS8Mandatory
KOTG913_WP2MANDTMANDTClientCLNT3Internal
KOTG913_WP2KAPPLKAPPLApplicationCHAR2Internal
KOTG913_WP2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG913_WP2VKORGVKORGSales OrganizationCHAR4Mandatory
KOTG913_WP2MATNRMATNRMaterialCHAR18Mandatory
KOTG913_WP2KUNNRKUNNR_VCustomerCHAR10Mandatory
KOTG913_WP2DATBIKODATBIValid toDATS8Mandatory
KOTG913_WP2DATABKODATABValid FromDATS8Mandatory
KOTG962_WP2MANDTMANDTClientCLNT3Internal
KOTG962_WP2KAPPLKAPPLApplicationCHAR2Internal
KOTG962_WP2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG962_WP2MATNRMATNRMaterialCHAR18Mandatory
KOTG962_WP2LAND1LLANDDestination CountryCHAR3Mandatory
KOTG962_WP2DATBIKODATBIValid toDATS8Mandatory
KOTG962_WP2DATABKODATABValid FromDATS8Mandatory
KOTG964_WP2MANDTMANDTClientCLNT3Internal
KOTG964_WP2KAPPLKAPPLApplicationCHAR2Internal
KOTG964_WP2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG964_WP2VKORGVKORGSales OrganizationCHAR4Mandatory
KOTG964_WP2MATNRMATNRMaterialCHAR18Mandatory
KOTG964_WP2LAND1LLANDDestination CountryCHAR3Mandatory
KOTG964_WP2DATBIKODATBIValid toDATS8Mandatory
KOTG964_WP2DATABKODATABValid FromDATS8Mandatory
KOTG501_PF2MANDTMANDTClientCLNT3Internal
KOTG501_PF2KAPPLKAPPLApplicationCHAR2Internal
KOTG501_PF2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG501_PF2LAND1LLANDDestination CountryCHAR3Mandatory
KOTG501_PF2MATKLMATKLMaterial GroupCHAR9Mandatory
KOTG501_PF2DATBIKODATBIValid toDATS8Mandatory
KOTG501_PF2DATABKODATABValid FromDATS8Mandatory
KOTG521_PF2MANDTMANDTClientCLNT3Internal
KOTG521_PF2KAPPLKAPPLApplicationCHAR2Internal
KOTG521_PF2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG521_PF2LAND1LLANDDestination CountryCHAR3Mandatory
KOTG521_PF2REGIOREGIORegionCHAR3Mandatory
KOTG521_PF2MATNRMATNRMaterialCHAR18Mandatory
KOTG521_PF2DATBIKODATBIValid toDATS8Mandatory
KOTG521_PF2DATABKODATABValid FromDATS8Mandatory
KOTG903_PF2MANDTMANDTClientCLNT3Internal
KOTG903_PF2KAPPLKAPPLApplicationCHAR2Internal
KOTG903_PF2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG903_PF2MATNRMATNRMaterialCHAR18Mandatory
KOTG903_PF2WERKSWERKS_DPlantCHAR4Mandatory
KOTG903_PF2KUNWEKUNWEShip-to PartyCHAR10Mandatory
KOTG903_PF2DATBIKODATBIValid toDATS8Mandatory
KOTG903_PF2DATABKODATABValid FromDATS8Mandatory
KOTG904_PF2MANDTMANDTClientCLNT3Internal
KOTG904_PF2KAPPLKAPPLApplicationCHAR2Internal
KOTG904_PF2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG904_PF2MATNRMATNRMaterialCHAR18Mandatory
KOTG904_PF2WERKSWERKS_DPlantCHAR4Mandatory
KOTG904_PF2KUNAGKUNAGSold-to PartyCHAR10Mandatory
KOTG904_PF2DATBIKODATBIValid toDATS8Mandatory
KOTG904_PF2DATABKODATABValid FromDATS8Mandatory
KOTG906_PF2MANDTMANDTClientCLNT3Internal
KOTG906_PF2KAPPLKAPPLApplicationCHAR2Internal
KOTG906_PF2KSCHLKSCHGListing/exclusion typeCHAR4Mandatory
KOTG906_PF2VKORGVKORGSales OrganizationCHAR4Mandatory
KOTG906_PF2LAND1LLANDDestination CountryCHAR3Mandatory
KOTG906_PF2DATBIKODATBIValid toDATS8Mandatory
KOTG906_PF2DATABKODATABValid FromDATS8Mandatory



Data Cleansing

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

IDCriticalityError Message/Report DescriptionRuleOutputSource System
2001-001

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 datePF2/ WP2
2001-002

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 datePF2/ WP2


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. 


Data Privacy and Sensitivity

Not applicable.


Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

  1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
    1. Perform full data extraction from relevant tables in the source system(s).
    2. Perform extraction through the application layer.
    3. Only if Syniti Migrate cannot connect to the source, data is loaded to the repository from the provided source system extract/ report.
  2. 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 DescriptionTeam 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 ScreenParameter NameSelection TypeRequirementValue 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 NameField DescriptionRule


Pending MDS and number of data in source system









Extraction Dependencies

Item #Step DescriptionTeam Responsible
1

Source System Availability

  • Ensure that the source database or application is accessible.
  • Confirm that necessary credentials and permissions are granted

Syensqo IT

2

Data Structure

  • Identify relationships between tables, views, and stored procedures.

Syniti

3

Referential Integrity

  • Ensure dependent records are extracted together.

Syniti

4

Extraction Methodology

  • Define whether extraction is full, incremental, or delta-based.
  • Establish batch processing schedules for large datasets.

Syniti

5

Performance and Scalability Considerations

  • Optimize extraction queries to prevent system overload.
  • Ensure network bandwidth supports data transfer volumes.

Syniti

6

Security and Compliance

  • Adhere to regulatory standards for sensitive information if applicable

Syniti

7

Data cleansing of legacy Material Master - Sales View with sales long text data 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:

  1. Perform value mapping and data transformation rules.
    1. Legacy values are mapped to the to-be values (this could include a default value)
    2. Values are transformed according to the rules defined in Syniti Migrate
  2. 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 DescriptionTeam 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 systemCondition TypeSource TableSource Key CombinationTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
2001-001WP2ZB01906Listing/exclusion type - Sales Organization - Customer - Material - Valid to - Valid FromS/4HANA



2001-002WP2ZB01913Listing/exclusion type - Sales Organization - Material - Customer - Valid to - Valid FromS/4HANA



2001-003WP2ZB01909Listing/exclusion type - Material - Destination Country - Region - Valid to - Valid FromS/4HANA



2001-004WP2ZB01908Listing/exclusion type - Sales Organization - Departure country - Valid to - Valid FromS/4HANA



2001-005WP2ZA01004Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material - Valid to - Valid FromS/4HANA



2001-006WP2ZA01001Listing/exclusion type - Customer - Material - Valid to - Valid FromS/4HANA



2001-007WP2ZREA964Listing/exclusion type - Sales Organization - Material - Destination Country - Valid to - Valid FromS/4HANA



2001-008WP2ZREA962Listing/exclusion type - Material - Destination Country - Valid to - Valid FromS/4HANA



2001-009PF2EXCL501Listing/exclusion type - Destination Country - Material Group - Valid to - Valid FromS/4HANA



2001-010PF2EXCL521Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid FromS/4HANA



2001-011PF2EXCL903List/excl. - Material - Plant - Ship-To Party - Valid to - Valid FromS/4HANA



2001-012PF2EXCL904List/excl. - Material - Plant - Sold-To Party - Valid to - Valid FromS/4HANA



2001-013PF2EXCL906Sales org. - Destination Country - Valid to - Valid FromS/4HANA



2001-014PF2ZEXC521Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid FromS/4HANA



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

Transformation Mapping

Mapping Table NameMapping Table Description

MAP_VKORG

Sales Organization Mapping Table

MAP_VTWEG

Distribution Channel Mapping Table

Pending MDS if this will be used

MAP_WERKS

Plant Mapping Table

MAP_MATKL

Material Group Mapping Table

MAP_ALAND

Country Mapping Table

For Departure Country and Destination Country

MAP_MATNR

Material Mapping Table

MAP_REGIO

Region Mapping Table

MAP_KUNNR

Customer Mapping Table

Covers mapping for ALL customers, incl.: KUNAG Sold-to and KUNWE Ship-to

MAP_KSCHL

Listing/exclusion type Mapping Table

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam 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

TaskAction

Compare Data Counts

  1. Verify row counts between source and target 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.
  2. Ensure unique constraints are maintained.

Test Referential Integrity

Confirm dependent records exist in related tables


Accuracy

TaskAction

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

TaskAction

Compare Data Count

  1. Verify row counts between source and target databases.
  2. Identify missing or duplicated records.
Review populated templates for missing or incorrect valuesUse checklists to verify completeness and correctness before submission



Accuracy

TaskAction

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 product the load file 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 DescriptionTeam 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 TypeError DescriptionAction 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 function team to validate the configuration

Configuration

There is mandatory field XXX missing

  1. Validate MDS if the fields are set as mandatory
  2. Validate if there is value in the pre-loading file
  3. Validate if the configuration for the mandatory fields are done properly


Post-Load Validation

Project Team

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

Completeness

TaskAction

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

  1. Validate that migrated data matches source records.
  2. Check for discrepancies in numerical values, text fields, and timestamps

Accuracy

TaskAction

Execute Sample Queries and Reports

  1. Run queries to validate business logic.
  2. Generate reports to compare expected vs. actual results

Conduct Post-Migration Reconciliation

Generate reports comparing pre- and post-migration data.


Business

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

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


Completeness

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



Accuracy

TaskAction

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

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

Go to Page History

Workflow history

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

  • No labels