Status
Owner	OMER-ext, Mohammed
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach to create Business Partners - Transporters/Forwarders in S/4 HANA.

Transporters/Forwarders (Carriers) are used in a Freight Order (FO) during the transport planning process, the carrier represents the party contracted to supply the service and equipment to deliver the freight service. Carriers are represented as supplier business partners in the ERP with the role of carrier assigned. When the carrier role is assigned to the business partner it becomes available for use as a carrier in SAP Transportation Management (TM), additionally the carrier role has the transport data tab which shows transportation relevant information, such as the standard carrier alpha code for the carrier.

<Assumption> The transporters/forwarders would be identified from the suppliers in ECC systems (subset of suppliers) and the carrier specific information would be collected in DCT and loaded to the business partner in S/4 HANA with carrier role.

Conversion Scope

The scope of this document covers the approach for converting active Transporters/Forwarders from Legacy Source Systems into S/4HANA following the BP-Transporters/Forwarders Master Data Design Standard. This includes:

• Capturing and using the BP-Transporter/Forwarder specific 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. Active transporters (which are suppliers in ECC system)

The data from legacy system excludes:

1. Out of scope suppliers (following the relevancy criteria for BP-Suppliers)

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT	Active transporters/forwarders from in-scope suppliers data (subset). This is referring to i) The output of relevancy criteria for Vendor master data (CNV-3007 Business Partners - General). ii) This list will be filtered based on a field in legacy vendor data and that filtered data should be populated in the DCT. Business needs to construct the data for the transporter/forwarder specific fields in the DCT.	TBD	S/4 HANA	TBD

Additional Information

Multi-language Requirement

Not Applicable.

Document Management

Not Applicable.

Legal Requirement

Not Applicable.

Special Requirements

Not Applicable.

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

The complete information of the key fields that hold the Business Partners - Transporters/Forwarders 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	Notes
BUT000, BUT100, BUT0ID, /SCMB/D_BPTMSLCT	PARTNER	PARTNER	Business Partner Number	CHAR	10	Mandatory	Automatically determined by the system when creating the Bussiness Partner.
BUT100	RLTYP	RLTYP	BP Role	CHAR	6	Mandatory	Role needs to be CRM010 to be considered for Transportation.
BUT000	NAME_ORG1	NAME_ORG1	Vendor/Carrier name	CHAR	40	Mandatory
ADRC	STREET	STREET	Street	CHAR	60	Mandatory
ADRC	HOUSE_NUM1	HOUSE_NUM1	House Number	CHAR	10	Mandatory
ADRC	POST_CODE1	POST_CODE1	Postal Code	CHAR	10	Mandatory
ADRC	CITY1	CITY1	City	CHAR	40	Mandatory
ADRC	COUNTRY	COUNTRY	Country	CHAR	3	Mandatory
ADRC	REGION	REGION	Region	CHAR	3	Mandatory
ADRC	TIME_ZONE	TIME_ZONE	Time Zone	CHAR	6	Mandatory
ADR6	SMTP_ADDR	SMTP_ADDR	Email	CHAR	241	Mandatory
BUT0ID	TYPE	TYPE	ID Type	CHAR	6	Mandatory	Filled by user. Standard ones to be used are TM0001 and BUP006. Additional ones could be created in SPRO in order to accommodate the external carrier IDs from external 3rd Party Apps like Transwide, CASS and TMS4S.
BUT0ID	IDNUMBER	IDNUMBER	Identification Number	CHAR	60	Mandatory	External ID to be used when integrating with other systems. Example: SAP TM integrated with E2Open. Same carrier can have a ID in S4 Syensqo's system but a different one in E2Open.
LFM1	EKORG	EKORG	Purchasing Organization	CHAR	4	Mandatory
/SCMB/D_BPTMSLCT	SLC		Transportation Service Level - Carrier	CHAR	2	Mandatory
/SCMB/D_BPTMSLCT	DESCRIPTION		Service Level code description	CHAR	40	Optional
/SCMB/D_BPTMORGU	SD_PRF_ID	SD_PRF_ID	Freight Settlement Profile ID	CHAR	10	Conditional	Only necessary of the Business Partner has a specific way to settle charges. In PPOME the Purchasing Organization has a Charge Profile that considers the generic FSD Prf ID. In case of a specific settlement as mentioned, it could be possible to create a specific FSD Prf ID per carrier. Freight Settlement Profile ID and Calculation Profile ID will be created in SPRO and then added here in case of Localizations. From a Core Model perspective, it will not be used unless there is a country that deviates from the Core Model for any reason.
/SCMB/D_BPTMORGU	CALC_PRF_ID	CALC_PRF_ID	Calculation Profile ID	CHAR	10	Conditional	Only necessary of the Business Partner has a specific way to calculate charges. In PPOME the Purchasing Organization has a Charge Profile that considers the generic Calculation Prf ID. In case of a specific calculation as mentioned, it could be possible to create a specific Calculation Prf ID per carrier.

Data Cleansing

Business Partners - Transporters/Forwarders 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.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
N/A	N/A	N/A	N/A	N/A	N/A

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

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

1. Syniti Migrate connects to the sources.
2. A subset of the Vendor master data (Business partners - General view) will be populated in the DCT for business to populate transporter/forwarder specific data.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
Legacy data extract and DCT steps
1	Take vendor general data (below fields) from the output of relevancy criteria for Vendor master data (CNV-3007 Business Partners - General). This should be across PF2 and WP2 systems. BUT000-BPEXT BUT000-BU_GROUP BUT000-NAME_ORG1 BUT000-NAME_ORG2	Syniti
2	Filter the data further based on ECC data field LFA1-ZZR_DOMAIN = 8.	Syniti
3	Populate the output of step 2 in BP-Transporter/Forwarder DCT.	Syniti
4	Business to populate the BP-Transporter/Forwarder specific data in DCT.	Data owner (Business)
5	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
6	The data which has passed validation checks in DCT will be used for transformation/further processing.	Syniti

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Business Partners - Transporters/Forwarders 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.

Business Partners - Transporters/Forwarders DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Ensure Syniti has the necessary connection and access to legacy systems	Syniti
2	Ensure that create, change and deletion of master data is freeze in legacy Production system	Legacy IT

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

Item #	Step Description	Team Responsible
1	Capture the data for Business Partners - Transporters/Forwarders 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	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

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.

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic	Notes
	DCT
	DCT				SAP S/4 HANA	BUT000, BUT100, BUT0ID, /SCMB/D_BPTMSLCT	PARTNER	Business Partner Number	Direct Mapping	BP should exist in SAP.
	DCT				SAP S/4 HANA	BUT0ID	TYPE	ID Type	Direct Mapping
	DCT				SAP S/4 HANA	BUT0ID	IDNUMBER	Identification Number	Direct Mapping
	DCT				SAP S/4 HANA	LFM1	EKORG	Purchasing Organization	Direct Mapping
	DCT				SAP S/4 HANA	/SCMB/D_BPTMORGU	SD_PRF_ID	Freight Settlement Profile ID	Direct Mapping
	DCT				SAP S/4 HANA	/SCMB/D_BPTMORGU	CALC_PRF_ID	Calculation Profile ID	Direct Mapping

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

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Field Name	Mapping Table Name	Mapping Table Description
partner	Vendor Number	LIFNR: Old Vendor Code to New Vendor Code cross reference

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 Business Partners - Transporters/Forwarders is complete	Functional Team (SCM)
4	Dependent Master Data records for Locations is loaded	Functional Team (SCM) + Data Team (SCM)

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the 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 Transportation zone name, description and Zone type 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: Mandatory Fields Field and Value Mapping Correctness Null Checks   4. Text Length 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

The following pre-load validations will be performed by the 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:

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 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 zones using Function_Loader_Inlay program or Custom Migration Cockpit Object.	Data Team (SCM)
4	Validate few records loaded by accessing standard transactions from S/4HANA E.g. Fiori app 'Define Transportation Zone'.	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

Business Partners - Transporters/Forwarders data will be loaded in the pre-cutover window.

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
3007	CNV-3007 Business Partners - General (Role 000000)

Error Handling

As part of the Business Partners - Transporters/Forwarders 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 Business Partners - Transporters/Forwarders load.

Error Type	Error Description	Action Taken
Configuration	Invalid or missing Control Strategy and Geocoding levels	Engage Functional team to expedite and fix the error in the system
Formatting Errors	One or more key fields are incorrectly formatted	Ensure formatting is done correctly (e.g., leading zeros). (Leading zero requirements will be confirmed when loading tool is available/tested)
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

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
Run Fiori app/tcode to check loaded data in SAP	Run Fiori app 'Define Transportation zone' 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

The following post-load validations will be performed by the 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 Business Partners - Transporters/Forwarders	Access the S/4HANA system (via Fiori app Define Transportation zone) to view loaded Business Partners - Transporters/Forwarders

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 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.
• Business Partners - Transporters/Forwarders 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

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