Purpose

The purpose of this document is to define the conversion approach to create GTS - Supplier/Customer-based LTSD in S/4 HANA.

Long-term supplier declarations (LTSD) proposals are created based on the feeder system documents transferred (purchase orders and/or goods receipts). Users can manage requests for LTSDs to their suppliers in addition to reminders for open requests. Customer-based LTSD refers to an Outbound Long-Term Supplier's Declaration (LTSD) that a company issues to its customers, rather than receives from suppliers. An LTSD is a declaration of preferential origin for goods, and while suppliers provide them to manufacturers, manufacturers (acting as suppliers to their customers) can also issue them to their own customers. These outbound LTSDs are typically based on company's billing documents and confirm that the goods are being sold meet the origin requirements for preferential tariff treatment under free trade agreements.

In SAP GTS (Global Trade Services), GTS - LTSD Request can be requested and managed through various functions. Users can request LTSDs with or without reference to logistics documents, or through an annual run process. The system allows for requesting, reminding, and maintaining LTSDs, including features for mass maintenance and partner material information transfer. 

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 without any transformations.

Conversion Scope

The scope of this document covers the approach for converting active GTS - Supplier/Customer-based LTSD from Legacy Source Systems into S/4HANA following the GTS - Supplier/Customer-based LTSD Master Data Design Standard.

The data from legacy system includes:

1. Data Migrated Current Year -2 Years

The data from legacy system excludes:

1. TBD

Additional Information

Multi-language Requirement

NA

Document Management

NA

Legal Requirement

NA

Special Requirements

NA

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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

1. The data exists. connects to the source and loads the data into . 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 ; 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 . 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)

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

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
3. Load approach: Migration Cockpit using Staging Tables

Load Run Sheet

Load Phase and Dependencies

Pre Cutover

Configuration

Conversion Objects

Error Handling

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.
• GTS - Supplier/Customer-based LTSD is in scope based on data design and any exception requested by business.

See also

Change log