Status

Page Status

Owner

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

The data from legacy system includes:

Timeframe considered for the data at the time of Go-Live: current year-2years

The data from legacy system excludes:

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

Product/Material Relevance
• The product or material must be flagged as relevant for export control, customs, or preference.
Scenario-Based Migration Decisions If (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

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

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.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
/SAPSLL/PRCLS	GUID_PRCLS	/SAPSLL/GUID_PRCLS	UUID PRCLS	RAW	16	System Generated
/SAPSLL/PRCLS	GUID_PR	/SAPSLL/GUID_PR	Product UUID	RAW	16	System Generated
/SAPSLL/PRCLS	STCTS	/SAPSLL/STCTS_N	Numbering Scheme	CHAR	10	Mandatory
/SAPSLL/PRCLS

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
/SAPSLL/PRCLS	GUID_PRCLS	/SAPSLL/GUID_PRCLS	UUID PRCLS	RAW	16	System Generated
/SAPSLL/PRCLS	GUID_PR	/SAPSLL/GUID_PR	Product UUID	RAW	16	System Generated
/SAPSLL/PRCLS	STCTS	/SAPSLL/STCTS_N	Numbering Scheme	CHAR	10	Mandatory
/SAPSLL/PRCLS	ENDUSE	/SAPSLL/ENDUSE	End Use	CHAR	5	Conditional
/SAPSLL/PRCLS	DATAB	/SAPSLL/DATAB_N	Valid From	DATS	8	Mandatory
/SAPSLL/PRCLS	DATBI	/SAPSLL/DATBI_N	Valid To	DATS	8	Mandatory
/SAPSLL/PRCLS	CCNGN	/SAPSLL/CCNGN_N	Number	CHAR	30	Mandatory
/SAPSLL/PRCLS	CTSCO	/SAPSLL/CTSCO	Remarks	CHAR	500	Conditional
/SAPSLL/PNTPR	GRVSY	/SAPSLL/GRVSY	Logical System Group	CHAR	10	System Generated
/SAPSLL/PNTPR	PRVSY	/SAPSLL/PRVSY	Product	CHAR	40	Mandatory
/SAPSLL/PNTPR	PRTYP	/SAPSLL/PRTYP	Prod. Cat. fr. Backend System for Legal and Logistics Serv.	CHAR	2	Mandatory
/SAPSLL/PNTPR	GUID_PR	/SAPSLL/GUID_16	GUID 16	RAW	16	System Generated
/SAPSLL/PNTPR	PRNUM	/SAPSLL/PRNUM	Internal Product Number	CHAR	20	System Generated
/SAPSLL/PNTPR	DATAB	/SAPSLL/RPTST	Valid-From Date	DEC	15Mandatory	System Generated
/SAPSLL/PNTPR	DATBI	/SAPSLL/RPTET	Valid -To Date	DEC	15Mandatory	System Generated
/SAPSLL/PNTPR	GUID_PRVSY	/SAPSLL/GUID_16	GUID 16	RAW	16	System Generated
/SAPSLL/PRLRG	GUID_PRLRG	/SAPSLL/GUID_PRLRG	UUID PRLRG	RAW	16	System Generated
/SAPSLL/PRLRG	GUID_PR	/SAPSLL/GUID_PR	Product UUID	RAW	16	System Generated
/SAPSLL/PRLRG	LGREG	/SAPSLL/LGREG_N	Legal Regulation	CHAR	5	Mandatory
/SAPSLL/PRLRG	DATAB	/SAPSLL/DATAB_N	Valid From	DATS	8	Mandatory
/SAPSLL/PRLRG	DATBI	/SAPSLL/DATBI_N	Valid To	DATS	8	Mandatory
/SAPSLL/PRLRG	SECGK	/SAPSLL/SECGK	Peculiarity Code	CHAR	10	Conditional
/SAPSLL/PRLRG	FOCON	/SAPSLL/FOCON	No Control	CHAR	1	Conditional
/SAPSLL/PRLRG	PMAST	/SAPSLL/PMAST	Individual Maintenance	CHAR	1	Conditional

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
NA	NA	NA	NA	NA	NA

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:

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.
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 Description	Team Responsible
1	Legacy System Extraction (WGPOGP) based on the Relevancy Rules from Table: /SAPSLL/PRCLS, /SAPSLL/PNTPR & /SAPSLL/PRLRG	Syniti

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value 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 Name	Field Description	Rule
NA

Extraction Dependencies

NA

Item #Step DescriptionTeam Responsible1Extract data from source systems WGPSyniti2Populate in a report in a Downloadable formatSyniti3Data is validated in ADMM ToolSyWay Data Team5The 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:

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

NA

Extraction Dependencies

Transformation Run Sheet

Item # Step Description Team 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
Team Responsible
1 Extract data from source systems OGP Syniti
2 Populate in a report in a Downloadable format Syniti
3 Data is validated in ADMM Tool SyWay Data Team
5 The 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:

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
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
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 system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	OGP	/SAPSLL/PRCLS	GUID_PRCLS	UUID PRCLS

Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1WGP/SAPSLL/PRCLSGUID_PRCLSUUID PRCLSS/4 HANA GTS/SAPSLL/PRCLSGUID_PRCLSUUID PRCLSSystem Generated 2WGP/SAPSLL/PRCLSGUID_PRProduct UUIDS/4 HANA GTS/SAPSLL/PRCLSGUID_PRProduct UUIDDirect Mapping3WGP/SAPSLL/PRCLSSTCTSNumbering SchemeS/4 HANA GTS/SAPSLL/PRCLSSTCTSNumbering SchemeDirect Mapping4WGP/SAPSLL/PRCLSENDUSEEnd Use

S/4 HANA GTS

/SAPSLL/PRCLS

ENDUSEEnd UseDirect Mapping

GUID_PRCLS	UUID PRCLS	System Generated
2	OGP

5WGP

/SAPSLL/PRCLS

DATAB

GUID_PR

Product UUID

Valid From6WGP/SAPSLL/PRCLSDATBIValid ToS/4 HANA GTS/SAPSLL/PRCLSDATBIValid ToDirect Mapping7WGP

S/4 HANA GTS

/SAPSLL/PRCLS

DATABValid FromDirect Mapping

GUID_PR

Product 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

3

OGP

/SAPSLL/PRCLS

CCNGN

STCTS

Number

Numbering Scheme

S/4 HANA GTS

/SAPSLL/PRCLS

CCNGN

STCTS

Number

Numbering Scheme

Direct Mapping

8

4

WGP

OGP	/SAPSLL/PRCLS

PRGHT

ENDUSE

Proportional Value

End Use

S/4 HANA GTS

/SAPSLL/PRCLS

PRGHT

ENDUSE

Proportional Value

End Use

Direct Mapping

9

5

WGP

OGP	/SAPSLL/PRCLS

CTSCO

DATAB

Remarks

Valid From

S/4 HANA GTS

/SAPSLL/PRCLS

CTSCO

DATAB

Remarks

Valid From

Direct Mapping

10

6

WGP

OGP	/SAPSLL/PRCLS

DRCNANo DRC Applicable

DATBI

Valid To

S/4 HANA GTS

/SAPSLL/PRCLS

DRCNA

DATBI

Valid To

No DRC Applicable

Direct Mapping

15

7

WGP

OGP

/SAPSLL/

PNTPR

PRCLS

GRVSY

CCNGN

Logical System Group

Number

S/4 HANA GTS

/SAPSLL/

PNTPR

PRCLS

GRVSY

CCNGN

Logical System Group

Number

Direct Mapping

16

8

WGP

OGP

/SAPSLL/

PNTPR

PRCLS

PRVSY

CTSCO

Product

Remarks

S/4 HANA GTS

/SAPSLL/

PNTPR

PRCLS

PRVSY

CTSCO

Product

Remarks

Direct Mapping

17

9

WGP

OGP	/SAPSLL/PNTPR

PRTYP

GRVSY

Logical System Group

Prod. Cat. fr. Backend System for Legal and Logistics Serv.

S/4 HANA GTS

/SAPSLL/PNTPR

PRTYPProd. Cat. fr. Backend System for Legal and Logistics Serv.Direct Mapping

GRVSY	Logical System Group	System Generated
10	OGP

18WGP

/SAPSLL/PNTPR

GUID_PR

PRVSY

Product

GUID 16

S/4 HANA GTS

/SAPSLL/PNTPR

GUID_PRGUID 16Direct Mapping

PRVSY	Product	Need to derive the new S/4 HANA Materials from Cross Reference Tables
11	OGP

19WGP

/SAPSLL/PNTPR

PRNUM

PRTYP

Prod. Cat. fr. Backend System for Legal and Logistics Serv.

Internal Product Number

S/4 HANA GTS

/SAPSLL/PNTPR

PRNUMInternal Product NumberDirect Mapping20

PRTYP

Prod. Cat. fr. Backend System for Legal and Logistics Serv.

Direct Mapping

Should always have fixed value of '01'

12

OGP

WGP

/SAPSLL/PNTPR

DATAB

GUID_PR

GUID 16

Valid-From Date

S/4 HANA GTS

/SAPSLL/PNTPR

DATABValid-From DateDirect Mapping

GUID_PR	GUID 16	System Generated
13	OGP

21WGP

/SAPSLL/PNTPR

DATBI

PRNUM

Internal Product Number

Valid -To Date

S/4 HANA GTS

/SAPSLL/PNTPR

DATBIValid -To DateDirect Mapping

PRNUM	Internal Product Number	System Generated
14	OGP

22WGP

/SAPSLL/PNTPR

GUID_PRVSY

DATAB

Valid-From Date

GUID 16

S/4 HANA GTS

/SAPSLL/PNTPR

GUID_PRVSYGUID 16Direct Mapping

DATAB	Valid-From Date	System Generated
15	OGP

23WGP

/SAPSLL/

PRLRG

PNTPR

GUID_PRLRG

DATBI

Valid -To Date

UUID PRLRG

S/4 HANA GTS

/SAPSLL/

PRLRG

PNTPR

GUID_PRLRGUUID PRLRGDirect Mapping

DATBI	Valid -To Date	System Generated
16	OGP

24WGP

/SAPSLL/

PRLRG

PNTPR

GUID_

PR

PRVSY

Product UUID

GUID 16

S/4 HANA GTS

/SAPSLL/

PRLRG

PNTPR

GUID_

PR

PRVSY

Product UUIDDirect Mapping

GUID 16	System Generated
17	OGP

25WGP

/SAPSLL/PRLRG

LGREG

GUID_PRLRG

UUID PRLRG

Legal Regulation

S/4 HANA GTS

/SAPSLL/PRLRG

LGREGLegal RegulationDirect Mapping

GUID_PRLRG	UUID PRLRG	System Generated
18	OGP

26WGP

/SAPSLL/PRLRG

DATAB

GUID_PR

Product UUID

Valid From

S/4 HANA GTS

/SAPSLL/PRLRG

DATABValid FromDirect Mapping

GUID_PR	Product UUID	System Generated
19	OGP

27WGP

/SAPSLL/PRLRG

DATBI

LGREG

Valid To

Legal Regulation

S/4 HANA GTS

/SAPSLL/PRLRG

DATBI

LGREG

Valid To

Legal Regulation

Direct Mapping

28

20

WGP

OGP	/SAPSLL/PRLRG

SECGK

DATAB

Peculiarity Code

Valid From

S/4 HANA GTS

/SAPSLL/PRLRG

SECGK

DATAB

Peculiarity Code

Valid From

Direct Mapping

29

21

WGP

OGP	/SAPSLL/PRLRG

CONGR

DATBI

Grouping

Valid To

S/4 HANA GTS

/SAPSLL/PRLRG

CONGR

DATBI

Grouping

Valid To

Direct Mapping

30

22

WGP

OGP	/SAPSLL/PRLRG

FOCON

SECGK

No Control

Peculiarity Code

S/4 HANA GTS

/SAPSLL/PRLRG

FOCON

SECGK

No Control

Peculiarity Code

Direct Mapping

31

23

WGP

OGP	/SAPSLL/PRLRG

PMAST

FOCON

Individual Maintenance

No Control

S/4 HANA GTS

/SAPSLL/PRLRG

PMAST

FOCON

Individual Maintenance

No Control

Direct Mapping

32

24

WGP

OGP	/SAPSLL/PRLRG

GUID_BOPHDBOP UUID

PMAST

Individual Maintenance

S/4 HANA GTS

/SAPSLL/PRLRG

GUID_BOPHD

PMAST

Individual Maintenance

BOP UUID

Direct Mapping

Transformation Mapping

Mapping Table Name	Mapping Table Description
zLegacyMatnumber	New 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

Task

Action

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:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks

Review Error Reports

Review 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

Task	Action
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

Task	Action
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:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
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
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
NA	NA

Conversion Objects

NA

Object #	Preceding Object Conversion Approach	NA
2019	Materials - Basic View

Error Handling

Error Type	Error Description	Action 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 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

Task	Action
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

Task	Action
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/SDREQHD PNTPR & /SAPSLL/SDREQITPRLRG

Business

Completeness

Task	Action
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

Task	Action
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.

Change log

Change History

limit	10

Nov 10, 2025	Actor	Type	Activity	Version
Approved	MUTHUSAMY-ext, Kunalan	State	changed state to Approved at 2:58 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v18
Edited following Tech Review	MUTHUSAMY-ext, Kunalan	State	gave Minor change approval at 2:58 pm [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Oct 29, 2025
	RAYUDU-ext, Narasimha Kumar	Edit	updated the page at 5:36 pm
Oct 28, 2025
	RAYUDU-ext, Narasimha Kumar	Comment	commented 10:21 am Updated Point 2.
		Edit	updated the page at 10:21 am
		Comment	commented 10:20 am Updated.
		Edit	updated the page at 10:20 am
	NAIR-ext, Divya	Comment	commented 7:51 am OGP will be GTS E4H only not GTS 11.
	NAIR-ext, Divya	Comment	commented 7:22 am This validity is if the product is having no control related to a compliance regulation. But for product classifications with value, it should take into account /SAPSLL/PRCLS- DATAB and /SAPSLL/PRCLS-DATBI

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 8

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Transformation

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log