| Status | Approved |
|---|---|
| Owner | |
| Stakeholders |
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:
- Material Basic Data View is migrated as per CNV-2019 Materials - Basic Data View.
- The Plant for Materials - International Trade Views has country = BR (Brazil) or IN (India) and is within the scope of S/4HANA.
- No flag for deletion at Plant level (MARC-LVORM)
| 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
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- 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
| Req # | Requirement Description | Team Responsible |
|---|---|---|
Selection Screen
| 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 with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| 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 to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in
- 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
| 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
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- 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
Configuration
| 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
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.