| Status | Revision in Progress |
|---|---|
| Owner | |
| 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:
- N/A (Manual data collection)
The data from legacy system excludes:
- N/A (Manual data collection)
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| DCT | Creation of TM-Transportation lanes | TBD | S/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.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| /SAPAPO/TR | locfr | locfr | Start Location/Zone | CHAR | 22 | Mandatory |
| /SAPAPO/TR | locto | locto | Destination Location/Zone | CHAR | 22 | Mandatory |
| /SAPAPO/TRM | valfr | valfr | Start date defaulted to date of migration/creation | NUM (DATE) | 15 | Mandatory |
| /SAPAPO/TRM | valto | valto | End date defaulted to 31.12.9999 | NUM (DATE) | 15 | Mandatory |
| /SAPAPO/TRM | DIST | DIST | Transportation Distance | NUM | 10,3 | Mandatory |
| /SAPAPO/TRM | DURAT | DURAT | Transport Duration | NUM | 11 | Mandatory |
| /SAPAPO/TRM | ttype | ttype | Means of Transport | CHAR | 10 | Mandatory |
| /SAPAPO/TRMC | stbase | stbase | Priority/Costs default should be D (cost*priority) | CHAR | 1 | Mandatory |
| /SAPAPO/TRMC | cobase | cobase | Cost Origin default should be T (cost calculated by component TCM) | CHAR | 1 | Mandatory |
| /SAPAPO/TRMC | cmbase | cmbase | Contin Move Type Two possibilities, depend on the scenario. | CHAR | 1 | Mandatory |
| /SAPAPO/TRMCARR | partner | partner | Carrier | CHAR | 10 | Mandatory |
| /SAPAPO/TRMCARR | ttype | ttype | Means of Transport | CHAR | 10 | Mandatory |
| /SAPAPO/TRMCARR | valfr | valfr | Start date defaulted to date of migration/creation | NUM (DATE) | 15 | Mandatory |
| /SAPAPO/TRMCARR | valto | valto | End date defaulted to 31.12.9999 | NUM (DATE) | 15 | Mandatory |
| /SAPAPO/TRMCARR | CARRTRCOST | CARRTRCOST | Transportation Cost | NUM | 15,2 | Mandatory |
| /SAPAPO/TRMCARR | CARRTRCOSTUNIT | CARRTRCOSTUNIT | Unit of Measure for Transportation Costs of a Product | CHAR | 3 | Mandatory |
| /SAPAPO/TRMCARR | CARRPRIO | CARRPRIO | Priority of Transportation Service Provider | CHAR | 3 | Mandatory |
Data Cleansing
Transportation lanes data will be populated directly in the Data Collection Template (DCT).
| 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 |
|---|---|---|
| 1 | Data is populated in the DCT or uploaded from downloaded Excel template | Data owner (Business) |
| 2 | If the data is uploaded to DCT in bulk via excel template, any upload errors need to be reviewed and corrected | Data owner (Business), Syniti/ Data Team |
| 3 | The data which has passed validation checks in DCT will be used for transformation/further processing | Syniti |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value 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
Please refer to the above Google sheet for the 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 |
|---|---|---|
| 1 | Capture the data for Transportation routes in DCT. Review and correct any errors if bulk uploading data via downloaded excel DCT template. | Business team |
| 2 | Ensure the mapping tables which are needed during transformation have been reviewed and signed off by business. | Business team, Data Team (SCM) |
| 3 | Obtain DCT Sign-off from Business | Business team, Data Team (SCM) |
| 4 | Generate Pre-Load reports | Data Team (Syniti) |
| 5 | Review and Validate Error and Preload Reports | Data Team (SCM) |
| 6 | Log errors as defects, if any and address resolutions. | Data Team (SCM) |
| 7 | Re-transform and re-validate the Pre-load reports if necessary. | Data Team (SCM), Data Team (Syniti) |
| 8 | Obtain preload validation sign-off from Business | Business + Functional (SCM) + Data Team (SCM) |
| 9 | Generate Load Files | Data Team (Syniti) |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1042-001 | DCT | SAP S/4 HANA | /SAPAPO/TR | locfr | Start Location/Zone | Copy (as is) | |||
| locto | Destination Location/Zone | Copy (as is) | |||||||
| /SAPAPO/TRM | valfr | Start date | Copy (as is) | ||||||
| /SAPAPO/TRM | valto | End date | Copy (as is) | ||||||
| /SAPAPO/TRM | dist | Transportation Distance | Copy (as is) | ||||||
| /SAPAPO/TRM | durat | Transport Duration | Copy (as is) | ||||||
| /SAPAPO/TRM | ttype | Means of Transport | Copy (as is) | ||||||
| /SAPAPO/TRMC | stbase | Priority/Costs | Copy (as is) | ||||||
| /SAPAPO/TRMC | cobase | Cost Origin | Copy (as is) | ||||||
| /SAPAPO/TRMC | cmbase | Contin Move Type | Copy (as is) | ||||||
| custom | srsys | Carrier Source system | This will be used together with legacy vendor (carrier) in determining the new (S4) BP number | ||||||
| /SAPAPO/TRMCARR | partner | Carrier | Use the legacy to SAP vendor mapping to determine the new (S4) BP number |
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
| TSP | TBD-Legacy to SAP vendor (business partner) |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | Data Team (SCM) |
| 2 | Value Mappings are according to the latest design | Functional Team (SCM) + Data Team (SCM) |
| 3 | SAP Transportation management configuration for transportation lanes is complete | Functional Team (SCM) + Data Team (SCM) |
| 4 | Dependent Master Data records for Locations and Zones are loaded | Functional Team (SCM) + Data Team (SCM) |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Check Values | Validate the pre-load data confirming the values are aligned with target system format |
| Validate template structure and required field population | Ensure mandatory fields like DESCRIPTION, SCH_TYPE, MOT, Locations (transportation stops), validity dates are filled |
| Verify Record Count | SCM Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | SCM Data Team to verify that all fields below meet pass the checks:
|
| Perform format validation (date, currency, decimal separators) | Standardize format to match SAP accepted input (e.g., YYYYMMDD for dates) |
| Review Error Reports | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data. |
| Conduct dry runs using LTMC or BAPIs and review logs | Analyze load results and correct format or conversion errors |
Business
Completeness
| Task | Action |
|---|---|
| Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload validation file. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | Business Data Owner/s to verify that all the data in the preload validation file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data). Review error reports in tool for any mismatch or missing transformed values. |
Load
The load process includes:
- Execute the automated data load into target system using load tool or produce 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 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)
Function_Loader_Inlay program or Custom Migration Cockpit Object (LTMOM) will have to be used for automated load of transportation lanes to SAP S/4 HANA TM. There is no standard object available in SAP Migration Cockpit for transportation lanes.
BAPI: <>
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure the load tools are transported into the correct system/instance. | Data Team (SCM) |
| 2 | Ensure Pre-load sign-offs are obtained. | Data Team (SCM) |
| 3 | Execute upload of Transportation lanes using Function_Loader_Inlay program or Custom Migration Cockpit Object. | Data Team (SCM) |
| 4 | Validate few records loaded by accessing standard transactions from S/4HNA E.g. Fiori app 'Display Transportation route'. | Data Team (SCM) |
| 5 | Generate the post load reports in tool. | Data Team (SCM), Data Team (Syniti) |
| 6 | Log errors as defects, if any and address resolutions. Close defects. | Data Team (SCM) |
| 7 | Resolve defects by reupload and re-generate post load reports if necessary. | Data Team (SCM), Data Team (Syniti) |
| 8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business team |
| 9 | Repeat steps 5 to 7 if necessary. | Data Team (SCM), Data Team (Syniti) |
Load Phase and Dependencies
Transportation lanes data will be loaded in the pre-cutover window.
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | SAP Transportation management configuration (MOT, Stage types, Default route type, Number range for default routes) |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1051 | TM - Locations |
| 1052 | TM - Transportation Zones |
Error Handling
As part of the transportation lanes 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 transportation lanes load.
| Error Type | Error Description | Action Taken |
|---|---|---|
| Configuration | Invalid or missing MOT, Stage types, Default route type | Engage Functional team to expedite and fix the error in the system |
| Formatting Errors | One or more key fields (e.g., TSP) are incorrectly formatted | Ensure formatting is done correctly (e.g., leading zeros for TSP) |
| Authorization Errors | Lack of access to execute load in target client/system | Raised access request; obtained necessary authorizations |
| Transformation Miss | Required transformation logic not applied before load | Re-applied transformation rules and revalidated source-target mapping |
| Technical Load Failure | File not processed due to syntax/format error or system issue | Reviewed logs; regenerated file; re-executed load after resolving issue |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Run Fiori app/tcode to check loaded data in SAP | Run Fiori app 'Display Transportation lane' to check if data has been loaded |
| Compare uploaded data against source file values | Use Custom reconciliation tools e.g. SQL Server or Excel based comparison tools to validate the number of records loaded against the load file record volume |
| Check for load errors in load tool | Review custom load tool or Legacy Transfer Migration Cockpit LTMC logs for any failures |
Accuracy
| Task | Action |
|---|---|
| Compare uploaded data against source file values | Use automated postload validation report or standard reports from S/4 HANA to validate field by field value match across all loaded records |
Business
Completeness
| Task | Action |
|---|---|
| Verify Count | Download Postload validation reports from Syniti and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file |
| Review loaded Transportation lanes | Access the S/4HANA system (via Fiori app Display Transportation lane) to view loaded transportation lanes |
Accuracy
| Task | Action |
|---|---|
| Compare Against Approved Load File | Cross-check data in S/4HANA against the final business-approved load file used for migration |
| Validate Accuracy of Converted/Transformed Data | Review any transformed fields (e.g., business partner number) for correctness |
| Log and Report Discrepancies | Use provided discrepancy log format or defect management tool to report any findings |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Transportation lanes 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.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||