You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Status

  Revision in Progress

Owner

OMER-ext, Mohammed 

Stakeholders

Purpose

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

In SAP Transportation Management (SAP TM), transportation lanes are a foundational master data object that represent the relationship between two locations, two transportation zones, or a combination of locations and transportation zones that expresses the direct reachability of the locations, or of all locations, within the transportation zones for a specific means of transport (MTr).

<Assumption> The data for TM-Transportation lanes 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 Transportation lanes in S/4HANA following the TM-Transportation lanes Master Data Design Standard. 

This includes:

  • Capturing and using the transportation lanes 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
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

DCTCreation of TM-Transportation lanesTBDS/4 HANA (TM)TBD















Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements




Target Design

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

TableFieldData ElementField DescriptionData TypeLengthRequirement
/SAPAPO/TRlocfrStart Location/ZoneCHAR22Mandatory
/SAPAPO/TRloctoDestination Location/ZoneCHAR22Mandatory
/SAPAPO/TRMvalfr

Start date


defaulted to date of migration/creation

NUM (DATE)15Mandatory
/SAPAPO/TRMvalto

End date


defaulted to 31.12.9999

NUM (DATE)15Mandatory
/SAPAPO/TRMDIST

Transportation Distance

NUM10,3Mandatory
/SAPAPO/TRMDURAT

Transport Duration

NUM11Mandatory
/SAPAPO/TRMttype
Means of TransportCHAR10Mandatory
/SAPAPO/TRMCstbase

Priority/Costs


default should be D (cost*priority)

CHAR1Mandatory
/SAPAPO/TRMCcobase

Cost Origin


default should be T (cost calculated by component TCM)

CHAR1Mandatory
/SAPAPO/TRMCcmbase

Contin Move Type


Two possibilities, depend on the scenario. 
For those lanes where we expect multidrops, then value is "Continuous move (Simple)".
For those cases where we do not want to multidrop, then value is "No Continuous Move".
It depends lane by lane. 

CHAR1Mandatory
/SAPAPO/TRMCARRpartner
CarrierCHAR10Mandatory
/SAPAPO/TRMCARRttype
Means of TransportCHAR10Mandatory
/SAPAPO/TRMCARRvalfr

Start date


defaulted to date of migration/creation

NUM (DATE)15Mandatory
/SAPAPO/TRMCARRvalto

End date


defaulted to 31.12.9999

NUM (DATE)15Mandatory
/SAPAPO/TRMCARRCARRTRCOST
Transportation CostNUM15,2Mandatory
/SAPAPO/TRMCARRCARRTRCOSTUNIT
Unit of Measure for Transportation Costs of a ProductCHAR3Mandatory
/SAPAPO/TRMCARRCARRPRIO
Priority of Transportation Service ProviderCHAR3Mandatory


Data Cleansing

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

IDCriticalityError Message/Report DescriptionRuleOutputSource 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:

  1. The data exists. connects to the source and loads the data into . 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 ; 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 . 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 DescriptionTeam Responsible
1Data is populated in the DCT or uploaded from downloaded Excel templateData owner (Business)
2If the data is uploaded to DCT in bulk via excel template, any upload errors need to be reviewed and correctedData owner (Business), Syniti/ Data Team
3The data which has passed validation checks in DCT will be used for transformation/further processingSyniti




Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set





















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

Please find below the DCT details.


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.

Field NameField DescriptionRule












Extraction Dependencies

Item #Step DescriptionTeam 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:

  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
  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 DescriptionTeam Responsible













Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































Transformation Mapping

Mapping Table NameMapping Table Description








Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible













Pre-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





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 DescriptionTeam 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 TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





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

Version Published Changed By Comment
CURRENT (v. 10) Dec 01, 2025 14:19 OMER-ext, Mohammed
v. 37 Sept 18, 2025 16:44 OMER-ext, Mohammed
v. 36 Sept 05, 2025 10:47 OMER-ext, Mohammed
v. 35 Sept 03, 2025 15:01 OMER-ext, Mohammed
v. 34 Sept 03, 2025 14:55 OMER-ext, Mohammed
v. 33 Sept 03, 2025 14:51 OMER-ext, Mohammed
v. 32 Aug 21, 2025 12:13 OMER-ext, Mohammed
v. 31 Aug 21, 2025 12:10 OMER-ext, Mohammed
v. 30 Aug 19, 2025 17:30 OMER-ext, Mohammed
v. 29 Aug 19, 2025 14:03 OMER-ext, Mohammed

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels