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

Compare with Current View Page History

« Previous Version 15 Next »

Status

  Approved

OwnerLIU-ext, Ekawati 
Stakeholders

Purpose

The purpose of this document is to define the data conversion approach to create Materials - Sales view with sales long text in S/4HANA.

Sales View is a part of the Material Master data that defines how a material is sold to customers. It's essential for creating sales orders, quotations, and other sales documents within the Sales and Distribution (SD) module. The Sales View includes information like sales organization, distribution channel, delivering plant, tax information, and sales-related text.

This conversion aims to migrate active and relevant Materials - Sales view with sales long text 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 Master Sales View including the sales long text from Legacy Source Systems into S/4HANA following the Materials - Sales view with sales long text Master Data Design Standard: DD-FUN-050 Master Data Standard_2003-Materials - Sales view with sales long text.

From the current system landscape, Materials - Sales view with sales long text exist in 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. Material Basic Data View is migrated as per CNV-2019 Materials - Basic Data View.
  2. The Sales Organization and Distribution Channel for Materials - Sales View with Sales Long Text is within the scope of S/4HANA.
  3. Flag for deletion at distribution chain/ sales organization level (MVKE-LVORM), Material Master Sales View is in the scope if:
    * No flag for deletion
    * With flag for deletion, but have sales transaction in the last 4 years for the sales organization in scope 


List of source systems and approximate number of records 

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2Materials - Sales view with sales long text35,000S/4HANA ROW35,000
WP2Materials - Sales view with sales long text55,000S/4HANA ROW55,000
PF2Materials - Sales view with sales long text0S/4HANA CUI0
WP2Materials - Sales view with sales long text30,000S/4HANA CUI30,000
PF2Materials - Sales view with sales long text10,000S/4HANA China10,000
WP2Materials - Sales view with sales long text10,000S/4HANA China10,000

Additional Information

Multi-language Requirement

N/A


Document Management

N/A

Legal Requirement

N/A

Special Requirements

Due to compliance requirement, there will be one SAP instance for Rest of the World (ROW), one for China and one for CUI. Based on the sales organization the Materials - Sales view with sales long text records will be migrated to respective SAP instances. 


Target Design

Materials - Sales View with Sales Long Text Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Materials - Sales View with Sales Long Text information follows the Master Data Standard document.

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
MVKEMATNRMATNRMaterialCHAR40Mandatory
MVKEVKORGVKORGSales OrganizationCHAR4Mandatory
MVKEVTWEGVTWEGDistribution ChannelCHAR2Mandatory
MVKELVORMLVOVKDF distr. chain lvlCHAR1Conditional
MVKEVMSTAVMSTADChain-spec. statusCHAR2Conditional
MVKEVMSTDVMSTDValid fromDATS8Conditional
MVKEAUMNGMINAUMinimum order qtyQUAN13Conditional
MVKELFMNGMINLFMinimum Delivery QtyQUAN13Conditional
MVKEEFMNGMINEFMin. MtO quantityQUAN13Conditional
MVKESCMNGSCHRTDelivery unitQUAN13Conditional
MVKESCHMESCHMEUnit Of Measure of Delivery UnitUNIT3Conditional
MVKEVRKMEVRKMESales UnitUNIT3Conditional
MVKEMTPOSMTPOSItem Category GroupCHAR4Mandatory
MVKEDWERKDWERK_EXTDelivering PlantCHAR4Conditional
MVKEPRODHPRODH_DProduct HierarchyCHAR18Conditional
MVKEKONDMKONDMMaterial Price GrpCHAR2Conditional
MVKEKTGRMKTGRMAcct Assmt Grp Mat.CHAR2Conditional
MVKEMVGR1MVGR1Material Group 1CHAR3Conditional
MVKEMVGR2MVGR2Material Group 2CHAR3Conditional
MVKEMVGR3MVGR3Material Group 3CHAR3Conditional
MVKEMVGR4MVGR4Material Group 4CHAR3Conditional
MVKEMVGR5MVGR5Material Group 5CHAR3Conditional
MVKERDPRFRDPRFRounding ProfileCHAR4Conditional
MLANMATNRMATNRMaterial NumberCHAR18Mandatory
MLANALANDALANDDeparture Ctry/Reg.CHAR3Mandatory
MLANTAXM1TAKLMTax ClassificationCHAR1Mandatory
MLANTAXM2TAKLMTax ClassificationCHAR1Conditional
MLANTAXM3TAKLMTax ClassificationCHAR1Conditional
MLANTAXM4TAKLMTax ClassificationCHAR1Conditional
MLANTAXM5TAKLMTax ClassificationCHAR1Conditional
MLANTAXM6TAKLMTax ClassificationCHAR1Conditional
MLANTAXM7TAKLMTax ClassificationCHAR1Conditional
MLANTAXM8TAKLMTax ClassificationCHAR1Conditional
MLANTAXM9TAKLMTax ClassificationCHAR1Conditional
STXHTDOBJECTTDOBJECTText objectCHAR10Mandatory
STXHTDNAMETDOBNAMEText NameCHAR70Mandatory
STXHTDIDTDIDText IDCHAR4Mandatory
STXHTDSPRASSPRASLanguage KeyLANG1Mandatory
Function ModuleLong Text
Text Details/ Long TextCHAR
Mandatory
ZFI_CN_INTMATCFGBUKRSBUKRSCompany CodeCHAR4Mandatory
ZFI_CN_INTMATCFGKUNNRKUNNRCustomerCHAR10Conditional
ZFI_CN_INTMATCFGMATNRMATNRMaterialCHAR18Mandatory
ZFI_CN_INTMATCFGPROD_NAMEPROD_NAMEProduct NameCHAR80Mandatory
ZFI_CN_INTMATCFGPROD_SPECPROD_SPECProduct SpecificationCHAR50Mandatory
ZFI_CN_INTMATCFGNO_STDNO_STDNo STD DescriptionCHAR1Mandatory


Data Cleansing

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


Materials - Sales view with sales long text

IDCriticalityError Message/Report DescriptionRuleOutputSource System

2003-001


Report of in-active material master for the sales organization in-scope for S/4HANA 

For material with active basic/ general and sales view; but not being used in any sales transaction for more than 3 years.

Data cleanser: to set flag for deletionPF2/ WP2

2003-002


Report of material master sales status for the sales organization in-scope for S/4HANA 

For material with active basic/ general and sales view; but sales status are not BLANK.

Data cleanser: to set flag for deletion after reviewPF2/ WP2

2003-003


Report of material master sales transaction for the sales organization in-scope for S/4HANAFor material with active basic/ general and sales view; get delivery for the last 3 years with Plant Country and Ship-to Party Country

To determine which distribution channel to be extended to: 10 - Export or 20 - Domestic

Always extend to: 30 - Intercompany

PF2/ WP2
2003-004

Fill in mandatory fields based on master data standards

  1. Departure Ctry/Reg.
  2. Tax Classification

And validate obsolete 'tax classification' maintained

For all active material with active basic/ general and sales view; but Departure Ctry/Reg. and Tax Classification are BLANK for all combination.Data cleanser: to fill up if all blank and update if there is obsolete tax classification.PF2/ WP2
2003-005

Validate obsolete 'item category group' maintained



PF2/ WP2
2003-006

Validate obsolete 'product hierarchy' maintained



PF2/ WP2
2003-007

Validate obsolete 'sales unit' maintained



PF2/ WP2
2003-008

Validate obsolete 'account assignment group material' maintained



PF2/ WP2
2003-009

Validate obsolete 'material group 1 to material group 5' maintained



PF2/ WP2
2003-010

Due to sales area definition change, multiple sales view record might merge into one record. If multiple records have different values, pick the main records.



PF2/ 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 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 source into Syniti Migrate for SAP ROW and SAP China relevant entities. 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.


For SAP CUI related entities, it will be alternative extraction process and the data will be stored in approved tools.

Extraction Run Sheet

Req #Requirement DescriptionTeam Responsible
2003-001- Identify the source systems and databases involved.
- Define the data objects (tables, fields and records) to be extracted.
- Establish business rules for data selection.		L2C Data team
2003-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
2003-003- Establish execution timelines and batch processing schedules.
- Assign responsibilities for extraction monitoring.
- Document dependencies on other migration tasks.		Syniti
2003-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 Organization
















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

Materials - Sales view with sales long text 

Field NameField DescriptionRule












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 MigrateData Team (Syniti)
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 DescriptionMapping TableTransformation Logic
Materials - Sales View with sales long text

Data Extraction Logic for Materials - Sales View with sales long text

1. Process by Source System
Perform the extraction steps from source system, i.e. WP2 and PF2.

2. Extract Materials - Sales View with sales long text - Data
Extract Materials - Sales View with sales long text from table - MVKE (Sales Data for Material) with the following filters:
Sales Organization (VKORG): include only records for in-scope Sales Organizations provided in the parameter list.
Include records only if the corresponding migrated target value exists in the target system.

3. Extract Materials - Sales View with sales long text - Tax Selection
For each material from table MVKE above; get the Country and Tax Classification from Tax Classification for Material (table - MLAN).

4. Extract Materials - Sales View with sales long text - Text Selection
For each item level from table MVKE above concatenate the material number (18 digit), sales organization (4 digit) and distribution channel (2 digit) and default text object = MVKE and Text ID - 0001; get the Text Name and Language from table - STXH (STXD SAPscript text file header).

Note: Text ID maybe maintained in multiple languages. To migrate for all languages. 

5. Extract Materials - Sales View with sales long text - Text Details
For each Text Object, Text Name, Text ID and Language from table - STXH above, get the Text Details via function module: read_text.

6. For China legal requirements, extract Product Name and Product Description from table: ZFI_CN_INTMATCFG. Pending confirmation if this will be migrated to Material Master or CMIR or keep it in add-on table.


2003-001WP2/ PF2MVKEMATNRMaterialS/4HANAMVKEMATNRMaterialMAP_MATNRMapping
2003-002WP2/ PF2MVKEVKORGSales OrganizationS/4HANAMVKEVKORGSales OrganizationMAP_VKORGMapping
2003-003WP2/ PF2MVKEVTWEGDistribution ChannelS/4HANAMVKEVTWEGDistribution ChannelRuleRULE:

1. Get ALL sales documents for the last 4 years for sales organization in scope and document category/ VBAK-VBTYP = C - Order and VBAK-VBTYP = I - Order w/o charge.
2. For PF2, exclude sales document type/ VBAK-AUART = M3/ M3 Reference order
3. Get valid sales documents for Materials - Sales View with sales long text; VBAK-VBELN, where VBAK-VKORG = MVKE-VKORG and VBAK-VTWEG = MVKE-VTWEG
4. From the valid sales document (point #3), get the Ship-to Party country; VBPA-LAND1, where VBPA-PARVW = SH/ Ship-to party
5.  From the valid sales document (point #3), get the Plant; VBAP-WERKS, where VBAP-VBELN = VBAK-VBELN and VBAP-MATNR = MVKE-MATNR.
6. Get the Plant country; T001W-LAND1, where T001W-WERKS = VBAP-WERKS
7. Select sales document for each Materials - Sales View with sales long text, where VBAK-VKORG = MVKE-VKORG and VBAK-VTWEG = MVKE-VTWEG and VBAP-MATNR = MVKE-MATNR:
- IF Plant Country = Ship-to Party Country: map to S/4HANA distribution channel = 20 Domestic
- IF Plant Country <> Ship-to Party Country: map to S/4HANA distribution channel = 10 Export

IF the sales order created for both 10 Export and 20 Domestic; then create 2 Materials - Sales View with sales long text as per distribution channel.

Note: ALL Materials - Sales View with sales long text should also be extended to distribution channel = 30 Intercompany
2003-004WP2/ PF2MVKELVORMDF distr. chain lvlS/4HANAMVKELVORMDF distr. chain lvl
Copy
2003-005WP2/ PF2MVKEVMSTADChain-spec. statusS/4HANAMVKEVMSTADChain-spec. status
Copy
Assumption: configuration will use the same code as per ECC
2003-006WP2/ PF2MVKEVMSTDValid fromS/4HANAMVKEVMSTDValid from
Copy
2003-007WP2/ PF2MVKEAUMNGMinimum order qtyS/4HANAMVKEAUMNGMinimum order qty
Copy
2003-008WP2/ PF2MVKELFMNGMinimum Delivery QtyS/4HANAMVKELFMNGMinimum Delivery Qty
Copy
2003-009WP2/ PF2MVKEEFMNGMin. MtO quantityS/4HANAMVKEEFMNGMin. MtO quantity
Copy
2003-010WP2/ PF2MVKESCMNGDelivery unitS/4HANAMVKESCMNGDelivery unit
Copy
2003-011WP2/ PF2MVKESCHMEUnit Of MeasureS/4HANAMVKESCHMEUnit Of MeasureMAP_MEINSMapping
2003-012WP2/ PF2MVKEVRKMESales UnitS/4HANAMVKEVRKMESales UnitMAP_MEINSMapping
2003-013WP2/ PF2MVKEMTPOSItem Category GroupS/4HANAMVKEMTPOSItem Category GroupMAP_MTPOSMapping
Still in progress - pending CR
Mapping table structure TBD as it will include Material Type in the mapping, e.g.
- S/4HANA material type ZDIR for Auxiliary items; item category group ZAN2
- ZDIR Distress/ Scrap/ Raw; ZAN3
- ZDIR Bonded Warehouse: ZAN4
2003-014WP2/ PF2MVKEDWERKDelivering PlantS/4HANAMVKEDWERKDelivering PlantMAP_WERKSMapping
2003-015WP2/ PF2MVKEPRODHProduct HierarchyS/4HANAMVKEPRODHProduct HierarchyMAP_PRODHRule
Still in progress - pending CR

PF2: get material group for the material extracted (point 1 and 2 above) then go to MAP_PRODH to get product hierarchy level 1, product hierarchy level 2 and product hierarchy level 3 also for Material Group 2 (Specialty Polymer)

WP2: get basic material for the material extracted (point 1 and 2 above) then go to MAP_PRODH to get product hierarchy level 1, product hierarchy level 2 and product hierarchy level 3 also for Material Group 3 (Novecare) and Material Group 4 (Technology Solutions)
2003-016WP2/ PF2MVKEKONDMMaterial Price GrpS/4HANAMVKEKONDMMaterial Price GrpMAP_KONDMMapping
2003-017WP2/ PF2MVKEKTGRMAcct Assmt Grp Mat.S/4HANAMVKEKTGRMAcct Assmt Grp Mat.MAP_KTGRMMapping
2003-018WP2/ PF2MVKEMVGR1Material Group 1S/4HANAMVKEMVGR1Material Group 1
Rule
Leave BLANK
2003-019WP2/ PF2MVKEMVGR2Material Group 2S/4HANAMVKEMVGR2Material Group 2
Rule
Refer to the rule for Product Hierarchy (2003-015) above.
2003-020WP2/ PF2MVKEMVGR3Material Group 3S/4HANAMVKEMVGR3Material Group 3
Rule
Refer to the rule for Product Hierarchy (2003-015) above.
2003-021WP2/ PF2MVKEMVGR4Material Group 4S/4HANAMVKEMVGR4Material Group 4
Rule
Refer to the rule for Product Hierarchy (2003-015) above.
2003-022WP2/ PF2MVKEMVGR5Material Group 5S/4HANAMVKEMVGR5Material Group 5
Rule
Leave BLANK
2003-023WP2/ PF2MVKERDPRFRounding ProfileS/4HANAMVKERDPRFRounding ProfileMAP_RDPRFMapping
2003-024WP2/ PF2MLANMATNRMaterial NumberS/4HANAMLANMATNRMaterial NumberMAP_MATNRMapping
2003-025WP2/ PF2MLANALANDDeparture Ctry/Reg.S/4HANAMLANALANDDeparture Ctry/Reg.
Copy
2003-026WP2/ PF2MLANTAXM1Tax ClassificationS/4HANAMLANTAXM1Tax ClassificationMAP_TAXKMMapping
2003-027WP2/ PF2MLANTAXM2Tax ClassificationS/4HANAMLANTAXM2Tax ClassificationMAP_TAXKMMapping
2003-028WP2/ PF2MLANTAXM3Tax ClassificationS/4HANAMLANTAXM3Tax ClassificationMAP_TAXKMMapping
2003-029WP2/ PF2MLANTAXM4Tax ClassificationS/4HANAMLANTAXM4Tax ClassificationMAP_TAXKMMapping
2003-030WP2/ PF2MLANTAXM5Tax ClassificationS/4HANAMLANTAXM5Tax ClassificationMAP_TAXKMMapping
2003-031WP2/ PF2MLANTAXM6Tax ClassificationS/4HANAMLANTAXM6Tax ClassificationMAP_TAXKMMapping
2003-032WP2/ PF2MLANTAXM7Tax ClassificationS/4HANAMLANTAXM7Tax ClassificationMAP_TAXKMMapping
2003-033WP2/ PF2MLANTAXM8Tax ClassificationS/4HANAMLANTAXM8Tax ClassificationMAP_TAXKMMapping
2003-034WP2/ PF2MLANTAXM9Tax ClassificationS/4HANAMLANTAXM9Tax ClassificationMAP_TAXKMMapping
2003-035WP2/ PF2STXHTDOBJECTText objectS/4HANASTXHTDOBJECTText object
Copy
2003-036WP2/ PF2STXHTDNAMEText NameS/4HANASTXHTDNAMEText Name
Concatenate:
1st 18 digit = Material Number
Next 4 digit = Sales Organization
Last 2 digit = Distribution Channel 
2003-037WP2/ PF2STXHTDIDText IDS/4HANASTXHTDIDText ID
Copy
2003-038WP2/ PF2STXHTDSPRASLanguage KeyS/4HANASTXHTDSPRASLanguage Key
Copy
Exclude ZH (Chinese)
2003-039WP2/ PF2Function ModuleLong TextText Details/ Long TextS/4HANA

Text Details
Copy Text Details
2003-040WP2/ PF2ZFI_CN_INTMATCFGBUKRSCompany CodeS/4HANA    To extend to all sales organization and distribution channel based on the company code
2003-041WP2/ PF2ZFI_CN_INTMATCFGKUNNRCustomerS/4HANA    IF ZFI_CN_INTMATCFG-KUNNR <> Blank; IGNORE
Will be migrated as CNV-1036 CMIR?
2003-042WP2/ PF2ZFI_CN_INTMATCFGMATNRMaterialS/4HANA   MAP_MATNRMapping
2003-043WP2/ PF2ZFI_CN_INTMATCFGPROD_NAMEProduct NameS/4HANA    Copy to STXH in this Materials - Sales view with sales long text?
2003-044WP2/ PF2ZFI_CN_INTMATCFGPROD_SPECProduct SpecificationS/4HANA     
2003-045WP2/ PF2ZFI_CN_INTMATCFGNO_STDNo STD DescriptionS/4HANA    Check box
Migrate to where?


Transformation Mapping

Mapping Table NameMapping Table Description
MAP_MATNRECC (PF2/ WP2) to S/4AHANA Material No. Mapping Table
MAP_VKORGECC (PF2/ WP2) to S/4AHANA Sales Organization Mapping Table
MAP_MEINSECC (PF2/ WP2) to S/4AHANA Unit of Measure Mapping Table
MAP_MTPOSECC (PF2/ WP2) to S/4AHANA Item Category Group Mapping Table
MAP_WERKSECC (PF2/ WP2) to S/4AHANA Plant Mapping Table
MAP_PRODHECC (PF2/ WP2) to S/4AHANA Product Hierarchy Mapping Table
MAP_KONDMECC (PF2/ WP2) to S/4AHANA Material Price Group Mapping Table
MAP_KTGRMECC (PF2/ WP2) to S/4AHANA Material Account Assignment Group Mapping Table
MAP_RDPRFECC (PF2/ WP2) to S/4AHANA Rounding Profile Mapping Table
MAP_TAXKMECC (PF2/ WP2) to S/4AHANA Material Tax Classification Mapping Table

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Source Data Integrity
- Ensure extracted data is complete, accurate, and consistent.
- Validate that data types and formats align with transformation requirements.		Syniti 
2Referential Integrity
- Ensure dependent records are transformed together or in advance		Syniti 
3Transformation Logic and Mapping
- Define data mapping rules between source and target schemas.		Data Team
4Performance and Scalability Considerations
- Optimize transformation processes for large datasets.
- Ensure system resources can handle transformation workloads		Syniti 
5Logging 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 Counts1. Verify row counts in the source databases.
2. Identify missing or duplicated records.
Validate the mandatory fieldsValidate there is value for all the mandatory fields
Validate Primary Keys and Unique Constraints1. Check for duplicate or missing primary key values, i.e. if there is same sales organization, distribution channel and material number.
2. Ensure unique constraints are maintained.
Test Referential IntegrityConfirm 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
1Load 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
2Load Methodology
- Specify the loading tools and technologies (Migration Cockpit, LSMW, custom loading program).		Syniti / US Based Consultant for S/4 HANA CUI instance
3Data 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 / US Based Consultant for S/4 HANA CUI instance
4Load Execution Plan
- Establish execution timelines and batch processing schedules.
- Assign responsibilities for monitoring execution.
- Document dependencies on other migration tasks		Syniti / US Based Consultant for S/4 HANA CUI instance
5Logging and Reporting
- Maintain detailed logs of loading activities.
- Generate summary reports on loaded data volume and quality.
- Define escalation procedures for errors		Syniti / US Based Consultant for S/4 HANA CUI instance


Load Phase and Dependencies

The Materials – Sales views with sales long text will be loaded in the pre-cutover period.

Before loading, it will have dependency on the configuration and 2019 - Materials-Basic View(required Material Types-ROH/FERT/HALB/SRV/DIEN/ZDIE/Packaging/Spares). The configuration needs to be transported into the respective system first, including the manual configuration such as the number range set up. And 2019 Materials-Basic View(required Material Types-ROH/FERT/HALB/SRV/DIEN/ZDIE/Packaging/Spares) have to be uploaded into the respective system first.

Configuration

Item #Configuration Item

1

Sales Organization

2

Distribution Channel

3

Unit of Measure

4

Material Status - Sales

5

Plant

6

Tax Condition Type

7

Tax Classification - Material

8

TBD - Statistics Group - Material

9

Product Hierarchy

10

Material Price Group

11

Account Assignment Group - Material

12

Item Category Group

13

Material Group 1

14

Material Group 2

15

Material Group 3

16

Material Group 5 → check MDS if this will be mapped to Material Group 4 in S/4HANA

17

Country: TBD - as ECC has quite  bit additional country, but the following 3 are being used/ have data in MLAN: EU (European Union), Q1 (Outside EU), XK (Kosovo)

Conversion Objects

Object #Preceding Object Conversion Approach

2019

Materials-Basic View(required Material Types-ROH/FERT/HALB/SRV/DIEN/ZDIE/Packaging/Spares





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 the main tables, such as MVKE has the same records as the loading file

Display Records

Pick up few random Material numbers, and Run the Material Report to validate the Material Sales View with Sales Text 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

  • Material - Sales view with sales long text Master Data Standard is up to date as on the date of documenting this conversion approach and data load. 
  • Materials - Sales views with sales long text 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. 15) Apr 29, 2026 13:44 LIU-ext, Ekawati
v. 30 Apr 28, 2026 08:36 LIU-ext, Ekawati
v. 29 Apr 23, 2026 10:31 LIU-ext, Ekawati
v. 28 Apr 20, 2026 08:15 LIU-ext, Ekawati
v. 27 Feb 27, 2026 10:31 LIU-ext, Ekawati
v. 26 Feb 27, 2026 09:42 LIU-ext, Ekawati
v. 25 Jan 16, 2026 16:33 LIU-ext, Ekawati
v. 24 Jan 06, 2026 12:51 LIU-ext, Ekawati
v. 23 Dec 17, 2025 11:03 LIU-ext, Ekawati
v. 22 Dec 17, 2025 07:27 LIU-ext, Ekawati

Go to Page History

Workflow history

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

  • No labels