Versions Compared

Old Version 9

changes.mady.by.user RAYUDU-ext, Narasimha Kumar

Saved on

compared with

New Version Current

changes.mady.by.user RAYUDU-ext, Narasimha Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

Page Status

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. 

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.


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:

  1. Timeframe considered for the data at the time of Go-Live: current year-2 years. Examples are provided in 3) Scenario Based 
    1. REQUESTED_START_DATE
    2. REQUESTED_END_DATE
  2.  LTSD Status Criteria
    •        The LTSD request must be open, pending, or recently completed.
    •        The LTSD must be linked to active suppliers or materials.
  3. Scenario-Based Migration Decisions (For Eg: Go-Live Date: July 2026)
    •        4.1 If the LTSD Requested End Date until December 2026 (same year as Go-Live), migrate the record.
    •        4.2 If the LTSD Requested End Date until December 2027 or later (future years), migrate the record.
    •        4.3 If the LTSD Requested End Date until January 2026 (same year as Go-Live), migrate the record.
    •        4.4 If the LTSD Requested End Date until January 2025, migrate the record to maintain two years of historical data (i.e., keep records from 2024, 2025, and 2026).

The data from legacy system excludes:

  1. Do not migrate declarations that do not meet the above validity, linkage, or cancellation requirements.


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/SAPSLL/SDRHD_GUIDRequest Header UUID-Primary Key (Universal Unique Identifier (UUID)) is linked to Primary key of /SAPSLL/SDREQIT-SDREQIT_UUIDRAW16System
/SAPSLL/SDREQHDREQUEST_NUMBER/SAPSLL/REQNUMLTSD Request-The LTSD RequestCHAR35Mandatory
/SAPSLL/SDREQHDSTATUS/SAPSLL/STATUSRequest Status-The LTSD Request status refers to: 1)ready to send, 2)sent, 3)completed, 4)reminder open, 5)reminder sentCHAR1Mandatory
/SAPSLL/SDREQHDOUTPUT FAILED/SAPSLL/OUTP_FAILEDOutput Failed-If LTSD request fails, the output will take an X (output failed), or blank if undefinedCHAR1Mandatory
/SAPSLL/SDREQHDADMIN_UNIT/SAPSLL/ADMIN_UNITAdministrative Unit-Group of plants mapped from feeder systemCHAR10Mandatory
/SAPSLL/SDREQHDLOGICAL_SYSTEM_GROUP/SAPSLL/LOGSYS_GRPLogical System Group-Logical System Group from where LTSD was requestedCHAR10Mandatory
/SAPSLL/SDREQHDRECEIVER/SAPSLL/RCVRRecipient-Business Partner Supplier who is receiving the LTSD RequestCHAR12Mandatory
/SAPSLL/SDREQHDREQUESTED_START_DATE/SAPSLL/REQSTRTDTRequested From-Requested FromDATS8Mandatory
/SAPSLL/SDREQHDREQUESTED_END_DATE/SAPSLL/REQENDDTRequested To-Requested ToDATS8Mandatory
/SAPSLL/SDREQHDREQUEST_DATE/SAPSLL/REQDATERequested On-Date when LTSD is requestedDATS8Mandatory
/SAPSLL/SDREQHDCONTACT_PERSON/SAPSLL/CONTACT_PERSContact Person-User who requested the LTSDCHAR12Mandatory
/SAPSLL/SDREQHDIS_MIGRATED/SAPSLL/ISMIGRATEDMigrated-For LTSD Requests migrated, this field will be marked as X (Migrated), otherwise blankCHAR1Mandatory
/SAPSLL/SDREQHDREMARK/SAPSLL/REMARKNote-Note/comment if anyCHAR255Mandatory
/SAPSLL/SDREQHDREMINDER_LEVEL/SAPSLL/REM_LEVELReminder 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 requestsNUMC2Mandatory
/SAPSLL/SDREQHDREMINDER_DATE/SAPSLL/REM_DATEReminder Date-Reminder DateDATS8Mandatory
/SAPSLL/SDREQHDCREA_DATE_TIME/SAPSLL/CREA_DTTMTime Stamp-Time Stamp generated by the system when LTSD was createdTIMESTAMP15System Generated
/SAPSLL/SDREQHDCREA_UNAME/SAPSLL/CREA_UNAMEUser Name-User name who generated the LTSD requestCHAR12System Generated
/SAPSLL/SDREQHDLCHG_DATE_TIME/SAPSLL/LCHG_DTTMTime Stamp-Time Stamp generated by the system when LTSD was createdTIMESTAMP15System Generated
/SAPSLL/SDREQHDLCHG_UNAME/SAPSLL/LCHG_UNAMEUser Name-User name who generated the LTSD requestCHAR12System Generated
/SAPSLL/SDREQITSDREQIT_UUID/SAPSLL/UUIDRequest Item UUID-Primary Key (Universal Unique Identifier (UUID)) is linked to Primary key of /SAPSLL/SDREQHD-SDREQHD_UUIDRAW16MandatorySystem Generated
/SAPSLL/SDREQITPREF_TRADE_AGREEEMENT/SAPSLL/PREFTAAgreement-The free trade agreement of the Legal RegulationCHAR10Mandatory
/SAPSLL/SDREQITPRODUCT_UUID/SAPSLL/UUIDProduct UUID-Product UUID linked to key from /SAPSLL/PAGGLOG-PRODUCT_UUIDRAW16System Generated
/SAPSLL/SDREQITSTATUS/SAPSLL/STA_SDREQITItem 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 openCHAR1Mandatory
/SAPSLL/SDREQITSOURCE/SAPSLL/SOURCESource-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)CHAR1Mandatory
/SAPSLL/SDREQITSDREQHD_UUID/SAPSLL/UUIDRequest Header UUID-Universal Unique Identifier (UUID) is linked to key of /SAPSLL/SDREQRF-SDREQHD_UUIDRAW16System Generated


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 & /SAPSLL/SDREQIT 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 – INT-GTS

Syniti

3

Go to Process Area Launch and Process the Object – GTS LTSD Request

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/SDREQHDSDREQHD_UUIDRequest Header UUIDS/4 HANA GTS /SAPSLL/SDREQHDSDREQHD_UUIDRequest Header UUIDThis Field should be used as a Link to Header and Item table
2WGP/SAPSLL/SDREQHDREQUEST_NUMBERLTSD RequestS/4 HANA GTS /SAPSLL/SDREQHDREQUEST_NUMBERLTSD RequestDirect Mapping
3WGP/SAPSLL/SDREQHDSTATUSRequest StatusS/4 HANA GTS /SAPSLL/SDREQHDSTATUSRequest StatusDirect Mapping
4WGP/SAPSLL/SDREQHDOUTPUT FAILEDOutput FailedS/4 HANA GTS /SAPSLL/SDREQHDOUTPUT FAILEDOutput FailedDirect Mapping
5WGP/SAPSLL/SDREQHDADMIN_UNITAdministrative UnitS/4 HANA GTS /SAPSLL/SDREQHDADMIN_UNITAdministrative UnitDirect Mapping
6WGP/SAPSLL/SDREQHDLOGICAL_SYSTEM_GROUPLogical System GroupS/4 HANA GTS /SAPSLL/SDREQHDLOGICAL_SYSTEM_GROUPLogical System GroupDirect Mapping
7WGP/SAPSLL/SDREQHDRECEIVERRecipientS/4 HANA GTS /SAPSLL/SDREQHDRECEIVERRecipientThis is the Supplier Number and need to to derive from Cross Reference Tables.
8WGP/SAPSLL/SDREQHDREQUESTED_START_DATERequested FromS/4 HANA GTS /SAPSLL/SDREQHDREQUESTED_START_DATERequested FromDirect Mapping
9WGP/SAPSLL/SDREQHDREQUESTED_END_DATERequested ToS/4 HANA GTS /SAPSLL/SDREQHDREQUESTED_END_DATERequested ToDirect Mapping
10WGP/SAPSLL/SDREQHDREQUEST_DATERequested OnS/4 HANA GTS /SAPSLL/SDREQHDREQUEST_DATERequested OnDirect Mapping
11WGP/SAPSLL/SDREQHDCONTACT_PERSONContact PersonS/4 HANA GTS /SAPSLL/SDREQHDCONTACT_PERSONContact PersonDirect Mapping
12WGP/SAPSLL/SDREQHDIS_MIGRATEDMigratedS/4 HANA GTS /SAPSLL/SDREQHDIS_MIGRATEDMigratedDirect Mapping
13WGP/SAPSLL/SDREQHDREMARKNoteS/4 HANA GTS /SAPSLL/SDREQHDREMARKNoteDirect Mapping
14WGP/SAPSLL/SDREQHDREMINDER_LEVELReminder LevelS/4 HANA GTS /SAPSLL/SDREQHDREMINDER_LEVELReminder LevelDirect Mapping
15WGP/SAPSLL/SDREQHDREMINDER_DATEReminder DateS/4 HANA GTS /SAPSLL/SDREQHDREMINDER_DATEReminder DateDirect Mapping
16WGP/SAPSLL/SDREQHDCREA_DATE_TIMETime StampS/4 HANA GTS /SAPSLL/SDREQHDCREA_DATE_TIMETime StampDirect Mapping
17WGP/SAPSLL/SDREQHDCREA_UNAMEUser NameS/4 HANA GTS /SAPSLL/SDREQHDCREA_UNAMEUser NameDirect Mapping
18WGP/SAPSLL/SDREQHDLCHG_DATE_TIMETime StampS/4 HANA GTS /SAPSLL/SDREQHDLCHG_DATE_TIMETime StampDirect Mapping
19WGP/SAPSLL/SDREQHDLCHG_UNAMEUser NameS/4 HANA GTS /SAPSLL/SDREQHDLCHG_UNAMEUser NameDirect Mapping
20WGP/SAPSLL/SDREQITSDREQIT_UUIDRequest Item UUIDS/4 HANA GTS /SAPSLL/SDREQITSDREQIT_UUIDRequest Item UUIDThis Field should be used as a Link to Header and Item table
21WGP/SAPSLL/SDREQITPREF_TRADE_AGREEEMENTAgreementS/4 HANA GTS /SAPSLL/SDREQITPREF_TRADE_AGREEEMENTAgreementDirect Mapping
22WGP/SAPSLL/SDREQITPRODUCT_UUIDProduct UUIDS/4 HANA GTS /SAPSLL/SDREQITPRODUCT_UUIDProduct UUIDDirect Mapping
23WGP/SAPSLL/SDREQITSTATUSItem StatusS/4 HANA GTS /SAPSLL/SDREQITSTATUSItem StatusDirect Mapping
24WGP/SAPSLL/SDREQITSOURCESourceS/4 HANA GTS /SAPSLL/SDREQITSOURCESourceDirect Mapping
25WGP/SAPSLL/SDREQITSDREQHD_UUIDRequest Header UUIDS/4 HANA GTS /SAPSLL/SDREQITSDREQHD_UUIDRequest Header UUIDDirect Mapping


Transformation Mapping

Mapping Table NameMapping Table Description
zLegacySupplierSAP S4 HANA BP

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 WGP 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/SDREQHD & /SAPSLL/SDREQIT


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

Change History
limit10