| Status | Revision in Progress |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to upload data in S/4 HANA. This file is aligned with the Conversion Specification Guidelines
---CHECKLIST - DATA TEAM---
- 1) Legacy systems (Logical Source and Target Systems are identified)
- 2) Extraction methods and file types
- 3) Scope relevancy criteria
- 4) Target structure/ Rules
- 5) MDS links
- 6) Cleansing rules
- 6a) Cleansing reports with technical information
- 6b) Profiling
- 6c) Cleansing reports which you need to be developed by Syniti
- 6d) Deduplication (with technical details of Table-Fields, Conditions)
- 6e) Frequency of running reports
- 7) Transformation - and for this DOMD template must be populate and final version of DOMD template should be copied to Transformation section in CSpecs
- 8) Configuration/Value mapping file link
- 9) Value Mappings (Data Mapping is provided for mappings which are not obvious to a suitably-skilled and experienced developer)
- 10) Load template link
- 11) Loading method (Processing Type is specified, i.e. Direct Input, BAPI, IDoc, Web Service, OData API, etc.)
- 12) Loading sequence or dependency
- 13Error handling requirements are specified / including alerting requirement / expected action on failure.
- 13) Data Analysis
- 14) Pre load validation
- 15) Post load validation
- 16) any Exceptions (Data Mapping is provided for mappings which are not obvious to a suitably-skilled and experienced developer)
- 17)Application log requirement if applicable to be specified.
- 18) Signoff
Conversion Scope
The scope of this document covers the approach for converting active Purchasing Info Records and Purchasing Conditions from legacy SAP ECC systems (PF2, WP2) into SAP S/4HANA, following the Procurement Master Data Design Standard.
For Syensqo, Info Records will be migrated to support operational purchasing, sourcing strategies, and integration with Ariba. These records will be validated, cleansed, and created centrally using the defined template and mapped fields.
From the current system landscape, Info Record data exists separately in the legacy systems (PF2 and WP2), with potential discrepancies in vendors, materials, pricing conditions. Harmonization and validation are required to ensure accurate and consolidated data in S/4HANA. While PF2 and WP2 serve as source systems, extensive mapping and transformation logic will be necessary to produce properly formatted load templates in line with the target design.
List of source systems and approximate number of records
Source | Scope | Source Approx No. of Records | Target System | Target ApproxNo. of Records |
|---|---|---|---|---|
QF2 | An initial extract of the relevant data will be provided in Google Sheet format to assist business in decision making on including any relevant data from Source Systems. | Info Records >>>26.161 (EINA) Info Records >>> 34.844 (EINE) Services >>> 12.038 (ASMD) | S4H | Info Records >>>26.161 (EINA)Info Records >>> 34.844 (EINE)Services >>> 12.038 (ASMD) as DCT |
WQ2 | Info Records >>> 121.916 (EINA) Info Records >>> 126.651 (EINE) Services >>> 2.892 (ASMD) | S4H | Info Records >>> 121.916 (EINA)Info Records >>> 126.651 (EINE)Services >>> 2.892 (ASMD) as DCT |
Additional Information
MDS Documents
Data Extraction
Data has been extracted from Production and files are kept here:
Extraction/Transformation Methods and File Types
Data is Extracted and Transformed by Syniti ADM, the staging area of the Migration Cockpit will be updated by Syniti.Relevancy Rules: PIRs from Source ECC → PIRs to Target S4/Hana [rules are aligned with Relevancy Criteria (Approved by BL)]
Core Relevancy Rules (Functional View)
In-Scope Vendors, Materials, Purchasing Organizations, and Plants
Included: Only Purchasing Info Records (PIRs) linked to vendors, materials, purchasing organizations, and plants that are defined as in scope in the corresponding MDS views
Excluded: PIRs marked for deletion or blocked, and pricing conditions that are expired or with a net price equal to zero are relevant to be excluded from Data Migration.
Activity and Usage
PIRs are considered relevant if they were used within the last four years, or if they are not marked for deletion or blocked, even when their validity end date is in the past
This approach is applied because expiry dates are not always consistently maintained in legacy systems
Pricing Data
Only PIRs with valid and non-expired pricing conditions are migrated
Net price (KONP-KBETR) must be greater than zero
Hierarchy
PIRs may exist at either Plant level or Purchasing Organization level
Both levels are considered valid provided they comply with the relevancy and pricing criteria
Contracts Supersede PIRs
When a contract exists in the target system with the same combination of Vendor | Material | Purchasing Organization | Plant, the contract takes precedence
In such cases, the corresponding Info Record (with the same key) must be excluded from migration, as the Plant-level contract governs the purchasing conditions
The only exception is for consignment scenarios, where PIRs remain mandatory even when a contract exists
Consignment Exception
For consignment contracts, the PIR is still required and must be created in the target system.
- Metadata/Qualification: There's a note of caution that PIRs in some divisions store essential metadata (like qualification data, parts numbers, comments about supplier qualification). The rule is to ensure such PIRs are not lost—validation from business is required to keep valuable metadata.
Additional Exclusion Criteria
Info Records linked to out-of-scope Vendors, Materials, Purchasing Organizations, or Plants are excluded
PIRs with no valid condition record or only expired conditions are excluded
PIRs where a Plant-level Contract already exists in the target system (Syniti to check in the stagging areas) for the same Vendor | Material | Purchasing Organization | Plant are excluded, as the contract manage all procurement conditions
Duplicate PIRs (same keys and identical pricing) must be consolidated into a single unique entry prior to migration
Complementary Info
Material is flagged as in scope according to MDS CNV-2019 Materials – Basic Data View
Vendor is flagged as in scope according to MDS CNV-3007 Business Partners – General (Role 000000)
Purchasing Organization (EINE.EKORG) is in scope based on enterprise structure mapping
Plant (EINE.WERKS) is in scope, or may be blank (initial)
Relevancy Rules: Service Master from Source ECC → PIRs to Target S4/Hana [rules are aligned with Relevancy Criteria (Approved by BL)]
Apply the data conversion defined in the DOMD file. For Service master records and Service materials (ASMD and MARA table), the Data Collection Template (DCT) must be completed by the Business. Based on the collected data, a decision is required on whether to migrate these services as Purchasing Info Records (PIRs) or as Contracts.
- Service Masters
Data will be captured in DCT - Data Collection Template
List of Service master records will be provided by functional leads (Dean and Anjali) after validation with Business and all PODs.
Pricing data for service masters will be collected in DCT and will be created as contracts or info records based on business confirmation.
Multi-language Requirement
Languages to be extracted (available on Source Systems)
SAP standard supports all ISO languages, ensure that all standard languages are considered in scope.
Languages to don't be extracted
The below language has been excluded from SyWay scope.
International Version | Description |
TH | Thai language |
Data Deduplication
Deduplication is not applied directly to this object. However, if either the vendor or the material is present on multiple systems, the data must be clubbed into a unique combination of Vendor|Material|PurchPrg|Plant in order to avoid inconsistencies.
Document Management
N/A
Legal Requirement
Minor efforts with taxation mapping are foreseen for some specific countries having specific taxations, the topic is limited to have the tax codes mapping (from Old to New tax code - functional team task).
Special Requirements
Processing Type ETL:
The extraction and transformation will be done by Syniti, while the loading will be executed by a Standard tool of SAP Migration Cockpit.
E - Extraction: Data will be Extracted from at least two source systems. This process will be executed by Syniti
T - Transform: Data will be Cleansed, Transformed, Merged, and staging areas of Migration Cockpit will be updated by Syniti
L - Loading: Data will be Loaded using the Migration Cockpit
Frequency of running reports
Preload Reports
Run before every load execution (Mock Loads, Dress Rehearsals, Cutover).
Purpose: to validate source-to-target transformations, business rules, and check for data quality issues before pushing into the Migration Cockpit.
Typically executed each time you release a wave or object for load.
Postload Reports
Run immediately after each load execution.
Purpose: to reconcile and confirm that what was loaded into SAP matches the expected records (counts, key fields, value checks, etc.).
Typically executed after every migration cycle (mock, dress rehearsal, final cutover).
Target Design
For Info Records the data hierarchy ID described below with the related SAP Tables expected to be Extracted / Transformed / Loaded. All target tables are being considered in the MDS document.
Value Mappings: Transformation DOMD (Source ECC)
The complete file is available on this LINK and the technical design of the target system for this conversion approach is detailed below.
| Source Field Information | Transform Rules | Target Field Information | |||||||||||||||||||||
| Sequence | Technical Source Table | Field Name | Technical Source Field | Field Format | Field Length | Comments | Mapping Type | Transform Rule or Default Value | Validation Rule | Comments | Datal Load Template | Sheet Name | Group | Field Description | Business Description | Check Table | Business Mandatory Y/N/C | System Mandatory Y/N/C | Type | Length | Decimal | Sap Table Name | Sap Field Name |
| EINA Table | |||||||||||||||||||||||
| 1.001 | EINA | INFNR | Legacy Number of Purchasing Info Record | Text | 80 | Transformation Rule | Transform Rule: Maintain the same number for each Info Record transaction. Since data is being merged from both PF2 and WP2 systems, it is not recommended to reuse the source number, as this could lead to number clashes or duplication conflicts. | - Mandatory for Migration Cockpit | Legacy Number of Purchasing Info Record | YES | YES | Text | 80 | S_EINA | INFNR | ||||||||
| 1.002 | EINA | MATNR | Product Number (Material Number - MATNR) | Text | 80 | Transformation Rule | Transformation Rule (MAPPING): 1) Use the source value, and lookup on the mapping table for <MATERIALS> and update the target field. 1.1) SKIP records where the material is out of scope | - Relevant for DataCleansing - Relevant for DataConversion
| Product Number | MARA-MATNR | YES | NO | Text | 80 | S_EINA | MATNR | |||||||
| 1.003 | EINA | MATKL | Product Group (Material Group - MATKL) | Text | 80 | Transformation Rule | Transformation Rule (MAPPING): 1) Use the source value, and lookup on the mapping table for <MATKL> and update the target field. 1.1) SKIP records where the material is out of scope | - Relevant for DataCleansing | Product Group | MARA-MAKT | YES | NO | Text | 80 | S_EINA | MATKL | |||||||
| 1.004 | EINA | LIFNR | Supplier's Account Number (Vendor Number - LIFNR) | Text | 80 | Transformation Rule | Transformation Rule (MAPPING): 1) Use the source value, and lookup on the mapping table for Vendor <LIFNR> and update the target field. 1.1) SKIP records where the vendor is out of scope | - Mandatory for Migration Cockpit | Supplier's Account Number | BP | YES | YES | Text | 80 | S_EINA | LIFNR | |||||||
| 1.005 | EINA | TXZ01 | Short Text for Purchasing Info Record | Text | 40 | Transformation Rule | Transformation Rule: 1) Copy source field value as-is to the target field (1:1 direct mapping). | Short Text for Purchasing Info Record | YES | NO | Text | 40 | S_EINA | TXZ01 | |||||||||
| 1.006 | EINA | SORTL | Sort Term for Non-Stock Info Records | Text | 10 | Transformation Rule | Transformation Rule: 1) Copy source field value as-is to the target field (1:1 direct mapping). | Sort Term for Non-Stock Info Records | NO | NO | Text | 10 | S_EINA | SORTL | |||||||||
| 1.007 | EINA | MEINS | Order Unit (ISO Format) | Text | 80 | Transformation Rule | Transformation Rule (MAPPING): 1)Use the source value, and lookup on the mapping table for Unit of Measure - UOM <MEINS> and update the target field. | Order Unit (ISO Format) | YES | NO | Text | 80 | S_EINA | MEINS | |||||||||
| 1.008 | EINA | UMREZ | Numerator for Conversion of Order Unit | Number | 5 | Transformation Rule | Transformation Rule: 1) Copy source field value as-is to the target field (1:1 direct mapping). | Numerator for Conversion of Order Unit | NO | NO | Number | 5 | S_EINA | UMREZ | |||||||||
| 1.009 | EINA | UMREN | Denominator for Conversion of Order Unit | Number | 5 | Transformation Rule | Transformation Rule: 1) Copy source field value as-is to the target field (1:1 direct mapping). | Denominator for Conversion of Order Unit | NO | NO | Number | 5 | S_EINA | UMREN | |||||||||
| 1.010 | EINA | IDNLF | Product Number Used by Supplier | Text | 35 | Transformation Rule | Transformation Rule: 1) Copy source field value as-is to the target field (1:1 direct mapping). | Product Number Used by Supplier | NO | NO | Text | 35 | S_EINA | IDNLF | |||||||||
| 1.011 | EINA | VERKF | Salesperson Responsible | Text | 30 | Transformation Rule | Transformation Rule: 1) Copy source field value as-is to the target field (1:1 direct mapping). | Salesperson Responsible | NO | NO | Text | 30 | S_EINA | VERKF | |||||||||
| 1.012 | EINA | TELF1 | Supplier's Telephone Number | Text | 16 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Supplier's Telephone Number | NO | NO | Text | 16 | S_EINA | TELF1 | |||||||||
| 1.013 | EINA | MAHN1 | Days for First Reminder/Expediter | Number | 3 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Days for First Reminder/Expediter | NO | NO | Number | 3 | S_EINA | MAHN1 | |||||||||
| 1.014 | EINA | MAHN2 | Days for Second Reminder/Expediter | Number | 3 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Days for Second Reminder/Expediter | NO | NO | Number | 3 | S_EINA | MAHN2 | |||||||||
| 1.015 | EINA | MAHN3 | Days for Third Reminder/Expediter | Number | 3 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Days for Third Reminder/Expediter | NO | NO | Number | 3 | S_EINA | MAHN3 | |||||||||
| 1.016 | EINA | LMEIN | Base Unit of Measure (ISO Format) | Text | 80 | Transformation Rule | Transformation Rule (MAPPING): 1)Use the source value, and lookup on the mapping table for Unit of Measure - UOM <MEINS> and update the target field. | Base Unit of Measure (ISO Format) | NO | NO | Text | 80 | S_EINA | LMEIN | |||||||||
| 1.017 | EINA | VABME | Variable Purchase Order Unit Active | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Variable Purchase Order Unit Active | NO | NO | Text | 80 | S_EINA | VABME | |||||||||
| 1.018 | EINA | WGLIF | Supplier Product Group | Text | 18 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Supplier Product Group | NO | NO | Text | 18 | S_EINA | WGLIF | |||||||||
| 1.019 | EINA | KOLIF | Prior Supplier | Text | 80 | Transformation Rule | Transformation Rule (MAPPING): 1) Use the source value, and lookup on the mapping table for Vendor <LIFNR> and update the target fields. | - Relevant for DataCleansing | Prior Supplier | NO | NO | Text | 80 | S_EINA | KOLIF | ||||||||
| 1.020 | EINA | URZLA | Country/Region of Origin | Text | 80 | Transformation Rule | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | Country/Region of Origin | NO | NO | Text | 80 | S_EINA | URZLA | |||||||||
| 1.021 | EINA | REGIO | Region | Text | 80 | Transformation Rule | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | Region | NO | NO | Text | 80 | S_EINA | REGIO | |||||||||
| 1.022 | EINA | MFRNR | Manufacturer | Text | 80 | Transformation Rule | Transformation Rule: Use the source value, and lookup on the mapping table for Vendors <LIFNR>. | -Relevant for Mapping | Manufacturer | NO | NO | Text | 80 | S_EINA | MFRNR | ||||||||
| 1.023 | EINA | LIFAB | Available (Deliverable) From | Date | Transformation Rule | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). Target field format: DD.MM.YYYY | Available (Deliverable) From | NO | NO | Date | S_EINA | LIFAB | |||||||||||
| 1.024 | EINA | LIFBI | Available (Deliverable) Until | Date | Transformation Rule | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). Target field format: DD.MM.YYYY | Available (Deliverable) Until | NO | NO | Date | S_EINA | LIFBI | |||||||||||
| 1.025 | EINA | RELIF | Indicator: Regular Supplier | Text | 1 | Transformation Rule | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | Indicator: Regular Supplier | NO | NO | Text | 1 | S_EINA | RELIF | |||||||||
| In order to select the data from STXL proceed as follow: STEP_1: Select * From STXL Where TDOBJECT = EINA TDNAME = <Info Record Number CHAR10) *Create one entry for each language STXL-TDSPRAS | |||||||||||||||||||||||
| 2.001 | EINA | INFNR | Legacy Number of Purchasing Info Record | Text | 80 | Transformation Rule | Transform Rule: Maintain the same number for each Info Record transaction. Since data is being merged from both PF2 and WP2 systems, it is not recommended to reuse the source number, as this could lead to number clashes or duplication conflicts. | - Mandatory for Migration Cockpit | Legacy Number of Purchasing Info Record | YES | YES | Text | 80 | S_EINA_TEXT | INFNR | ||||||||
| 2.002 | STXL | TDSPRAS | Language Key | Text | 80 | Transformation Rule | Transformation Rule: After apply the data selection, use each line encountered in STXL-TDSPRAS | - Mandatory for Migration Cockpit | Language Key | YES | YES | Text | 80 | S_EINA_TEXT | TDSPRAS | ||||||||
| 2.003 | STXL | CLUSTD | Text | Text | unrestricted | Transformation Rule | Transformation Rule: Target field is equal to STXL-CLUSTD | - Mandatory for Migration Cockpit | Text | YES | YES | Text | unrestricted | S_EINA_TEXT | TEXT | ||||||||
| 3.001 | EINE | INFNR | Legacy Number of Purchasing Info Record | Text | 80 | Transformation Rule | Transform Rule: Maintain the same number for each Info Record transaction. Since data is being merged from both PF2 and WP2 systems, it is not recommended to reuse the source number, as this could lead to number clashes or duplication conflicts. | - Mandatory for Migration Cockpit | Legacy Number of Purchasing Info Record | YES | YES | Text | 80 | S_EINE | INFNR | ||||||||
| 3.002 | EINE | EKORG | Purchasing Organization | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG> 1.1) SKIP record where the PurchOrg is out of scope | - Mandatory for Migration Cockpit | Purchasing Organization | YES | YES | Text | 80 | S_EINE | EKORG | ||||||||
| 3.003 | EINE | ESOKZ | Purchasing Info Record Category | Text | 80 | Transformation Rule | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatory for Migration Cockpit | Purchasing Info Record Category | YES | YES | Text | 80 | S_EINE | ESOKZ | ||||||||
| 3.004 | EINE | WERKS | Plant | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Plant <WERKS> 1.1) SKIP records where the plant is out of scope | - Relevant for DataCleansing | Plant | NO | NO | Text | 80 | S_EINE | WERKS | ||||||||
| 3.005 | EINE | EKGRP | Purchasing Group | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Purchasing Group <EKGRP> | - Relevant for DataCleansing | Purchasing Group | NO | NO | Text | 80 | S_EINE | EKGRP | ||||||||
| 3.006 | EINE | WAERS | Currency Key(ISO Format) | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Currency <WAERS> | - Relevant for DataConversion
| Currency Key(ISO Format) | NO | NO | Text | 80 | S_EINE | WAERS | ||||||||
| 3.007 | EINE | MINBM | Minimum Purchase Order Quantity | Number | 13,3 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Minimum Purchase Order Quantity | NO | NO | Number | 13,3 | S_EINE | MINBM | |||||||||
| 3.008 | EINE | NORBM | Standard Purchase Order Quantity | Number | 13,3 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Mandatory for Migration Cockpit | Standard Purchase Order Quantity | YES | YES | Number | 13,3 | S_EINE | NORBM | ||||||||
| 3.009 | EINE | APLFZ | Planned Delivery Time in Days | Number | 3 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Planned Delivery Time in Days | NO | NO | Number | 3 | S_EINE | APLFZ | |||||||||
| 3.010 | EINE | UEBTO | Overdelivery Tolerance Limit | Number | 3,1 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Overdelivery Tolerance Limit | NO | NO | Number | 3,1 | S_EINE | UEBTO | |||||||||
| 3.011 | EINE | UEBTK | Indicator:Unlimited Overdelivery Allowed | Text | 1 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Indicator:Unlimited Overdelivery Allowed | NO | NO | Text | 1 | S_EINE | UEBTK | |||||||||
| 3.012 | EINE | UNTTO | Underdelivery Tolerance Limit | Number | 3,1 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Underdelivery Tolerance Limit | NO | NO | Number | 3,1 | S_EINE | UNTTO | |||||||||
| 3.013 | EINE | BWTAR | Valuation Type | Text | 10 | Transformation Rule | Transformation Rule (MAPPING): Use the source value, and lookup on the mapping table for <VALUATION_TYPE) and update the target field. | - Relevant for DataConversion | Valuation Type | NO | NO | Text | 10 | S_EINE | BWTAR | ||||||||
| 3.014 | EINE | MTXNO | Ind: Prod. Master Rec. PO Text Not Rele. | Text | 1 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Ind: Prod. Master Rec. PO Text Not Rele. | NO | NO | Text | 1 | S_EINE | MTXNO | |||||||||
| 3.015 | EINE | WEBRE | Indicator: GR-Based Invoice Verification | Text | 1 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Indicator: GR-Based Invoice Verification | NO | NO | Text | 1 | S_EINE | WEBRE | |||||||||
| 3.016 | EINE | KZABS | Ind: Order Acknowledgment Requirement | Text | 1 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Ind: Order Acknowledgment Requirement | NO | NO | Text | 1 | S_EINE | KZABS | |||||||||
| 3.017 | EINE | MWSKZ | Tax on Sales/Purchases Code | Text | 80 | Transformation Rule | Transformation Rule (MAPPING): Use the source value, and lookup on the mapping table for <TAX_CODE> and update the target field. | - Relevant for DataConversion | Tax on Sales/Purchases Code | NO | NO | Text | 80 | S_EINE | MWSKZ | ||||||||
| 3.018 | EINE | TXDAT_FROM | Valid-From Date of the Tax Rate | Date | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Valid-From Date of the Tax Rate | NO | NO | Date | S_EINE | TXDAT_FROM | |||||||||||
| 3.019 | EINE | EVERS | Shipping Instructions | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Relevant for DataConversion | Shipping Instructions | NO | NO | Text | 80 | S_EINE | EVERS | ||||||||
| 3.020 | EINE | BSTAE | Confirmation Control Key | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Relevant for DataConversion
| Confirmation Control Key | NO | NO | Text | 80 | S_EINE | BSTAE | ||||||||
| 3.021 | EINE | XERSN | Ind: No Evaluated Receipt Settlem. (ERS) | Text | 1 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Ind: No Evaluated Receipt Settlem. (ERS) | NO | NO | Text | 1 | S_EINE | XERSN | |||||||||
| 3.022 | EINE | MHDRZ | Minimum Remaining Shelf Life | Number | 4 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Minimum Remaining Shelf Life | NO | NO | Number | 4 | S_EINE | MHDRZ | |||||||||
| 3.023 | EINE | IPRKZ | Period Ind. for Min. Remain. Shelf Life | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Period Ind. for Min. Remain. Shelf Life | NO | NO | Text | 80 | S_EINE | IPRKZ | |||||||||
| 3.024 | EINE | BSTMA | Maximum Purchase Order Quantity | Number | 13,3 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Maximum Purchase Order Quantity | NO | NO | Number | 13,3 | S_EINE | BSTMA | |||||||||
| 3.025 | EINE | EXPRF_LAND1 | Foreign Trade: Country/Region | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Foreign Trade: Country/Region | NO | NO | Text | 80 | S_EINE | EXPRF_LAND1 | |||||||||
| 3.026 | EINE | EXPRF | Foreign Trade: Procedure | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Foreign Trade: Procedure | NO | NO | Text | 80 | S_EINE | EXPRF | |||||||||
| 3.027 | EINE | RDPRF | Rounding Profile | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Relevant for DataConversion | Rounding Profile | NO | NO | Text | 80 | S_EINE | RDPRF | ||||||||
| 3.028 | EINE | VENDOR_RMA_REQ | Supplier RMA Number Required | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Supplier RMA Number Required | NO | NO | Text | 80 | S_EINE | VENDOR_RMA_REQ | |||||||||
| 3.029 | EINE | AUT_SOURCE | Relevant for Automatic Sourcing | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Relevant for Automatic Sourcing | NO | NO | Text | 80 | S_EINE | AUT_SOURCE | |||||||||
| 3.030 | EINE | SKTOF | Ind: Item Does Not Qualify for Cash Disc | Text | 1 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Ind: Item Does Not Qualify for Cash Disc | NO | NO | Text | 1 | S_EINE | SKTOF | |||||||||
| 3.031 | EINE | MEPRF | Price Determinat. (Pricing) Date Control | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Price Determinat. (Pricing) Date Control | NO | NO | Text | 80 | S_EINE | MEPRF | |||||||||
| 3.032 | EINE | INCOV | Incoterms Version | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Incoterms Version | NO | NO | Text | 80 | S_EINE | INCOV | |||||||||
| 3.033 | EINE | INCO1 | Incoterms | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Relevant for DataConversion | Incoterms | NO | NO | Text | 80 | S_EINE | INCO1 | ||||||||
| 3.034 | EINE | INCO2_L | Incoterms Location 1 | Text | 70 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Incoterms Location 1 | NO | NO | Text | 70 | S_EINE | INCO2_L | |||||||||
| 3.035 | EINE | INCO3_L | Incoterms Location 2 | Text | 70 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Incoterms Location 2 | NO | NO | Text | 70 | S_EINE | INCO3_L | |||||||||
| After processing all entries, verify that the EINA table contains at least one record matching the specified EINA-MATNR and EINA-LIFNR values. If no corresponding entry exists in EINA, the transaction must be deleted. | |||||||||||||||||||||||
| 4.001 | EINE | INFNR | Legacy Number of Purchasing Info Record | Text | 80 | Transformation Rule | Transform Rule: Maintain the same number for each Info Record transaction. Since data is being merged from both PF2 and WP2 systems, it is not recommended to reuse the source number, as this could lead to number clashes or duplication conflicts. | COND.INFNR ← EINA-INFNR | - Mandatory for Migration Cockpit | Legacy Number of Purchasing Info Record | YES | YES | Text | 80 | S_COND | INFNR | |||||||
| 4.002 | EINE | EKORG | Purchasing Organization | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG> 1.1) SKIP record where the PurchOrg is out of scope | COND.EKORG ← EINE-EKORG | - Mandatory for Migration Cockpit | Purchasing Organization | YES | YES | Text | 80 | S_COND | EKORG | |||||||
| 4.003 | EINE | ESOKZ | Purchasing Info Record Category | Text | 80 | Transformation Rule | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | COND.ESOKZ ← EINE-ESOKZ | - Mandatory for Migration Cockpit | Purchasing Info Record Category | YES | YES | Text | 80 | S_COND | ESOKZ | |||||||
| 4.004 | EINE | WERKS | Plant | Text | 80 | Transformation Rule | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Plant <WERKS> 1.1) SKIP records where the plant is out of scope | COND.WERKS ← EINE-WERKS | Plant | YES | YES | Text | 80 | S_COND | WERKS | ||||||||
| 4.005 | KONP | KOPOS | Condition Sequence Number | Number | 2 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | COND.KOPOS ← KONP-KOPOS | - Mandatory for Migration Cockpit | Condition Sequence Number | YES | YES | Number | 2 | S_COND | KOPOS | |||||||
| 4.006 | KONP | KSCHL | Condition Type | Text | 80 | Transformation Rule: 1) Use the source value to update the target field AS-IS QF2: Condition Tables: 016, 017, 018, 025, 028, 066, 067, 118 Condition Types: PB00, P000, PN00, PC | COND.COND_TYPE ← KONP-KSCHL (PB00) | - Mandatory for Migration Cockpit | Condition Type | YES | YES | Text | 80 | S_COND | COND_TYPE | ||||||||
| 4.007 | KONH | DATAB | Valid From | Date | Transformation Rule: 1) Use the source value to update the target field AS-IS | COND.VALID_FROM ← KONH-DATAB | - Mandatory for Migration Cockpit | Valid From | YES | YES | Date | S_COND | VALID_FROM | ||||||||||
| 4.008 | KONH | DATBI | Valid To | Date | Transformation Rule: 1) Use the source value to update the target field AS-IS | COND.VALID_TO ← KONH-DATBI | - Mandatory for Migration Cockpit | Valid To | YES | YES | Date | S_COND | VALID_TO | ||||||||||
| 4.009 | KONM | KRECH | Calculation Type | Text | 80 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Calculation Type | NO | NO | Text | 80 | S_COND | KRECH | ||||||||||
| 4.010 | KONP | KBETR | Amount | Number | 31,3 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Amount | NO | NO | Number | 31,3 | S_COND | KBETR_EXT | ||||||||||
| 4.011 | KONP | KONWA | Condition Unit (Currency or Percentage) | Text | 80 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Condition Unit (Currency or Percentage) | NO | NO | Text | 80 | S_COND | KONWA | ||||||||||
| 4.012 | KONP | KPEIN | Condition Pricing Unit | Number | 5 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Condition Pricing Unit | NO | NO | Number | 5 | S_COND | KPEIN | ||||||||||
| 4.013 | KONP | KMEIN | Condition Unit of Measure ISO | Text | 80 | Transformation Rule (MAPPING): 1)Use the source value, and lookup on the mapping table for Unit of Measure - UOM <MEINS> and update the target field. | Condition Unit of Measure ISO | NO | NO | Text | 80 | S_COND | KMEIN | ||||||||||
| 4.014 | KONP | KUMZA | Numerator for Conversion | Number | 5 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Numerator for Conversion | NO | NO | Number | 5 | S_COND | KUMZA | ||||||||||
| 4.015 | KONP | KUMNE | Denominator for Conversion | Number | 5 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Denominator for Conversion | NO | NO | Number | 5 | S_COND | KUMNE | ||||||||||
| 4.016 | MARA | MEINS | Base Unit of Measure ISO | Text | 80 | Transformation Rule (MAPPING): 1)Use the source value, and lookup on the mapping table for Unit of Measure - UOM <MEINS> and update the target field. | Base Unit of Measure ISO | NO | NO | Text | 80 | S_COND | MEINS | ||||||||||
| 4.017 | KONM | KONMS | Condition Scale Unit of Measure ISO | Text | 80 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Condition Scale Unit of Measure ISO | NO | NO | Text | 80 | S_COND | KONMS | ||||||||||
| 4.018 | COND | EXCLUSION_IND | Condition Exclusion Indicator | Text | 80 | Transformation Rule: NO RULE - send blanks | Condition Exclusion Indicator | NO | NO | Text | 80 | S_COND | EXCLUSION_IND | ||||||||||
| 5.001 | EINE | INFNR | Legacy Number of Purchasing Info Record | Text | 80 | Transform Rule: Maintain the same number for each Info Record transaction. Since data is being merged from both PF2 and WP2 systems, it is not recommended to reuse the source number, as this could lead to number clashes or duplication conflicts. | - Mandatory for Migration Cockpit | Legacy Number of Purchasing Info Record | YES | YES | Text | 80 | S_SCALES | INFNR | |||||||||
| 5.002 | EINE | EKORG | Purchasing Organization | Text | 80 | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG> 1.1) SKIP record where the PurchOrg is out of scope | - Mandatory for Migration Cockpit | Purchasing Organization | YES | YES | Text | 80 | S_SCALES | EKORG | |||||||||
| 5.003 | EINE | ESOKZ | Purchasing Info Record Category | Text | 80 | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatory for Migration Cockpit | Purchasing Info Record Category | YES | YES | Text | 80 | S_SCALES | ESOKZ | |||||||||
| 5.004 | EINE | WERKS | Plant | Text | 80 | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Plant <WERKS> 1.1) SKIP records where the plant is out of scope | Plant | NO | NO | Text | 80 | S_SCALES | WERKS | ||||||||||
| 5.005 | KONP | KOPOS | Condition Sequence Number | Number | 2 | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Mandatory for Migration Cockpit | Condition Sequence Number | YES | YES | Number | 2 | S_SCALES | KOPOS | |||||||||
| 5.006 | KONP | KSCHL | Condition Type | Text | 80 | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Mandatory for Migration Cockpit | Condition Type | YES | YES | Text | 80 | S_SCALES | COND_TYPE | |||||||||
| 5.007 | KONH | DATAB | Valid From | Date | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Mandatory for Migration Cockpit | Valid From | YES | YES | Date | S_SCALES | VALID_FROM | |||||||||||
| 5.008 | KONH | DATBI | Valid To | Date | Transformation Rule: 1) Use the source value to update the target field AS-IS | - Mandatory for Migration Cockpit | Valid To | YES | YES | Date | S_SCALES | VALID_TO | |||||||||||
| 5.009 | SCALES | LINE_NO | Scale Item Number | Number | 4 | Transformation Rule: 1) ROW_NUMBER() OVER(PARTITION BY KONM-KNUMH, KONM-KOPOS ORDER BY KONM-KONMS) | - Mandatory for Migration Cockpit | Scale Item Number | YES | YES | Number | 4 | S_SCALES | LINE_NO | |||||||||
| 5.010 | KONM | STFKZ | Scale Quantity | Number | 15,3 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Scale Quantity | NO | NO | Number | 15,3 | S_SCALES | KSTBM | ||||||||||
| 5.011 | KONP | KBETR | Scale Rate | Number | 31,3 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Scale Rate | NO | NO | Number | 31,3 | S_SCALES | KBETR | ||||||||||
| 5.012 | KONM | KONMS | Scale Value | Number | 28,3 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Scale Value | NO | NO | Number | 28,3 | S_SCALES | SCALE_VAL | ||||||||||
| 5.013 | KONM | KONWS | Scale Rate | Number | 31,3 | Transformation Rule: 1) Use the source value to update the target field AS-IS | Scale Rate | NO | NO | Number | 31,3 | S_SCALES | KBETR_VAL | ||||||||||
| The entries from STXL table for EINE are composed as follow: STXL-TDOBJECT = EINE STXL-TDNAME = [INFO REC CODE-INFNR CHAR10] [ESOKZ CHAR1] [PLANT-WERKS CHAR4] Create one entry for each record, and apply data Conversion for Purchasing Org and Plant | |||||||||||||||||||||||
| 6.001 | STXL | TDOBJECT | Text Object | Text | 80 | Transform Rule: Maintain the same number for each Info Record transaction. Since data is being merged from both PF2 and WP2 systems, it is not recommended to reuse the source number, as this could lead to number clashes or duplication conflicts. | - Mandatory for Migration Cockpit | Legacy Number of Purchasing Info Record | YES | YES | Text | 80 | S_EINE_TEXT | INFNR | |||||||||
| 6.002 | STXL | EKORG | Purchasing Organization | Text | 80 | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG> 1.1) SKIP record where the PurchOrg is out of scope | - Mandatory for Migration Cockpit | Purchasing Organization | YES | YES | Text | 80 | S_EINE_TEXT | EKORG | |||||||||
| 6.003 | STXL | ESOKZ | Purchasing Info Record Category | Text | 80 | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatory for Migration Cockpit | Purchasing Info Record Category | YES | YES | Text | 80 | S_EINE_TEXT | ESOKZ | |||||||||
| 6.004 | STXL | WERKS | Plant | Text | 80 | Transformation Rule: 1) Use the source value, and lookup on the mapping table for Plant <WERKS> 1.1) SKIP records where the plant is out of scope | Plant | NO | NO | Text | 80 | S_EINE_TEXT | WERKS | ||||||||||
| 6.005 | STXL | TDSPRAS | Language Key | Text | 80 | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatory for Migration Cockpit | Language Key | YES | YES | Text | 80 | S_EINE_TEXT | TDSPRAS | |||||||||
| 6.006 | STXL | TEXT | Text | Text | unrestricted | Transformation Rule: Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatory for Migration Cockpit | Text | YES | YES | Text | unrestricted | S_EINE_TEXT | TEXT | |||||||||
Data Merging Strategy
According to the Source Data, this option doesn't seem to be realistic; but in cases where the same Material|Vendor|PurchOrg|Plant(can be empty) combination exists across multiple source systems (due to system consolidation), it is recommended to apply the following merging rules:
| ID | Scenario | Action |
|---|---|---|
| 001 | Same combination of Material|Vendor|PurchOrg|Plant | Apply data conversion and identify duplicate records, merging them when possible |
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
N/AExtraction
Data Analysis: Retention Level EINA|EINE
PF2: A017, A018 ==> 163.554 records analysed
WP2: A017, A018, A025 AND A067 ==> 311.123 records analysed
| Table | Key fields | Contains Info Record Number? | Typical usage |
|---|---|---|---|
| A016 | Vendor / Material | No | Info Record price without plant level (general vendor–material) |
| A017 | Plant / Vendor / Material | No | Plant-specific PIR (what you showed) |
| A018 | Vendor / Material / Info Record | Yes (INFNR) | Info Record-specific pricing (when PIR number matters) |
| A068 | Plant / Vendor / Material / Info Record | Yes (INFNR) | PIR-specific and plant-specific |
Data Analysis: Condition Types
PF2: PB00, PC ==> 163.554 records analysed
WP2: PB00, ZI01 ==> 313.154 records analysed
Extraction Run Sheet
| Req # | Requirement Description | Team Responsible |
|---|---|---|
| 001 | Verify connectivity and authorizations to source ECC systems before execution. | SyWay Data Team |
| 002 | Confirm selection scope: Purchasing Organizations, Plants, Vendors, and Materials to be included in the extraction. | SyWay Data Team |
| 003 | Execute data-profiling query to validate record counts and existence of Info Records (EINA/EINE) before the extraction run. | SyWay Data Team |
| 005 | Extract Info Records for Vendors that are not marked for deletion (LFM1-LOEVM ≠ ‘X’) and are within scope. | SyWay Data Team |
| 006 | Extract Info Records for active Vendors and Materials only – exclude entries with deletion or obsolete flags. | SyWay Data Team |
| 007 | Extract Info Records for Materials that are not marked for deletion and belong to valid Info Record combinations. | SyWay Data Team |
| 008 | Extract condition records (KONH/KONP, A017/A018/...) corresponding to valid Info Records, using non-overlapping validity dates. | SyWay Data Team |
| 009 | Extract long texts (STXH/STXL) for valid Info Records and ensure language completeness (including all ISO languages and excluding out of scope languages) | SyWay Data Team |
| 010 | Perform record-count validation per table (EINA, EINE, KONH, KONP, STXH, STXL) against expected totals and log results. | SyWay Data Team |
| 011 | Capture extraction metrics (runtime, volume, record counts, warnings/errors) and store in extraction log. | SyWay Data Team |
| 012 | Submit extraction output for validation and functional sign-off prior to upload to Syniti Staging. | SyWay Data Team |
Selection Screen
A Target Ready Data Collection Template will be created for the required data, except for fields that need transformation as per the defined transformation rules. These templates will follow the format required by the target S/4HANA Info Record & Purchasing Pricing Configuration.| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Topic N/A | ||||
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Purchasing Info Record data with exception of some fields which require transformation as mentioned in the transformation rule.The creation of Data collection template must be aligned with the field status of Info Record + Calculation Schema (configurations) for Condition types, Access sequence and Associated Condition Tables. For now, the following Template is prepared based on Pricing Configurations from S/4HANA Sandbox environment. This will be replaced once the pricing configuration is ready.
Date | DCT File (Current Link) |
|---|---|
20251027 |
Notes
The DCT must align with the field status of the target Info Record view and the Pricing Procedure schema approved by the Functional Team,
Where transformation logic applies (example PurchOrg, Plant, Incoterms, Currency), reference should be made to the Transformation Mapping Table maintained by the Data Governance team,
Once the final pricing configuration is frozen, this DCT can be regenerated with the exact condition types(per country - considering respective mapping), access sequences, and validity schema.
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
001 | Vendor - The Info Record is created for a specific vendor, therefore the vendor must exist and be active | S2P |
002 | Material - The Info Record is for a specific material, therefore the material must exist and be active | S2P |
003 | Purchasing Organization - Mandatory organizational level (configuration). Must be valid for both the vendor and material | S2P |
004 | Plant (optional) - If a plant-specific Info Record is used, the plant must be valid (included on scope) and maintained | FICO |
005 | Currency & UoM - Must align with vendor master and material master data | S2P |
006 | Tax Code - Should exist in system and be consistent with vendor's country and plant region | S2P |
007 | Conditions - Purchasing conditions (price, discounts, scales) are typically stored in condition records. Linked to Info Records via condition tables | S2P |
008 | Vendor Master Settings - The vendor must have the purchasing organization maintained in purchasing view | S2P |
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.
- Legacy values are mapped to the to-be values (this could include a default value)
- 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 | Identify target S/4HANA fields and determine applicable legacy source fields from both ECC systems WP2, PF2 | Functional Team (S2P)+ Data Team (S2P) |
| 2 | Review condition types and access tables used in each ECC source systems WP2, PF2 | Business Team + Functional Team (S2P) |
| 3 | Map legacy field values to S/4HANA target values (including field-level mapping and technical names) | Data Team (S2P), Data Team (Syniti) |
| 4 | Define value mapping rules for fields requiring standardization or harmonization across the two source systems WP2, PF2. | Functional Team (S2P)+ Data Team (S2P) |
| 5 | Identify and agree on default values where legacy data is incomplete or inconsistent | Business Team + Functional Team (S2P) |
| 6 | Configure transformation rules in Syniti Migrate (including calculated fields, formatting rules, etc.) | Data Team (Syniti), Data Team (S2P) |
| 7 | Review transformation logic and mappings with Business for confirmation | Business Team + Functional Team (S2P) |
| 8 | Perform initial transformation run and generate draft target-ready dataset | Data Team (Syniti), |
| 9 | Review draft target-ready data for structure and completeness | Data Team (S2P), Functional Team (S2P) |
| 10 | Share transformed data with Business for Pre-load Validation | Business Team |
| 11 | Incorporate feedback from Business and refine mappings or transformation logic as needed | Data Team (S2P) |
| 12 | Finalize and approve transformed data as Target Ready Load File | Business + Functional (S2P) + Data Team (S2P) |
| 13 | Handover final file to Load Team or trigger the load via Syniti Load Workbench | Data Team (Syniti), Data Load Team |
| 14 | Material and Vendor must exist in the target system. Only include Info Records where both MARA-MATNR and LFA1-LIFNR are valid and being migrated to S4Hana; | Data Team (Syniti), Data Load Team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
1094-001 | Legacy | EINA | INFNR | Legacy Number of Purchasing Info Record | S/4HANA | EINA | INFNR | Legacy Number of Purchasing Info Record | Generate the Info Record number and keep this mapping in a reference table (this might be used for Transactional Data). *depending on the upload method, the Info Record number would be automatically generated. |
1094-002 | Legacy | EINA | MATNR | Material | S/4HANA | EINA | MATNR | Material | Select the new Material Code from the mapping table and update the corresponding target structure accordingly. |
1094-003 | Legacy | EINA | MATKL | Material Group | MATKL | Material Group | MATKL | Material Group | Select the new Material Group from the mapping table and update the corresponding target structure accordingly. |
1094-004 | Legacy | EINA | LIFNR | Vendor | S/4HANA | EINA | LIFNR | Vendor | Select the new Vendor Code from the mapping table and update the corresponding target structure accordingly. |
1094-005 | Legacy | EINA | INCO1 | Incoterm | S/4HANA | EINA | INCO1 | Incoterm | Select the Incoterm Code from the mapping table and update the corresponding target structure accordingly. |
1094-006 | Legacy | EINA | MEINS | Order Unit | S/4HANA | EINA | MEINS | Order Unit | Select the new Order Unit Code from the mapping table and update the corresponding target structure accordingly. |
1094-007 | Legacy | EINA | MFRNR | Manufacturer | S/4HANA | EINA | MFRNR | Manufacturer | Select the new Manufacturer Code from the mapping table and update the corresponding target structure accordingly. |
1094-008 | Legacy | EINE | WERKS | Plant | S/4HANA | EINE | WERKS | Plant | Select the new Plant Code from the mapping table and update the corresponding target structure accordingly. |
1094-009 | Legacy | EINE | WAERS | Currency | S/4HANA | EINE | WAERS | Currency | Select the new Currency Code from the mapping table and update the corresponding target structure accordingly. |
1094-010 | Legacy | EINE | MWSKZ | Tax Code | S/4HANA | EINE | MWSKZ | Tax Code | Select the new Tax Code from the mapping table and update the corresponding target structure accordingly. |
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
LIFNR (LFA1-LIFNR) | <Vendor> → not yet available |
MATNR (MARA-MATNR) | <Material> → not yet available |
WERKS (T001W-WERKS_ | |
EKORG (T024E-EKORG) | |
EKGRP (T024-EKGRP) | |
MATKL (T023-MATKL) | <Material Group> → not yet available |
MEINS (T006-MEINS) | <Unit of Measure> → not yet available |
MWSKZ (T007A-MWSKZ) |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 001 | Value Mapping Tables are complete | Functional Team (S2P) + Data Team (S2P) |
| 002 | Info Record & Pricing configuration are complete | Functional Team (S2P) + Data Team (S2P) |
| 003 | Org structure configuration is complete | Functional Team (S2P) + Data Team (S2P) |
| 004 | Dependent Master Data records for Customer and Material are loaded | Functional Team (S2P) + Data Team (S2P) |
| 005 | Master Data – Vendor | Data Team (S2P) |
| 006 | Master Data – Material | Data Team (S2P) |
| 007 | Configuration – Purchasing Organization | Functional Team (S2P) |
| 008 | Configuration – Plant | Functional Team (S2P) |
| 009 | Configuration – Product Group | Functional Team (S2P) |
| 010 | Configuration – Vendor | Functional Team (S2P) |
| 011 | Configuration – Material | Functional Team (S2P) |
| 012 | Configuration – Material Group | Functional Team (S2P) |
| 013 | Configuration – Unit of Measure | Functional Team (S2P) |
| 014 | Configuration – Purchasing Organization | Functional Team (S2P) |
| 015 | Configuration – Purchasing Group | Functional Team (S2P) |
| 016 | Configuration – Incoterms | Functional Team (S2P) |
| 017 | Configuration – Condition Types | Functional Team (S2P) |
| 018 | Configuration – Tax Code | Functional Team (S2P) |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| Configuration | Ensure necessary configurations are in place in target system and field mapping is aligned with access sequence, condition types |
| Review Mapping Table | Ensure all the source organization units are mapped with target values |
| Check Values | Validate the pre-load data confirming the values are aligned with target system format and |
| Validate template structure and required field population | Ensure mandatory fields are filled |
Total number of records | SyWay S2P Data Team to verify that the total number of records in the Preload and Load Sheets are equal |
Vendor Validation | Check if the vendor exists in the target system and is active for the Basic Data and Purchasing Organization. This object has to be loaded before Info Records and Price Conditions. |
Material Validation | Check if the material exists in the target system and is active for the purchasing organization. This object has to be loaded before Info Records and Price Conditions. |
Mandatory Field Check | Verify whether all mandatory Fields are properly updated: EINA-LIFNR |
Info Record Category | Check if the Info Record Category (EINE-ESOKZ) has been properly migrated and in case of conversion check the final result. |
Relevancy Rules | Develop automated reports to assess info record relevancy based on multiple criteria including Vendor (considering deletion flags, and purchasing organization), Material (and deletion flags) and price conditions validity |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | SyWay S2P Data Team to verify that all fields below meet pass the 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 |
Value Format Validation | Ensure fields follow correct format for Dates / Currency / Decimals (according to user’s logon) |
Code & Value Mapping Validation | Check if all legacy values are mapped to valid target values (generally applicable for Materials / Vendors / UOM / Currency) |
Referential Integrity Check | Validate that linked data exists and matches. Check cases like: |
Duplicate Detection | Identify and remove duplicate entries in the dataset |
Business Rule Compliance | Ensure compliance with agreed rules, for instance |
| Review Mapping Table | Ensure all the source organization units are mapped with target values |
| Check mapping rules against configuration, including the fields related to prices and conditions ( access sequences, condition tables) | Cross-check mapping sheet with customizing entries |
| Perform format validation (date, currency, decimal separators) | Standardize format to match SAP accepted input (e.g., YYYYMMDD for dates) |
| Implement logic to detect duplicate condition records | Example: Run duplicate checks using key combinations (e.g., MATNR + EKORG + WERKS) |
| Conduct dry runs using LTMC or BAPIs and review logs | Analyze load results and correct format or conversion errors |
Business
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| Review populated templates for missing or incorrect values ( | confirm that all mandatory fields are populated, values are in scope, and field formats align with target S/4HANA definitions. |
| Ensure all required fields are properly covered | Confirm that Vendor, Material, Plant, Purchasing Organisation, Price, and Conditions are fully populated and consistent across EINA, EINE, and KONH/KONP datasets. |
| Validate coverage of in-scope Purchasing Organisations and Plants | Verify that all mapped EKORG and WERKS combinations exist for the expected materials and vendors. |
| Check that all relevant Condition Types are present | Confirm that each Info Record contains required pricing condition types (e.g. PBXX, FRA1, RA01) according to target Pricing Procedure. Consider as being mandatory to have a price for each Info Rec. |
| Verify language coverage for texts | Ensure that long texts (STXH/STXL) exist for at least English or another Syensqo language, and that obsolete or duplicate texts are removed (in case was expected) |
| Confirm accuracy of mapped values | Review mapped fields (e.g. Incoterms, Payment Terms, Currency) to ensure harmonization with approved master data mappings. |
| Validate deletion and blocking flags | Ensure no record is incorrectly marked as deleted or blocked unless explicitly confirmed by Syensqo Business. |
| Review price validity and activity | Confirm that validity dates (DATAB, DATBI) cover the go-live date and that prices reflect the latest active vendor conditions |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that all fields below meet pass the 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 |
Value Format Validation | Ensure fields follow correct format for Dates / Currency / Decimals (according to user’s logon) |
Code & Value Mapping Validation | Check if all legacy values are mapped to valid target values (generally applicable for Materials / Vendors / UOM / Currency) |
Referential Integrity Check | Validate that linked data exists and matches. Check cases like: |
Duplicate Detection | Identify and remove duplicate entries in the dataset |
Business Rule Compliance | Ensure compliance with agreed rules, for instance |
Outlier & Range Checks | Detect extreme or invalid values (e.g., out-of-range weights) |
Load
The loading process includes:
- Once the data is provided on the Staging Areas of Migration Cockpit and prerequisite activities are completed, the Data Loading process would be ready to be performed
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Loading Methods
Migration Cockpit has been elected to execute the data loading of Purchasing Info Records. The Loading Method has been defined as MM - Purchasing info record with conditions.
Loading Templates (Migration Cockpit)
| Template | Loading File (.XML) |
|---|---|
| Purchasing info record with conditions | |
| Purchasing info record- extend existing record | Source data for MM - Purchasing info record- extend existing record.xml |
| Object classification - Purchasing info record (EINA) | |
| Sample Loading File | |
| DCT for Info Records |
Exclusion List
Using the description field, exclude all records that contain any of the following Words on it's description.
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
| 001 | Confirm readiness of final approved data sets for each ECC source system WP2 and PF2 | Business / Functional Team |
| 002 | Validate transformation rules and mappings in Syniti tool | Data Team (S2P-Data) |
| 003 | Generate target-ready load files based on S/4HANA condition table format | Data Team (Syniti) |
| 004 | Review and approve load files before execution | Business / Functional Team |
| 005 | Execute automated data load using Syniti into the S/4HANA system (or generate manual load files if required) | Data Team (Syniti) |
| 006 | Monitor load progress and capture load statistics (records loaded, errors, duplicates, etc.) | Data Team (Syniti) / Technical Team |
| 007 | Extract loaded data from S/4HANA for post-load validation | Data Team (Syniti) |
| 008 | Perform post-load data validation (compare target data with source/approved files) for all loaded pricing condition types | Data Team (S2P-Data) |
| 009 | Log and resolve any data load errors or mismatches identified during validation | Data Team (S2P-Data) + Functional Team |
| 010 | Obtain business sign-off on successful load and validation | Business Team |
| 011 | Generate post load report is all steps are validated | Data Team (S2P-Data) / Data Team (Syniti |
| 012 | Archive load logs, error reports, and validation results for audit/compliance | Data Team (S2P-Data) / Data Team (Syniti) / PMO |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item | |
|---|---|---|
| 001 | Configurations | Ensure all configurations related to Info Records and Purchasing Conditions are active in the target S/4HANA environment. This includes condition tables (A017, A018), access sequences, condition types, calculation schema, and pricing procedures. |
| 002 | Organization Data | Confirm that all required Organizational Units (Purchasing Organizations, Plants, Company Codes, and Valuation Areas) are configured and available in the target system |
| 003 | Vendor Master Data | Vendors (LIFNR) must be loaded and extended to the relevant Purchasing Organizations and Company Codes before Info Records are created |
| 004 | Material Master Data | Materials (MATNR) must be loaded and extended to the relevant Plants and Purchasing Views before Info Record load execution |
| 005 | Unit of Measure & Currency | Validate that all UoM (MARM) and currency (TCUR*) configurations exist and match those used in the source Info Records and condition tables. |
| 006 | Tax and Incoterm Configuration | Ensure tax codes, Incoterm versions, and Incoterm values (INCO1/INCO2_L/INCOV) are configured in the target system |
| 007 | Purchasing Groups | Confirm all Purchasing Groups used in source Info Records are configured and mapped in S/4HANA. |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
Vendor | Execute a data conversion in order to retrieve the new vendor code |
Material | Execute a data conversion in order to retrieve the new material code |
Material Group | Execute a data conversion in order to retrieve the new material group |
Unit of Measure (UoM) | Execute a data conversion in order to retrieve the new UoM code |
Payment Terms | Execute a data conversion in order to retrieve the new Payment Term |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
| Invalid Date Range | Valid From (DATAB) is after Valid To (DATBI) | Corrected the date range to ensure DATAB < DATBI and in required date format |
| Duplicate Records | Identical key combinations found more than once in the load file | Duplicates removed or merged as per business rule. Aligned with Business and documented for future loads |
| Unmapped Values | Values for fields like UoM, Currency, etc. not mapped in Syniti | Updated mapping tables; ensured value conversion aligned with S/4HANA settings |
| Invalid Currency Format | Incorrect currency formatting or unsupported currency code | Standardized to valid ISO currency codes (e.g., USD, EUR, JPY) |
| Invalid Number Format | KBETR or KPEIN contains special characters or comma separators | Cleaned formatting; ensured decimal values used with '.' as separator |
| Authorization Errors | Lack of access to execute load in target client/system | Raised access request; obtained necessary authorizations |
| Transformation Miss | Required transformation logic not applied before load | Re-applied transformation rules and revalidated source-target mapping |
| Obsolete Master Data | Vendor or material master data no longer exists in target system | Replaced or removed based on business input |
| Technical Load Failure | File not processed due to syntax/format error or system issue | Reviewed logs; regenerated file; re-executed load after resolving issue |
Post-Load Validation
Project Team
The following post-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| Ensure all required fields are properly covered | Confirm that Vendor, Material, Plant, Purchasing Organisation, Price, and Conditions are fully populated and consistent across EINA, EINE, and KONH/KONP datasets |
| Validate coverage of in-scope Purchasing Organisations and Plants | Verify that all mapped EKORG and WERKS combinations exist for the expected materials and vendors. |
| Check that all relevant Condition Types are present | Confirm that each Info Record contains required pricing condition types (e.g. PBXX, FRA1, RA01) according to target Pricing Procedure. |
| Verify language coverage for texts | Ensure that long texts (STXH/STXL) exist for at least English and project languages (FR/NL/DE/PT-BR), and that obsolete or duplicate texts are removed |
| Confirm accuracy of mapped values | Review mapped fields (e.g. Incoterms, Payment Terms, Currency) to ensure harmonization with approved master data mappings |
| Validate deletion and blocking flags | Ensure no record is incorrectly marked as deleted or blocked unless explicitly confirmed by business |
| Review price validity | Confirm that validity dates (DATAB, DATBI) cover the go-live date and that prices reflect the latest active vendor conditions. |
Accuracy
| Task | Action |
|---|---|
| Compare uploaded data against source file values | Use Custom reconciliation tools to validate the following
|
| Verify Key Field Values | Ensure values like Condition Type, Material, Customer, Sales Org, Validity Dates, and Rates are correctly populated |
Business
The involvement of the business team is essential to confirm the completeness and accuracy of Purchasing Conditions once the data is loaded into S/4HANA. By reviewing Info Records and their related condition records, they help ensure that the migration meets business expectations. This early validation minimizes the risk of errors, supports a seamless cutover, and guarantees that pricing mechanisms work as intended from the first day of system usage.Completeness
| Task | Action |
|---|---|
| Participate in Post-Load Walkthroughs | Join scheduled validation sessions with the migration and functional teams |
| Review Loaded Condition Records | Access the S/4HANA system to view loaded info records and purchasing price conditions |
| Check for Missing Records | Identify any missing records that were expected but not loaded |
Accuracy
| Task | Action |
|---|---|
| Compare Against Approved Load File | Cross-check data in S/4HANA against the final business-approved load file used for migration |
| Validate Accuracy of Converted/Transformed Data | Review any transformed fields (e.g., currency conversion, unit mappings) for correctness |
| Log and Report Discrepancies | Use provided discrepancy log format or defect management tool to report any findings |
Syniti Reports
| # | Topic | Jira Ticket | Creation Date | Resolution Date | |
| 001 | Total Number of Records (RAW) in WP2 and QP2 | ||||
| 003 | Total Number of Records after applying data selection in WP2 and QP2 | ||||
| 004 | Reports per Eligibility Reason
| ||||
| 005 | Report the Info Records without Tax Information EINA-MATNR EINE-MWSKZ | ||||
| 006 | Coordinate with Gaurav’s team to develop automated reports to assess info record relevancy based on multiple criteria including vendor, material, deletion flags, and price conditions validity (35:26) |
Open Questions
| # | Topic | Jira Ticket | Creation Date| | Resolution Date | Solution Provided | Status | ANSWER |
| 001 | MDS Review CNV-1094: Missing info of Data Type & Length for all fields | ||||||
| 003 | Please mention on the MDS the clear rules on how pricing conditions (gross price, discounts, surcharges) must be maintained in the Info Record. | ||||||
| 004 | A mapping for Tax Codes are necessary (OLD|NEW) Please provide the Config Workbook. | ||||||
| 005 | Currently, there is no defined data mapping for the field EINE-J_1BNBM (NCM Code). Should we assume a 1:1 load without conversion, given that the field is populated in the legacy system? Although this field is marked as not required, legacy data exists. How should we plan to handle the mapping for this case?Please mention on the MDS | ||||||
| 006 | Retention Level for Info Records: should all Info Records have a Plant (EINA-WERKS) assigned. | ||||||
| 007 | Bhargavi: I've understood that ALL info records should be created at Plant Level, could you please confirm? | ||||||
| 008 | Bhargavi: is it a decision that for the same retention level Material|Vendor|PurchOrg|Plant a Contracts and Info Records cannot coexist on the same DB? In case this is a decision taken, should Info Records give priority to Contracts during the data migration and exclude the info record for those entries? |
MDS Review
| # | Topic | Jira Ticket | Creation Date| | Resolution Date | Solution Provided | Status | ANSWER |
| 001 | MDS Review CNV-1094: Missing info of Data Type & Length for all fields | ||||||
| 003 |
PF2: A016, A017, A018 ==> 163.554 records analysed | PDM-691 |
|
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||