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

Compare with Current View Page History

« Previous Version 12 Next »

Status

  Approved

Owner

LIU-ext, Ekawati 

StakeholdersCIRULE, Anita

Purpose

The purpose of this document is to define the data conversion approach to create Customer Material Information Records (CMIR) in S/4 HANA.

Customer material info records (CMIRs) are used to store specific information about a material from a customer's perspective. This information helps in streamlining sales order processing and ensuring accurate order fulfilment. CMIRs link a customer's material number and description to the corresponding SAP material number, allowing for efficient order creation and data consistency. 

This conversion aims to migrate active and relevant customer material information 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 Customer Material Information Records (CMIR) from Legacy Source Systems into S/4HANA following the Customer Material Information Records (CMIR) Master Data Design Standard: DD-FUN-050 Master Data Standard_1036-Customer Material Information Records(CMIR).

From the current system landscape, Customer Material Information Records (CMIR) 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: 

  1. All active Customer Material Information Records (CMIR), where: 

    1. Customer sales view migrated as per CNV-3003 Business Partners - Customer (Sales and Service) - FLCU01
    2. AND Material sales view migrated as per CNV-2003 Materials - Sales view with sales long text.
    3. AND Sales organization is in scope of S/4HANA
    4. AND Distribution channel is in scope of S/4HANA
    5. OR Plant is in scope of S/4HANA (this is optional field; in ECC not all data have this maintained)
  2. For records selected in point #1 above; TEXT will be migrated if the Text ID and the language are included in the transformation mapping table.


List of source systems and approximate number of records: 
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WP2

Customer Material Info Records, table: KNMT

26,000

S/4HANA ROW

26,000

PF2

Customer Material Info Records, table: KNMT

10,000

S/4HANA ROW

10,000

WP2Customer Material Info Records, table: KNMT5,000S/4HANA China5,000
PF2Customer Material Info Records, table: KNMT500S/4HANA China500
WP2Customer Material Info Records, table: KNMT

51,000

S/4HANA CUI

51,000

PF2Customer Material Info Records, table: KNMTN/AS/4HANA CUIN/A
WP2Customer Material Info Records, Text, table: STXH, text ID: 00012,000S/4HANA ROW2,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90104,000S/4HANA ROW4,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 901110,000S/4HANA ROW10,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90128,000S/4HANA ROW8,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90136,000S/4HANA ROW6,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90162,000S/4HANA ROW2,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90281,000S/4HANA ROW1,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 9029500S/4HANA ROW500
WP2Customer Material Info Records, Text, table: STXH, text ID: 9030100S/4HANA ROW100
WP2Customer Material Info Records, Text, table: STXH, text ID: 90324,000S/4HANA ROW4,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90344,000S/4HANA ROW4,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 905150S/4HANA ROW50
WP2Customer Material Info Records, Text, table: STXH, text ID: 9053200S/4HANA ROW200
WP2Customer Material Info Records, Text, table: STXH, text ID: 9054200S/4HANA ROW200
WP2Customer Material Info Records, Text, table: STXH, text ID: 905650S/4HANA ROW50
WP2Customer Material Info Records, Text, table: STXH, text ID: 905750S/4HANA ROW50
PF2Customer Material Info Records, Text, table: STXH, text ID: Z51010S/4HANA ROW10
PF2Customer Material Info Records, Text, table: STXH, text ID: Z51520S/4HANA ROW20
PF2Customer Material Info Records, Text, table: STXH, text ID: Z54010S/4HANA ROW10
PF2Customer Material Info Records, Text, table: STXH, text ID: Z55030S/4HANA ROW30
PF2Customer Material Info Records, Text, table: STXH, text ID: Z57010S/4HANA ROW10
PF2Customer Material Info Records, Text, table: STXH, text ID: Z60020S/4HANA ROW20
PF2Customer Material Info Records, Text, table: STXH, text ID: Z61050S/4HANA ROW50
PF2Customer Material Info Records, Text, table: STXH, text ID: Z63010S/4HANA ROW10
PF2Customer Material Info Records, Text, table: STXH, text ID: Z65010S/4HANA ROW10
PF2Customer Material Info Records, Text, table: STXH, text ID: Z67010S/4HANA ROW10
PF2Customer Material Info Records, Text, table: STXH, text ID: Z68010S/4HANA ROW10
PF2Customer Material Info Records, Text, table: STXH, text ID: Z95050S/4HANA ROW50
WP2Customer Material Info Records, Text, table: STXH, text ID: 00012,000S/4HANA China2,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 901010S/4HANA China10
WP2Customer Material Info Records, Text, table: STXH, text ID: 9011500S/4HANA China500
WP2Customer Material Info Records, Text, table: STXH, text ID: 90122,000S/4HANA China2,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90132,000S/4HANA China2,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90162,000S/4HANA China2,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 9028500S/4HANA China500
WP2Customer Material Info Records, Text, table: STXH, text ID: 902950S/4HANA China50
WP2Customer Material Info Records, Text, table: STXH, text ID: 903010S/4HANA China10
WP2Customer Material Info Records, Text, table: STXH, text ID: 9032500S/4HANA China500
WP2Customer Material Info Records, Text, table: STXH, text ID: 9034500S/4HANA China500
WP2Customer Material Info Records, Text, table: STXH, text ID: 000150S/4HANA CUI50
WP2Customer Material Info Records, Text, table: STXH, text ID: 9010500S/4HANA CUI500
WP2Customer Material Info Records, Text, table: STXH, text ID: 90113,000S/4HANA CUI3,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 90122,000S/4HANA CUI2,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 9013100S/4HANA CUI100
WP2Customer Material Info Records, Text, table: STXH, text ID: 90162,000S/4HANA CUI2,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 902850S/4HANA CUI50
WP2Customer Material Info Records, Text, table: STXH, text ID: 90298,000S/4HANA CUI8,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 903010S/4HANA CUI10
WP2Customer Material Info Records, Text, table: STXH, text ID: 90321,000S/4HANA CUI1,000
WP2Customer Material Info Records, Text, table: STXH, text ID: 9034500S/4HANA CUI500
WP2Customer Material Info Records, Text, table: STXH, text ID: 905110S/4HANA CUI10
WP2Customer Material Info Records, Text, table: STXH, text ID: 905310S/4HANA CUI10
WP2Customer Material Info Records, Text, table: STXH, text ID: 905410S/4HANA CUI10
WP2Customer Material Info Records, Text, table: STXH, text ID: 905510S/4HANA CUI10
WP2Customer Material Info Records, Text, table: STXH, text ID: 905610S/4HANA CUI10
WP2Customer Material Info Records, Text, table: STXH, text ID: 905710S/4HANA CUI10

Additional Information

Multi-language Requirement

As per MDS, Text are only migrated for the valid/ approved language.

Document Management

N/A

Legal Requirement

N/A

Special Requirements

Due to compliance requirement, there will be one SAP instance for Rest of the World (ROW), one for China and one for CUI. Based on the sales organization the cross selling records will be migrated to respective SAP instances.

  


Target Design

Customer Material Information Records (CMIR) Data strictly adheres to the Master Data Standard. The complete information of the tables and key fields that hold the Customer Material Information Records (CMIR) information follows the Master Data Standard document.

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
KNMTVKORGVKORGSales OrganizationCHAR4Mandatory
KNMTVTWEGVTWEGDistribution ChannelCHAR2Mandatory
KNMTKUNNRKUNNR_VCustomerCHAR10Mandatory
KNMTMATNRMATNRMaterialCHAR40Mandatory
KNMTSORTLSORTLSearch termCHAR10Optional
KNMTKDMATMATNR_KUCustomer MaterialCHAR35Optional
KNMTPOSTXKDPTXCustomer DescriptionCHAR40Optional
KNMTLPRIOLPRIODelivery PriorityNUMC2Optional
KNMTMINLFMINLFMinimum Delivery QtyQUAN13Optional
KNMTKZTLFKZTLFPart.dlv./itemCHAR1Optional
KNMTANTLFANTLFMax.Part.DeliveriesDEC1Optional
KNMTUNTTOUNTTOUnderdel. ToleranceDEC3Optional
KNMTUEBTOUEBTOOverdeliv. ToleranceDEC3Optional
KNMTUEBTKUEBTK_VUnlimited ToleranceCHAR1Optional
KNMTWERKSWERKS_EXTPlantCHAR4Optional
KNMTRDPRFRDPRFRounding ProfileCHAR4Optional
KNMTMEGRUMEGRUUnit of Measure GrpCHAR4Optional
KNMTVWPOSVWPOSItem UsageCHAR4Optional
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10Optional
STXHTDNAMETDOBNAMENameCHAR70Optional
STXHTDIDTDIDText IDCHAR4Optional
STXHTDSPRASSPRASLanguage KeyLANG1Optional


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

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

Source System/ Customer No./ Customer Name/ Country/ Company Code/ Company Code Name/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Division/ Division Name/ Flag for deletion for all area level/ Flag for deletion at company code level/ Flag for deletion at sales area level

PF2/ WP2

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

Source System/ Customer No./ Customer Name/ Country/ Company Code/ Company Code Name/ Posting block for all company code/ Posting block at company code level

PF2/ WP2

1036-003

C1Customer with sales blockSales block for all sales area (KNA1-CASSD) OR sales block at sales area level (KNVV-CASSD) is "X" - YesSource System/ Customer No./ Customer Name/ Country/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Division/ Division Name/ Sales block for all sales area/ Sales block at sales area levelPF2/ WP2
1036-004C1Customer 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.

Source System/ Customer No./ Customer Name/ Country/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Division/ Division Name/ Order block for all sales area (code + description)/ Order block at sales area level (code + description)/ Delivery block for all sales area (code + description)/ Delivery block at sales area level (code + description)/ Billing block for all sales area (code + description)/ Billing block at sales area level (code + description)PF2/ WP2
1036-005C1Material 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 

Source System/ Material No./ Material Description/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Flag for deletion at client level/ Flag for deletion at distribution chain levelPF2/ WP2
1036-006C1Material with distribution-chain material status

Cross-distribution-chain material status (MARA-MSTAV) OR Distribution-chain-specific material status (MVKE-VMSTA) is NOT BLANK 

Source System/ Material No./ Material Description/ Sales Organization/ Sales Organization Name/ Distribution Channel/ Distribution Channel Name/ Cross-distribution-chain material status code and the description/ Distribution-chain-specific material status code and the descriptionPF2/ WP2

How to clean: Customer invalid - Data cleanser to delete all materials in the CMIR, material invalid - Data cleanser to delete the invalid material 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, i.e. Syensqo ECC system WP2 and PF2. The extracted data is then staged for transformation.


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


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

Data Privacy and Sensitivity

N/A


Extraction

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

  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
1036-001- Identify the source systems (WP2 and PF2) and databases involved.
- Define the data objects (tables such as KNMT, STXH, function module: read_text for respective data from STXH, fields, records) to be extracted.
- Establish business rules for data selection.		Syniti / LTC Data team
1036-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
1036-003- Establish execution timelines and batch processing schedules.
- Assign responsibilities for extraction monitoring.
- Document dependencies on other migration tasks.		Syniti
1036-004- Define error handling mechanisms for extraction failures.Syniti


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set

Sales OrganizationMultipleValid Sales organization for extractionIn-Scope Sales Organizations
















Data Collection Template (DCT)

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

DCT Rules

Field NameField DescriptionRule
N/A










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


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
1Identify target S/4HANA fields and determine applicable legacy source fields from ECC system (PF2/ WP2).Functional Team (L2C) + Data Team (L2C)
2Map legacy field values to S/4HANA target values (including field-level mapping and technical names)Data Team (L2C), Data Team (Syniti)
3Define value mapping rules for fields requiring standardization or harmonization across the source systemsFunctional Team (L2C) + Data Team (L2C)
4Identify and agree on default values where legacy data is incomplete or inconsistentBusiness Team + Functional Team (L2C)
5Configure transformation rules in Syniti Migrate Data Team (Syniti), Data Team (L2C)
6Review transformation logic and mappings with Business for confirmationBusiness Team + Functional Team (L2C)
7Perform initial transformation run and generate draft target-ready datasetData Team (Syniti)
8Review draft target-ready data for structure and completenessData Team (L2C), Functional Team (L2C)
9Share transformed data with Business for Pre-load ValidationBusiness Team
10Incorporate feedback from Business and refine mappings or transformation logic as neededData Team (L2C)
11Finalize and approve transformed data as Target Ready Load FileBusiness + Functional (L2C) + Data Team (L2C)
12Handover final file to Load Team or trigger the load via Syniti Load WorkbenchData Team (Syniti), Data Load Team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































Transformation Mapping

Mapping Table NameMapping Table Description

MAP_VKORG

Sales Organization Mapping Table

MAP_VTWEG

Distribution Channel Mapping Table

Syniti to provide Sales Report for the last 3 years for sales organization/ customer/ material with plant & ship-to country to determine the distribution channel 

MAP_WERKS

Plant Mapping Table

WERKS - Plant

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

MAP_MATNR

Material Mapping Table

MAP_KUNNR

Customer Mapping Table

Covers mapping for ALL customers, incl.:

KUNAG Sold-to 

KUNWE Ship-to

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 / US Based Consultant for SAP CUI instance

2

Referential Integrity

- Ensure dependent records are transformed together or in advance

Syniti / US Based Consultant for SAP CUI instance

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 / US Based Consultant for SAP CUI instance

5

Logging and Error Handling

- Maintain detailed logs of transformation activities.

- Define error-handling procedures for failed transformations

Syniti / US Based Consultant for SAP CUI instance


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 Counts
  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
1Confirm readiness of final approved data sets for each ECC source system WP2 and PF2Business / Functional Team
2Validate transformation rules and mappings in Syniti toolData Team (L2C-Data)
3Generate target-ready load files based on S/4HANA customer material info records table formatData Team (Syniti)
4Review and approve load files before executionBusiness / Functional Team
5Execute the upload program in the S/4HANA system Data Load Team
6Monitor load progress and capture load statistics (records loaded, errors, duplicates, etc.)Data Team (Syniti) / Technical Team
7Extract loaded data from S/4HANA for post-load validationData Team (Syniti)
8Perform post-load data validation (compare target data with source/ approved files) for all loaded cross selling condition recordsData Team (L2C-Data)
9Log and resolve any data load errors or mismatches identified during validationData Team (L2C-Data) + Functional Team
10Obtain business sign-off on successful load and validationBusiness Team
11Archive load logs, error reports, and validation results for audit/complianceData Team (L2C-Data) / Data Team (Syniti) / PMO


Load Phase and Dependencies

The Customer Material Information Records (CMIR) 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
5
6
7
8
9

10


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 has the same records as the loading file

Display Records

Pick up a few random Customer and Material, and run t-code: VD53 to validate the Customer Material Information Records (CMIR) 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 ReconciliationGenerate 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

  • Customer Material Information Records (CMIR) Master Data Standard is up to date as on the date of documenting this conversion approach and data load. 
  • Customer Material Information Records (CMIR) 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 SAP CUI instance, the migration activity will be handled by US based data consultant. 


See also

Change log

Version Published Changed By Comment
CURRENT (v. 12) Apr 20, 2026 07:46 LIU-ext, Ekawati
v. 39 Feb 27, 2026 07:28 LIU-ext, Ekawati
v. 38 Feb 04, 2026 13:22 LIU-ext, Ekawati
v. 37 Jan 15, 2026 14:40 LIU-ext, Ekawati
v. 36 Jan 14, 2026 13:29 LIU-ext, Ekawati
v. 35 Dec 07, 2025 12:21 LIU-ext, Ekawati
v. 34 Nov 24, 2025 15:17 LIU-ext, Ekawati
v. 33 Nov 24, 2025 15:14 LIU-ext, Ekawati
v. 32 Nov 24, 2025 10:13 LIU-ext, Ekawati
v. 31 Oct 24, 2025 16:46 LIU-ext, Ekawati

Go to Page History

Workflow history

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

  • No labels