Purpose

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

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

Conversion Scope

The scope of this document covers the approach for converting active Material Listing and Exclusions from Legacy Source Systems into S/4HANA following the Material Listing and Exclusions Master Data Design Standard.

From the current system landscape, Material Master data exists separately in the legacy systems (PF2 and WP2), with potential discrepancies in both systems. Harmonization and validation are required to ensure accurate and consolidated data in S/4HANA. While PF2 and WP2 serve as source systems, extensive mapping and transformation logic will be necessary to produce properly formatted load templates in line with the target design.

The data from legacy system includes: Final relevancy rule pending MDS

1. All active Material Listing or Material Exclusions, where valid from date up to 1 year after S/4HANA Go-Live date AND valid to date beyond S/4HANA Go-Live date AND each of the below as per table combination:
   1. Customer/ Sold-to/ Ship-to sales view migrated as per CNV-3003 Business Partners - Customer (Sales and Service) - FLCU01 
   2. Material sales view migrated as per CNV-2003 Materials - Sales view with sales long text.
   3. Sales organization in scope of S/4HANA
   4. Distribution Channel (pending MDS if this will be in-scope for Material Listing and Exclusions and how to map)
   5. Plant in scope of S/4HANA
   6. Material Group in scope of S/4HANA
   7. Country in scope of S/4HANA (pending MDS, e.g. XK - Kosovo available in WP2 but not in Sandpit)
   8. Region in scope of S/4HANA

The data from legacy system excludes:

1. Invalid Material Listing or Material Exclusions; none of the above

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

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 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 (pending MDS). 

1. The Material Listing and Material Exclusions have below sales organizations in the table in-scope. 
2. The Material Listing and Material Exclusions have below Plants in the table in-scope (Plant list to be provided). 
3. If the Material Listing and Material Exclusions do not used sales organization or plant in the table in-scope, e.g. RecipCntry/Matl group; then it will be migrated to all 3 instances (ROW, CUI and China). 

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

1. The Material Listing and Material Exclusions have below sales organizations in the table in-scope. 
2. The Material Listing and Material Exclusions have below Plants in the table in-scope (Plant list to be provided). 
3. If the Material Listing and Material Exclusions do not used sales organization or plant in the table in-scope, e.g. RecipCntry/Matl group; then it will be migrated to all 3 instances (ROW, CUI and China). 

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

1. The Material Listing and Material Exclusions have below sales organizations in the table in-scope. 
2. The Material Listing and Material Exclusions have below Plants in the table in-scope (Plant list to be provided). 
3. If the Material Listing and Material Exclusions do not used sales organization or plant in the table in-scope, e.g. RecipCntry/Matl group; then it will be migrated to all 3 instances (ROW, CUI and China). 

One Sales Organization per GBU 

As elaborated in KDD060 - Sales Enterprise Structure, in the S/4Hana design, one sales organization will be mapped to one GBU. Therefore, it is possible that one sales organization in legacy system is mapped to multiple sales organization in the S/4HANA. When such scenario happens, one record of material listing and exclusions will be split into multiple records based on the mapping.

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.

Data Cleansing

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

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

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

Selection Screen

Data Collection Template (DCT)

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

DCT Rules

Material Listing and Exclusions

Extraction Dependencies

List the steps that need to occur before extraction can commence

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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

The Material Listing and Exclusions will be loaded in the pre-cutover period.

Before loading, it will have dependency on the following configuration and data objects in the S/4 HANA.

Configuration

List the Configurations required before loading can commence

Conversion Objects

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

Post-Load Validation

Project Team

Completeness

Accuracy

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

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Material Listing and Exclusions is in scope based on data design and any exception requested by business.
• There will be 3 SAP instances, one for ROW, one for China and one for CUI only.
• For S/4HANA CUI instance, the migration activity will be handled by US based data consultant.

See also

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