Purpose

The purpose of this document is to define the conversion approach to create TM-Transportation zones in S/4 HANA TM (Transportation Management).

The transportation zone is a geographical grouping of locations that is used for the purpose of routing. It can be the combination of country, state, postcodes, or individual locations.

 The data for transportation zones in S/4 TM would need to be constructed in data collection template (DCT). The existing legacy data would be provided in google sheet for reference.

Conversion Scope

The scope of this document covers the approach for creating Transportation zones in S/4HANA following the TM Transportation zones Master Data Design Standard. This includes:

• Capturing and using the Transportation zone data in data collection template (DCT).
• Applying transformation logic via Syniti to conform with the S/4 HANA data model.
• Loading the transformed data into SAP S/4 HANA while ensuring data integrity.

The data from legacy system includes:

1. N/A (Manual data collection)

The data from legacy system excludes:

1. N/A (Manual data collection)

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The complete information of the key fields that hold the default route information follows the Master Data Standard document.

The technical design of the target for this conversion approach.

Data Cleansing

Transportation zone data will be populated directly in the Data Collection Template (DCT).

Conversion Process

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

Please note that the data may have to be loaded in multiple target systems (US instance, China instance and RoW).

Data Privacy and Sensitivity

Extraction

1. Syniti Migrate connects to the sources.
2. An initial extract of the relevant Transportation zones will be loaded into a google sheet report to assist business with any rationalization.

If the data does not exist in legacy systems, the data will be manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate.

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

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

1. The extracted report will be loaded into the required structure using the DCT.
2. Standardization activities (including deduplication, standardization and additions)  will be carried out within the DCT.

Please refer to the below Google sheet for the DCT rules (main DCT page and another page for non English descriptions).

Transportation zones DCT Rules

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

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

Please check the attached file for the complete source-to-target field mapping, validation checks and proposed error messages. The validation checks list is not exhaustive and may change over time as the design and configuration of the system evolves.

Transformation Mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence

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

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also

Change log

Workflow history