Status
Owner	RAYUDU-ext, Narasimha Kumar
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 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

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WGP	TBD

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.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
/SAPSLL/DOOHD	DOOHD_UUID		Document of Origin UUID	CHAR	18	Mandatory
/SAPSLL/DOOHD	CATEGORY		Document of Origin Category
/SAPSLL/DOOHD	TYPE		Document of Origin Type
/SAPSLL/DOOHD	ADMIN_UNIT		Administrative Unit
/SAPSLL/DOOHD	LOGICAL_SYSTEM_GROUP		Logical System Group
/SAPSLL/DOOHD	PARTNER		Business Partner Number
/SAPSLL/DOOHD	PARTNER_ADRNR		Address Number of Entry in Address File
/SAPSLL/DOOHD	DOC_OF_ORIGIN		Document of Origin
/SAPSLL/DOOHD	DIRECTION		Document of Origin Direction
/SAPSLL/DOOHD	EXT_DOO_REFERENCE		Supplier Document of Origin Reference
/SAPSLL/DOOHD	AGGRGD_PREF_STAT		Aggregated Preference Status
/SAPSLL/DOOHD	ISSUE_DATE		Date of Issue
/SAPSLL/DOOHD	ISSUE_STATUS		Document of Origin - Issue Status
/SAPSLL/DOOHD	OUTPUT FAILED		Output Failed
/SAPSLL/DOOHD	IS_REISSUE		Document of Origin Reissue
/SAPSLL/DOOHD	RELEASE_STATUS		Document of Origin - Release Status
/SAPSLL/DOOHD	CANCELLATION_DATE		Document of Origin - Cancelation Date
/SAPSLL/DOOHD	IS_MIGRATED		Object Originates from Migration
/SAPSLL/DOOHD	PARTNER_ADRNR_REFTYPE		Address Source
/SAPSLL/DOOHD	VALIDITY_START_DATE		LTSD Validity Start
/SAPSLL/DOOHD	VALIDITY_END_DATE		LTSD Validity End
/SAPSLL/DOOHD	HOLD		On Hold
/SAPSLL/DOOHD	REMARK		Note for Document of Origin
/SAPSLL/DOOHD	CONTACT_PERSON		Contact Person (User)
/SAPSLL/DOOHD	EXT_REQ_REFERENCE		Customer LTSD Request Reference
/SAPSLL/DOOHD	IC_PROCESSING_TYPE		Cross-Company-Code Process Type
/SAPSLL/DOOHD	IC_DOOHD_UUID		Document of Origin UUID
/SAPSLL/DOOHD	CREA_DATE_TIME		UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun)
/SAPSLL/DOOHD	CREA_UNAME		User Name
/SAPSLL/DOOHD	LCHG_DATE_TIME		UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun)
/SAPSLL/DOOHD	LCHG_UNAME		User Name
/SAPSLL/DOOHD	DUMMY		Single-Character Flag
/SAPSLL/DOOIT	DOOIT_UUID		Document of Origin Item UUID
/SAPSLL/DOOIT	DOOHD_UUID		Document of Origin UUID
/SAPSLL/DOOIT	PRODUCT_UUID		Product UUID
/SAPSLL/DOOIT	HS_CODE		Commodity Code
/SAPSLL/DOOIT	NUMBER_SCHEME		Numbering Scheme
/SAPSLL/DOOIT	RELEASE_DATE		Release Date
/SAPSLL/DOOIT	RELEASE_STATUS		Release Status
/SAPSLL/DOOIT	AGGRGD_PREF_STAT		Aggregated Preference Status
/SAPSLL/DOOIT	SOURCE		Item Source
/SAPSLL/DOOIT	DUMMY		Single-Character Flag
/SAPSLL/DOOPS	DOOPS_UUID		Preference Statement UUID
/SAPSLL/DOOPS	DOOIT_UUID		Document of Origin Item UUID
/SAPSLL/DOOPS	DOOHD_UUID		Document of Origin UUID
/SAPSLL/DOOPS	PREF_TRADE_AGREEMENT		Agreement
/SAPSLL/DOOPS	ISSUE_STATUS		Issue Status
/SAPSLL/DOOPS	PREF_STMNT_DETN_DATE		Preference Determination Date
/SAPSLL/DOOPS	PROCUREMENT_INDICATOR		Procurement
/SAPSLL/DOOPS	PREF_STATEMENT_CODE		Cust.Pref.Statement
/SAPSLL/DOOPS	INTERNAL_PREF_STATUS		Int.Pref.Statement LTSD
/SAPSLL/DOOPS	PREF_INDICATOR_SCHEME		Schema for Pref. Statements
/SAPSLL/DOOPS	PREF_STMNT_CODE_CHANGED_MNLLY		Changed Manually
/SAPSLL/DOOPS	PREF_MODEL_ID		Preference Model ID
/SAPSLL/DOOPS	SOURCE		Source
/SAPSLL/DOOPS	DUMMY		Single-Character Flag

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.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

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

Req #	Requirement Description	Team Responsible

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

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

Item #	Step Description	Team Responsible

Transformation Rules

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