You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Status

  Approved

Owner

RAYUDU-ext, Narasimha Kumar 

Stakeholders

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.


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


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WGPTBD


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.

TableFieldData ElementField DescriptionData TypeLengthRequirement
/SAPSLL/DOOHDDOOHD_UUID
Document of Origin UUID
/SAPSLL/DOOHDCATEGORY
Document of Origin Category


/SAPSLL/DOOHDTYPE
Document of Origin Type


/SAPSLL/DOOHDADMIN_UNIT
Administrative Unit


/SAPSLL/DOOHDLOGICAL_SYSTEM_GROUP
Logical System Group


/SAPSLL/DOOHDPARTNER
Business Partner Number


/SAPSLL/DOOHDPARTNER_ADRNR
Address Number of Entry in Address File


/SAPSLL/DOOHDDOC_OF_ORIGIN
Document of Origin


/SAPSLL/DOOHDDIRECTION
Document of Origin Direction


/SAPSLL/DOOHDEXT_DOO_REFERENCE
Supplier Document of Origin Reference


/SAPSLL/DOOHDAGGRGD_PREF_STAT
Aggregated Preference Status


/SAPSLL/DOOHDISSUE_DATE
Date of Issue


/SAPSLL/DOOHDISSUE_STATUS
Document of Origin - Issue Status


/SAPSLL/DOOHDOUTPUT FAILED
Output Failed


/SAPSLL/DOOHDIS_REISSUE
Document of Origin Reissue


/SAPSLL/DOOHDRELEASE_STATUS
Document of Origin - Release Status


/SAPSLL/DOOHDCANCELLATION_DATE
Document of Origin - Cancelation Date


/SAPSLL/DOOHDIS_MIGRATED
Object Originates from Migration


/SAPSLL/DOOHDPARTNER_ADRNR_REFTYPE
Address Source


/SAPSLL/DOOHDVALIDITY_START_DATE
LTSD Validity Start


/SAPSLL/DOOHDVALIDITY_END_DATE
LTSD Validity End


/SAPSLL/DOOHDHOLD
On Hold


/SAPSLL/DOOHDREMARK
Note for Document of Origin


/SAPSLL/DOOHDCONTACT_PERSON
Contact Person (User)


/SAPSLL/DOOHDEXT_REQ_REFERENCE
Customer LTSD Request Reference


/SAPSLL/DOOHDIC_PROCESSING_TYPE
Cross-Company-Code Process Type


/SAPSLL/DOOHDIC_DOOHD_UUID
Document of Origin UUID


/SAPSLL/DOOHDCREA_DATE_TIME
UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun)


/SAPSLL/DOOHDCREA_UNAME
User Name


/SAPSLL/DOOHDLCHG_DATE_TIME
UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun)


/SAPSLL/DOOHDLCHG_UNAME
User Name


/SAPSLL/DOOHDDUMMY
Single-Character Flag


/SAPSLL/DOOITDOOIT_UUID
Document of Origin Item UUID


/SAPSLL/DOOITDOOHD_UUID
Document of Origin UUID


/SAPSLL/DOOITPRODUCT_UUID
Product UUID


/SAPSLL/DOOITHS_CODE
Commodity Code


/SAPSLL/DOOITNUMBER_SCHEME
Numbering Scheme


/SAPSLL/DOOITRELEASE_DATE
Release Date


/SAPSLL/DOOITRELEASE_STATUS
Release Status


/SAPSLL/DOOITAGGRGD_PREF_STAT
Aggregated Preference Status


/SAPSLL/DOOITSOURCE
Item Source


/SAPSLL/DOOITDUMMY
Single-Character Flag


/SAPSLL/DOOPSDOOPS_UUID
Preference Statement UUID


/SAPSLL/DOOPSDOOIT_UUID
Document of Origin Item UUID


/SAPSLL/DOOPSDOOHD_UUID
Document of Origin UUID


/SAPSLL/DOOPSPREF_TRADE_AGREEMENT
Agreement


/SAPSLL/DOOPSISSUE_STATUS
Issue Status


/SAPSLL/DOOPSPREF_STMNT_DETN_DATE
Preference Determination Date


/SAPSLL/DOOPSPROCUREMENT_INDICATOR
Procurement


/SAPSLL/DOOPSPREF_STATEMENT_CODE
Cust.Pref.Statement


/SAPSLL/DOOPSINTERNAL_PREF_STATUS
Int.Pref.Statement LTSD


/SAPSLL/DOOPSPREF_INDICATOR_SCHEME
Schema for Pref. Statements


/SAPSLL/DOOPSPREF_STMNT_CODE_CHANGED_MNLLY
Changed Manually


/SAPSLL/DOOPSPREF_MODEL_ID
Preference Model ID


/SAPSLL/DOOPSSOURCE
Source


/SAPSLL/DOOPSDUMMY
Single-Character Flag



Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System


























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

Req #Requirement DescriptionTeam Responsible













Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set





















Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field NameField DescriptionRule












Extraction Dependencies

Item #Step DescriptionTeam 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 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

Item #Step DescriptionTeam Responsible













Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































Transformation Mapping

Mapping Table NameMapping Table Description








Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible













Pre-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





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













Load Phase and Dependencies

Configuration

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

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





Key Assumptions

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


See also

Change log

Version Published Changed By Comment
CURRENT (v. 2) Oct 17, 2025 15:20 RAYUDU-ext, Narasimha Kumar
v. 9 Oct 15, 2025 19:13 RAYUDU-ext, Narasimha Kumar
v. 8 Oct 15, 2025 19:08 RAYUDU-ext, Narasimha Kumar
v. 7 Oct 13, 2025 10:54 RAYUDU-ext, Narasimha Kumar
v. 6 Oct 09, 2025 12:54 RAYUDU-ext, Narasimha Kumar
v. 5 Oct 09, 2025 12:53 RAYUDU-ext, Narasimha Kumar
v. 4 Oct 03, 2025 09:47 RAYUDU-ext, Narasimha Kumar
v. 3 Oct 03, 2025 09:45 RAYUDU-ext, Narasimha Kumar Transformation Rules
v. 2 Oct 02, 2025 00:42 RAYUDU-ext, Narasimha Kumar
v. 1 Oct 01, 2025 17:47 RAYUDU-ext, Narasimha Kumar

  • No labels