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

OwnerRAYUDU-ext, Narasimha Kumar 
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to define GTS - LTSD Request in S/4 HANA GTS Edition.

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. 


Conversion Scope

The scope of this document covers the approach for converting active GTS - LTSD Request from Legacy Source System into GTS S/4HANA following the GTS - LTSD Request Data Design Standard. 

The data from legacy system includes:

LTSD Request status:

  1. Ready to send
  2. Sent
  3. Completed
  4. Reminder open
  5. Reminder sent 

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

WGPTBDTBD

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/SDREQHDSDREQHD_UUID
Request Header UUID-Primary Key (Universal Unique Identifier (UUID)) is linked to Primary key of /SAPSLL/SDREQIT-SDREQIT_UUIDCHAR30Mandatory
/SAPSLL/SDREQHDREQUEST_NUMBER
LTSD Request-The LTSD Request


/SAPSLL/SDREQHDSTATUS
Request Status-The LTSD Request status refers to: 1)ready to send, 2)sent, 3)completed, 4)reminder open, 5)reminder sent


/SAPSLL/SDREQHDOUTPUT FAILED
Output Failed-If LTSD request fails, the output will take an X (output failed), or blank if undefined


/SAPSLL/SDREQHDADMIN_UNIT
Administrative Unit-Group of plants mapped from feeder system


/SAPSLL/SDREQHDLOGICAL_SYSTEM_GROUP
Logical System Group-Logical System Group from where LTSD was requested


/SAPSLL/SDREQHDRECEIVER
Recipient-Business Partner Supplier who is receiving the LTSD Request


/SAPSLL/SDREQHDREQUESTED_START_DATE
Requested From-Requested From


/SAPSLL/SDREQHDREQUESTED_END_DATE
Requested To-Requested To


/SAPSLL/SDREQHDREQUEST_DATE
Requested On-Date when LTSD is requested


/SAPSLL/SDREQHDCONTACT_PERSON
Contact Person-User who requested the LTSD


/SAPSLL/SDREQHDIS_MIGRATED
Migrated-For LTSD Requests migrated, this field will be marked as X (Migrated), otherwise blank


/SAPSLL/SDREQHDREMARK
Note-Note/comment if any


/SAPSLL/SDREQHDREMINDER_LEVEL
Reminder Level-Reminder levels for LTSD are used to manage the sending of reminders to suppliers for pending declarations. This functionality helps ensure timely receipt of declarations by allowing users to set up and manage reminders for outstanding requests


/SAPSLL/SDREQHDREMINDER_DATE
Reminder Date-Reminder Date


/SAPSLL/SDREQHDCREA_DATE_TIME
Time Stamp-Time Stamp generated by the system when LTSD was created


/SAPSLL/SDREQHDCREA_UNAME
User Name-User name who generated the LTSD request


/SAPSLL/SDREQHDLCHG_DATE_TIME
Time Stamp-Time Stamp generated by the system when LTSD was created


/SAPSLL/SDREQHDLCHG_UNAME
User Name-User name who generated the LTSD request


/SAPSLL/SDREQITSDREQIT_UUID
Request Item UUID-Primary Key (Universal Unique Identifier (UUID)) is linked to Primary key of /SAPSLL/SDREQHD-SDREQHD_UUID


/SAPSLL/SDREQITPREF_TRADE_AGREEEMENT
Agreement-The free trade agreement of the Legal Regulation


/SAPSLL/SDREQITPRODUCT_UUID
Product UUID-Product UUID linked to key from /SAPSLL/PAGGLOG-PRODUCT_UUID


/SAPSLL/SDREQITSTATUS
Item Status-Preference request item status: 1)ready to send, 2)sent, 3)response received, 4)completed, 5)reminder sent, 6) canceled, 7) excluded, 8) reminder open


/SAPSLL/SDREQITSOURCE
Source-Source of Product in a Request (1. purchasing document, 2. material document, 3. added manually, 4. purchasing document and material document , 5. annual request run)


/SAPSLL/SDREQITSDREQHD_UUID
Request Header UUID-Universal Unique Identifier (UUID) is linked to key of /SAPSLL/SDREQRF-SDREQHD_UUID



Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
NANANANANA



Conversion Process

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


Data Privacy and Sensitivity

NA


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
1Legacy System Extraction (WGP) based on the Relevancy Rules from Table: /SAPSLL/SDREQHD Syniti










Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
NA




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
NA

Extraction Dependencies

Item #Step DescriptionTeam Responsible
1Extract data from source systems WGPSyniti
2Populate in a report in a Downloadable formatSyniti
3Data is validated in ADMM ToolSyWay Data Team
5The data which has passed validation  will be used for transformation/further processing Business/Data Owners


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

1

Obtain Transformation Rules Sign-off from Business.

SCM Data Team

2

In dspMigrate, select the wave – S4/HANA – P2F-SCM

Syniti

3

Go to Process Area Launch and Process the Object – Characteristics

Syniti

4

Review and Validate Error and Preload Reports

Syniti

5

Execute the transformation to prepare the target tables

Syniti

6

Validate data from pre-load and error reports

Business/Data owner

7

Generate load files

Syniti


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1WGP/SAPSLL/PREVDSDREQHD_UUIDRequest Header UUIDS/4 HANA GTS /SAPSLL/SDREQHDSDREQHD_UUIDRequest Header UUIDDirect Mapping
2WGP/SAPSLL/PREVDREQUEST_NUMBERLTSD RequestS/4 HANA GTS /SAPSLL/SDREQHDREQUEST_NUMBERLTSD RequestDirect Mapping
3WGP/SAPSLL/PREVDSTATUSRequest StatusS/4 HANA GTS /SAPSLL/SDREQHDSTATUSRequest StatusDirect Mapping
4WGP/SAPSLL/PREVDOUTPUT FAILEDOutput FailedS/4 HANA GTS /SAPSLL/SDREQHDOUTPUT FAILEDOutput FailedDirect Mapping
5WGP/SAPSLL/PREVDADMIN_UNITAdministrative UnitS/4 HANA GTS /SAPSLL/SDREQHDADMIN_UNITAdministrative UnitDirect Mapping
6WGP/SAPSLL/PREVDLOGICAL_SYSTEM_GROUPLogical System GroupS/4 HANA GTS /SAPSLL/SDREQHDLOGICAL_SYSTEM_GROUPLogical System GroupDirect Mapping
7WGP/SAPSLL/PREVDRECEIVERRecipientS/4 HANA GTS /SAPSLL/SDREQHDRECEIVERRecipientDirect Mapping
8WGP/SAPSLL/PREVDREQUESTED_START_DATERequested FromS/4 HANA GTS /SAPSLL/SDREQHDREQUESTED_START_DATERequested FromDirect Mapping
9WGP/SAPSLL/PREVDREQUESTED_END_DATERequested ToS/4 HANA GTS /SAPSLL/SDREQHDREQUESTED_END_DATERequested ToDirect Mapping
10WGP/SAPSLL/PREVDREQUEST_DATERequested OnS/4 HANA GTS /SAPSLL/SDREQHDREQUEST_DATERequested OnDirect Mapping
11WGP/SAPSLL/PREVDCONTACT_PERSONContact PersonS/4 HANA GTS /SAPSLL/SDREQHDCONTACT_PERSONContact PersonDirect Mapping
12WGP/SAPSLL/PREVDIS_MIGRATEDMigratedS/4 HANA GTS /SAPSLL/SDREQHDIS_MIGRATEDMigratedDirect Mapping
13WGP/SAPSLL/PREVDREMARKNoteS/4 HANA GTS /SAPSLL/SDREQHDREMARKNoteDirect Mapping
14WGP/SAPSLL/PREVDREMINDER_LEVELReminder LevelS/4 HANA GTS /SAPSLL/SDREQHDREMINDER_LEVELReminder LevelDirect Mapping
15WGP/SAPSLL/PREVDREMINDER_DATEReminder DateS/4 HANA GTS /SAPSLL/SDREQHDREMINDER_DATEReminder DateDirect Mapping
16WGP/SAPSLL/PREVDCREA_DATE_TIMETime StampS/4 HANA GTS /SAPSLL/SDREQHDCREA_DATE_TIMETime StampDirect Mapping
17WGP/SAPSLL/PREVDCREA_UNAMEUser NameS/4 HANA GTS /SAPSLL/SDREQHDCREA_UNAMEUser NameDirect Mapping
18WGP/SAPSLL/PREVDLCHG_DATE_TIMETime StampS/4 HANA GTS /SAPSLL/SDREQHDLCHG_DATE_TIMETime StampDirect Mapping
19WGP/SAPSLL/PREVDLCHG_UNAMEUser NameS/4 HANA GTS /SAPSLL/SDREQHDLCHG_UNAMEUser NameDirect Mapping
20WGP/SAPSLL/PREVDITMSDREQIT_UUIDRequest Item UUIDS/4 HANA GTS /SAPSLL/SDREQITSDREQIT_UUIDRequest Item UUIDDirect Mapping
21WGP/SAPSLL/PREVDITMPREF_TRADE_AGREEEMENTAgreementS/4 HANA GTS /SAPSLL/SDREQITPREF_TRADE_AGREEEMENTAgreementDirect Mapping
22WGP/SAPSLL/PREVDITMPRODUCT_UUIDProduct UUIDS/4 HANA GTS /SAPSLL/SDREQITPRODUCT_UUIDProduct UUIDDirect Mapping
23WGP/SAPSLL/PREVDITMSTATUSItem StatusS/4 HANA GTS /SAPSLL/SDREQITSTATUSItem StatusDirect Mapping
24WGP/SAPSLL/PREVDITMSOURCESourceS/4 HANA GTS /SAPSLL/SDREQITSOURCESourceDirect Mapping
25WGP/SAPSLL/PREVDITMSDREQHD_UUIDRequest Header UUIDS/4 HANA GTS /SAPSLL/SDREQITSDREQHD_UUIDRequest Header UUIDDirect Mapping


Transformation Mapping

Mapping Table NameMapping Table Description
/SAPSLL/PREVDPreference: Long-Term Vendor Declaration - Header
/SAPSLL/PREVDITMPreference: Long-Term Vendor Declaration - Item




Transformation Dependencies

List the steps that need to occur before transformation can commence

1

Ensure Legacy System tables completeness

Syniti

2

Ensure all Transformation mappings are up to date.

Syniti


Pre-Load Validation

Project Team


Completeness

TaskAction
Verify Load File Count

SCM Data Team to verify that the total number of relevant records from the  WGP System is equal to the total number of records in the Preload and Load Sheets.

Verify Consent

Verify the appropriate consents for the records have been obtained by the business/Data Owners and properly recorded


Accuracy

TaskAction

Conversion Accuracy

SCM Data team to verify that all the data in the load table/file is accurate as contents and transformation rules with below checks: 

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
Review Error ReportsReview and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

Completeness

TaskAction
Verify Record Count

Business Data Owner/s to verify that the total number of relevant records in Syniti tool equal to the total number of records in the Preload and Load Sheets.

Verify Consent

Verify that the appropriate consents for the records have been obtained by the business and properly recorded


Accuracy

TaskAction

Conversion Accuracy

Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules.


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

Item #Step DescriptionTeam Responsible

1

Ensure Pre-load sign-offs are obtained.

SCM Data team

2

Go to the load tool and select the correct load Program.

SCM Data team

3

Proceed with Data load.

SCM Data team

4

Validate few records loaded by accessing standard transactions.

SCM Data team

5

Generate the post load reports in the tool.

SCM Data team

6

Log errors as defects, if any and address resolutions. Close defects.

SCM Data team

7

Resolve defects by re-upload and re-generate post load reports if necessary.

SCM Data team

8

Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.

Business

9

Repeat steps 5 to 7 if necessary.

SCM Data team


Load Phase and Dependencies

Pre Cutover

Configuration

Item #Configuration Item
TBD




Conversion Objects

Object #Preceding Object Conversion Approach
NANA




Error Handling

Error TypeError DescriptionAction Taken
Configuration<configuration> is not valid/missing

If it is a missing configuration item, then engage Functional team to expedite and fix the error in the system.

Invalid Data

<parameter> is not valid.

The parameter entry needs to be reviewed

If it is an invalid data, business needs to review and correct the source of the data either in OGP or if it’s mapped in DCT.

Technical Setup

Interface / Connection issue within target system’s landscape

N/A – the data will be loaded directly to S/4HANA GTS System environment


Post-Load Validation

Project Team

Completeness

TaskAction
Verify the count

Verify that the record count in the post-load file is the same as the record count based on the relevancy (including any deduplication) results 


Accuracy

TaskAction

Data Accuracy

SCM Data team to verify that all the data in the post load table/file is accurate as per signed-off transformation rules

Error Reports

Verify that all necessary error reports have been validated, and that errors have been addressed.

Data Consistency

Verify that the data loaded is correctly reflected in Table: /SAPSLL/PREVD & /SAPSLL/PREVDITM


Business

Completeness

TaskAction

Verify Count

Verify that the record count in the post load file is the same as the record count based on the relevancy (including deduplication) results

Validate Loaded Data

Validate, as per the load files signed-off, that all records were created


Accuracy

TaskAction

Data Accuracy

Verify that all the data in the S/4HANA GTS table is accurate as per signed-off transformation rules


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 September 2025.
  • GTS - LTSD Request 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 27, 2025 10:40 RAYUDU-ext, Narasimha Kumar
v. 9 Oct 27, 2025 10:39 RAYUDU-ext, Narasimha Kumar Corrections from Functional
v. 8 Oct 17, 2025 15:13 RAYUDU-ext, Narasimha Kumar
v. 7 Oct 16, 2025 12:57 RAYUDU-ext, Narasimha Kumar
v. 6 Oct 15, 2025 18:55 RAYUDU-ext, Narasimha Kumar
v. 5 Oct 13, 2025 18:18 RAYUDU-ext, Narasimha Kumar
v. 4 Oct 13, 2025 10:53 RAYUDU-ext, Narasimha Kumar
v. 3 Oct 02, 2025 14:43 RAYUDU-ext, Narasimha Kumar
v. 2 Sept 29, 2025 21:06 RAYUDU-ext, Narasimha Kumar
v. 1 Sept 29, 2025 17:16 RAYUDU-ext, Narasimha Kumar

  • No labels