| Status | |
|---|---|
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
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.
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:
- Timeframe considered for the data at the time of Go-Live: current year-2years
- /SAPSLL/PRPREFDATBI ( Valid From )
/SAPSLL/PRPREFDATAB ( Valid To)
- /SAPSLL/PRPREFDATBI ( Valid From )
The data from legacy system excludes:
- TBD
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| WGP | TBD | TBD |
Additional Information
Multi-language Requirement
NA
Document Management
NA
Legal Requirement
NA
Special Requirements
NA
Target Design
With Functional input, document the technical design of the target fields that are in the scope of this document.
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| /SAPSLL/PRPREF | GUID_PRPREF | /SAPSLL/UNID | Primary Key as GUID in 'RAW' Format | RAW | 16 | System Generated |
| /SAPSLL/PRPREF | GUID_PR | /SAPSLL/UNID | Primary Key as GUID in 'RAW' Format | RAW | 16 | System Generated |
| /SAPSLL/PRPREF | GUID_MODEL | /SAPSLL/UNID | Preference Model | RAW | 16 | Mandatory |
| /SAPSLL/PRPREF | LGREG | /SAPSLL/LGREG | Legal Regulation | CHAR | 8 | Mandatory |
| /SAPSLL/PRPREF | PRFTY | /SAPSLL/PRFTY | Type of Preference Data in Product Master | CHAR | 2 | Mandatory |
| /SAPSLL/PRPREF | PRMET | /SAPSLL/PRMET | Comparison Method | CHAR | 2 | Mandatory |
| /SAPSLL/PRPREF | DATBI | DATBI | Valid-To Date | DATS | 8 | Mandatory |
| /SAPSLL/PRPREF | DATAB | DATAB | Valid-From Date | DATS | 8 | Mandatory |
| /SAPSLL/PRPREF | PREFE | /SAPSLL/PREFE | Preference Indicator | CHAR | 8 | Mandatory |
| /SAPSLL/PRPREF | PREKE | /SAPSLL/PREKE | Customs Preference Statement | CHAR | 8 | Mandatory |
| /SAPSLL/PRPREF | QUANT | /SAPSLL/QUANT | Quantity as Floating Point Field | DEC | 15(3) | Mandatory |
| /SAPSLL/PRPREF | QUAUM | /SAPSLL/QUAUM | Unit of Measure | UNIT | 3 | Mandatory |
| /SAPSLL/PRPREF | VALCP | /SAPSLL/VALCP | Preferential Threshold Value | CURR | 15(2) | Conditional |
| /SAPSLL/PRPREF | VALUE_BASIS_VALCP | /SAPSLL/VALBS | Value Basis of Threshold | CURR | 15(2) | Conditional |
| /SAPSLL/PRPREF | VALUE_BASIS_VALCPA | /SAPSLL/VALBS | Second Value Basis | CURR | 15(2) | Conditional |
| /SAPSLL/PRPREF | VALOR | /SAPSLL/VALOR | Positive Share | CURR | 15(2) | Conditional |
| /SAPSLL/PRPREF | VALNO | /SAPSLL/VALNO | Proportion of Dutiable Components | CURR | 15(2) | Conditional |
| /SAPSLL/PRPREF | VLCUR | WAERS | Currency | CUKY | 5 | Mandatory |
| /SAPSLL/PRPREF | MODEL | /SAPSLL/MODEL | Preference Model | CHAR | 8 | Mandatory |
| /SAPSLL/PRPREF | ERNAM | ERNAM | Name of User Who Created the Object | CHAR | 12 | System Generated |
| /SAPSLL/PRPREF | CRTSP | CRTSP | Date and Time When Object Was Created | TIMS | 6 | System Generated |
| /SAPSLL/PRPREF | AENAM | AENAM | Name of User Who Changed the Object | CHAR | 12 | System Generated |
| /SAPSLL/PRPREF | CHTSP | CHTSP | Name of User Who Changed the Object | TIMS | 6 | System Generated |
| /SAPSLL/PRPREF | PURLA | /SAPSLL/PURLA | Preferential Country/Region of Origin | CHAR | 3 | Conditional |
| /SAPSLL/PNTPR | GRVSY | /SAPSLL/PNTPRGRVSY | Logical System Group | CHAR | 4 | Mandatory |
| /SAPSLL/PNTPR | PRVSY | /SAPSLL/PNTPRGRVSY | Product | CHAR | 4 | Mandatory |
| /SAPSLL/PNTPR | PRTYP | /SAPSLL/PNTPRPRTYP | Prod. Cat. fr. Backend System for Legal and Logistics Serv. | CHAR | 4 | Mandatory |
| /SAPSLL/PNTPR | GUID_PR | /SAPSLL/UNID | Primary Key as GUID in 'RAW' Format | RAW | 16 | System Generated |
| /SAPSLL/PNTPR | PRNUM | /SAPSLL/PNTPR | Internal Product Number | CHAR | 10 | System Generated |
| /SAPSLL/PNTPR | DATAB | DATAB | Valid-From Date | DATS | 8 | System Generated |
| /SAPSLL/PNTPR | DATBI | DATBI | Valid -To Date | DATS | 8 | System Generated |
Data Cleansing
All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.
If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| NA |
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
NAExtraction
Extract data from a source into Syniti Migrate. There are 2 possibilities:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti Migrate; 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate
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 (WGP) based on the Relevancy Rules from Table: /SAPSLL/PRPREF & /SAPSLL/PNTPR | Syniti |
Selection Screen
If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.| 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 Object data with exception of some fields which require transformation as mentioned in the transformation rule.<Object> DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| NA |
Extraction Dependencies
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Extract data from source systems WGP | 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 Syniti Migrate to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate
- 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 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 system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | WGP | /SAPSLL/PRPREF | GUID_PRPREF | Primary Key as GUID in 'RAW' Format | S/4 HANA GTS | /SAPSLL/PRPREF | GUID_PRPREF | Primary Key as GUID in 'RAW' Format | Direct Mapping |
| 2 | WGP | /SAPSLL/PRPREF | GUID_PR | Primary Key as GUID in 'RAW' Format | S/4 HANA GTS | /SAPSLL/PRPREF | GUID_PR | Primary Key as GUID in 'RAW' Format | Direct Mapping |
| 3 | WGP | /SAPSLL/PRPREF | GUID_MODEL | Preference Model | S/4 HANA GTS | /SAPSLL/PRPREF | GUID_MODEL | Preference Model | Direct Mapping |
| 4 | WGP | /SAPSLL/PRPREF | LGREG | Legal Regulation | S/4 HANA GTS | /SAPSLL/PRPREF | LGREG | Legal Regulation | Direct Mapping |
| 5 | WGP | /SAPSLL/PRPREF | PRFTY | Type of Preference Data in Product Master | S/4 HANA GTS | /SAPSLL/PRPREF | PRFTY | Type of Preference Data in Product Master | Direct Mapping |
| 6 | WGP | /SAPSLL/PRPREF | PRMET | Comparison Method | S/4 HANA GTS | /SAPSLL/PRPREF | PRMET | Comparison Method | Direct Mapping |
| 7 | WGP | /SAPSLL/PRPREF | DATBI | Valid-To Date | S/4 HANA GTS | /SAPSLL/PRPREF | DATBI | Valid-To Date | Direct Mapping |
| 8 | WGP | /SAPSLL/PRPREF | DATAB | Valid-From Date | S/4 HANA GTS | /SAPSLL/PRPREF | DATAB | Valid-From Date | Direct Mapping |
| 9 | WGP | /SAPSLL/PRPREF | PREFE | Preference Indicator | S/4 HANA GTS | /SAPSLL/PRPREF | PREFE | Preference Indicator | Direct Mapping |
| 10 | WGP | /SAPSLL/PRPREF | PREKE | Customs Preference Statement | S/4 HANA GTS | /SAPSLL/PRPREF | PREKE | Customs Preference Statement | Direct Mapping |
| 11 | WGP | /SAPSLL/PRPREF | QUANT | Quantity as Floating Point Field | S/4 HANA GTS | /SAPSLL/PRPREF | QUANT | Quantity as Floating Point Field | Direct Mapping |
| 12 | WGP | /SAPSLL/PRPREF | QUAUM | Unit of Measure | S/4 HANA GTS | /SAPSLL/PRPREF | QUAUM | Unit of Measure | Direct Mapping |
| 13 | WGP | /SAPSLL/PRPREF | VALCP | Preferential Threshold Value | S/4 HANA GTS | /SAPSLL/PRPREF | VALCP | Preferential Threshold Value | Direct Mapping |
| 14 | WGP | /SAPSLL/PRPREF | VALUE_BASIS_VALCP | Value Basis of Threshold | S/4 HANA GTS | /SAPSLL/PRPREF | VALUE_BASIS_VALCP | Value Basis of Threshold | Direct Mapping |
| 16 | WGP | /SAPSLL/PRPREF | VALUE_BASIS_VALCPA | Second Value Basis | S/4 HANA GTS | /SAPSLL/PRPREF | VALUE_BASIS_VALCPA | Second Value Basis | Direct Mapping |
| 17 | WGP | /SAPSLL/PRPREF | VALOR | Positive Share | S/4 HANA GTS | /SAPSLL/PRPREF | VALOR | Positive Share | Direct Mapping |
| 18 | WGP | /SAPSLL/PRPREF | VALNO | Proportion of Dutiable Components | S/4 HANA GTS | /SAPSLL/PRPREF | VALNO | Proportion of Dutiable Components | Direct Mapping |
| 20 | WGP | /SAPSLL/PRPREF | VLCUR | Currency | S/4 HANA GTS | /SAPSLL/PRPREF | VLCUR | Currency | Direct Mapping |
| 21 | WGP | /SAPSLL/PRPREF | MODEL | Preference Model | S/4 HANA GTS | /SAPSLL/PRPREF | MODEL | Preference Model | Direct Mapping |
| 22 | WGP | /SAPSLL/PRPREF | ERNAM | Name of User Who Created the Object | S/4 HANA GTS | /SAPSLL/PRPREF | ERNAM | Name of User Who Created the Object | Direct Mapping |
| 23 | WGP | /SAPSLL/PRPREF | CRTSP | Date and Time When Object Was Created | S/4 HANA GTS | /SAPSLL/PRPREF | CRTSP | Date and Time When Object Was Created | Direct Mapping |
| 24 | WGP | /SAPSLL/PRPREF | AENAM | Name of User Who Changed the Object | S/4 HANA GTS | /SAPSLL/PRPREF | AENAM | Name of User Who Changed the Object | Direct Mapping |
| 25 | WGP | /SAPSLL/PRPREF | CHTSP | Name of User Who Changed the Object | S/4 HANA GTS | /SAPSLL/PRPREF | CHTSP | Name of User Who Changed the Object | Direct Mapping |
| 26 | WGP | /SAPSLL/PRPREF | PURLA | Preferential Country/Region of Origin | S/4 HANA GTS | /SAPSLL/PRPREF | PURLA | Preferential Country/Region of Origin | Direct Mapping |
| 27 | WGP | /SAPSLL/PNTPR | GRVSY | Logical System Group | S/4 HANA GTS | /SAPSLL/PNTPR | GRVSY | Logical System Group | Direct Mapping |
| 28 | WGP | /SAPSLL/PNTPR | PRVSY | Product | S/4 HANA GTS | /SAPSLL/PNTPR | PRVSY | Product | Need to derive the New SAP S4 HANA Material Number based on the Cross Reference Tables |
| 29 | WGP | /SAPSLL/PNTPR | PRTYP | Prod. Cat. fr. Backend System for Legal and Logistics Serv. | S/4 HANA GTS | /SAPSLL/PNTPR | PRTYP | Prod. Cat. fr. Backend System for Legal and Logistics Serv. | Direct Mapping |
| 30 | WGP | /SAPSLL/PNTPR | GUID_PR | Primary Key as GUID in 'RAW' Format | S/4 HANA GTS | /SAPSLL/PNTPR | GUID_PR | Primary Key as GUID in 'RAW' Format | Direct Mapping |
| 31 | WGP | /SAPSLL/PNTPR | PRNUM | Internal Product Number | S/4 HANA GTS | /SAPSLL/PNTPR | PRNUM | Internal Product Number | Direct Mapping |
| 32 | WGP | /SAPSLL/PNTPR | DATAB | Valid-From Date | S/4 HANA GTS | /SAPSLL/PNTPR | DATAB | Valid-From Date | Direct Mapping |
| 33 | WGP | /SAPSLL/PNTPR | DATBI | Valid -To Date | S/4 HANA GTS | /SAPSLL/PNTPR | DATBI | Valid -To Date | Direct Mapping |
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
| zLegacyMaterial | Legacy Material Number |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure Legacy System tables completeness | Syniti |
2 | Ensure all Transformation mappings are up to date. | Syniti |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| 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
| 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:
|
| 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
The following pre-load validations will be performed by the 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
Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence
Configuration
List the Configurations required before loading can commence
| Item # | Configuration Item |
|---|---|
| TBD | |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| TBD | |
Error Handling
The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management
| 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 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
The following post-load validations will be performed by the 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/PRPREF & /SAPSLL/PNTPR |
Business
The following post-load validations will be performed by the 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 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
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.