Purpose

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

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/4 HANA 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:

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

1. Material with sales view block: X-distr.chain status OR DChain-spec. status are not blank or not 63 (Available for Sale) 

Image Removed

List of source systems and approximate number of records

*MVKE Sales Organization X 3 Distribution Channel

Source Approx No. of Records

No. of Records

WP2

Materials - Sales View

S/4HANA ROW

PF2

S/4HANA ROW

WP2

PF2

WP2

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

20260227-Eka: the following are updated in this Conversion Specs:

1. Refer to CR0279 - Update Conversion Specs to remove mention of CUI System
2. DCT-MLAN: remove pre-population
3. Transformation:
   1. As the pre-population is removed from DCT-MLAN, default tax code to 1 (taxable) for combination Material / Country not in ECC.
   2. Distribution Channel based on sales organization country instead of plant country
4. Delete Cleansing Report - Material Sales Text for all language

20260420-Eka: Refer to CR0455 - L2C CNV-3003 Distribution channel logic enhancement: Update this Conversion Specs Distribution Channel logic to follow CNV-3003

List of source systems and approximate number of records 

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

Due to compliance requirement

PF2

Additional Information

Multi-language Requirement

Not Applicable

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.

, there will be one SAP instance

for Rest of the World (ROW) and one for China and one for CUI. For Materials - Sales view with sales long text, the same data will be created in all 2 SAP instances as it is Tier 1 object with central data governance and maintenance rule.

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

ALL Data Cleansing should be after Relevancy Rule

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. 

Image Added

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

Selection Screen

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Materials - Sales view with sales long text data with exception of some fields which require transformation as mentioned in the transformation rule.

Materials - Sales view with sales long text - FULL DCT

DCT for when data not available in ECC, e.g. service material master data (table: ASMD), service material for WP2/ PF2 billing via Finance to S/4 billing via SD, new sales organization in scope with legacy system non-ECC, Duplicate Data by Distribution Channel, etc.

Business to manually fill-up/ update all required fields.

Note: all rules specified below should be documented as a tooltip in the DC Page.

1. Rule as per Target Design for material type, e.g. Mandatory, Conditional, Not Used
2. Rule as per Table below

 Materials - Sales view with sales long text - MLAN DCT

DCT for when Tax data not available in ECC, e.g. service material master data (table: ASMD), service material for WP2/ PF2 billing via Finance to S/4 billing via SD, new sales organization in scope with legacy system non-ECC, Duplicate Data by Distribution Channel, new plant assignment to sales organization in S/4HANA. DCT for when data not available in ECC, etc.
Refer to Transformation Rule for MLAN-ALAND:
1. Get all S/4 Plants assigned to the S/4 Sales Organization
2. Get Plant Country (T001W-LAND1) for all Plants from #1
3. IF Plant Country = to existing MLAN-ALAND: COPY
4. IF Plant Country <> to existing MLAN-ALAND: due to new plant assignment in S/4, Business to collect the information and update the respective DCT.

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 ECC

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

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. S/4 Sales Organization is representing GBU. 
Get GBU based on the Material Profit Centre (MARC-PRCTR).
6.1. If the material GBU are not the same with S/4 Sales Organization GBU; exclude the material from transformation, but add it to Cleansing report.
6.2. If multiple ECC Sales Organization merge into 1 S/4 Sales Organization; include in the transformation if the material GBU is the same as S/4 Sales Organization GBU. Else exclude and add to the Cleansing report.
6.3. If 1 ECC Sales Organization is split into multiple S/4 Sales Organization; transform the material to respective S/4 Sales Organization where material GBU same as S/4 Sales Organization GBU. Else exclude and add to the Cleansing report.

Following are the logic to find Material GBU:

WP2

Image Added

1. Refer to CNV-2010 Materials - General Plant Data/ S.Loc Data for material type where profit centre will be required
2. Get Material, Plant, Maintenance Status, DF at plant level, Profit Centre (screenshot column: A, B, D, E, F) from MARC (Plant Data for Material), where flag for deletion/ MARC-LVORM = blank and Plant is in-scope.
3. Get the Company Code T001K-BUKRS (screenshot column: H) for the Plant (T001W-WERKS), where Valuation Area T001K-BWKEY = T001W-BWKEY
4. Get the Sales Organization in-scope TVKO-VKORG for Company Code TVKO-BUKRS in the list (from #3) and TVKWZ-VKORG for Plant in the list (from #2). Add another records/ lines if there are multiple Sales Organizations.
5. Get Controlling Area (screenshot column: I) for the Company Code from table: TKA02
6. Get Profit Centre ID (screenshot column: G): concatenate Controlling Area (from #5) and Profit Centre (from #2)
7. Get Profit Centre Group (screenshot column: J): VLOOKUP (Profit Centre ID,SETLEAF!ID:SETNAME,3,FALSE) from table: SETLEAF (from #B)
8. Get Value Stream Codification (screenshot column: K): digit 7 and 8 of Profit Centre Group (from #7)
9. Get GBU (screenshot column: L): VLOOKUP (Value Stream Codification,'GBU Lookup '!A:B,2,FALSE) - from #A.

Image Added

A. GBU Lookup

a. File: https://wiki.syensqo.com/display/CostFAQ/Rules+-+Material+Profit+Center 

b. Refer to: ZY - Is used to define a specific GBU code as follows (the currently active GBU's are the ones highlighted):

c. Open the link to: WP2 Codification Value Streams Master (OBSOLETE)

d. Download the file and go to worksheet: 1. Liste VS

e. Get “Value Stream Codification” code from column V and GBU description from column A 

f. Combine #b and #e; then remove duplicate

Image Added

B. Get all records from table: SETLEAF, where SETLEAF-SETCLASS = 0106 (Profit Centre Group)

• • Insert ID (screenshot column: I): concatenate Organizational Unit (screenshot column: B) and From Value (screenshot column: G)
  • Copy Set Name (screenshot column: C) and paste to the last column (screenshot column: K)

 PF2

Image Added

1. Refer to CNV-2010 Materials - General Plant Data/ S.Loc Data for material type where profit centre will be required
2. Get Material, Plant, Profit Centre, DF at plant level,  (screenshot column: A, B, E, G) from MARC (Plant Data for Material), where flag for deletion/ MARC-LVORM = blank and Plant is in-scope.
3. Get the Company Code T001K-BUKRS (screenshot column: D) for the Plant (T001W-WERKS), where Valuation Area T001K-BWKEY = T001W-BWKEY 
4. Get the Sales Organization in-scope TVKO-VKORG for Company Code TVKO-BUKRS in the list (from #3) and TVKWZ-VKORG for Plant in the list (from #2). Add another record/ line if there are multiple Sales Organizations.
5. Get Profit Centre Name CEPCT-KTEXT (screenshot column: F), where CEPCT-PRCTR = MARC-PRCTR and CEPCT-SPRAS = EN
6. Get Division MARA-SPART (screenshot column: H), where MARC-MATNR = MARA-MATNR and MARA-LVORM = blank.
7. Get Plant Div ID (screenshot column: I): concatenate Plant (from #2) and Division (from #5)
8. Get Business Area (screenshot column: J): VLOOKUP (Plant Div ID, T134G!C:D, 2, FALSE) from table: T134G (from #A)
9. Get Division (screenshot column: K): digit 2 and 3 of Business Area (from #8)
10. Get Sub Business Unit ZZR_REPO_DIV-ZZRSBU (screenshot column: L), where Division (from #9) = ZZR_REPO_DIV-ZZRDIV
11. Get Business Unit ZZR_REPO_SBU-ZZRBU (screenshot column: M), where ZZR_REPO_DIV-ZZRSBU (from #10) = ZZR_REPO_SBU-ZZRSBU
12. Get Division (PCtr) (screenshot column: N): digit 2 and 3 of Profit Centre Name (from #5)
13. IF Business Area (screenshot column: J) = #N/A: get Sub BU ZZR_REPO_DIV-ZZRSBU (screenshot column: P), where Division (PCtr) (from #12) = ZZR_REPO_DIV-ZZRDIV
14. IF Business Area (screenshot column: J) = #N/A: get BU ZZR_REPO_SBU-ZZRBU (screenshot column: Q), where ZZR_REPO_DIV-ZZRSBU (from #13) = ZZR_REPO_SBU-ZZRSBU
15. Get Final BU (screenshot column: R): If BU from #11 not blank, use it, else use the BU value from #14.
16. Get BU Description ZZR_REPO_SBU-ZZRSBU_MNAME (screenshot column: S), where ZZR_REPO_SBU-ZZRSBU (from #15) = ZZR_REPO_SBU-ZZRSBU

Image Added

A. Get all records from table: T134G:

• • Insert Plant Div ID (screenshot column: C): concatenate Plant (screenshot column: A) and Division (screenshot column: B)

Rule to determine GBU from: Rules - PF1 - Profit center

20260420-Eka: Refer to CR0455 - L2C CNV-3003 Distribution channel logic enhancement: Update this Conversion Specs Distribution Channel logic to follow CNV-3003

Transformation Rules FULL DCT

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

 Transformation Mapping

Data Cleansing

2003-001

2003-002

2003-003

Set sales view block for material not eligible for migration

Check the usage of material sales view not in use for 5 years and without stock, but still active

Conversion Process

The high-level process is represented by the diagram below:

Image Removed

Data Privacy and Sensitivity

Extraction

Extract data from a source into . There are 2 possibilities:

1. The data exists. connects to the source and loads the data into . 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 ; 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 . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

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

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

Extraction Execution Plan

- Establish execution timelines and batch processing schedules.

- Assign responsibilities for extraction monitoring.

- Document dependencies on other migration tasks.

Syniti

Data Quality and Validation

- Define error handling mechanisms for extraction failures.

Syniti

Selection Screen

Data Collection Template (DCT)

Materials - Sales view with sales long text DCT Rules

Extraction Dependencies

Source System Availability

• Ensure that the source database or application is accessible.
• Confirm that necessary credentials and permissions are granted

Syensqo IT

Data Structure

• Identify relationships between tables, views, and stored procedures.

Syniti

Referential Integrity

• Ensure dependent records are extracted together.

Syniti

Extraction Methodology

• Define whether extraction is full, incremental, or delta-based.
• Establish batch processing schedules for large datasets.

Syniti

Performance and Scalability Considerations

• Optimize extraction queries to prevent system overload.
• Ensure network bandwidth supports data transfer volumes.

Syniti

Security and Compliance

• Adhere to regulatory standards for sensitive information if applicable

Syniti

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

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

Transformation Rules

Transformation Mapping

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

Unit of Measure Mapping

MVKE_VRKME shares the same mapping table with Basic view (MARA_MEINS).

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

Material Status - Sales Mapping

MVSTAV - Cross Distribution Chain

VMSTA - Distribution Chain Specific

Check the configuration in ECC & S/4 HANA if we need this mapping or not? Or if status <> blank then excluded from ECC download?

Plant Mapping

WERKS - Plant

DWERK - Delivering Plant

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

Statistics Group - Material Mapping

TBD

Product Hierarchy Mapping

MARA_PRDHA - Basic Data 1

MVKE_PRODH - Sales: Sales Org. 2

Prod. Hierarchies' levels are the same. Share the same mapping table with Basic view (MARA_PRDHA).

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

Item Category Group Mapping

MTPOS_MARA - Basic Data 1

MTPOS - Sales: Sales Org. 2

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

Material Group 1 Mapping

Use in QF2

Material Group 2 Mapping

Use in QF2 and WQ2

Material Group 3 Mapping

Use in QF2

Material Group 5 Mapping

Use in WQ2

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

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