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 Material Listing and Exclusions in S/4 HANA.

Summarise how the data is currently utilized and set up in the legacy system/s and how object is intended to be represented in S/4, and any other relevant information

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:

1. All active Material Listing; valid to date beyond S/4 Go-Live date AND customer as per CNV-3003 AND material as per CNV-2003.
2. All active Material Exclusions; valid to date beyond S/4 Go-Live date AND customer as per CNV-3003 AND material as per CNV-2003.

The data from legacy system excludes:

1. Inactive Material Listing; table not active anymore OR valid to date before S/4 Go-Live date OR customer not included in CNV-3003 or material not included in CNV-2003.
2. Inactive Material Exclusions; table not active anymore OR valid to date before S/4 Go-Live date OR customer not included in CNV-3003 or material not included in CNV-2003.

List of source systems and approximate number of records (double check the number and exclude flag for deletion for customer and material)

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WP2	Table: KOTG001 Listing/exclusion type - Customer - Material - Valid to - Valid From Without sales organization but there are data for inclusion - Z002 (Cust/Restricted used), e.g. WP2 - SO 3480790 where customer 65429 is marked for deletion and listing type Z002 no longer assigned to procedure A00001. CHECK in detail	5,000	S/4 HANA	5,000
WP2	Table: KOTG004 Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material - Valid to - Valid From	100	S/4 HANA	100
WP2	Table: KOTG906 Listing/exclusion type - Sales Organization - Customer - Material - Valid to - Valid From	120,000	S/4 HANA	120,000
WP2	Table: KOTG908 Listing/exclusion type - Sales Organization - Departure country - Valid to - Valid From	50	S/4 HANA	50
WP2	Table: KOTG909 Listing/exclusion type - Material - Destination Country - Region - Valid to - Valid From	3,000	S/4 HANA	3,000
WP2	Table: KOTG913 Listing/exclusion type - Sales Organization - Material - Customer - Valid to - Valid From	300	S/4 HANA	300
WP2	Table: KOTG962 Listing/exclusion type - Material - Destination Country - Valid to - Valid From	150	S/4 HANA	150
WP2	Table: KOTG964 Listing/exclusion type - Sales Organization - Material - Destination Country - Valid to - Valid From	85,000	S/4 HANA	85,000
PF2	Table: KOTG501 Listing/exclusion type - Destination Country - Material Group - Valid to - Valid From	15,500	S/4 HANA	15,500
PF2	Table: KOTG521 Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From	50	S/4 HANA	50
PF2	Table: KOTG903 List/excl. - Material - Plant - Ship-To Party - Valid to - Valid From	50	S/4 HANA	50
PF2	Table: KOTG904 List/excl. - Material - Plant - Sold-To Party - Valid to - Valid From	50	S/4 HANA	50
PF2	Table: KOTG906 Sales org. - Destination Country - Valid to - Valid From	100	S/4 HANA	100

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

Material Listing and Exclusions

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 which will reside in CUI, the migration will be handled by US based data consultant. 

Please refer to the link for the entity mapping for each instance. In case the data object is applicable for multiples instances, what business rule to follow?

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

1. The Material has sales organization data in below entities. 
2. If the Material is used in both ROW entities and others, then the Sales View data needs to be created in both SAP ROW and others instances.

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

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

1. The Material has sales organization data in below entities. 
2. If the Material is used in both China entities and others, then the Sales View data needs to be created in both SAP China and other instances.

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

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

1. The Material has sales organization data in below entities. 
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 and other instances.

PF2	5782	SOLVAY SPOL US
WP2	US05	Solvay US Novecare
WP2	US23	Technology Solutions
WP2	US32	Composite Materials
WP2	US33	CEM Defense Material
WP2	US50	Composite Mat (7008)

  

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.

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.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
2001-001		Set valid to date to before S/4HANA Go-Live date	For Listing/ Exclusion which the table combination is no longer valid, e.g. customer flagged for deletion, material flagged for deletion,	Pending MDS	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

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

Material Listing and Exclusions

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

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
MAP_VTWEG	Distribution Channel Mapping SyWay - Sales Area.pptx --> All the actual distribution channels and divisions won't exist in the to-be solution Check current Dist.Ch. and discuss with Functional team and how to do the mapping
MAP_MSTAV	Material Status - Sales Mapping MSTAV - Cross Distribution Chain is used in WQ2 Exclusions (code: 05 and 11) Check the configuration in ECC for 05 and 11 and the mapping to S/4 HANA. Discuss with the Functional team if the material master for these 2 codes will be migrated to S/4?
MAP_WERKS	Plant Mapping WERKS - Plant Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi
MAP_MATKL	Material Group Mapping
MAP_ALAND	Country Mapping
MAP_MATNR	Material Mapping
MAP_REGIO	Region Mapping
MAP_KUNNR	Customer Mapping Covers mapping for ALL customers, incl.: KUNAG Sold-to  KUNWE Ship-to
MAP_KSCHL	Listing/exclusion type

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Source Data Integrity - Ensure extracted data is complete, accurate, and consistent. - Validate that data types and formats align with transformation requirements.	Syniti
2	Referential Integrity - Ensure dependent records are transformed together or in advance	Syniti
3	Transformation Logic and Mapping - Define data mapping rules between source and target schemas.	Data Team
4	Performance and Scalability Considerations - Optimize transformation processes for large datasets. - Ensure system resources can handle transformation workloads	Syniti
5	Logging and Error Handling - Maintain detailed logs of transformation activities. - Define error-handling procedures for failed transformations	Syniti

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Compare Data Counts	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
Verify Record Count	Business Data Owner/s to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets.

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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

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

List the Configurations required before loading can commence

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
11	Cross-Distribution-Chain Material Status (X-distr.chain status)

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

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

Accuracy

Task	Action
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
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
Perform Manual Testing	Conduct manual spot-checks for additional assurance.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Material Listing and Exclusions is in scope based on data design and any exception requested by business.

Any additional key assumptions.

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