Status
Owner	LIU-ext, Ekawati
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the 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.

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 Material Sales View Master Data Design Standard. 

From the current system landscape, Material Master data exists separately in the legacy systems (WP2 and PF2), with potential discrepancies in both organizations. Harmonization and validation are required to ensure accurate and consolidated data in S/4HANA. While WP2 and PF2 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:

1. Material Basic Data View is migrated (re: CNV-2019 Materials - Basic Data View).
2. The Sales Organization and Distribution Channel for Materials - Sales View with Sales Long Text are in-scope of S/4HANA.
3. There is no flag for deletion at client/ general level (MARA-LVORM) in the Material Basic View.
4. OR no flag for deletion at distribution chain/ sales organization level (MVKE-LVORM) in the Material Sales View.

The data from legacy system excludes:

1. The Sales Organization and Distribution Channel for Materials - Sales View with Sales Long Text are out-scope of S/4HANA.

List of source systems and approximate number of records (double check the number and exclude flag for deletion. also check if we can split by domestic, export and intercompany)

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WP2	Materials - Sales View	93,000	S/4HANA ROW	93,000
PF2	Materials - Sales View		S/4HANA ROW
WP2	Materials - Sales View	13,500	S/4HANA China	13,500
PF2	Materials - Sales View		S/4HANA China
WP2	Materials - Sales View	63,000	S/4HANA CUI	63,000
PF2	Materials - Sales View		S/4HANA CUI

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

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. The migration for CUI related entities will be covered by US based data consultant using separate tools.

Special Requirements

Materials - Sales View with Sales Long Text

A. Different SAP Instance Migration Approach

Due to compliance requirement, there will be one SAP instance for Rest of the World (ROW), one for China and one for CUI.

1. For entities in China, the data will be loaded into SAP China instance while the entire migration process will remain the same as rest of the world.
2. For entities in CUI instance, the migration will be handled by US based data consultant. 

 - To identify the record is for SAP ROW Instance, it will use below logic. 

1. The Material has sales view data in below sales organizations. 
2. If the Material is used in both ROW entities and China, then the Sales View data needs to be created in both S/4HANA ROW and China instances.

System	Sales Organization Code	Sales Organization Description	Country
PF2	3383	SOLVAY SPOL KR	KR
PF2	5686	SOLVAY QUIMICA (AR)	AR
PF2	5782	SOLVAY SPOL US	US
PF2	5835	SOLVAY SPOL IT	IT
PF2	5846	SOLVAY SPOL JP	JP
PF2	5955	SOLVAY SPECIALIT IN	IN
PF2	5978	SOLVAY SPOL BE	BE
PF2	6080	SOLVAY FRANCE FR	FR
PF2	6327	SLV SP CHEM ASIA PAC	SG
WP2	AE01	AE Composite Matls	AE
WP2	AU01	Technology Solutions	AU
WP2	AU02	AU Novecare	AU
WP2	BR42	Quimicos BR Novecare	BR
WP2	BR44	Quimicos BR SpecPoly	BR
WP2	BR47	Quimicos BR Tech Sol	BR
WP2	CA12	Technology Solutions	CA
WP2	CA15	Cytec CA Novecare	CA
WP2	CL01	Cytec Chile Tech Sol	CL
WP2	FRAZ	SPOP Novecare	FR
WP2	GB34	Solvay Solutions UK	GB
WP2	ID01	CYID Tech Solutions	ID
WP2	IN04	SSIPL IN Novecare	IN
WP2	IT07	Novecare Italie	IT
WP2	JP02	Solvay Japan, Ltd	JP
WP2	JP03	Solvay Nicca, Ltd	JP
WP2	JP10	Technology Solutions	JP
WP2	KR11	CY KR Novecare	KR
WP2	KR12	CY KR Tech Solutions	KR
WP2	MX01	MX Tech Solutions	MX
WP2	MX02	MX Novecare	MX
WP2	MX08	MX Spec Polymers	MX
WP2	NL01	Cytec Ind BV TS	NL
WP2	NL05	Solvay Sol NL Noveca	NL
WP2	NZ01	Solvay New Zealand	NZ
WP2	PE01	Technology Solutions	PE
WP2	SG03	Solvay Sp Chem SG	SG
WP2	SG08	SSCAP SG Tech Sol	SG
WP2	TH01	Technology Solutions	TH
WP2	TH03	Solvay (Bangpoo) SC	TH
WP2	US05	Solvay US Novecare	US
WP2	US23	Technology Solutions	US
WP2	US50	Composite Mat (7008)	US

- To identify the record is for SAP China Instance, it will use below logic. 

1. The Material has sales view data in below sales organizations. 
2. If the Material is used in both China entities and ROW, then the Sales View data needs to be created in both S/4HANA China and ROW instances.

System	Sales Organization Code	Sales Organization Description	Country
PF2	5876	SOLVAY SHANGHAI LTD	CN
PF2	5991	SOLVAY SPEC POLYMERS	CN
WP2	CN15	Solvay ZJ Novecare	CN
WP2	CN18	Zhuhai SLV Novecare	CN
WP2	CN19	Solvay ZJG Novecare	CN
WP2	CN27	Solvay ZJ Tech Sol	CN
WP2	CN28	CYIS Tech Solutions	CN
WP2	CN36	CYIS Composites Matl	CN
WP2	CN41	CEM (SH) Compos Mats	CN

 - To identify the record is for SAP CUI Instance, it will use below logic. 

1. The Material has sales view data in below sales organizations. 
2. If the Material is used in both CUI entities and others, then the Sales View data needs to be created in both SAP CUI by US based data team and other instances by non-US based data team.

System	Sales Organization Code	Sales Organization Description	Country
WP2	DE13	Composites Materials	DE
WP2	GB40	Composites Materials	GB
WP2	US32	Composite Materials	US
WP2	US33	CEM Defense Material	US

  

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 master data sales view will be split into multiple records based on the mapping.

To double check on the Profit Centre in Material Master.

- there is no company code assignment in the profit centre master data, but can be created with multiple controlling area (table: CEPC)
- GBU (Novecare/ Technology Solutions) is maintained in field: person responsible (free text)
- Same profit centre can have different person responsible based on the controlling area

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.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MARA	MATNR	MATNR	Material Number	CHAR	18	Mandatory

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

ID	Criticality	Error Message/Report Description	Rule	Output	Source 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 deletion	PF2/ 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 review	PF2/ WP2
2003-003		Report of material master sales transaction for the sales organization in-scope for S/4HANA	For 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 Departure Ctry/Reg. 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 (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. 

For CUI instance, the ETL process will be similar, but it will not use Syniti tool.

Data Privacy and Sensitivity

For SAP CUI instances, the data will be processed by US Based consultants.

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 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 / US Based Consultant for S/4HANA CUI instance 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 / US Based Consultant for S/4HANA CUI instance
Extraction Execution Plan	- Establish execution timelines and batch processing schedules. - Assign responsibilities for extraction monitoring. - Document dependencies on other migration tasks.	Syniti / US Based Consultant for S/4HANA CUI instance
Data Quality and Validation	- Define error handling mechanisms for extraction failures.	Syniti / US Based Consultant for S/4HANA CUI instance

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

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 Data Object 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 Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team 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 / US Based Consultant for S/4HANA CUI instance
3	Referential Integrity Ensure dependent records are extracted together.	Syniti / US Based Consultant for S/4HANA CUI instance
4	Extraction Methodology Define whether extraction is full, incremental, or delta-based. Establish batch processing schedules for large datasets.	Syniti / US Based Consultant for S/4HANA CUI instance
5	Performance and Scalability Considerations Optimize extraction queries to prevent system overload. Ensure network bandwidth supports data transfer volumes.	Syniti / US Based Consultant for S/4HANA CUI instance
6	Security and Compliance Adhere to regulatory standards for sensitive information if applicable	Syniti / US Based Consultant for S/4HANA CUI instance
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 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 / US Based Consultant for S/4HANA CUI instance

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2/ WP2	MVKE	MATNR	Material	S/4HANA	MVKE	MATNR	Material	Map from source to target as per CNV-2019 Materials - Basic Data View
2	PF2/ WP2	MVKE	VKORG	Sales Organization	S/4HANA	MVKE	VKORG	Sales Organization	Map from source to target using mapping table: MAP_VKORG
3	PF2/ WP2	MVKE	VTWEG	Distribution Channel	S/4HANA	MVKE	VTWEG	Distribution Channel	Extend all to 30 - Intercompany 10 - Export and 20 - Domestic; to be decided based on the transaction data (plant country - ship-to country)
4	PF2/ WP2	MVKE	VERSG	Matl statistics grp	S/4HANA	MVKE	VERSG	Matl statistics grp	TBD
5	PF2/ WP2	MVKE	VMSTA	DChain-spec. status	S/4HANA	MVKE	VMSTA	DChain-spec. status	Map from source to target using mapping table: MAP_VMSTA
6	PF2/ WP2	MVKE	SCHME	Unit Of Measure	S/4HANA	MVKE	SCHME	Unit Of Measure	Map from source to target using mapping table: MAP_MEINS
7	PF2/ WP2	MVKE	VRKME	Sales Unit	S/4HANA	MVKE	VRKME	Sales Unit	Map from source to target using mapping table: MAP_MEINS
8	PF2/ WP2	MVKE	MTPOS	Item Category Group	S/4HANA	MVKE	MTPOS	Item Category Group	Map from source to target using mapping table: MAP_MTPOS TBD - If source is blank, copy value from General Item Category Group (MARA-MTPOS_MARA)
9	PF2/ WP2	MVKE	DWERK	Delivering Plant	S/4HANA	MVKE	DWERK	Delivering Plant	Map from source to target using mapping table: MAP_WERKS
10	PF2/ WP2	MVKE	PRODH	Product Hierarchy	S/4HANA	MVKE	PRODH	Product Hierarchy	Map from source to target using mapping table: MAP_PRODH
11	PF2/ WP2	MVKE	KONDM	Material Price Grp	S/4HANA	MVKE	KONDM	Material Price Grp	Map from source to target using mapping table: MAP_KONDM
12	PF2/ WP2	MVKE	KTGRM	Acct Assmt Grp Mat.	S/4HANA	MVKE	KTGRM	Acct Assmt Grp Mat.	Map from source to target using mapping table: MAP_KTGRM
13	PF2/ WP2	MVKE	MVGR1	Material Group 1	S/4HANA	MVKE	MVGR1	Material Group 1	Map from source to target using mapping table: MAP_MVGR1
14	PF2/ WP2	MVKE	MVGR2	Material Group 2	S/4HANA	MVKE	MVGR2	Material Group 2	Map from source to target using mapping table: MAP_MVGR2
15	PF2/ WP2	MVKE	MVGR3	Material Group 3	S/4HANA	MVKE	MVGR3	Material Group 3	Map from source to target using mapping table: MAP_MVGR3
16	PF2/ WP2	MVKE	MVGR4	Material Group 4	S/4HANA	MVKE	MVGR4	Material Group 4	TBD - Map from source to target using mapping table: MAP_MVGR4
17	PF2/ WP2	MVKE	MVGR5	Material Group 5	S/4HANA	MVKE	MVGR5	Material Group 5	Map from source to target using mapping table: MAP_MVGR5
18	PF2/ WP2	MLAN	ALAND	Departure Ctry/Reg.	S/4HANA	MLAN	ALAND	Departure Ctry/Reg.	Map from source to target using mapping table: MAP_ALAND
19	PF2/ WP2	MLAN	TAXM1	Tax Classification	S/4HANA	MLAN	TAXM1	Tax Classification	TBD - Map from source to target using mapping table: MAP_TAXKM
20	PF2/ WP2	MLAN	TAXM2	Tax Classification	S/4HANA	MLAN	TAXM2	Tax Classification	TBD - Map from source to target using mapping table: MAP_TAXKM
21	PF2/ WP2	MLAN	TAXM3	Tax Classification	S/4HANA	MLAN	TAXM3	Tax Classification	TBD - Map from source to target using mapping table: MAP_TAXKM
22	PF2/ WP2	MLAN	TAXM4	Tax Classification	S/4HANA	MLAN	TAXM4	Tax Classification	TBD - Map from source to target using mapping table: MAP_TAXKM
23	PF2/ WP2	MLAN	TAXM5	Tax Classification	S/4HANA	MLAN	TAXM5	Tax Classification	TBD - Map from source to target using mapping table: MAP_TAXKM
24	PF2/ WP2	MLAN	TAXM6	Tax Classification	S/4HANA	MLAN	TAXM6	Tax Classification	TBD - Map from source to target using mapping table: MAP_TAXKM
25	PF2/ WP2	MLAN	TAXM7	Tax Classification	S/4HANA	MLAN	TAXM7	Tax Classification	TBD - Map from source to target using mapping table: MAP_TAXKM
26	PF2/ WP2	MLAN	TAXM8	Tax Classification	S/4HANA	MLAN	TAXM8	Tax Classification	TBD - Map from source to target using mapping table: MAP_TAXKM

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
MAP_VKORG	Sales Organization Mapping Table
MAP_MEINS	Unit of Measure Mapping Table
MAP_VMSTA	Material Status - Sales Mapping Table
MAP_WERKS	Plant Mapping Table
MAP_ALAND	Country Mapping Table (to be used for Tax Country Mapping)
MAP_TAXKM	Material Tax Classification Mapping Table This mapping table has combination of Tax Country, Sequence No., Tax Category and Tax Classification. Pending MDS to correct the mapping.
MAP_PRODH	Product Hierarchy Mapping Table
MAP_KONDM	Material Price Group Mapping Table
MAP_KTGRM	Account Assignment Group - Material Mapping Table
MAP_MTPOS	Item Category Group Mapping Table
MAP_MVGR1	Material Group 1 Mapping Table Use in QF2
MAP_MVGR2	Material Group 2 Mapping Table Use in QF2 and WQ2
MAP_MVGR3	Material Group 3 Mapping Table Use in QF2
MAP_MVGR5	Material Group 5 Mapping → will this be map MVGR4? Use in WQ2

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 / US Based Consultant for S/4HANA CUI instance
2	Referential Integrity - Ensure dependent records are transformed together or in advance	Syniti / US Based Consultant for S/4HANA 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 S/4HANA 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 S/4HANA CUI instance

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Compare Data Counts	Verify row counts between source and target databases. Identify missing or duplicated records.
Validate the mandatory fields	Validate there is value for all the mandatory fields
Validate Primary Keys and Unique Constraints	Check for duplicate or missing primary key values. Ensure unique constraints are maintained.
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	Compare field values across systems Validate data formats and structures

Business

The following pre-load validations will be performed by the Business.

Completeness

Task	Action
Compare Data Counts	Verify row counts between source and target databases. Identify missing or duplicated records.
Review populated templates for missing or incorrect values	Use checklists to verify completeness and correctness before submission

Accuracy

Task	Action
Conversion Accuracy	Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/ mapping rules (and signed-off DCT data).

Load

The load process includes:

1. Execute the automated data load into target system using load tool or 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 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 / US Based Consultant for S/4 HANA CUI instance
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 / US Based Consultant for S/4 HANA CUI instance
4	Load 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
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 / 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 Type	Error Description	Action Taken
Configuration / Data Transformation	The value XXX for field XXX doesn't exist	Check the mapping/ conversion is done properly in the loading file Validate the target value is configured/ transported in the target system Reach out to function team to validate the configuration
Configuration	There is mandatory field XXX missing	Validate MDS if the fields are set as mandatory Validate if there is value in the pre-loading file 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

Task	Action
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	Validate that migrated data matches source records. Check for discrepancies in numerical values, text fields, and timestamps

Accuracy

Task	Action
Execute Sample Queries and Reports	Run queries to validate business logic. 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

Task	Action
Perform Source-to-Target Comparisons	Validate that migrated data matches source records. Check for discrepancies in numerical values, text fields, and timestamps
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

• 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

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history