Purpose

The purpose of this document is to define the conversion approach to create Default routes in S/4 HANA TM (Transportation management).

Default route functionality in S/4 HANA TM (Transportation management) solution is different from routes functionality in SAP ECC, the tables and fields are different. [Assumption] The data for default routes in S/4 would need to be constructed in data collection template (DCT).

Default route defines the sequence of stops for a given source and destination combination, which can be locations or zones. For a given source and destination, SAP TM determines matching default routes and chooses the most specific one; a direct location match is more specific than a zone match. Default routes can be modified manually where the desired route is different to that proposed.

Conversion Scope

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

• Capturing and using the default route 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)

List of source systems and approximate number of records

Additional Information

Multi-language Requirement

Default route description will be made available in English.

Multi language is supported for default routes. Login via a different language will show the description displayed in the logon language if the language key is maintained.

As per KDD055, there are 8 languages in scope: English, French, Italian and Mandarin and Brazilian Portuguese, German, Spanish and Thai.

Document Management

Not applicable.

Legal Requirement

Not applicable.

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

Target Design

Default route data adheres to the Master Data Standard. 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

Default route data will be populated directly in the Data Collection Template (DCT).

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.

Conversion Process

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

Data Privacy and Sensitivity

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

Selection Screen

Data Collection Template (DCT)

A Target Ready Data Collection Template will be created for the required data, except for fields that need transformation as per the defined transformation rules. It will follow the format required by the target S/4HANA Default route.

Please find below the DCT details.

<Object> DCT Rules

Discuss with Syniti Later if we capture all languages in one DCT or if to split another DCT for other Languages.

Please refer to the above Google sheet for the DCT rules.

Extraction Dependencies

Not applicable.

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

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

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

Conversion Objects

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

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

Workflow history