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 - International Trade Views in S/4 HANA and GTS.

The International Trade view in SAP S/4HANA is designed to support companies in managing all regulatory and compliance requirements related to cross-border trade. It replaces the classic "Foreign Trade" views from SAP ECC and centralizes key data needed for customs, export, and import processes.

Conversion Scope

The scope of this document covers the approach for converting active Materials - International Trade Views from Legacy Source Systems into S/4HANA and GTS following the Materials - International Trade Views Master Data Design Standard: DD-FUN-050 Master Data Standard_2029-Materials - International Trade Views. 

From the current system landscape, Materials - International Trade Views exist in both legacy systems - PF2 and WP2 (Foreign Trade: Export Data and Foreign Trade: Import Data). Harmonization and validation are required to ensure the accurate and consolidated data in S/4HANA and GTS. 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 includes:

1. Material Basic Data View is migrated as per CNV-2019 Materials - Basic Data View.
2. The Plant for Materials - International Trade Views has country = BR (Brazil) or IN (India) and is within the scope of S/4HANA.
3. No flag for deletion at Plant level (MARC-LVORM)

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Materials - International trade views	2,000	S/4HANA ROW	2,000
WP2	Materials - International trade views	20,000	S/4HANA ROW	20,000
PF2	Materials - International trade views	0	S/4HANA CUI	0
WP2	Materials - International trade views	0	S/4HANA CUI	0
PF2	Materials - International trade views	0	S/4HANA China	0
WP2	Materials - International trade views	0	S/4HANA China	0
PF2	Materials - International trade views	2,000	GTS	2,000
WP2	Materials - International trade views	20,000	GTS	20,000

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

Material CFOP category:  is used to determine the proper CFOP. The CFOP determines the nature of the transaction (such as sale, purchase, return, import, or transfer) and is required for proper tax calculation and electronic fiscal document (NF-e) generation in Brazil.

Control Code - BR: NCM codes are required for materials used in company codes to comply with tax and legal reporting. The NCM code determines applicable federal taxes (e.g., IPI, PIS, COFINS) and is printed on the nota fiscal.

Control Code - IN: HSN codes are required for materials used in India company codes to comply with GST tax determination and legal reporting.

Special Requirements

Due to compliance requirement, there will be one SAP instance for Rest of the World (ROW), one for China and one for CUI. Based on the Plant the Materials - International Trade Views records will be migrated to respective SAP instances. 

For Material CFOP category records, it will also be migrated to GTS.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this 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.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extract data from a source into Syniti Migrate. 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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible

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

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.

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

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

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

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

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

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

Business

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

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

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

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

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

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

Post-Load Validation

Project Team

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

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

Business

The following post-load validations will be performed by the business.

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

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object 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