Purpose

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

Schedules define a sequence of transportation stops such as ports, airports, or gateways, that is valid for a specific period of time. Ships, trucks, or airplanes can move goods at recurring times along the whole sequence or any part of it.

The data for TM Schedules in S/4 would need to be constructed in data collection template (DCT).

Conversion Scope

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

• Capturing and using the TM Schedule 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

Schedule description will be made available in English.

Multi language is supported for schedules (KDD055 provides guidelines on the supported languages).  Login via a different language will show the description displayed in the logon language if the language key is maintained.

Document Management

Not Applicable.

Legal Requirement

Not Applicable.

Special Requirements

Not Applicable.

Target Design

The complete information of the key fields that hold the TM Schedules information follows the Master Data Standard document.

The technical design of the target for this conversion approach.

Data Cleansing

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

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)

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

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

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

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

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 produce 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 with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_DCT, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE) 

The following options will need to be explored during data migration build to select the best possible solution: 

i) via import from Microsoft Excel using the report /SCMTMS/SCH_UPLOAD or

ii)Function_Loader_Inlay program or

iii) Custom Migration Cockpit Object (LTMOM).

The load file format can be finalized when development system is available.

BAPI: /SCMTMS/BAPI_SCHEDULE_SAVEMULT

Load Run Sheet

Load Phase and Dependencies

TM Schedules data will be loaded in the pre-cutover window.

Configuration

Conversion Objects

Error Handling

As part of the TM Schedules data load to S/4HANA  using the Syniti data migration tool, various data quality, configuration, and technical challenges may arise.

The following table outlines the most commonly observed error types during data load, and the corrective actions typically taken to resolve them. This helps ensure consistency in issue handling, improves traceability during cutover, and supports smooth end-to-end execution of the TM Schedules load.

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.
• TM Schedules is in scope based on data design and any exception requested by business.
• Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
• The list of validation checks in transformation section is not exhaustive and may change over time as the design and configuration of the system evolves.

See also

Change log