| 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 - Supplier/Customer-based LTSD in S/4 HANA.
Long-term supplier declarations (LTSD) proposals are created based on the feeder system documents transferred (purchase orders and/or goods receipts). Users can manage requests for LTSDs to their suppliers in addition to reminders for open requests. Customer-based LTSD refers to an Outbound Long-Term Supplier's Declaration (LTSD) that a company issues to its customers, rather than receives from suppliers. An LTSD is a declaration of preferential origin for goods, and while suppliers provide them to manufacturers, manufacturers (acting as suppliers to their customers) can also issue them to their own customers. These outbound LTSDs are typically based on company's billing documents and confirm that the goods are being sold meet the origin requirements for preferential tariff treatment under free trade agreements.
Conversion Scope
The scope of this document covers the approach for converting active GTS - Supplier/Customer-based LTSD from Legacy Source Systems into S/4HANA following the GTS - Supplier/Customer-based LTSD Master Data Design Standard.
The data from legacy system includes:
- Data Migrated Current Year -2 Years
The data from legacy system excludes:
- TBD
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| WGP | 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/DOOHD | DOOHD_UUID | /SAPSLL/UUID | Document of Origin UUID | RAW | 16 | System |
| /SAPSLL/DOOHD | CATEGORY | /SAPSLL/CATEGORY | Document of Origin Category | CHAR | 4 | Mandatory |
| /SAPSLL/DOOHD | TYPE | /SAPSLL/TYPE | Document of Origin Type | CHAR | 4 | Mandatory |
| /SAPSLL/DOOHD | ADMIN_UNIT | /SAPSLL/ADMIN_UNIT | Administrative Unit | CHAR | 10 | Mandatory |
| /SAPSLL/DOOHD | LOGICAL_SYSTEM_GROUP | /SAPSLL/LOGSYS_GRP | Logical System Group | CHAR | 10 | Mandatory |
| /SAPSLL/DOOHD | PARTNER | /SAPSLL/PARTNER | Business Partner Number | CHAR | 12 | Mandatory |
| /SAPSLL/DOOHD | PARTNER_ADRNR | /SAPSLL/ADRNR | Address Number of Entry in Address File | CHAR | 10 | Mandatory |
| /SAPSLL/DOOHD | DOC_OF_ORIGIN | /SAPSLL/DOC_ORIGIN | Document of Origin | CHAR | 35 | Mandatory |
| /SAPSLL/DOOHD | DIRECTION | /SAPSLL/DIRECTION | Document of Origin Direction | CHAR | 1 | Mandatory |
| /SAPSLL/DOOHD | EXT_DOO_REFERENCE | /SAPSLL/EXT_DOO_REF | Supplier Document of Origin Reference | CHAR | 35 | Mandatory |
| /SAPSLL/DOOHD | AGGRGD_PREF_STAT | /SAPSLL/AGGR_PREF_STAT | Aggregated Preference Status | CHAR | 1 | Mandatory |
| /SAPSLL/DOOHD | ISSUE_DATE | /SAPSLL/ISSUE_DATE | Date of Issue | DATS | 8 | Mandatory |
| /SAPSLL/DOOHD | ISSUE_STATUS | /SAPSLL/ISSUE_STATUS | Document of Origin - Issue Status | CHAR | 1 | Mandatory |
| /SAPSLL/DOOHD | OUTPUT FAILED | /SAPSLL/OUTP_FAILED | Output Failed | CHAR | 1 | Mandatory |
| /SAPSLL/DOOHD | IS_REISSUE | /SAPSLL/IS_REISSUE | Document of Origin Reissue | CHAR | 1 | Mandatory |
| /SAPSLL/DOOHD | RELEASE_STATUS | /SAPSLL/RELEASE_STATUS | Document of Origin - Release Status | CHAR | 1 | Mandatory |
| /SAPSLL/DOOHD | CANCELLATION_DATE | /SAPSLL/CANCEL_DATE | Document of Origin - Cancelation Date | DATS | 8 | Mandatory |
| /SAPSLL/DOOHD | IS_MIGRATED | /SAPSLL/ISMIGRATED | Object Originates from Migration | CHAR | 1 | Mandatory |
| /SAPSLL/DOOHD | PARTNER_ADRNR_REFTYPE | /SAPSLL/ADRNR_REFTYPE | Address Source | CHAR | 4 | Mandatory |
| /SAPSLL/DOOHD | VALIDITY_START_DATE | /SAPSLL/VALID_FROM | LTSD Validity Start | DATS | 8 | Mandatory |
| /SAPSLL/DOOHD | VALIDITY_END_DATE | /SAPSLL/VALID_TO | LTSD Validity End | DATS | 8 | Mandatory |
| /SAPSLL/DOOHD | HOLD | /SAPSLL/HOLD | On Hold | CHAR | 1 | Mandatory |
| /SAPSLL/DOOHD | REMARK | /SAPSLL/REMARK | Note for Document of Origin | CHAR | 255 | Mandatory |
| /SAPSLL/DOOHD | CONTACT_PERSON | /SAPSLL/CONTACT_PERS | Contact Person (User) | CHAR | 12 | Mandatory |
| /SAPSLL/DOOHD | EXT_REQ_REFERENCE | /SAPSLL/EXT_REQ_REF | Customer LTSD Request Reference | CHAR | 35 | Mandatory |
| /SAPSLL/DOOHD | IC_PROCESSING_TYPE | /SAPSLL/IC_PROC_TYPE | Cross-Company-Code Process Type | CHAR | 4 | Mandatory |
| /SAPSLL/DOOHD | IC_DOOHD_UUID | /SAPSLL/UUID | Document of Origin UUID | RAW | 16 | System |
| /SAPSLL/DOOHD | CREA_DATE_TIME | /SAPSLL/CREA_DTTM | UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun) | TIMESTAMP | 15 | Mandatory |
| /SAPSLL/DOOHD | CREA_UNAME | /SAPSLL/CREA_UNAME | User Name | CHAR | 12 | Mandatory |
| /SAPSLL/DOOHD | LCHG_DATE_TIME | /SAPSLL/LCHG_DTTM | UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun) | TIMESTAMP | 15 | Mandatory |
| /SAPSLL/DOOHD | LCHG_UNAME | /SAPSLL/LCHG_UNAME | User Name | CHAR | 12 | Mandatory |
| /SAPSLL/DOOHD | DUMMY | /SAPSLL/DUMMY | Single-Character Flag | CHAR | 1 | Mandatory |
| /SAPSLL/DOOIT | DOOIT_UUID | /SAPSLL/UUID | Document of Origin Item UUID | RAW | 16 | System |
| /SAPSLL/DOOIT | DOOHD_UUID | /SAPSLL/UUID | Document of Origin UUID | RAW | 16 | System |
| /SAPSLL/DOOIT | PRODUCT_UUID | /SAPSLL/UUID | Product UUID | RAW | 16 | System |
| /SAPSLL/DOOIT | HS_CODE | /SAPSLL/HS_CODE | Commodity Code | CHAR | 18 | Mandatory |
| /SAPSLL/DOOIT | NUMBER_SCHEME | /SAPSLL/NUM_SCHEME | Numbering Scheme | CHAR | 4 | Mandatory |
| /SAPSLL/DOOIT | RELEASE_DATE | /SAPSLL/REL_DATE | Release Date | DATS | 8 | Mandatory |
| /SAPSLL/DOOIT | RELEASE_STATUS | /SAPSLL/REL_STATUS | Release Status | CHAR | 1 | Mandatory |
| /SAPSLL/DOOIT | AGGRGD_PREF_STAT | /SAPSLL/AGGR_PREF_STAT | Aggregated Preference Status | CHAR | 1 | Mandatory |
| /SAPSLL/DOOIT | SOURCE | /SAPSLL/SOURCE | Item Source | CHAR | 1 | Mandatory |
| /SAPSLL/DOOIT | DUMMY | /SAPSLL/DUMMY | Single-Character Flag | CHAR | 1 | Mandatory |
| /SAPSLL/DOOPS | DOOPS_UUID | /SAPSLL/UUID | Preference Statement UUID | RAW | 16 | System |
| /SAPSLL/DOOPS | DOOIT_UUID | /SAPSLL/UUID | Document of Origin Item UUID | RAW | 16 | System |
| /SAPSLL/DOOPS | DOOHD_UUID | /SAPSLL/UUID | Document of Origin UUID | RAW | 16 | System |
| /SAPSLL/DOOPS | PREF_TRADE_AGREEMENT | /SAPSLL/PREFTA | Agreement | CHAR | 10 | Mandatory |
| /SAPSLL/DOOPS | ISSUE_STATUS | /SAPSLL/ISSUE_STATUS | Issue Status | CHAR | 1 | Mandatory |
| /SAPSLL/DOOPS | PREF_STMNT_DETN_DATE | /SAPSLL/PREF_ST_DET_DATE | Preference Determination Date | DATS | 8 | Mandatory |
| /SAPSLL/DOOPS | PROCUREMENT_INDICATOR | /SAPSLL/PROC_IND | Procurement | CHAR | 1 | Mandatory |
| /SAPSLL/DOOPS | PREF_STATEMENT_CODE | /SAPSLL/PREF_STMT_CODE | Cust.Pref.Statement | CHAR | 4 | Mandatory |
| /SAPSLL/DOOPS | INTERNAL_PREF_STATUS | /SAPSLL/INT_PREF_STATUS | Int.Pref.Statement LTSD | CHAR | 1 | Mandatory |
| /SAPSLL/DOOPS | PREF_INDICATOR_SCHEME | /SAPSLL/PREF_IND_SCHEME | Schema for Pref. Statements | CHAR | 4 | Mandatory |
| /SAPSLL/DOOPS | PREF_STMNT_CODE_CHANGED_MNLLY | /SAPSLL/PREF_STMT_CHG_MNL | Changed Manually | CHAR | 1 | Mandatory |
| /SAPSLL/DOOPS | PREF_MODEL_ID | /SAPSLL/PREF_MODEL_ID | Preference Model ID | CHAR | 10 | System |
| /SAPSLL/DOOPS | SOURCE | /SAPSLL/SOURCE | Source | CHAR | 1 | Mandatory |
| /SAPSLL/DOOPS | DUMMY | /SAPSLL/DUMMY | Single-Character Flag | CHAR | 1 | Mandatory |
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 | 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 - Supplier/Customer-based LTSD | 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 |
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 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 system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | WGP | /SAPSLL/DOOHD | DOOHD_UUID | Document of Origin UUID | S/4 HANA GTS | /SAPSLL/DOOHD | DOOHD_UUID | Document of Origin UUID | Direct Mapping |
| 2 | WGP | /SAPSLL/DOOHD | CATEGORY | Document of Origin Category | S/4 HANA GTS | /SAPSLL/DOOHD | CATEGORY | Document of Origin Category | Direct Mapping |
| 3 | WGP | /SAPSLL/DOOHD | TYPE | Document of Origin Type | S/4 HANA GTS | /SAPSLL/DOOHD | TYPE | Document of Origin Type | Direct Mapping |
| 4 | WGP | /SAPSLL/DOOHD | ADMIN_UNIT | Administrative Unit | S/4 HANA GTS | /SAPSLL/DOOHD | ADMIN_UNIT | Administrative Unit | Direct Mapping |
| 5 | WGP | /SAPSLL/DOOHD | LOGICAL_SYSTEM_GROUP | Logical System Group | S/4 HANA GTS | /SAPSLL/DOOHD | LOGICAL_SYSTEM_GROUP | Logical System Group | Direct Mapping |
| 6 | WGP | /SAPSLL/DOOHD | PARTNER | Business Partner Number | S/4 HANA GTS | /SAPSLL/DOOHD | PARTNER | Business Partner Number | Direct Mapping |
| 7 | WGP | /SAPSLL/DOOHD | PARTNER_ADRNR | Address Number of Entry in Address File | S/4 HANA GTS | /SAPSLL/DOOHD | PARTNER_ADRNR | Address Number of Entry in Address File | Direct Mapping |
| 8 | WGP | /SAPSLL/DOOHD | DOC_OF_ORIGIN | Document of Origin | S/4 HANA GTS | /SAPSLL/DOOHD | DOC_OF_ORIGIN | Document of Origin | Direct Mapping |
| 9 | WGP | /SAPSLL/DOOHD | DIRECTION | Document of Origin Direction | S/4 HANA GTS | /SAPSLL/DOOHD | DIRECTION | Document of Origin Direction | Direct Mapping |
| 10 | WGP | /SAPSLL/DOOHD | EXT_DOO_REFERENCE | Supplier Document of Origin Reference | S/4 HANA GTS | /SAPSLL/DOOHD | EXT_DOO_REFERENCE | Supplier Document of Origin Reference | Direct Mapping |
| 11 | WGP | /SAPSLL/DOOHD | AGGRGD_PREF_STAT | Aggregated Preference Status | S/4 HANA GTS | /SAPSLL/DOOHD | AGGRGD_PREF_STAT | Aggregated Preference Status | Direct Mapping |
| 12 | WGP | /SAPSLL/DOOHD | ISSUE_DATE | Date of Issue | S/4 HANA GTS | /SAPSLL/DOOHD | ISSUE_DATE | Date of Issue | Direct Mapping |
| 13 | WGP | /SAPSLL/DOOHD | ISSUE_STATUS | Document of Origin - Issue Status | S/4 HANA GTS | /SAPSLL/DOOHD | ISSUE_STATUS | Document of Origin - Issue Status | Direct Mapping |
| 14 | WGP | /SAPSLL/DOOHD | OUTPUT_FAILED | Output Failed | S/4 HANA GTS | /SAPSLL/DOOHD | OUTPUT_FAILED | Output Failed | Direct Mapping |
| 15 | WGP | /SAPSLL/DOOHD | IS_REISSUE | Document of Origin Reissue | S/4 HANA GTS | /SAPSLL/DOOHD | IS_REISSUE | Document of Origin Reissue | Direct Mapping |
| 16 | WGP | /SAPSLL/DOOHD | RELEASE_STATUS | Document of Origin - Release Status | S/4 HANA GTS | /SAPSLL/DOOHD | RELEASE_STATUS | Document of Origin - Release Status | Direct Mapping |
| 17 | WGP | /SAPSLL/DOOHD | CANCELLATION_DATE | Document of Origin - Cancelation Date | S/4 HANA GTS | /SAPSLL/DOOHD | CANCELLATION_DATE | Document of Origin - Cancelation Date | Direct Mapping |
| 18 | WGP | /SAPSLL/DOOHD | IS_MIGRATED | Object Originates from Migration | S/4 HANA GTS | /SAPSLL/DOOHD | IS_MIGRATED | Object Originates from Migration | Direct Mapping |
| 19 | WGP | /SAPSLL/DOOHD | PARTNER_ADRNR_REFTYPE | Address Source | S/4 HANA GTS | /SAPSLL/DOOHD | PARTNER_ADRNR_REFTYPE | Address Source | Direct Mapping |
| 20 | WGP | /SAPSLL/DOOHD | VALIDITY_START_DATE | LTSD Validity Start | S/4 HANA GTS | /SAPSLL/DOOHD | VALIDITY_START_DATE | LTSD Validity Start | Direct Mapping |
| 21 | WGP | /SAPSLL/DOOHD | VALIDITY_END_DATE | LTSD Validity End | S/4 HANA GTS | /SAPSLL/DOOHD | VALIDITY_END_DATE | LTSD Validity End | Direct Mapping |
| 22 | WGP | /SAPSLL/DOOHD | HOLD | On Hold | S/4 HANA GTS | /SAPSLL/DOOHD | HOLD | On Hold | Direct Mapping |
| 23 | WGP | /SAPSLL/DOOHD | REMARK | Note for Document of Origin | S/4 HANA GTS | /SAPSLL/DOOHD | REMARK | Note for Document of Origin | Direct Mapping |
| 24 | WGP | /SAPSLL/DOOHD | CONTACT_PERSON | Contact Person (User) | S/4 HANA GTS | /SAPSLL/DOOHD | CONTACT_PERSON | Contact Person (User) | Direct Mapping |
| 25 | WGP | /SAPSLL/DOOHD | EXT_REQ_REFERENCE | Customer LTSD Request Reference | S/4 HANA GTS | /SAPSLL/DOOHD | EXT_REQ_REFERENCE | Customer LTSD Request Reference | Direct Mapping |
| 26 | WGP | /SAPSLL/DOOHD | IC_PROCESSING_TYPE | Cross-Company-Code Process Type | S/4 HANA GTS | /SAPSLL/DOOHD | IC_PROCESSING_TYPE | Cross-Company-Code Process Type | Direct Mapping |
| 27 | WGP | /SAPSLL/DOOHD | IC_DOOHD_UUID | Document of Origin UUID | S/4 HANA GTS | /SAPSLL/DOOHD | IC_DOOHD_UUID | Document of Origin UUID | Direct Mapping |
| 28 | WGP | /SAPSLL/DOOHD | CREA_DATE_TIME | UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun) | S/4 HANA GTS | /SAPSLL/DOOHD | CREA_DATE_TIME | UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun) | Direct Mapping |
| 29 | WGP | /SAPSLL/DOOHD | CREA_UNAME | User Name | S/4 HANA GTS | /SAPSLL/DOOHD | CREA_UNAME | User Name | Direct Mapping |
| 30 | WGP | /SAPSLL/DOOHD | LCHG_DATE_TIME | UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun) | S/4 HANA GTS | /SAPSLL/DOOHD | LCHG_DATE_TIME | UTC Time Stamp in Long Form (YYYMMDDhhmmsmmmuuun) | Direct Mapping |
| 31 | WGP | /SAPSLL/DOOHD | LCHG_UNAME | User Name | S/4 HANA GTS | /SAPSLL/DOOHD | LCHG_UNAME | User Name | Direct Mapping |
| 32 | WGP | /SAPSLL/DOOHD | DUMMY | Single-Character Flag | S/4 HANA GTS | /SAPSLL/DOOHD | DUMMY | Single-Character Flag | Direct Mapping |
| 33 | WGP | /SAPSLL/DOOIT | DOOIT_UUID | Document of Origin Item UUID | S/4 HANA GTS | /SAPSLL/DOOIT | DOOIT_UUID | Document of Origin Item UUID | Direct Mapping |
| 34 | WGP | /SAPSLL/DOOIT | DOOHD_UUID | Document of Origin UUID | S/4 HANA GTS | /SAPSLL/DOOIT | DOOHD_UUID | Document of Origin UUID | Direct Mapping |
| 35 | WGP | /SAPSLL/DOOIT | PRODUCT_UUID | Product UUID | S/4 HANA GTS | /SAPSLL/DOOIT | PRODUCT_UUID | Product UUID | Direct Mapping |
| 36 | WGP | /SAPSLL/DOOIT | HS_CODE | Commodity Code | S/4 HANA GTS | /SAPSLL/DOOIT | HS_CODE | Commodity Code | Direct Mapping |
| 37 | WGP | /SAPSLL/DOOIT | NUMBER_SCHEME | Numbering Scheme | S/4 HANA GTS | /SAPSLL/DOOIT | NUMBER_SCHEME | Numbering Scheme | Direct Mapping |
| 38 | WGP | /SAPSLL/DOOIT | RELEASE_DATE | Release Date | S/4 HANA GTS | /SAPSLL/DOOIT | RELEASE_DATE | Release Date | Direct Mapping |
| 39 | WGP | /SAPSLL/DOOIT | RELEASE_STATUS | Release Status | S/4 HANA GTS | /SAPSLL/DOOIT | RELEASE_STATUS | Release Status | Direct Mapping |
| 40 | WGP | /SAPSLL/DOOIT | AGGRGD_PREF_STAT | Aggregated Preference Status | S/4 HANA GTS | /SAPSLL/DOOIT | AGGRGD_PREF_STAT | Aggregated Preference Status | Direct Mapping |
| 41 | WGP | /SAPSLL/DOOIT | SOURCE | Item Source | S/4 HANA GTS | /SAPSLL/DOOIT | SOURCE | Item Source | Direct Mapping |
| 42 | WGP | /SAPSLL/DOOIT | DUMMY | Single-Character Flag | S/4 HANA GTS | /SAPSLL/DOOIT | DUMMY | Single-Character Flag | Direct Mapping |
| 43 | WGP | /SAPSLL/DOOPS | DOOPS_UUID | Preference Statement UUID | S/4 HANA GTS | /SAPSLL/DOOPS | DOOPS_UUID | Preference Statement UUID | Direct Mapping |
| 44 | WGP | /SAPSLL/DOOPS | DOOIT_UUID | Document of Origin Item UUID | S/4 HANA GTS | /SAPSLL/DOOPS | DOOIT_UUID | Document of Origin Item UUID | Direct Mapping |
| 45 | WGP | /SAPSLL/DOOPS | DOOHD_UUID | Document of Origin UUID | S/4 HANA GTS | /SAPSLL/DOOPS | DOOHD_UUID | Document of Origin UUID | Direct Mapping |
| 46 | WGP | /SAPSLL/DOOPS | PREF_TRADE_AGREEMENT | Agreement | S/4 HANA GTS | /SAPSLL/DOOPS | PREF_TRADE_AGREEMENT | Agreement | Direct Mapping |
| 47 | WGP | /SAPSLL/DOOPS | ISSUE_STATUS | Issue Status | S/4 HANA GTS | /SAPSLL/DOOPS | ISSUE_STATUS | Issue Status | Direct Mapping |
| 48 | WGP | /SAPSLL/DOOPS | PREF_STMNT_DETN_DATE | Preference Determination Date | S/4 HANA GTS | /SAPSLL/DOOPS | PREF_STMNT_DETN_DATE | Preference Determination Date | Direct Mapping |
| 49 | WGP | /SAPSLL/DOOPS | PROCUREMENT_INDICATOR | Procurement | S/4 HANA GTS | /SAPSLL/DOOPS | PROCUREMENT_INDICATOR | Procurement | Direct Mapping |
| 50 | WGP | /SAPSLL/DOOPS | PREF_STATEMENT_CODE | Cust.Pref.Statement | S/4 HANA GTS | /SAPSLL/DOOPS | PREF_STATEMENT_CODE | Cust.Pref.Statement | Direct Mapping |
| 51 | WGP | /SAPSLL/DOOPS | INTERNAL_PREF_STATUS | Int.Pref.Statement LTSD | S/4 HANA GTS | /SAPSLL/DOOPS | INTERNAL_PREF_STATUS | Int.Pref.Statement LTSD | Direct Mapping |
| 52 | WGP | /SAPSLL/DOOPS | PREF_INDICATOR_SCHEME | Schema for Pref. Statements | S/4 HANA GTS | /SAPSLL/DOOPS | PREF_INDICATOR_SCHEME | Schema for Pref. Statements | Direct Mapping |
| 53 | WGP | /SAPSLL/DOOPS | PREF_STMNT_CODE_CHANGED_MNLLY | Changed Manually | S/4 HANA GTS | /SAPSLL/DOOPS | PREF_STMNT_CODE_CHANGED_MNLLY | Changed Manually | Direct Mapping |
| 54 | WGP | /SAPSLL/DOOPS | PREF_MODEL_ID | Preference Model ID | S/4 HANA GTS | /SAPSLL/DOOPS | PREF_MODEL_ID | Preference Model ID | Direct Mapping |
| 55 | WGP | /SAPSLL/DOOPS | SOURCE | Source | S/4 HANA GTS | /SAPSLL/DOOPS | SOURCE | Source | Direct Mapping |
| 56 | WGP | /SAPSLL/DOOPS | DUMMY | Single-Character Flag | S/4 HANA GTS | /SAPSLL/DOOPS | DUMMY | Single-Character Flag | Direct Mapping |
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
| /SAPSLL/DOOHD | Header Table |
| /SAPSLL/DOOIT | Item Table |
| /SAPSLL/DOOPS | Preference Statement Table |
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
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
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 approach: Migration Cockpit using Staging Tables
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 | |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| NA | NA |
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
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/SDREQHD & /SAPSLL/SDREQIT |
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
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- GTS - Supplier/Customer-based LTSD is in scope based on data design and any exception requested by business.
Any additional key assumptions.
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.