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 TM-Transportation zones in S/4 HANA TM (Transportation Management).

The transportation zone is a geographical grouping of locations that is used for the purpose of routing. It can be the combination of country, state, postcodes, or individual locations.

 The data for transportation zones in S/4 TM would need to be constructed in data collection template (DCT). The existing legacy data would be provided in google sheet for reference.

Conversion Scope

The scope of this document covers the approach for creating Transportation zones in S/4HANA following the TM Transportation zones Master Data Design Standard. This includes:

• Capturing and using the Transportation zone 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

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT	Creation of TM Transportation zones An initial extract of the transportation zones will be provided in google sheet format to assist business in decision making on including any relevant data from PF2 and WP2.	TBD	S/4 HANA (TM)	TBD

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

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 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
/SCMB/ZONE	ID_ZONE	MATNR	Transportation Zone Name	CHAR	20	Mandatory
/SCMB/ZONET	DESCR		Description	CHAR	40	Mandatory
/SCMB/ZONET	SPRAS		Language Key 8 languages in scope: English, French, Italian and Mandarin and Brazilian Portuguese, German, Spanish and Thai, as per KDD055	CHAR	1	Mandatory
/SCMB/ZONE	TYPE_ZONE		Zone Type	CHAR	1	Mandatory
/SAPAPO/LOC	XPOS		Longitude coordinate	CHAR	15	Optional
/SAPAPO/LOC	YPOS		Latitude coordinate	CHAR	15	Optional
/SAPAPO/LOC	PRECISID		Precision  of a Geo location	CHAR	4	Optional
/SAPAPO/LOC	TZONE		Time Zone	CHAR	6	Optional
/SAPAPO/LOC	ZPOS		Location Altitude	NUM	9,3	Optional
/SAPAPO/LOC	GEO_VALIDITY_END		Validity End of Geo Data	NUM (DATE)		Optional
/SAPAPO/LOC	MATCH_GC		Percentage of accuracy (coordinates)	NUM	3	Optional
/SAPAPO/LOC	GC_LEVEL		Geocoding Level for a Location	NUM	4	Optional
/SAPAPO/LOC	STRATEGY		Strategy to determine the coordinates	CHAR	10	Optional
SCMB/ZONE_D	ID_LOC_EXT		Location Code	CHAR	20	Optional
SCMB/ZONE_D	LOC_TYPE		Location Type	CHAR	4	Optional
SCMB/ZONE_P, SCMB/ZONE_R	COUNTRYISO		Country Key	CHAR	2	Optional
SCMB/ZONE_P	PCODE_FROM		Postal code_from	CHAR	10	Optional
SCMB/ZONE_P	PCODE_TO		Postal code_to	CHAR	10	Optional
SCMB/ZONE_R	REGION		Region (State, Province, County)	CHAR	3	Optional

Data Cleansing

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

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. An initial extract of the relevant Transportation zones will be loaded into a google sheet report to assist business with any rationalization.

If the data does not exist in legacy systems, the data will be manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	SyWay Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team

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 Transportation zone data with exception of some fields which require transformation as mentioned in the transformation rule.

1. The extracted report will be loaded into the required structure using the DCT.
2. Standardization activities (including deduplication, standardization and additions)  will be carried out within the DCT.

Please refer to the below Google sheet for the DCT rules (main DCT page and another page for non English descriptions).

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

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

Transformation Mapping

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

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object is in scope based on data design and any exception requested by business.

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