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)

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 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 China, then the Sales View data needs to be created in both SAP ROW and China instances.

- 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 ROW, then the Sales View data needs to be created in both SAP China and ROW instances.

 - 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 by US based data team and other instances by non-US based data team.

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.

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

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)

DCT Rules

Materials - Sales view with sales long text 

Extraction Dependencies

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

The following pre-load validations will be performed by the 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 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

Conversion Objects

Error Handling

Post-Load Validation

Project Team

The following post-load validations will be performed by the 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

• 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

Workflow history