Purpose

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

Freight agreements serve as contracts with companies providing transportation services, as well as service providers for transportation related services. They contain links to charge sheets for rates and validity dates. The parties involved in the contract are the purchasing organisation and the carrier.

The freight agreement has a header detail for elements at the header, and then agreement items for different agreements Freight Agreement represents the actual contract with the carrier. Each agreement must have at least one item and calculation sheet assigned to perform charge calculation./Freight forwarder. The Freight Agreement can have 1 to many Calculation Sheets, and each Calculation Sheet can have 1 to many Charge Types.

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

This includes:

• Capturing and using the Freight agreements 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)

There are two key components i.e. Calculation sheet and Rate table which drive important functionality in Freight Agreement and they have to be created in DCT/SAP before they can be referenced in the Freight Agreement.

The below diagram shows the relationship between the different components (the data in the diagram is for illustration purposes).

Image Added

DCT pages should be built for the following components as part of 9053 Freight Agreement object.

• Freight Agreement header and items
• Calculation sheet header and items (this gets referenced in the agreement line item)
• Rate table header and items (this gets referenced in the calculation sheet)

There should be at least one calculation sheet and one rate table in the Freight Agreement.

TM functional team have mentioned that they would create the structure for rate tables in SAP S/4 system as a design activity. These would then be used for uploading the relevant rate table data in SAP using the excel integration feature (to download template and upload the populated data). Data team would create the Freight Agreement and calculation sheet data in SAP as part of data load activities.

The DCT design for rate tables would need to be reviewed at a later stage to see if any adjustments are required for the DCT as a result of the above described approach.

TM and Procurement data owner (business) would need to collaborate closely on maintaining the correct Outline Agreement (Purchase Contract) in the Freight Agreement DCT. 

Additional Information

Multi-language Requirement

Not Applicable.

Document Management

Not Applicable.

Legal Requirement

Not Applicable.

Special Requirements

Not Applicable.

Target Design

The complete information of the key fields that hold the Freight agreements information follows the Master Data Standard document.

The technical design of the target for this conversion approach.

Data Cleansing

Freight agreements 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

Extract data from a source into . There are 2 possibilities:

The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti ADMM. 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

Selection Screen

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for TM Freight Agreement 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.

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

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 product 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) 

Custom load tool will need to be developed for loading rate table, calculation sheet and Freight Agreement data. There is no known standard SAP mass upload tool for Freight Agreement.

The load file format can be finalized when the load tool is developed.

Please refer to the below SAP community post for more information.

https://community.sap.com/t5/supply-chain-management-q-a/creation-of-freight-agreement-using-excel-integration/qaq-p/11756669

Load Run Sheet

Load Phase and Dependencies

Freight agreements data will be loaded in the cutover window.

Configuration

Conversion Objects

Error Handling

As part of the Freight agreements 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.

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.
• Freight agreements 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.
• Any additional key assumptions.

See also

Change log

Workflow history