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

Compare with Current View Page History

« Previous Version 4 Next »

Status

  Approved

Owner

RAYUDU-ext, Narasimha Kumar 

Stakeholders

Purpose

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

GTS Preference Status is used to indicate whether a product or transaction qualifies for preferential treatment under international trade agreements (such as free trade agreements or customs unions).

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.

Scope of this includes only legal regulations for preference legal code 06 should be created here. Need to link the legal regulation name from the old GTS system and the new legal regulation name in Syway GTS system 

Conversion Scope

The scope of this document covers the approach for converting active GTS Preference Status from Legacy Source Systems into S/4HANA following the GTS Preference Status Master Data Design Standard.


The data from legacy system includes:

  1. Timeframe considered for the data at the time of Go-Live: current year-2years
    1. /SAPSLL/PRPREFDATBI ( Valid From )
      /SAPSLL/PRPREFDATAB ( Valid To)

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

 WGP
TBDTBD

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/PRPREFGUID_PRPREF/SAPSLL/UNIDPrimary Key as GUID in 'RAW' FormatRAW16System Generated
/SAPSLL/PRPREFGUID_PR/SAPSLL/UNIDPrimary Key as GUID in 'RAW' FormatRAW16System Generated
/SAPSLL/PRPREFGUID_MODEL/SAPSLL/UNIDPreference ModelRAW16Mandatory
/SAPSLL/PRPREFLGREG/SAPSLL/LGREGLegal RegulationCHAR8Mandatory
/SAPSLL/PRPREFPRFTY/SAPSLL/PRFTYType of Preference Data in Product MasterCHAR2Mandatory
/SAPSLL/PRPREFPRMET/SAPSLL/PRMETComparison MethodCHAR2Mandatory
/SAPSLL/PRPREFDATBIDATBIValid-To DateDATS8Mandatory
/SAPSLL/PRPREFDATABDATABValid-From DateDATS8Mandatory
/SAPSLL/PRPREFPREFE/SAPSLL/PREFEPreference IndicatorCHAR8Mandatory
/SAPSLL/PRPREFPREKE/SAPSLL/PREKECustoms Preference StatementCHAR8Mandatory
/SAPSLL/PRPREFQUANT/SAPSLL/QUANTQuantity as Floating Point FieldDEC15(3)Mandatory
/SAPSLL/PRPREFQUAUM/SAPSLL/QUAUMUnit of MeasureUNIT3Mandatory
/SAPSLL/PRPREFVALCP/SAPSLL/VALCPPreferential Threshold ValueCURR15(2)Conditional
/SAPSLL/PRPREFVALUE_BASIS_VALCP/SAPSLL/VALBSValue Basis of ThresholdCURR15(2)Conditional
/SAPSLL/PRPREFVALUE_BASIS_VALCPA/SAPSLL/VALBSSecond Value BasisCURR15(2)Conditional
/SAPSLL/PRPREFVALOR/SAPSLL/VALORPositive ShareCURR15(2)Conditional
/SAPSLL/PRPREFVALNO/SAPSLL/VALNOProportion of Dutiable ComponentsCURR15(2)Conditional
/SAPSLL/PRPREFVLCURWAERSCurrencyCUKY5Mandatory
/SAPSLL/PRPREFMODEL/SAPSLL/MODELPreference ModelCHAR8Mandatory
/SAPSLL/PRPREFERNAMERNAMName of User Who Created the ObjectCHAR12System Generated
/SAPSLL/PRPREFCRTSPCRTSPDate and Time When Object Was CreatedTIMS6System Generated
/SAPSLL/PRPREFAENAMAENAMName of User Who Changed the ObjectCHAR12System Generated
/SAPSLL/PRPREFCHTSPCHTSPName of User Who Changed the ObjectTIMS6System Generated
/SAPSLL/PRPREFPURLA/SAPSLL/PURLAPreferential Country/Region of OriginCHAR3Conditional
/SAPSLL/PNTPRGRVSY/SAPSLL/PNTPRGRVSYLogical System GroupCHAR4Mandatory
/SAPSLL/PNTPRPRVSY/SAPSLL/PNTPRGRVSYProductCHAR4Mandatory
/SAPSLL/PNTPRPRTYP/SAPSLL/PNTPRPRTYP    Prod. Cat. fr. Backend System for Legal and Logistics Serv.CHAR4Mandatory
/SAPSLL/PNTPRGUID_PR/SAPSLL/UNIDPrimary Key as GUID in 'RAW' FormatRAW16System Generated
/SAPSLL/PNTPRPRNUM/SAPSLL/PNTPR    Internal Product NumberCHAR10System Generated
/SAPSLL/PNTPRDATABDATABValid-From DateDATS8System Generated
/SAPSLL/PNTPRDATBIDATBIValid -To DateDATS8System Generated


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
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:

  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/PRPREF & /SAPSLL/PNTPR 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 Preference Status

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/PRPREFGUID_PRPREFPrimary Key as GUID in 'RAW' FormatS/4 HANA GTS /SAPSLL/PRPREFGUID_PRPREFPrimary Key as GUID in 'RAW' Format

Direct Mapping - TBD

2WGP/SAPSLL/PRPREFGUID_PRPrimary Key as GUID in 'RAW' FormatS/4 HANA GTS /SAPSLL/PRPREFGUID_PRPrimary Key as GUID in 'RAW' FormatDirect Mapping - TBD
3WGP/SAPSLL/PRPREFGUID_MODELPreference ModelS/4 HANA GTS /SAPSLL/PRPREFGUID_MODELPreference ModelDirect Mapping
4WGP/SAPSLL/PRPREFLGREGLegal RegulationS/4 HANA GTS /SAPSLL/PRPREFLGREGLegal RegulationDirect Mapping
5WGP/SAPSLL/PRPREFPRFTYType of Preference Data in Product MasterS/4 HANA GTS /SAPSLL/PRPREFPRFTYType of Preference Data in Product Master

Direct Mapping

Allowed values are Preference, Calculation, Vendor

6WGP/SAPSLL/PRPREFPRMETComparison MethodS/4 HANA GTS /SAPSLL/PRPREFPRMETComparison Method

Direct Mapping

Allowed values are 0 to 6

7WGP/SAPSLL/PRPREFDATBIValid-To DateS/4 HANA GTS /SAPSLL/PRPREFDATBIValid-To DateDirect Mapping
8WGP/SAPSLL/PRPREFDATABValid-From DateS/4 HANA GTS /SAPSLL/PRPREFDATABValid-From DateDirect Mapping
9WGP/SAPSLL/PRPREFPREFEPreference IndicatorS/4 HANA GTS /SAPSLL/PRPREFPREFEPreference Indicator

Direct Mapping

Allowed Values are 10 to 66 are depending on the value chosen in customs preference statement

10WGP/SAPSLL/PRPREFPREKECustoms Preference StatementS/4 HANA GTS /SAPSLL/PRPREFPREKECustoms Preference Statement

Direct Mapping

Allowed Values are A, B,C1,C12,C123,C123E,C12E,C13,C13E,C1E,C2,C23,C3,C4,X

11WGP/SAPSLL/PRPREFQUANTQuantity as Floating Point FieldS/4 HANA GTS /SAPSLL/PRPREFQUANTQuantity as Floating Point FieldDirect Mapping
12WGP/SAPSLL/PRPREFQUAUMUnit of MeasureS/4 HANA GTS /SAPSLL/PRPREFQUAUMUnit of MeasureDirect Mapping
13WGP/SAPSLL/PRPREFVALCPPreferential Threshold ValueS/4 HANA GTS /SAPSLL/PRPREFVALCPPreferential Threshold ValueDirect Mapping
14WGP/SAPSLL/PRPREFVALUE_BASIS_VALCPValue Basis of ThresholdS/4 HANA GTS /SAPSLL/PRPREFVALUE_BASIS_VALCPValue Basis of ThresholdDirect Mapping
16WGP/SAPSLL/PRPREFVALUE_BASIS_VALCPASecond Value BasisS/4 HANA GTS /SAPSLL/PRPREFVALUE_BASIS_VALCPASecond Value BasisDirect Mapping
17WGP/SAPSLL/PRPREFVALORPositive ShareS/4 HANA GTS /SAPSLL/PRPREFVALORPositive ShareDirect Mapping
18WGP/SAPSLL/PRPREFVALNOProportion of Dutiable ComponentsS/4 HANA GTS /SAPSLL/PRPREFVALNOProportion of Dutiable ComponentsDirect Mapping
20WGP/SAPSLL/PRPREFVLCURCurrencyS/4 HANA GTS /SAPSLL/PRPREFVLCURCurrencyDirect Mapping
21WGP/SAPSLL/PRPREFMODELPreference ModelS/4 HANA GTS /SAPSLL/PRPREFMODELPreference ModelDirect Mapping
22WGP/SAPSLL/PRPREFERNAMName of User Who Created the ObjectS/4 HANA GTS /SAPSLL/PRPREFERNAMName of User Who Created the ObjectDirect Mapping
23WGP/SAPSLL/PRPREFCRTSPDate and Time When Object Was CreatedS/4 HANA GTS /SAPSLL/PRPREFCRTSPDate and Time When Object Was CreatedDirect Mapping
24WGP/SAPSLL/PRPREFAENAMName of User Who Changed the ObjectS/4 HANA GTS /SAPSLL/PRPREFAENAMName of User Who Changed the ObjectDirect Mapping
25WGP/SAPSLL/PRPREFCHTSPName of User Who Changed the ObjectS/4 HANA GTS /SAPSLL/PRPREFCHTSPName of User Who Changed the ObjectDirect Mapping
26WGP/SAPSLL/PRPREFPURLAPreferential Country/Region of OriginS/4 HANA GTS /SAPSLL/PRPREFPURLAPreferential Country/Region of OriginDirect Mapping
27WGP/SAPSLL/PNTPRGRVSYLogical System GroupS/4 HANA GTS /SAPSLL/PNTPRGRVSYLogical System GroupDirect Mapping
28WGP/SAPSLL/PNTPRPRVSYProductS/4 HANA GTS /SAPSLL/PNTPRPRVSYProductNeed to derive the New SAP S4 HANA Material Number based on the Cross Reference Tables
29WGP/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
30WGP/SAPSLL/PNTPRGUID_PRPrimary Key as GUID in 'RAW' FormatS/4 HANA GTS /SAPSLL/PNTPRGUID_PRPrimary Key as GUID in 'RAW' FormatDirect Mapping - TBD
31WGP/SAPSLL/PNTPRPRNUMInternal Product NumberS/4 HANA GTS /SAPSLL/PNTPRPRNUMInternal Product NumberDirect Mapping
32WGP/SAPSLL/PNTPRDATABValid-From DateS/4 HANA GTS /SAPSLL/PNTPRDATABValid-From DateDirect Mapping
33WGP/SAPSLL/PNTPRDATBIValid -To DateS/4 HANA GTS /SAPSLL/PNTPRDATBIValid -To DateDirect Mapping


Transformation Mapping

Mapping Table NameMapping Table Description
zLegacyMaterialLegacy Material Number






Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible

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

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

Configuration

Item #Configuration Item
TBD




Conversion Objects

Object #Preceding Object Conversion Approach
TBD




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/PRPREF & /SAPSLL/PNTPR


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


See also

Change log

Version Published Changed By Comment
CURRENT (v. 4) Oct 17, 2025 15:17 RAYUDU-ext, Narasimha Kumar
v. 6 Oct 16, 2025 15:14 RAYUDU-ext, Narasimha Kumar Peer Review Comments
v. 5 Oct 16, 2025 10:14 RAYUDU-ext, Narasimha Kumar
v. 4 Oct 14, 2025 18:24 RAYUDU-ext, Narasimha Kumar
v. 3 Oct 14, 2025 18:13 RAYUDU-ext, Narasimha Kumar
v. 2 Oct 13, 2025 11:13 RAYUDU-ext, Narasimha Kumar
v. 1 Oct 10, 2025 18:29 RAYUDU-ext, Narasimha Kumar

  • No labels