Purpose

The purpose of this document is to define the conversion approach to create GTS Preference Status in S/4 HANA based on Master Data Standards GTS Preference Status. 

GTS Preference Status is used to indicate whether a product or transaction qualifies for preferential treatment under international trade agreements (such as free trade agreements or customs unions).

As part of the Syway program, WGP - GTS 11.0 will be upgraded to SAP S/4 GTS E4H Edition. For this master data object, the data must be extracted from the current system and loaded into the new GTS E4H system with minimal transformations.

Scope of this includes only legal regulations for preference legal code 06 should be created here. Need to link the legal regulation name from the old GTS system and the new legal regulation name in Syway GTS system 

Conversion Scope

The scope of this document covers the approach for converting active GTS Preference Status from Legacy Source Systems into S/4HANA following the GTS Preference Status Master Data Design Standard.

The data from legacy system includes:

1. Timeframe considered for the data at the time of Go-Live: current year-2years.
   1. /SAPSLL/PRPREFDATBI ( Valid From )
   2. /SAPSLL/PRPREFDATAB ( Valid To)
2. Preference Status Validity
   1.The preference status must be valid and current.
   2.The linked product or material must be active
   3.Only include records associated with Legal Regulation 06.
3. Scenario-Based Migration Decisions (For Eg: Go-Live Date: July 2026)
   1. If the preference status is valid until December 2026 (same year as Go-Live), migrate the record.
   2. If the preference status is valid until December 2027 or later (future years), migrate the record.
   3. If the preference status is valid until January 2026 (same year as Go-Live), migrate the record.
   4. If the preference status is valid until January 2025, migrate the record to maintain two years of historical data (i.e., keep records from 2024, 2025, and 2026).

List of source systems and approximate number of records

Additional Information

Multi-language Requirement

NA

Document Management

NA

Legal Requirement

NA

Special Requirements

NA

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

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.

Conversion Process

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

Extraction

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

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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)

<Object> DCT Rules

Extraction Dependencies

List the steps that need to occur before extraction can commence

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

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

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

Conversion Objects

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

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• The Master Data Standards document is a evolving document where value mappings/validation checks are still being finalized as we are currently in the detailed phase as of October 2025.
• GTS - Preference Status is in scope based on data design and any exception requested by business.

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