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

Compare with Current View Page History

« Previous Version 17 Current »

Status

  Approved

Owner

RAYUDU-ext, Narasimha Kumar 

Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create GTS Classifications in S/4 HANA GTS Edition.

Product classification in SAP GTS (Global Trade Services) is the process of assigning standardized codes to products for international trade. These codes are essential for complying with customs regulations, export controls, and trade agreements.

As part of the Syway program, OGP- 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 Classification from Legacy Source Systems into S/4HANA following the GTS Classifications Master Data Design Standard.

The data from legacy system includes:

  1. Product/Material Relevance
    •        The product or material must be flagged as relevant for export control, customs, or preference.
  2. Scenario-Based Migration Decisions (For Eg: Go-Live Date: July 2026) Fields: /SAPSLL/PRCLS- DATAB - Valid From and /SAPSLL/PRCLS-DATBI - Valid To
    •        1 If the classification end date is December 2026 (same year as Go-Live), migrate the record.
    •        2 If the classification end date is December 2027 or later (future years), migrate the record.
    •        3 If the classification end date is January 2026 (same year as Go-Live), migrate the record.
    •        4 If the classification end date is January 2025, migrate the record to maintain 2 years of historical data (especially if it is linked to a license that is still valid).

List of source systems and approximate number of records 

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

OGPTBDTBD

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/PRCLSGUID_PRCLS/SAPSLL/GUID_PRCLSUUID PRCLSRAW16System Generated
/SAPSLL/PRCLSGUID_PR/SAPSLL/GUID_PRProduct UUIDRAW16System Generated
/SAPSLL/PRCLSSTCTS/SAPSLL/STCTS_NNumbering SchemeCHAR10Mandatory
/SAPSLL/PRCLSENDUSE/SAPSLL/ENDUSEEnd UseCHAR5Conditional
/SAPSLL/PRCLSDATAB/SAPSLL/DATAB_NValid FromDATS8Mandatory
/SAPSLL/PRCLSDATBI/SAPSLL/DATBI_NValid ToDATS8Mandatory
/SAPSLL/PRCLSCCNGN/SAPSLL/CCNGN_NNumberCHAR30Mandatory
/SAPSLL/PRCLSCTSCO/SAPSLL/CTSCORemarksCHAR500Conditional
/SAPSLL/PNTPRGRVSY/SAPSLL/GRVSYLogical System GroupCHAR10System Generated
/SAPSLL/PNTPRPRVSY/SAPSLL/PRVSYProductCHAR40Mandatory
/SAPSLL/PNTPRPRTYP/SAPSLL/PRTYPProd. Cat. fr. Backend System for Legal and Logistics Serv.CHAR2Mandatory
/SAPSLL/PNTPRGUID_PR/SAPSLL/GUID_16GUID 16RAW16System Generated
/SAPSLL/PNTPRPRNUM/SAPSLL/PRNUMInternal Product NumberCHAR20System Generated
/SAPSLL/PNTPRDATAB/SAPSLL/RPTSTValid-From DateDEC15System Generated
/SAPSLL/PNTPRDATBI/SAPSLL/RPTETValid -To DateDEC15System Generated
/SAPSLL/PNTPRGUID_PRVSY/SAPSLL/GUID_16GUID 16RAW16System Generated
/SAPSLL/PRLRGGUID_PRLRG/SAPSLL/GUID_PRLRGUUID PRLRGRAW16System Generated
/SAPSLL/PRLRGGUID_PR/SAPSLL/GUID_PRProduct UUIDRAW16System Generated
/SAPSLL/PRLRGLGREG/SAPSLL/LGREG_NLegal RegulationCHAR5Mandatory
/SAPSLL/PRLRGDATAB/SAPSLL/DATAB_NValid FromDATS8Mandatory
/SAPSLL/PRLRGDATBI/SAPSLL/DATBI_NValid ToDATS8Mandatory
/SAPSLL/PRLRGSECGK/SAPSLL/SECGKPeculiarity CodeCHAR10Conditional
/SAPSLL/PRLRGFOCON/SAPSLL/FOCONNo ControlCHAR1Conditional
/SAPSLL/PRLRGPMAST/SAPSLL/PMASTIndividual MaintenanceCHAR1Conditional


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
NANANANANANA



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 (OGP) based on the Relevancy Rules from Table: /SAPSLL/PRCLS, /SAPSLL/PNTPR & /SAPSLL/PRLRG 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
NANANA

Extraction Dependencies


Item #Step DescriptionTeam Responsible
1Extract data from source systems OGPSyniti
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 Classifications

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
1OGP/SAPSLL/PRCLSGUID_PRCLSUUID PRCLSS/4 HANA GTS/SAPSLL/PRCLSGUID_PRCLSUUID PRCLSSystem Generated
2OGP/SAPSLL/PRCLSGUID_PRProduct UUIDS/4 HANA GTS/SAPSLL/PRCLSGUID_PRProduct UUID

System Generated

Need to link the Legacy product number and S/4 product number. Find the GUID_PR from table /SAPSLL/PNTPR and map it here

3OGP/SAPSLL/PRCLSSTCTSNumbering SchemeS/4 HANA GTS/SAPSLL/PRCLSSTCTSNumbering SchemeDirect Mapping
4OGP/SAPSLL/PRCLSENDUSEEnd UseS/4 HANA GTS/SAPSLL/PRCLSENDUSEEnd UseDirect Mapping
5OGP/SAPSLL/PRCLSDATABValid FromS/4 HANA GTS/SAPSLL/PRCLSDATABValid FromDirect Mapping
6OGP/SAPSLL/PRCLSDATBIValid ToS/4 HANA GTS/SAPSLL/PRCLSDATBIValid ToDirect Mapping
7OGP/SAPSLL/PRCLSCCNGNNumberS/4 HANA GTS/SAPSLL/PRCLSCCNGNNumberDirect Mapping
8OGP/SAPSLL/PRCLSCTSCORemarksS/4 HANA GTS/SAPSLL/PRCLSCTSCORemarksDirect Mapping
9OGP/SAPSLL/PNTPRGRVSYLogical System GroupS/4 HANA GTS/SAPSLL/PNTPRGRVSYLogical System GroupSystem Generated
10OGP/SAPSLL/PNTPRPRVSYProductS/4 HANA GTS/SAPSLL/PNTPRPRVSYProductNeed to derive the new S/4 HANA Materials from Cross Reference Tables
11OGP/SAPSLL/PNTPRPRTYPProd. Cat. fr. Backend System for Legal and Logistics Serv.S/4 HANA GTS/SAPSLL/PNTPRPRTYPProd. Cat. fr. Backend System for Legal and Logistics Serv.

Direct Mapping

Should always have fixed value of '01'

12OGP/SAPSLL/PNTPRGUID_PRGUID 16S/4 HANA GTS/SAPSLL/PNTPRGUID_PRGUID 16System Generated
13OGP/SAPSLL/PNTPRPRNUMInternal Product NumberS/4 HANA GTS/SAPSLL/PNTPRPRNUMInternal Product NumberSystem Generated
14OGP/SAPSLL/PNTPRDATABValid-From DateS/4 HANA GTS/SAPSLL/PNTPRDATABValid-From DateSystem Generated
15OGP/SAPSLL/PNTPRDATBIValid -To DateS/4 HANA GTS/SAPSLL/PNTPRDATBIValid -To DateSystem Generated
16OGP/SAPSLL/PNTPRGUID_PRVSYGUID 16S/4 HANA GTS/SAPSLL/PNTPRGUID_PRVSYGUID 16System Generated
17OGP/SAPSLL/PRLRGGUID_PRLRGUUID PRLRGS/4 HANA GTS/SAPSLL/PRLRGGUID_PRLRGUUID PRLRGSystem Generated
18OGP/SAPSLL/PRLRGGUID_PRProduct UUIDS/4 HANA GTS/SAPSLL/PRLRGGUID_PRProduct UUIDSystem Generated
19OGP/SAPSLL/PRLRGLGREGLegal RegulationS/4 HANA GTS/SAPSLL/PRLRGLGREGLegal RegulationDirect Mapping
20OGP/SAPSLL/PRLRGDATABValid FromS/4 HANA GTS/SAPSLL/PRLRGDATABValid FromDirect Mapping
21OGP/SAPSLL/PRLRGDATBIValid ToS/4 HANA GTS/SAPSLL/PRLRGDATBIValid ToDirect Mapping
22OGP/SAPSLL/PRLRGSECGKPeculiarity CodeS/4 HANA GTS/SAPSLL/PRLRGSECGKPeculiarity CodeDirect Mapping
23OGP/SAPSLL/PRLRGFOCONNo ControlS/4 HANA GTS/SAPSLL/PRLRGFOCONNo ControlDirect Mapping
24OGP/SAPSLL/PRLRGPMASTIndividual MaintenanceS/4 HANA GTS/SAPSLL/PRLRGPMASTIndividual MaintenanceDirect Mapping

Transformation Mapping


Mapping Table NameMapping Table Description
zLegacyMatnumberNew Material Numbers






Transformation Dependencies

List the steps that need to occur before transformation can commence

1

Ensure Legacy System tables completeness

Syniti

2

Ensure Classification file must be uploaded from data provider both compliance and customs. 

SyWay-Functional.

2

Ensure all Transformation mappings are up to date.

Syniti





Pre-Load Validation

Project Team

Completeness

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

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
NANA




Conversion Objects

Object #Preceding Object Conversion Approach
2019Materials - Basic View




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/PRCLS, /SAPSLL/PNTPR & /SAPSLL/PRLRG


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 transform


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 - Classifications is in scope based on data design and any exception requested by business.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 17) Oct 29, 2025 17:36 RAYUDU-ext, Narasimha Kumar
v. 17 Oct 28, 2025 10:21 RAYUDU-ext, Narasimha Kumar
v. 16 Oct 28, 2025 10:20 RAYUDU-ext, Narasimha Kumar
v. 15 Oct 27, 2025 14:40 RAYUDU-ext, Narasimha Kumar
v. 14 Oct 17, 2025 15:07 RAYUDU-ext, Narasimha Kumar
v. 13 Oct 17, 2025 13:44 RAYUDU-ext, Narasimha Kumar
v. 12 Oct 17, 2025 13:39 RAYUDU-ext, Narasimha Kumar
v. 11 Oct 16, 2025 21:01 RAYUDU-ext, Narasimha Kumar
v. 10 Oct 16, 2025 20:52 RAYUDU-ext, Narasimha Kumar
v. 9 Oct 16, 2025 18:12 RAYUDU-ext, Narasimha Kumar

Go to Page History

  • No labels