| Status | Approved |
|---|---|
| Owner | |
| Stakeholders |
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.
The transporters/forwarders need to be identified from the existing supplier data in legacy ECC systems. This subset will then be used for data enrichment. The data enrichment will involve collecting or constructing the data to support Transportation management functionality in future S4 HANA system (examples of some of the new fields: Freight Settlement Profile ID, Calculation Profile ID).
Conversion Scope
The scope of this document covers BP role assignment (CRM010) and 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:
- Active transporters (which are suppliers in ECC system)
The data from legacy system excludes:
- Out of scope suppliers (following the relevancy criteria for BP-Suppliers)
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2, WP2, 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 (An initial extract of the relevant data will be provided in google sheet format to assist business). Business needs to construct the data for the transporter/forwarder specific fields in the DCT. | TBD | S/4 HANA | TBD |
The CNV-3007 Business Partners – General (Role 000000) relevancy criteria will also be used for this conversion document.
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 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, LFM1, /SCMB/D_BPTMORGU | 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 | 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, /SCMB/D_BPTMORGU | EKORG, ORGU | EKORG | Purchasing Organization | CHAR | 4 | Mandatory | |
| /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).
| 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:
Data Privacy and Sensitivity
Extraction
- Syniti Migrate connects to the sources.
- 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.
| 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. Examples of some of the new fields: Freight Settlement Profile ID, Calculation Profile ID. | 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 |
| 7 | In every mock rehearsal, there may be new vendors created in the legacy system. If they satisfy steps 1 and 2 above, the delta needs to be appended to the vendors list in the DCT. Business would need to review and construct the data for the delta list. | Data owner (Business), Syniti/ Data Team |
Selection Screen
| 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.
The extracted report will be loaded into the required structure using the DCT.
Delta Data Management: Initial collection will be done via the initial extract and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will need to be identified and appended to the existing records in the DCT.
Please refer to the below Google sheet for the DCT rules.
Business Partners - Transporters/Forwarders DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| 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:
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 Syniti platform
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 | LFA1 relevancy execution in Syniti across both legacy ECC systems | Syniti |
2 | 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 |
3 | Ensure the mapping tables which are needed during transformation have been reviewed and signed off by business. | Business team, Data Team (SCM) |
4 | Obtain DCT Sign-off from Business | Data Team (SCM) |
5 | Generate Pre-Load reports | Data Team (Syniti) |
6 | Review and Validate Error and Preload Reports | Data Team (SCM) |
7 | Log errors as defects, if any and address resolutions. | Data Team (SCM) |
8 | Re-transform and re-validate the Pre-load reports if necessary. | Data Team (SCM), Data Team (Syniti) |
9 | Obtain preload validation sign-off from Business | Business + Functional (SCM) + Data Team (SCM) |
10 | 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 | N/A | zLegacySys | Field to capture legacy source system | N/A | N/A | zLegacySys | Vendor Source system | This will be used together with legacy vendor (carrier) in determining the new (S4) BP number | ||
| DCT | SAP S/4 HANA | BUT000, BUT100, BUT0ID, LFM1, /SCMB/D_BPTMORGU | PARTNER | Business Partner Number | Value mapping: Use the legacy to SAP vendor mapping table to determine the new (S4) BP number | Carrier (Business partner) should exist in SAP. | ||||
| SAP S/4 HANA | BUT100 | RLTYP | BP Role | Default to CRM010 |
| |||||
| 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, /SCMB/D_BPTMORGU | EKORG, ORGU | 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
| 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 | Extract PF2/WP2 source tables – LFA1 | Syniti |
| 2 | Dependent Master Data records for Business Partners - General (Role 000000) is loaded | Functional Team (SCM) + Data Team (SCM) |
| 3 | Ensure DCT tables completeness | Data Team (SCM) |
| 4 | Value Mappings are according to the latest design | Functional Team (SCM) + Data Team (SCM) |
| 5 | SAP Transportation management configuration for Business Partners - Transporters/Forwarders is complete | Functional 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 ID Type, Identification number and Purchasing Organization 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. |
| Verify Relevancy Rules | Verify that the relevancy rules were correctly applied |
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. |
Review Error Reports | Verify that all necessary error reports have been validated, and that errors have been addressed. |
Verify Transformation Rules | Verify that the transformation rules are correct and have been carried out correctly |
Load
The load process includes:
- Execute the automated data load into target system using load tool or product 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
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 BP-Transporter/Forwarders data using Migration Cockpit Object. | Data Team (SCM) |
| 4 | Validate few records loaded by accessing standard transactions from S/4HANA E.g. Fiori app 'Define Business Partner'. | 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
| Item # | Configuration Item |
|---|---|
| 1 | SAP USER profile (SU3) Date and Decimal Notation Formats are in sync with the load format |
| 2 | Purchasing Organization configuration (Enterprise structure) |
| 3 | Define Settlement Profile (Freight Settlement Profile) |
| 4 | Define Calculation Profile (Calculation profile ID) |
| 5 | Define Identification Types (ID Type) |
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 ID Type, Freight Settlement and Calculation Profile | 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
Completeness
| Task | Action |
|---|---|
| Run Fiori app/tcode to check loaded data in SAP | Run Fiori app 'Define Business Partner' 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 Business Partners - Transporters/Forwarders | Access the S/4HANA system (via Fiori app Define Business Partner) 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
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||