| Status |
| |
|---|---|---|
| Owner | ||
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach for uploading Purchasing Info Record data into SAP S/4HANA. This includes the end-to-end method for extracting legacy data, applying the required transformation and validation rules, and preparing the final load files according to the approved templates and mapped fields.
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 Purchasing Info Record Master Data Standard(MDS) document. For Syensqo, Info Records will be migrated to support operational purchasing, sourcing strategies. These records will be validated, cleansed, and migrated to S4HANA based on MDS Fields and Governance rule.
From the current system landscape, Info Record data exists separately in the legacy systems (PF2 and WP2).
List of source systems and approximate number of records
Source Info Record
Source | Scope | Source Approx No. of Records | Target System | Target ApproxNo. of Records |
|---|---|---|---|---|
PF2 | An initial extract of the relevant* Inforecords data will be provided to the Business to support their decision-making regarding which info records should be migrated as Info Records and which should be migrated as Contracts.Relevant Info Records that are not flagged for deletion, and Purchasing Organization (+Plant where applicable) fall within the defined Enterprise Structure. In addition, both the Vendor and the Material must also be within scope. *RELEVANT Info records that are not marked for the deletion for inscope Purchasing Org/Plant based on the Enterprise Structure and Material based on Relevancy rule for 2019-Basic View and Vendors based on Relevancy rule for 3007-BP general. | Info Records >>>9.815 (EINA) Info Records >>> 10.230 (EINE) | S4H | |
WP2 | Info Records >>> 32.314 (EINA) Info Records >>> 34.364 (EINE) | S4H | ||
PF2 / WP2 | Data Analysis: EINA|EINE|KONP, condition records may exist for the following tables. PF2: A067, A017, A066, A018, A025, A028
WP2: A067, A017, A066, A018, A025, A028
Count of records per table:
|
|
|
Source DCT for Services/Other Material Types
Source | Scope | Source Approx No. of Records | Target System | Target ApproxNo. of Records |
|---|---|---|---|---|
PF2 | Data will be migrated for Relevant* Info records.Data will be populated in 'Data Collection DCT' by Business for Service master records or other materials (if required) for creation of PIRs where Inforecords are not in Legacy or data cannot be cleansed in Legacy.*RELEVANT Info records are those which are not marked for the deletion and are in 'inscope' Purchasing Org/Plant based on the Enterprise Structure and where Material are inscope based on Relevancy rule for 2019-Basic View and 2020_Material Purchasing view and Vendors are inscope based on Relevancy rule for 3007-BP general/3026/3027. | Services >>> 9.821 (PF2.ASMD) Services >>> 59 (PF2.MARA) | S4H | Services >>> 9.821 (ASMD) as DCT Services >>> 59 (MARA) as DCT |
WP2 | Services >>> 353 (WP2.ASMD) Services >>> 54 (WP2.MARA) | S4H | Services >>> 353 (ASMD) as DCT Services >>> 54 (MARA) as DCT |
Relevancy Rules
- Relevancy Rule from ECC (for non service materials)
1) PIRs for in-scope materials per the ObjectID CNV-2019 / CNV-2020 (Materials) relevancy rules will be migrated;
2) PIRs for in-scope Vendors per the ObjectID CNV-3007 / CNV-3026 / CNV-3027 (Vendors) relevancy rule will be migrated;
3) PIRs with in-scope and valid pricing conditions/scales (if used in legacy) will be migrated. PIRs without price are valid to be migrated.
4) Info records with current validity dates will be migrated. (IF EINA-LIFBI (LIFB) is not empty, then it should be >= Today's date )
5) Scales for valid Info records will be migrated.
6) if Info records are missing or cannot be created or cleansed in ECC then data must be collected from Business (DCT).
7) Info records with given conditions will be out of scope:
i) deletion flag at Header/item level
ii) Blocked (Header Level: IF EINA-SPINF LOEKZ is not initial. the entire Info Record is blocked (including the entries from EINE)) OR (ItemLevel: IF EINE-LOEKZ is not initial. The info record is blocked for the combination Vendor | Material | Purch Org | Plant)
iii) expired validity dates
iv) pricing conditions not in scope
v) Info records for Plants and/or Purchasing Organizations not in scope as per enterprise structure (ES)
8) PIRs Migration Rules (- decision for migration of Info Records will depend on given conditions)
- IF Contract exit at material level, than no PIR to be migrated
- IF an Ariba Catalog exists for the Vendor | Material | Purchasing Organisation, than no PIR to be migrated. (Catalogs data to be extracted from Ariba).
- IF Contract is at Material Group level then PIR is required to be migrated
- IF Consignment PIR, it must be migrated even if a contract already exists for the same Vendor / Material / PurchOrg
- IF a valid PIR with EINA-IDNLF Supplier Material Number maintained, then this PIR must remain in scope for migration, and cannot be suppressed by another rule
- IF we have an existing PIR with an Order Unit maintained (EINE-MEINS), and this Order Unit differs from the Order Unit in the material master (MARA-BSTME), then this PIR must remain in scope for migration to ensure the correct Order Unit is defaulted in the Purchase Order.
- Decision on Intercompany PIRs migration:
g1) For Intercompany only Pricing Condition will be loaded
g2) For the migration, Intercompany pricing condition records will be extracted from Legacy ECC (where available) and need to be reviewed by Finance before upload. PaPM will not send Price value just after GoLive.
TBC - Intercompany PIR migration Decision - Jira Ticket 1064
- Relevancy Rule from DCT (mainly for Service materials or where PIRs missing or cannot be cleansed in Legacy )
1) For Service master records and Service materials (ASMD and MARA table), the Data Collection Template (DCT) must be completed by the Business.
2) List of Service master records will be provided by functional leads(in DCT - 2019 Material Basic View), after validation with Business and other PODs.
3) Pricing data for service masters will be collected in DCT to create PIRs.
Process for NON-Service Materials
RULES in 'Decision by Rule' in Table1.
9) Decision on Intercompany PIRs migration:
9a) For Intercompany, only Pricing Condition will be loaded
9b) For the migration, Intercompany pricing condition records will be extracted from Legacy ECC (where available) and need to be reviewed by Finance before upload. PaPM will not send Price value just after GoLive.
TBC - Intercompany PIR migration Decision - Jira Ticket 1064
- Relevancy Rule from DCT (mainly for Service materials or where PIRs missing or cannot be cleansed in Legacy )
1) For Service master records and Service materials (ASMD and MARA table), the Data Collection Template (DCT) must be completed by the Business.
2) List of Service master records will be provided by functional leads(in DCT - 2019 Material Basic View), after validation with Business and other PODs.
3) Pricing data for service masters will be collected in DCT to create PIRs.
Process for NON-Service Materials
- Extract the Extract the data from Production.
- Prepare Excel reports to support the decision-making process.
- Share the Excel reports with the Business with pre populated field 'Decision by Rule' based on point8) above, so they can check which records are relevant for PIR creation.
- After review 'Decision by Rule' the Business can approve or makes the decision to override the rule by changing the decision in 'Migrate_AS' field. Once Business decision is done, data for selected Inforecord numbers will be extracted directly from ECC, and the necessary transformation rules will be applied for migration..
NOTES
- If PIRs with materials do not have Plant populated then we must check with
Business that Price will be applied to all plants. - For Intercompany only Pricing Condition will be loaded
DCT for Business Decision: Data Owners are required to confirm which existing legacy PIRs should be migrated as Purchasing Info Records in the new system.
Once the Data Owners finalize the list, the corresponding PIR data will be extracted from the legacy system, transformed, and will be loaded into S/4HANA.
Table1:
| Field Description | Usage of the field | SAP Fields |
| UNIQUE_ID | Unique ID defined by Syniti | |
| RELEASE NO. | Release of the object | |
| SOURCE SYSTEM | Source System ID | |
| TARGET SYSTEM | Target System ID | |
| Purchase Info Record | Info record Code | EINA-INFNR |
| Material Number | Material Code with leading zeros | EINA-MATNR |
| Material (Golden record) | ||
| Material Group | Material Group | EINA-MATKL |
| Account Number of Supplier(Vendor) | Account Number of Supplier | EINA-LIFNR |
| Vendor (Golden record) | ||
| Short Text For Purchasing Info Record | Short Text For Purchasing Info Record | EINA-TXZ01 |
| Order unit | Order Unit | EINA-MEINS |
| Base UoM | Base Unit of Measure | MARA-MEINS |
| Numerator for Conversion of Order Unit to Base Unit | Numerator for Conversion of Order Unit to Base Unit | MARM-UMREZ |
| Denominator for Conversion of Order Unit to Base Unit | Denominator for Conversion of Order Unit to Base Unit | MARM-UMREN |
| Vendor Material Number | Material Number Used by Supplier | EINA-IDNLF |
| Purchasing Organization | Purchasing Organization | EINE-EKORG |
| Infotype | Purchasing Info Record Category | EINE-ESOKZ |
| Purchasing info record category Description | Purchasing info record category Description | DD07T-DDTEXT |
| Plant | Plant | EINE-WERKS |
| Planned Delivery Time (in Days) | Planned Delivery Time (in Days) | EINE-PLIFZ |
| Available From Date | DD/MM/YYYY | EINA-LIFAB |
Available To date | DD/MM/YYYY | EINA-LIFBI |
| Currency | Currency | EINE-WAERS |
| Minimum Order Quantity | Min Order Quantity | EINE-MINBM |
| Standard Purchase Order Quantity | Standard Purchase Order Quantity | EINE-NORBM |
| Net Price in Purchasing Info Record | Net Price | Apply the pricing logic to retrieved from the mentioned access sequence the first price encountered. A017, A066, A018, A025, A028, A067 |
| Price unit (per quantity) | Price unit (per quantity) | |
| Order Price Unit | Order Price Unit | |
| Pricing Condition Start date | DD/MM/YYYY | |
| Pricing condition End Date | DD/MM/YYYY | |
| Intercompany Flag | <YES / NO> | If LFA1 = ZZR_SEGT_ATTR = 'G' Then 'Yes' |
| Info Record consignment flag | <YES / NO> | IF EINE-ESOKZ = 2 |
| Purchasing Group | Purchasing Group | EINE-EKGRP |
| ECC Contract Flag | <YES / NO> | Join EKKO-BSART = K and: 1)Match on (Material + Vendor+ Purchasing Org) or Material + Vendor+ Purchasing Org+ Plant) and 1a) Contract is Active and 1b) Contract validity Date has not expired IF value is encountered, Populate = YES ---------------If 1) is not found then ------------ 2) Match on (Material Grp + Vendor+ Purchasing Org) or Match on (Material Grp + Vendor+ Purchasing Org + Plant) 2a) Contract is Active and 2b) Contract validity Date has not expired IF value is encountered, Populate = YES |
| Contract (Material number) | ||
| Contract (Material group) | ||
| Contract Number | ||
| Total Number of Contracts | ||
| ICERTIS Contract flag | <YES / NO> The link key is Vendor | Purchasing Organisation | We will request Icertis Contract information (when available) and you will add flag based on key (Vendor + Purchasing Org) match |
| Ariba Catalog Flag | <YES / NO> Catalog info File will be extracted from Ariba | Check Supplier LFA1-ZZR_ZLATR6 = 'CEA' or 'CIA' or 'CIM' or 'COA', or 'CSA' and Ariba Supplier = PIR supplier |
| Decision by Rule |
5a) If a valid PIR exist with EINA-IDNLF Vendor Material Number then PIR needs to be migrated then Populate value = PIR is required 5b) If Order Unit (EINA-MEINS) on PIR differs from the Order Unit in the material master (MARA-BSTME), then Populate = PIR is required 7. ELSE populate value = 'TBC by Business' | |
| Migrate_AS_As (Business_Decision) | Possible Values: Populate based on field 'Decision by Rule' -TBC by Business - Catalog BUSINESS INPUT ALLOWED TO OVERRIDE THE 'DECISION BY RULE' Note: Transformation will be applied where Decision = 'PIR' or 'Pricing Conditions' | |
| Choose Golden PIR | Created Drop Down <X / ' '> BUSINESS INPUT ALLOWED |
|
| Business_Approval_For_Migration | Pre-populated field : Business confirmation flag = 'yes'/'no' BUSINESS INPUT ALLOWED |
|
| Z_DELETE | Exclude Info Record Record to be migrated BUSINESS INPUT ALLOWED | |
| z Comment | <OPEN TEXT FIELD> BUSINESS INPUT ALLOWED |
Additional Information
MDS Documents
Date | Current Link |
|---|---|
20250915 |
Additional Information
Multi-language Requirement (TBC) Jira Ticket 1063
Multi language is supported for Purchase Info Records. Login via a different language will show the description displayed in the logon language if the language key is maintained.
The following languages are allowed:
- Core languages: EN - English, FR - French, IT - Italian and ZH - Mandarin.
- Additional languages: PT - Portuguese, DE - German, ES - Spanish,
TH - Thai(descoped by CR0086, users can no use TH as their login language). - Supplier languages that are possible: FR - French, EN - English, ES - Spanish, DE - German, IT - Italian, NL - Dutch, PT - Portuguese, ZH - Mandarin, PL - Polish, JA - Japanese, KO - Korean, FI - Finnish, BG - Bulgarian, RU - Russian, TH- Thai, ZF - Chinese traditional, SK - Slovak, Z9 - Brazil Portuguese. (TH has not been descoped from such requirements where we need to send a document to a supplier in there own language, therefore it should be valid for Info Records Text.)
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
N/ATarget 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.
| draw.io Diagram | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Target Design
The technical design of the target for this conversion approach.
Follow MDS for Governance Rules.Google Drive Live Link url https://docs.google.com/spreadsheets/d/1atpR0RJMY_SDubf5CznIJ4WdFHsWC0mq/edit?gid=1399282990#gid=1399282990
| Technical Table-Field | Field Label | Description | Syensqo Requirement | Data Type | Length |
| EINA | MATNR | Material number referenced by the Info Record. | Required | CHAR | 18 |
| EINA | LIFNR | Supplier (Business Partner/Vendor) for this Info Record. | Required | CHAR | 10 |
| EINA | TXZ01 | Short text/description used for free-text PIRs. | Conditional | CHAR | 40 |
| EINA | IDNLF | Supplier’s material number/reference. | Conditional | CHAR | 35 |
| EINA | LTSNR | Supplier subrange identifier. | Conditional | NUMC | 10 |
| EINA | MFRNR | Manufacturer number. | Conditional | CHAR | 10 |
| EINE | EKORG | Purchasing organization responsible for this PIR. | Required | CHAR | 4 |
| EINE | ESOKZ | Info type (Standard, Subcontracting, Consignment, Pipeline). | Required | CHAR | 1 |
| EINE | WERKS | Plant for which the PIR applies. | Conditional | CHAR | 4 |
| EINE | EKGRP | Purchasing group (buyer responsibility). | Conditional | CHAR | 3 |
| EINE | WAERS | Currency for PIR pricing. | Conditional | CUKY | 5 |
| EINE | MINBM | Minimum order quantity. | Conditional | QUAN | 13 |
| EINE | NORBM | Standard order quantity. | Conditional | QUAN | 13 |
| EINE | APLFZ | Planned delivery time from supplier. | Conditional | TIMS | 6 |
| EINE | UEBTO | Overdelivery tolerance limit. | Conditional | CHAR | 30 |
| EINE | UEBTK | Unlimited overdelivery allowed. | Conditional | CHAR | 30 |
| EINE | UNTTO | Underdelivery tolerance. | Conditional | CHAR | 30 |
| EINE | NETPR | Net price. | Conditional | CURR | 11 |
| EINE | PEINH | Price unit (per quantity). | Conditional | DEC | 5 |
| EINE | BPRME | Order price unit. | Conditional | CURR | 11 |
| EINE | WEBRE | GR-Based Invoice Verification flag. | Conditional | CHAR | 30 |
| EINE | KZABS | Acknowledgment required from supplier. | Conditional | CHAR | 40 |
| EINE | MWSKZ | Tax code. | Conditional | CHAR | 2 |
| EINE | BWTAR | Valuation type (split valuation). | Conditional | CHAR | 30 |
| EINE | EVERS | Shipping instructions. | Conditional | CHAR | 30 |
| EINE | MEPRF | Price date category. | Conditional | DATS | 8 |
| EINE | INCO1 | Incoterms. | Conditional | CHAR | 30 |
| EINE | INCO2 | Incoterms location. | Conditional | CHAR | 30 |
| EINE | XERSN | No ERS (Evaluated Receipt Settlement). | Conditional | CHAR | 1 |
| EINE | VERID | Production version (subcontracting). | Conditional | CHAR | 30 |
| EINE | BSTMA | Maximum order quantity. | Conditional | QUAN | 13 |
| EINE | RDPRF | Rounding profile. | Conditional | CHAR | 30 |
| EINE | J_1BNBM | NCM code (Brazil). | Conditional | CHAR | 30 |
| EINE | INCOV | Incoterm version. | Conditional | CHAR | 30 |
| EINE | INCO2_L | Extended Incoterms location fields. | Conditional | CHAR | 30 |
| EINE | INCO3_L | Extended Incoterms location fields. | Conditional | CHAR | 30 |
| EINE | INCO2_KEY | Incoterms location keys. | Conditional | CHAR | 30 |
| EINE | INCO3_KEY | Incoterms location keys. | Conditional | CHAR | 30 |
| A018 | KAPPL | Application (e.g., “M” for purchasing). | Conditional | CHAR | 30 |
| A018 | KSCHL | Condition type key. | Conditional | CHAR | 30 |
| A018 | DATBI | Valid-to date. | Conditional | DATS | 8 |
| A018 | DATAB | Valid-from date. | Conditional | DATS | 8 |
| KONP | KSCHL | Condition type (price, discount, surcharge, etc.). | Conditional | CHAR | 30 |
| KONP | STFKZ | Scale type. | Conditional | CHAR | 1 |
| KONP | KZBZG | Scale base type. | Conditional | CHAR | 1 |
| KONP | KSTBM | Scale quantity. | Conditional | QUAN | 13 |
| KONP | KONMS | Scale unit of measure. | Conditional | CHAR | 30 |
| KONP | KSTBW | Scale value. | Conditional | CURR | 11 |
| KONP | KONWS | Scale currency. | Conditional | CUKY | 5 |
| KONP | KRECH | Calculation type. | Conditional | CHAR | 30 |
| KONP | KBETR | Condition amount. | Conditional | CURR | 11 |
| KONP | KONWA | Condition currency. | Conditional | CUKY | 5 |
| KONP | KPEIN | Pricing unit. | Conditional | DEC | 5 |
| KONP | KMEIN | Unit of measure for condition. | Conditional | UNIT | 3 |
| KONP | PRSCH | Scale group. | Conditional | CHAR | 30 |
| KONP | KUMZA | Numerator for scale conversion. | Conditional | CHAR | 30 |
| KONP | KUMNE | Denominator for scale conversion. | Conditional | CHAR | 30 |
| KONP | MEINS | Base unit. | Conditional | UNIT | 3 |
| KONP | MXWRT | Lower limit for validity. | Conditional | CHAR | 30 |
| KONP | GKWRT | Upper limit. | Conditional | CHAR | 30 |
| KONP | PKWRT | Planned condition value. | Conditional | CHAR | 30 |
| KONP | FKWRT | Cumulative value. | Conditional | CURR | 11 |
| KONP | RSWRT | Cumulative accrual. | Conditional | CHAR | 30 |
| KONP | KWAEH | Condition currency key. | Conditional | CUKY | 5 |
| KONP | UKBAS | Planned basis. | Conditional | CHAR | 30 |
| KONP | KZNEP | Exclusion indicator. | Conditional | CHAR | 1 |
| KONP | LIFNR | Supplier. | Conditional | CHAR | 10 |
| KONP | MWSK1 | Tax code. | Conditional | CHAR | 30 |
| KONP | BOMAT | Material for settlement. | Conditional | CHAR | 30 |
| KONP | KBRUE | Accrual. | Conditional | CHAR | 30 |
| KONP | KSPAE | Retroactive pricing indicator. | Conditional | CHAR | 30 |
| KONP | BOSTA | Condition record status. | Conditional | CHAR | 30 |
| KONP | UMA_PI | Promotion number. | Conditional | CHAR | 30 |
| KONP | UMA_AG | Sales deal number. | Conditional | CHAR | 30 |
| KONP | UMA_SQ | Sales quotation number. | Conditional | CHAR | 30 |
| KONP | VALTG | Additional value days. | Conditional | CURR | 11 |
| KONP | VALDT | Fixed value date. | Conditional | DATS | 8 |
| KONP | ZTERM | Payment terms. | Conditional | CHAR | 30 |
| KONP | ANZAUF | Number of orders. | Conditional | NUMC | 10 |
| KONP | MIKBAS | Minimum condition base value. | Conditional | CHAR | 30 |
| KONP | MXKBAS | Maximum condition base. | Conditional | CHAR | 30 |
| KONP | OMXWRT | Maximum condition value. | Conditional | CURR | 11 |
| KONP | LF_STG | Increment scale. | Conditional | CHAR | 30 |
| KONP | LF_KAL | Pricing scale. | Conditional | CHAR | 30 |
| KONP | VKKAL | Relevance to pricing. | Conditional | CHAR | 30 |
| KONP | AKTNR | Promotion number. | Conditional | NUMC | 10 |
| KONP | UMA_BO | Agreement number. | Conditional | CHAR | 30 |
| KONP | MWSK2 | Withholding tax code. | Conditional | CHAR | 30 |
| KONP | VERTT | Contract type. | Conditional | CHAR | 30 |
| KONP | VERTN | Contract number. | Conditional | NUMC | 10 |
| KONP | VBEWA | Flow type. | Conditional | CHAR | 30 |
| KONP | MDFLG | Matrix maintenance flag. | Conditional | CHAR | 30 |
| KONP | KFRST | Release status. | Conditional | CHAR | 30 |
| KONP | UASTA | Condition processing status. | Conditional | CHAR | 30 |
| KONH | KVEWE | Application usage. | Conditional | CHAR | 1 |
| KONH | KOTABNR | Condition table number. | Conditional | NUMC | 10 |
| KONH | KSCHL | Condition type. | Conditional | CHAR | 30 |
| KONH | DATAB | Valid-from date. | Conditional | DATS | 8 |
| KONH | DATBI | Valid-to date. | Conditional | DATS | 8 |
| KONH | KOSRT | Search term. | Conditional | CHAR | 30 |
| KONH | KZUST | Responsibility indicator. | Conditional | CHAR | 30 |
| KONH | LICNO | License number. | Conditional | CHAR | 35 |
| KONH | LICDT | License date. | Conditional | DATS | 8 |
| KONH | REFERENCE | Reference text. | Conditional | CHAR | 35 |
| KONH | PRICEAPPROVALREQUEST | Price approval request number. | Conditional | CHAR | 30 |
| A017 | KAPPL | Application for pricing (Purchasing = “M”). | Conditional | CHAR | 30 |
| A017 | KSCHL | Condition type key (e.g., price, discount, freight). | Conditional | CHAR | 30 |
| A017 | LIFNR | Supplier relevant for the condition record. | Conditional | CHAR | 10 |
| A017 | MATNR | Material applicable to the condition. | Conditional | CHAR | 18 |
| A017 | EKORG | Purchasing organization owning the condition. | Conditional | CHAR | 4 |
| A017 | WERKS | Plant for which the condition is valid. | Conditional | CHAR | 4 |
| A017 | ESOKZ | Infotype (Standard, Subcontracting, Consignment). | Conditional | CHAR | 1 |
| A017 | DATBI | Valid-to date of the condition. | Conditional | DATS | 8 |
| A017 | DATAB | Valid-from date of the condition. | Conditional | DATS | 8 |
| A017 | VAKEY | Vendor + Material | Conditional | CHAR | 30 |
| A025 | KAPPL | Application for pricing (Purchasing). | Conditional | CHAR | 30 |
| A025 | KSCHL | Condition type for the condition record. | Conditional | CHAR | 30 |
| A025 | LIFNR | Supplier associated with the condition. | Conditional | CHAR | 10 |
| A025 | EKORG | Purchasing organization for the condition. | Conditional | CHAR | 4 |
| A025 | MATKL | Material group applicable to the condition. | Conditional | CHAR | 9 |
| A025 | INFNR | Info record number (if condition tied to PIR). | Conditional | NUMC | 10 |
| A025 | WERKS | Plant where the condition applies. | Conditional | CHAR | 4 |
| A025 | ESOKZ | Infotype used to classify procurement type. | Conditional | CHAR | 1 |
| A025 | DATBI | Valid-to date for the condition. | Conditional | DATS | 8 |
| A025 | DATAB | Valid-from date. | Conditional | DATS | 8 |
| A025 | VAKEY | Vendor + Plant + P. Org | Conditional | CHAR | 30 |
| A028 | KAPPL | Application (Purchasing). | Conditional | CHAR | 30 |
| A028 | KSCHL | Condition type. | Conditional | CHAR | 30 |
| A028 | LIFNR | Supplier. | Conditional | CHAR | 10 |
| A028 | EKORG | Purchasing organization. | Conditional | CHAR | 4 |
| A028 | MATKL | Material group. | Conditional | CHAR | 9 |
| A028 | INFNR | Info record number. | Conditional | NUMC | 10 |
| A028 | ESOKZ | Infotype. | Conditional | CHAR | 1 |
| A028 | DATBI | Valid-to date. | Conditional | DATS | 8 |
| A028 | DATAB | Valid-from date. | Conditional | DATS | 8 |
| A028 | VAKEY | Vendor + Material + Plant | Conditional | CHAR | 30 |
| A066 | KAPPL | Pricing application. | Conditional | CHAR | 30 |
| A066 | KSCHL | Condition type. | Conditional | CHAR | 30 |
| A066 | LIFNR | Supplier. | Conditional | CHAR | 10 |
| A066 | MATNR | Material. | Conditional | CHAR | 18 |
| A066 | EKORG | Purchasing organization. | Conditional | CHAR | 4 |
| A066 | ESOKZ | Infotype. | Conditional | CHAR | 1 |
| A066 | BSTME | Order unit for pricing. | Conditional | UNIT | 3 |
| A066 | DATBI | Valid-to date. | Conditional | DATS | 8 |
| A066 | DATAB | Valid-from date. | Conditional | DATS | 8 |
| A067 | KAPPL | Pricing application. | Conditional | CHAR | 30 |
| A067 | KSCHL | Condition type. | Conditional | CHAR | 30 |
| A067 | LIFNR | Supplier. | Conditional | CHAR | 10 |
| A067 | MATNR | Material. | Conditional | CHAR | 18 |
| A067 | EKORG | Purchasing organization. | Conditional | CHAR | 4 |
| A067 | ESOKZ | Infotype. | Conditional | CHAR | 1 |
| A067 | WERKS | Plant. | Conditional | CHAR | 4 |
| A067 | BSTME | Order unit. | Conditional | UNIT | 3 |
| A067 | DATBI | Valid-to date. | Conditional | DATS | 8 |
| A067 | DATAB | Valid-from date. | Conditional | DATS | 8 |
| KONW | KSTBW | Scale value threshold. | Conditional | CURR | 11 |
| KONW | KBETR | Condition amount for this scale level. | Conditional | CURR | 11 |
| KONM | KSTBM | Quantity threshold for scale. | Conditional | CURR | 11 |
| KONM | KBETR | Condition amount for this quantity level. | Conditional | CURR | 11 |
Data Cleansing
Data Cleansing Reports
Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created.
| Cleansing Report | Objective | Comments |
|---|---|---|
Report: Check PIRs where EINA-LIFBI [not DATBI] <= today’s date, however the Info Record is not deleted (EINA-LOEKZ is not set). | Objective: Identify Info records that are not deleted, however is not anymore valid to be used. | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. |
| Report: Vendor Status / Blocking Issues impacting PIR usability (vendor blocked for purchasing / marked for deletion) | Objective: Identify whether the Vendor related to the info record is blocked, while the Info Record is still valid, | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. |
| Report: Material Status / Blocking Issues impacting PIR usability (material blocked for procurement / deleted) | Objective: Identify whether the Material related to the info record is blocked, while the Info Record is still valid, | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. |
| Report: All entries deleted at EINE, but activated EINA | Objective: Identify whether the tables EINA and EINE are aligned | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. |
| Report: Identify Valid Info Records in scope and without a Price | Objective: Multiple valid Inforecors (not deleted) are created, however there's no price assigned to it. It even had a historic of prices. | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. |
| Report: Identify all records where a Contract and PIR exist on the source systems. | Objective: For Syensqo both documents cannot be valid on the same period. All data has to be validated | |
| Report: Check Purchasing UOM adheres to S4 ISO standard | Object: Cleanse the UOMs that are not in scope. | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. |
| Report: Deduplication checks | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. | |
| Report: Report the valid Info Records and are in scope for migration; however, no pricing condition is maintained for it. | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. | |
| Report: Check whether the Rounding Profile used for the Info Record is in scope for the TO-BE | Note: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. | |
| Report: Valid Info Records without a price 0,00 | Objective: Set records that are not valid as deleted | |
| Report: Fuzzy Analysis of Purchasing Info Record (PIR) Usage - NOTE: The reports should be based on the completion of the 'Decision DCT' by the Business, ensuring that we know which PIRs are required to be created. | Object: Identify potentially duplicate or redundant PIRs based on actual usage over the last 5 years. |
Checks that each valid Info Record, have an a active material (MARA-LVORM = '').
Once List of PIRs to be migrated is confirmed by Business:
Deduplication Report is required for
Set1 - Vendor + Material + Purchase Org (due to PIRs from 2 ECC Systems or due to Vendor/Material Deduplication)
Set2 - Vendor + Material +Purchase Org + Plant (due to PIRs from 2 ECC Systems or due to Vendor/Material Deduplication)
Check the Pricing Conditions with a validity dated bigger than 1 Year
Identify Valid PIRs in scope, but without a Price or Zero price
Identify the Vendor Material Number (EINA-INDLF) that is different on the same record between WP2 and PF2 systems
Conversion Process
The high-level process is represented by the diagram below:
DCT to be used for
1) Info records for Service Materials
2) Info records which are not found in ECC
3) Info Records that cannot be cleansed in Source System.
e
Data Privacy and Sensitivity
N/AExtraction
Extraction Run Sheet
001 | PIRs will be extracted from ECC (PF2 and WP2) based on Business decision in 'DCT for Business Decision' and will be transformed for migration. | Syniti |
| Req # | Requirement Description | Team Responsible |
|---|---|---|
| 001 | Verify connectivity and authorizations to source ECC systems before execution. | Syniti Team |
| 002 | Confirm selection scope: Purchasing Organizations, Plants, Vendors, and Materials to be included in the extraction. | Syniti Team |
| 005 | Extract Info Records for Vendors that are not marked for deletion (LFM1-LOEVM ≠ ‘X’) and are within scope. | Syniti Team |
| 006 | Extract Info Records for active Vendors and Materials only – exclude entries with deletion or obsolete flags. | Syniti Team |
| 007 | Extract Info Records for Materials that are not marked for deletion and belong to valid Info Record combinations. | Syniti Team |
| 008 | Extract condition records (KONH/KONP, A017/A018/...) corresponding to valid Info Records, using non-overlapping validity dates. | Syniti 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) | Syniti Team |
| 012 | Submit extraction output for validation to Business | 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) - Material/Service Master records
This template captures the essential fields required for the Purchasing Info Record (PIR) object. The structure of DCT to be used when data needs to be collected or enriched (manually), especially for services or records not available or incomplete in the legacy system; it should collect information for header / item / condition type / scales / long text (where required).
This table describes the dependencies between the DCT files for each Object:
Object | Rule |
Regular PIR | Can have up to 5 DCTs, with the following dependency: DCT 2 – Exclusively depends from 1 DCT 3 – May depend from 1 (Basic Data related) or 2 (Purch Org related) DCT 4 – Directly dependent from 2 DCT 5 – Directly dependent from 4 *Syniti updates Stagging Areas of the MC |
DCT for Price Conditions (IC) | DCT 4 – Doesn’t have precedent DCTs DCT 5 – Directly dependent from DCT 4 *Syniti updates CSV files for COND_A IDoc |
1 - DCT for PIR: -
Data Collection Template (DCT) - Material/Service Master records
This template captures the essential fields required for the Purchasing Info Record (PIR) object. The structure of DCT to be used when data needs to be collected or enriched manually, especially for services or records not available or incomplete in the legacy system; it should collect information for header / item / condition type / scales / long text (where required).
Basic Data Info
| Field Name | Data Type | Length | Description | Rule |
| INFNR | CHAR | 10 | Info Record Number | Required |
| EINA-MATNR | CHAR | 18 | Material Number | Required |
| EINA-MATKL | CHAR | 9 | Material Group | Conditional |
| EINA-LIFNR | CHAR | 10 | Vendor Number | Required |
| EINA-TXZ01 | CHAR | 40 | Sort term for Non-Stock Info Records | Conditional |
| EINA-TXZ01 | CHAR | 40 | Short Text | Conditional |
| EINA-MEINS | UNIT | 3 | Order Unit | Conditional |
| EINA-UMREZ | NUMC | 5 | Numerator for Conversion | Conditional |
| EINA-UMREN | NUMC | 5 | Denominator for Conversion | Conditional |
| EINA-IDNLF | CHAR | 35 | Material Number Used by Supplier | Conditional |
| EINA-VERKF | CHAR | 30 | Salesperson at vendor | Conditional |
| EINA-TELF1 | CHAR | 16 | Vendor’s telephone number | Conditional |
| EINA-MAHN1 | CURR | 11 | Dunning amount limit (level 1) | Conditional |
| EINA-MAHN2 | CURR | 11 | Dunning amount limit (level 2) | Conditional |
| EINA-MAHN3 | CURR | 11 | Dunning amount limit (level 3) | Conditional |
| EINA-LMEIN | UNIT | 3 | Base unit of measure. | Conditional |
| EINA-VABME | CURR | 13 | Total value of purchase order items | Conditional |
| EINA-WGLIF | CHAR | 3 | Vendor country key | Conditional |
| EINA-KOLIF | CHAR | 10 | Collective number for vendor | Conditional |
| EINA-URZLA | CHAR | 3 | Terms of payment key | Conditional |
| EINA-REGIO | CHAR | 3 | Region (state, province, county) | Conditional |
| EINA-MFRNR | CHAR | 10 | Manufacturer number | Conditional |
| EINA-LIFAB | DATS | 8 | Validity start date of vendor record | Conditional |
| EINA-LIFBI | DATS | 8 | Validity end date of vendor record | Conditional |
| EINA-RELIF | CHAR | 1 | Relevant for automatic release (indicator) | Conditional |
Long Text General Data
2 - DCT for PIR: - Purchase Organization Info
| Field Name | Data Type | Length | Description | Rule |
| INFNR | CHAR | 10 | Info Record Number | Required |
| EINE-EKORG | CHAR | 4 | Purchasing Organization | Required |
| EINE-ESOKZ | CHAR | 1 | Info Category (Standard/Subcontracting/Consignment) | Required |
| EINE-WERKS | CHAR | 4 | Plant | Required |
| EINE-EKGRP | CHAR | 3 | Purchasing Group | Required |
| EINE-WAERS | CUKY | 5 | Currency Key | Required |
| EINE-MINBM | QUAN | 13,3 | Minimum Order Quantity | Required |
| EINE-NORBM | QUAN | 13,3 | Normal Order Quantity | Conditional |
| EINE-APLFZ | DEC | 3 | Planned Delivery Time (in Days) | Conditional |
| EINE-UEBTO | DEC | 3 | Overdelivery Tolerance Limit (%) | Conditional |
| EINE-UEBTK | CHAR | 1 | Unlimited Overdelivery Allowed (Indicator) | Conditional |
| EINE-UNTTO | DEC | 3 | Under delivery Tolerance Limit (%) | Conditional |
| EINE-BWTAR | CHAR | 10 | Valuation Type | Conditional |
| EINE-MTXNO | CHAR | 20 | Material Text Number | Conditional |
| EINE-WEBRE | CHAR | 1 | Goods Receipt-Based Invoice Verification | Conditional |
| EINE-KZABS | CHAR | 1 | Final Invoice Indicator | Conditional |
| EINE-MWSKZ | CHAR | 2 | Tax Code | Conditional |
| EINE-EVERS | CHAR | 2 | Shipping Instructions | Conditional |
| EINE-BSTAE | CHAR | 2 | Confirmation Control Key | Conditional |
| EINE-XERSN | CHAR | 1 | Reminder for Goods Receipt | Conditional |
| EINE-MHDRZ | DEC | 3 | Minimum Remaining Shelf Life (in Days) | Conditional |
| EINE-IPRKZ | CHAR | 1 | Info Record Update Indicator | Conditional |
| EINE-BSTMA | QUAN | 13 | Maximum Order Quantity | Conditional |
| EINE-EXPRF | CHAR | 1 | Export/Import Indicator | Conditional |
| EINE-RDPRF | CHAR | 1 | Rounding Profile | Conditional |
| EINE-VENDOR_RMA_REQ | CHAR | 1 | Vendor RMA (Return Material Authorization) Required | Conditional |
| EINE-SKTOF | CHAR | 1 | Cash Discount Indicator | Conditional |
| EINE-MEPRF | CHAR | 1 | Price Determination Schema (Pricing Profile) | Conditional |
| EINE-INCOV | CHAR | 3 | Incoterms Version | Conditional |
| EINE-INCO1 | CHAR | 3 | Incoterms (Part 1) | Conditional |
| EINE-INCO2_L | CHAR | 70 | Incoterms Location 1 (Long Text) | Conditional |
| EINE-INCO3_L | CHAR | 70 | Incoterms Location 2 (Long Text) | Conditional |
| EINE-NETPR | CURR | 11 | Net price. | Conditional |
| EINE-PEINH | DEC | 5 | Price unit (per quantity). | Conditional |
| EINE-BPRME | CURR | 11 | Order price unit. | Conditional |
| EINE-J_1BNBM | CHAR | 30 | NCM code (Brazil) | Conditional |
| unit. | Conditional | |||
| EINE-J_1BNBM | CHAR | 30 | NCM code (Brazil) | Conditional |
3 - DCT for PIR: - Long Text
| Field Name | Data Type | Length | Description | Rule |
| INFNR | CHAR | 10 | Info Record Number | Required |
| EKORG | CHAR | 4 | Purchasing Organization *To create a text for General Data, send the field empty | Required |
| ESOKZ | CHAR | 1 | Purchasing Info Category (Standard, Subcontracting, Consignment, Pipeline) *To create a text for General Data, send the field empty | Required |
| WERKS | CHAR | 4 | Plant | Required |
| TDSPRAS | CHAR | 1 | Language Key | Required |
| TEXT | CHAR | Text | Required |
4 - DCT for PIR: - Conditions
| Field Name | Data Type | Length | Description | Rule |
| INFNR | CHAR | 10 | Info Record Number | Required |
| COND-EKORG | CHAR | 4 | Purchasing Organization | Required |
| COND-ESOKZ | CHAR | 1 | Purchasing Info Category (Standard, Subcontracting, Consignment, Pipeline) | Required |
| COND-WERKS | CHAR | 4 | Plant | Required |
| COND-KOPOS | NUMC | 3 | Sequential Number of Condition Record | Required |
| COND-COND_TYPE | CHAR | 4 | Condition Type (e.g., PB00, PBXX, RA01) | Required |
| COND-VALID_FROM | DATS | 8 | Validity Start Date for the Condition | Conditional |
| COND-VALID_TO | DATS | 8 | Validity End Date for the Condition | Conditional |
| KRECH | CHAR | 1 | Calculation Type for Condition (e.g., Percentage, Amount) | Conditional |
| COND-KBETR_EXT | CURR | 11 | Condition Amount (External Representation) | Conditional |
| COND-KONWA | CUKY | 5 | Currency Key for Condition | Conditional |
| COND-KPEIN | DEC | 5 | Pricing Unit (Base Quantity for Condition) | Conditional |
| COND-KMEIN | UNIT | 3 | Condition Unit (Unit of Measure for Condition) | Conditional |
| COND-KUMZA | DEC | 5 | Numerator for Condition Conversion Factor | Conditional |
| COND-KUMNE | DEC | 5 | Denominator for Condition Conversion Factor | Conditional |
| COND-MEINS | UNIT | 3 | Base Unit of Measure | Conditional |
| COND-KONMS | UNIT | 3 | Condition Unit of Measure (Alternative) | Conditional |
| COND-EXCLUSION_IND | CHAR | 1 | Exclusion Indicator (for Condition Exclusion Logic) | Conditional |
5 - DCT for PIR: - Scales
| Field Name | Data Type | Length | Description | Rule |
| INFNR | CHAR | 10 | Info Record Number | Required - Field reference from above condition DCT |
| EKORG | CHAR | 4 | Purchasing Organization | Required - Field reference from above condition DCT |
| ESOKZ | CHAR | 1 | Purchasing Info Category (Standard, Subcontracting, Consignment, Pipeline) | Required - Field reference from above condition DCT |
| WERKS | CHAR | 4 | Plant | Required - Field reference from above condition DCT |
| KOPOS | NUMC | 3 | Sequential Number of Condition Record | Required |
| COND_TYPE | CHAR | 4 | Condition Type (e.g., PB00, PBXX, RA01) | Required |
| VALID_FROM | DATS | 8 | Validity Start Date for Condition | Conditional |
| VALID_TO | DATS | 8 | Validity End Date for Condition | Conditional |
| LINE_NO | NUMC | 6 | Scale Line Number | Conditional |
| KSTBM_QTY | QUAN | 13 | Scale Quantity or Value Basis (threshold for scale) | Conditional |
| KBETR_QTY | CURR | 11 | Condition Rate (price or percentage) | Conditional |
| SCALE_VAL | CURR | 13 | Scale Value (e.g., price value corresponding to KSTBM) | Conditional |
| KBETR_VAL | CURR | 13 | Calculated Condition Amount for the Scale Level | Conditional |
Long Text Purchasing Organization
| Data Type | Length | Description | Rule | |
| INFNR | CHAR | 10 | Info Record Number | Required |
| EKORG | CHAR | 4 | Purchasing Organization | Required |
| ESOKZ | CHAR | 1 | Purchasing Info Category (Standard, Subcontracting, Consignment, Pipeline) | Required |
| WERKS | CHAR | 4 | Plant | Required |
| TDSPRAS | CHAR | 1 | Language Key | Required | TEXT | CHAR | Text | Required |
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| 001 | ECC system access and table authorizations (connectivity) | Syniti team |
| 002 | SQL access to Production DB or a copy of it's relevant tables (connectivity) | Syniti team |
| 003 | Availability of DCT information for cases where Info Records are missing in ECC but required in S/4. | Data team |
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:
- 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 Mapping/Rules (Source ECC / DCT)
| Source Field Information | Transform Rules | Target Field Information | |||||||||||||
| Sequence | Technical Source Table | Field Name | Technical Source Field | Field Type | Field Length | Mapping Type | Transform Rule or Default Value | Validation Rule Inline with Governance Rule | Comments | Field Description | Type | Length | Decimal | Sap Table Name | Sap Field Name |
| 1.001 | EINA | ||||||||||||||
| INFNR | Legacy Number of Purchasing Info Record | NUMC | 10 | Not for Intercompany IF DCT Intercompany Flag <> "", target structure is empty (skipt the record) | - Mandatoryfor Migration Cockpit | Legacy Number of Purchasing Info Record | NUMC | 10 | EINA | INFNR | ||||
| 1.002 | EINA/DCT | ECC/DCT: MATNR |
DCT: Material Number
| (Material Number | CHAR | 18 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for <MATERIALS> and update the target field. | - Relevant for DataCleansing - Relevant for DataConversion (Mapping)
| Product Number | CHAR | 18 | EINA | MATNR | |||
| 1.003 | EINA |
ECC/DCT: |
MATKL | Material Group - MATKL | CHAR | 9 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for <MATKL> and update the target field. | Dependent on Configuration | - Relevant for DataCleansing | Product Group | CHAR | 9 | EINA | MATKL | |
| 1.004 | EINA | ECC/DCT: LIFNR |
| Supplier's Account Number (Vendor Number - LIFNR) | CHAR | 10 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Vendor <LIFNR> and update the target field. | - Mandatoryfor Migration Cockpit | Supplier's Account Number | CHAR | 10 | EINA | LIFNR | |||
| 1.005 | EINA | ECC/DCT: TXZ01 |
| Short Text for Purchasing Info Record | CHAR | 40 | 1) Copy source field value as-is to the target field (1:1 direct mapping). | Short Text for Purchasing Info Record | CHAR | 40 | EINA | TXZ01 | |||||||
| 1.006 | EINA | ECC: SORTL | Sort Term for Non-Stock Info Records | CHAR | 20 | 1) Copy source field value as-is to the target field (1:1 direct mapping). | Sort Term for Non-Stock Info Records | CHAR | 20 | EINA | SORTL | ||||
| 1.007 | EINA | ECC/DCT: MEINS |
DCT: Order unit
| Order Unit (ISO Format) | UNIT | 3 | Transformation Rule | 1)Use the source value, and lookup on the mapping table for Unit of Measure - UOM <MEINS> and update the target field. | Dependent on Configuration | - Relevant for DataConversion (Mapping) | Order Unit (ISO Format) | UNIT | 3 | EINA | MEINS | ||
| 1.008 | EINA | ECC/DCT: UMREZ |
| Numerator for Conversion of Order Unit | NUMC | 5 | 1) Copy source field value as-is to the target field (1:1 direct mapping). | Numerator for Conversion of Order Unit | NUMC | 5 | EINA | UMREZ | |||||
| 1.009 | EINA | ECC/DCT: UMREN |
| Denominator for Conversion of Order Unit |
| NUMC | 5 | 1) Copy source field value as-is to the target field (1:1 direct mapping). | Denominator for Conversion of Order Unit | NUMC | 5 | EINA | UMREN | ||||
| 1.010 | EINA | ECC/DCT:: IDNLF |
| Material Number Used by Supplier | CHAR | 35 | 1) Copy source field value as-is to the target field (1:1 direct mapping). | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Product Number Used by Supplier | CHAR | 35 | EINA | IDNLF | ||||||
| 1.011 | EINA | ECC/DCT: VERKF | Salesperson Responsible | CHAR | 30 | 1) Copy source field value as-is to the target field (1:1 direct mapping). | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Salesperson Responsible | CHAR | 30 | EINA | VERKF | |||
| 1.012 | EINA | ECC/DCT: TELF1 | Supplier's Telephone Number | CHAR | 16 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Supplier's Telephone Number | CHAR | 16 | EINA | TELF1 | |||
| 1.013 | EINA | ECC/DCT: MAHN1 | Days for First Reminder/Expediter | NUMC | 1 | 1) Use the source value to update the target field AS-IS | Days for First Reminder/Expediter | NUMC | 1 | EINA | MAHN1 | ||||
| 1.014 | EINA | ECC/DCT: MAHN2 | Days for Second Reminder/Expediter | NUMC | 1 | 1) Use the source value to update the target field AS-IS | Days for Second Reminder/Expediter | NUMC | 1 | EINA | MAHN2 | ||||
| 1.015 | EINA | ECC/DCT: MAHN3 | Days for Third Reminder/Expediter | NUMC | 1 | 1) Use the source value to update the target field AS-IS | Days for Third Reminder/Expediter | NUMC | 1 | EINA | MAHN3 | ||||
| 1.016 | EINA | ECC: URZNR | Change Number | CHAR | 12 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure | Change Number | CHAR | 12 | EINA | URZNR | |||
| 1.017 | EINA | ECC: URZDT | Valid to | CHAR | 10 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure | Valid to | CHAR | EINA | URZDT | ||||
| 1.018 | EINA | ECC: URZLA | C/R. of Origin | CHAR | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure | C/R. of Origin | CHAR | EINA | URZLA | |||||
| 1.019 | EINA | ECC: URZTP | Certif. Cat. | CHAR | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure | Certif. Cat. | CHAR | EINA | URZTP | |||||
| 1.020 | EINA | ECC: URZZT | Time Stamp (UTC) | DEC (packed) | 15 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure | Time Stamp (UTC) | DEC (packed) | 15 | EINA | URZZT | |||
| 1.021 | EINA | ECC/DCT: LMEIN | Base Unit of Measure (ISO Format) | UNIT | 3 | Transformation Rule | 1)Use the source value, and lookup on the mapping table for Unit of Measure - UOM <MEINS> and update the target field. | - Relevant for DataConversion (Mapping) | Base Unit of Measure (ISO Format) | UNIT | 3 | EINA | LMEIN | ||
| 1.022 | EINA | ECC/DCT: REGIO | Region | CHAR |
| 2 | Copy source field value as-is to the target field (1:1 direct mapping). | Region | CHAR | 30 | EINA | REGIO | |||||||||
| 1.023 | EINA | ECC/DCT: VABME | Variable Purchase Order Unit Active | UNIT | 3 | Transformation Rule | 1) Use the source value to update the target field AS-IS | - Relevant for DataConversion (Mapping) | Variable Purchase Order Unit Active | UNIT | 3 | EINA | VABME | ||
| 1.024 | EINA | ECC/DCT: WGLIF | Supplier Material Group | CHAR | 30 | Transformation Rule | 1) Use the source value to update the target field AS-IS | ECC/DCT: | Supplier Product Group | CHAR | 30 | EINA | WGLIF | ||
| 1.025 | EINA | ECC/DCT: LIFAB |
DCT: Available From Date
| Available (Deliverable) From | CHAR | 30 | Copy source field value as-is to the target field (1:1 direct mapping). Target field format: DD.MM.YYYY | Available (Deliverable) From | CHAR | 30 | EINA | LIFAB | ||||
| 1.026 | EINA | ECC/DCT: LIFBI |
| Available |
| (Deliverable) Until | CHAR | 30 | Copy source field value as-is to the target field (1:1 direct mapping). Target field format: DD.MM.YYYY | Available (Deliverable) Until | CHAR | 30 | EINA | LIFBI | |||||||
| 1.027 | EINA | ECC/DCT: KOLIF | Prior Supplier | CHAR | 10 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Vendor <LIFNR> and update the target fields. | - Relevant for DataCleansing | Prior Supplier | CHAR | 10 | EINA | KOLIF | ||
| 1.028 | EINA | ECC: ANZPU | Number of Price Units | DEC (packed) | 5 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure | Number of Price Units | DEC (packed) | 5 | EINA | ANZPU | |||
| 1.030 | EINA | ECC/DCT: RELIF | Indicator: Regular Supplier | CHAR | 10 | Copy source field value as-is to the target field (1:1 direct mapping). | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Indicator: Regular Supplier | CHAR | 10 | EINA | RELIF | |||
| 1.031 | EINA | ECC/DCT: URZLA | Country/Region of Origin | CHAR | 30 | Copy source field value as-is to the target field (1:1 direct mapping). | Country/Region of Origin | CHAR | 30 | EINA | URZLA | ||||
| 1.032 | EINA | ECC/DCT: MFRNR | Manufacturer | CHAR | 10 | Transformation Rule | Use the source value, and lookup on the mapping table for Vendors <LIFNR>. | Applies only if business condition is met (e.g. Supplier type, region, or material category). | - Relevant for DataConversion (Mapping) | Manufacturer | CHAR | 10 | EINA | MFRNR | |
| For a direct extraction - 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 | ECC: INFNR | Legacy Number of Purchasing Info Record | NUMC | 10 | - Mandatoryfor Migration Cockpit | Legacy Number of Purchasing Info Record | NUMC | 10 | EINA | INFNR | ||||
| 2.002 | STXL | ECC/DCT: TDSPRAS | Language Key | LANG | 1 | Transformation Rule | After apply the data selection, use each line encountered in STXL-TDSPRAS//Not for Intercompany | - Mandatoryfor Migration Cockpit | Language Key | LANG | 1 | EINA | TDSPRAS | ||
| 2.003 | STXL | ECC: CLUSTD DCT: TEXT | Text | LRAW | 7902 | Target field is equal to STXL-CLUSTD/Not for Intercompany | - Mandatoryfor Migration Cockpit | Text | LRAW | 7902 | EINA | TEXT | |||
| 3.001 | EINE | ECC: INFNR | Legacy Number of Purchasing Info Record | NUMC | 10 | Not for Intercompany IF DCT Intercompany Flag <> "", target structure is empty (skipt the record) | - Mandatoryfor Migration Cockpit | Legacy Number of Purchasing Info Record | NUMC | 10 | EINE | INFNR | |||
| 3.002 | EINE | ECC/DCT: EKORG | |||||||||||||
DCT: Purchasing Organization
| Purchasing Organization | CHAR | 4 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG> | Dependent on Configuration | - Mandatoryfor Migration Cockpit | Purchasing Organization | CHAR | 4 | EINE | EKORG | ||
| 3.003 | EINE |
ECC/DCT: |
ESOKZ | Purchasing Info Record Category | CHAR | 1 | Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatoryfor Migration Cockpit | Purchasing Info Record Category | CHAR | 1 | EINE | ESOKZ | |||
| 3.004 | EINE | ECC/DCT: WERKS |
| Plant | CHAR | 4 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Plant <WERKS> | Applies only if the PIR is applicable for a specific Plant, Dependent on Configuration | - Relevant for DataCleansing | Plant | CHAR | 4 | EINE | WERKS | ||
| 3.005 | EINE | ECC/DCT: EKGRP |
| Purchasing Group |
| CHAR | 3 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Purchasing Group <EKGRP> | Applies only if the PIR is linked to a specific Pgroup; Dependent on Configuration | - Relevant for DataCleansing | Purchasing Group | CHAR | 3 | EINE | EKGRP | |
| 3.006 | EINE | ECC/DCT: WAERS |
| Currency |
| Key(ISO Format) | CUKY | 5 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Currency <WAERS> | Dependent on Configuration | - Relevant for DataConversion (Mapping) | Currency Key(ISO Format) | CUKY | 5 | EINE | WAERS | |
| 3.007 | EINE | ECC/DCT: MINBM |
| Minimum Purchase Order Quantity | QUAN | 13 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Minimum Purchase Order Quantity | QUAN | 13 | EINE | MINBM | ||||
| 3.008 | EINE | ECC/DCT: NORBM |
| Standard Purchase Order Quantity |
| QUAN | 13 | 1) Use the source value to update the target field AS-IS 2) If source field is empty, update the target field with value "1" | - Mandatoryfor Migration Cockpit | Standard Purchase Order Quantity | QUAN | 13 | EINE | NORBM | |||
| 3.009 | EINE | ECC/DCT: APLFZ |
| Planned Delivery Time in Days | TIMS | 6 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Planned Delivery Time in Days | TIMS | 6 | EINE | APLFZ | ||||||
| 3.010 | EINE | ECC/DCT: UEBTO | Overdelivery Tolerance Limit | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Overdelivery Tolerance Limit | CHAR | 30 | EINE | UEBTO | |||
| 3.011 | EINE | ECC/DCT: UEBTK | Indicator:Unlimited Overdelivery Allowed | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Indicator:Unlimited Overdelivery Allowed | CHAR | 30 | EINE | UEBTK | |||
| 3.012 | EINE | ECC/DCT: UNTTO | Underdelivery Tolerance Limit | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Underdelivery Tolerance Limit | CHAR | 30 | EINE | UNTTO | |||
| 3.013 | EINE | ECC: ANGNR | Quotation | CHAR | 10 | 1) Use the source value to update the target field AS-IS. | 20251127 *NOT PRESENT in Migration Cockpit structure. | Quotation | CHAR | 10 | EINE | ANGNR | |||
| 3.014 | EINE | ECC: ANGDT | Quotation from | DATS | 10 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure. | Quotation from | DATS | 10 | EINE | ANGDT | |||
| 3.015 | EINE | ECC: NETPR DCT: Net Price in Purchasing Info Record | Net Price | DEC | 11,2 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure. | Net Price | DEC | 11,2 | EINE | NETPR | |||
| 3.016 | EINE | ECC: PEINH DCT: Price unit (per quantity) | Price Unit | DEC | 3 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure. | Price Unit | DEC | 3 | EINE | PEINH | |||
| 3.018 | EINE | ECC/DCT: INCO2 | Incoterms (Part 2) | CHAR | 28 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure. | Incoterms (Part 2) | CHAR | 28 | EINE | INCO2 | |||
| 3.019 | EINE | ECC: MEGRU | Quantity Conversion Group | CHAR | 4 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure. | Quantity Conversion Group | CHAR | 4 | EINE | MEGRU | |||
| 3.020 | EINE | ECC/DCT: J_1BNBM | NCM Code | CHAR | 16 | 1) Use the source value to update the target field AS-IS | 20251127 *NOT PRESENT in Migration Cockpit structure. | Nota Fiscal: Base Calculation Indicator | CHAR | 16 | EINE | J_1BNBM | |||
| 3.021 | EINE | ECC/DCT: BWTAR | Valuation Type | CHAR | 30 | Transformation Rule | Use the source value, and lookup on the mapping table for <VALUATION_TYPE) and update the target field. | - Relevant for DataConversion (Mapping) | Valuation Type | CHAR | 30 | EINE | BWTAR | ||
| 3.022 | EINE | ECC/DCT: |
| MTXNO | Ind: Prod. Master Rec. PO Text Not Rele. | NUMC | 10 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Ind: Prod. Master Rec. PO Text Not Rele. | NUMC | 10 | EINE | MTXNO | |||||
| 3.023 | EINE | ECC/DCT: WEBRE | Indicator: GR-Based Invoice Verification | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier, region, or material category). | Indicator: GR-Based Invoice Verification | CHAR | 30 | EINE | WEBRE | |||
| 3.024 | EINE | ECC/DCT: |
| KZABS | Ind: Order Acknowledgment Requirement | CHAR | 40 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Ind: Order Acknowledgment Requirement | CHAR | 40 | EINE | KZABS | |||||
| 3.025 | EINE | ECC/DCT: MWSKZ | Tax on Sales/Purchases Code | CHAR | 2 | Transformation Rule | Use the source value, and lookup on the mapping table for <TAX_CODE> and update the target field. | Applies only if business condition is met (e.g. Supplier type, region, or material category). Dependent on Configuration | - Relevant for DataConversion (Mapping) | Tax on Sales/Purchases Code | CHAR | 2 | EINE | MWSKZ | |
| 3.027 | EINE | ECC/DCT: |
| EVERS | Shipping Instructions | CHAR | 30 | Transformation Rule | 1) Use the source value to update the target field AS-IS applying Data Conversion | Applies only if business condition is met (e.g. Supplier type, region, or material category). | - Relevant for DataConversion (Mapping) | Shipping Instructions | CHAR | 30 | EINE | EVERS | |
| 3.028 | EINE | ECC/DCT: BSTAE | Confirmation Control Key | CHAR |
| 4 | Transformation Rule | Default value equal to '0001' |
| Confirmation Control Key | CHAR | 30 | EINE | BSTAE | |||||||
| 3.029 | EINE | ECC/DCT: XERSN | Ind: No Evaluated Receipt Settlem. (ERS) | CHAR | 1 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Ind: No Evaluated Receipt Settlem. (ERS) | CHAR | 1 | EINE | XERSN | |||
| 3.030 | EINE | ECC/DCT: |
| MHDRZ | Minimum Remaining Shelf Life | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Minimum Remaining Shelf Life | CHAR | 30 | EINE | MHDRZ | |||||
| 3.031 | EINE | ECC/DCT: IPRKZ | Period Ind. for Min. Remain. Shelf Life | CHAR | 2 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Period Ind. for Min. Remain. Shelf Life | CHAR | 2 | EINE | IPRKZ | |||
| 3.032 | EINE | ECC/DCT: BSTMA | Maximum Purchase Order Quantity | QUAN | 13 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Maximum Purchase Order Quantity | QUAN | 13 | EINE | BSTMA | |||
1) Use the source value to update the target field AS-IS | |||||||||||||||
| 3.034 | EINE | ECC/DCT: EXPRF | Foreign Trade: Procedure | CHAR | 30 | Transformation Rule | 1) Use the source value to update the target field AS-IS | Applies only if the PIR is linked to a specific Pgroup; Dependent on Configuration | Foreign Trade: Procedure | CHAR | 30 | EINE | EXPRF | ||
| 3.035 | EINE | ECC/DCT: RDPRF | Rounding Profile | CHAR | 30 | Transformation Rule | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | - Relevant for DataConversion | Rounding Profile | CHAR | 30 | EINE | RDPRF | |
| 3.036 | EINE | ECC/DCT: |
| VENDOR_RMA_REQ | Supplier RMA Number Required | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Supplier RMA Number Required | CHAR | 30 | EINE | VENDOR_RMA_REQ | ||||||
| 3.038 | EINE | ECC/DCT: SKTOF | Ind: Item Does Not Qualify for Cash Disc | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Ind: Item Does Not Qualify for Cash Disc | CHAR | 30 | EINE | SKTOF | ||||
| 3.039 | EINE | ECC/DCT: |
| MEPRF | Price Determinat. (Pricing) Date Control | DATS | 8 | 1) Use the source value to update the target field AS-IS | Price Determinat. (Pricing) Date Control | DATS | 8 | EINE | MEPRF | ||||||
| 3.040 | EINE | ECC/DCT: INCOV | Incoterms Version | CHAR | 30 | Transformation Rule | 1) Use the source value to update the target field AS-IS | Incoterms Version | CHAR | 30 | EINE | INCOV | |||
| 3.041 | EINE | ECC/DCT: INCO1 | Incoterms | CHAR | 30 | Transformation Rule | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | - Relevant for DataConversion (Mapping) | Incoterms | CHAR | 30 | EINE | INCO1 | |
| 3.042 | EINE | ECC/DCT: INCO2_L | Incoterms Location 1 | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Incoterms Location 1 | CHAR | 30 | EINE | INCO2_L | |||
| 3.043 | EINE | ECC/DCT: INCO3_L | Incoterms Location 2 | CHAR | 30 | 1) Use the source value to update the target field AS-IS | Applies only if business condition is met (e.g. Supplier type, region, or material category). | Incoterms Location 2 | CHAR | 30 | EINE | INCO3_L | |||
| 4.001 | EINE | ECC: INFNR | Legacy Number of Purchasing Info Record | CHAR | |||||||||||
| 80 | Note: Transformation will be applied where Decision = 'PIR' or 'Pricing Conditions' IF DCT Intercompany Flag <> "", target structure is empty | - Mandatoryfor Migration Cockpit | Legacy Number of Purchasing Info Record | Text | 80 | EINE | INFNR | ||||||||
| 4.002 | EINE | ECC: EKORG DCT: Purchasing Organization | Purchasing Organization | CHAR | 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 | COND.EKORG ← EINE-EKORG | - Mandatoryfor Migration Cockpit | Purchasing Organization | Text | 80 | EINE | EKORG | |
| 4.003 | EINE | ECC: ESOKZ DCT: Infotype | Purchasing Info Record Category | CHAR |
| 1 | Transformation Rule | Copy source field value as-is to the target field (1:1 direct mapping). | COND.ESOKZ ← EINE-ESOKZ | - Mandatoryfor Migration Cockpit | Purchasing Info Record Category | Text | 80 | EINE | ESOKZ | |
| 4.004 | EINE | ECC: WERKS DCT: Plant | ECC: Plant | CHAR |
| 4 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Plant <WERKS> | COND.WERKS ← EINE-WERKS | - Relevant for DataConversion (Mapping) | Plant | Text | 80 | EINE | WERKS | ||||||
| 4.005 | KONP | ECC: KOPOS | Condition Sequence Number | NUMC | 2 | 1) Use the source value to update the target field AS-IS ELSE "1" | COND.KOPOS ← KONP-KOPOS | - Mandatoryfor Migration Cockpit | Condition Sequence Number | Number | 2 | KONP | KOPOS | ||
| 4.006 | KONP | ECC/DCT: KSCHL | Condition Type | CHAR |
| 4 | Transformation Rule | 1) IF ECC is the source system: Use the source value to update the target field AS-IS ELSEIF DCT is the source, condition type is equal to PB00 |
Mandatory to have PB00 or equivalent condition type for each record, but not limited to have only this condition type. Dependent on Configuration | - Mandatoryfor Migration Cockpit - Relevant for DataConversion (Mapping) | Condition Type | Text | 80 | KONP | KSCHL | ||||||
| 4.007 | KONH | ECC: DATAB DCT: Pricing Condition Start date | Valid From | Date | 1) Use the source value to update the target field AS-IS | COND.VALID_FROM ← KONH-DATAB | - Mandatoryfor Migration Cockpit | Valid From | Date | KONH | VALID_FROM | ||||
| 4.008 | KONH | ECC: DATBI DCT: Pricing condition End Date | Valid To | Date | 1) Use the source value to update the target field AS-IS | COND.VALID_TO ← KONH-DATBI | - Mandatoryfor Migration Cockpit | Valid To | Date | KONH | VALID_TO | ||||
| 4.009 | KONM | ECC: KRECH | Calculation Type | CHAR | 80 | Transformation Rule | 1) Use the source value to update the target field AS-IS | Calculation Type | Text | 80 | KONM | KRECH | |||
| 4.010 | KONP | ECC: KBETR DCT: Net Price in Purchasing Info Record | Amount | NUMC | 31,3 | 1) Use the source value to update the target field AS-IS | Amount | Number | 31,3 | KONP | KBETR | ||||
| 4.011 | KONP | ECC: KONWA DCT: Currency | Condition Unit (Currency or Percentage) | CHAR | 80 | 1) Use the source value to update the target field AS-IS | Condition Unit (Currency or Percentage) | Text | 80 | KONP | KONWA | ||||
| 4.012 | KONP | ECC: KPEIN DCT: Price unit (per quantity) | Condition Pricing Unit | NUMC | 5 | 1) Use the source value to update the target field AS-IS | Condition Pricing Unit | Number | 5 | KONP | KPEIN | ||||
| 4.013 | KONP | ECC: KMEIN DCT: Order Price Unit | Condition Unit of Measure ISO | CHAR | 80 | Transformation Rule | 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 | Text | 80 | KONP | KMEIN | |||
| 4.014 | KONP | ECC: KUMZA DCT: Numerator for Conversion of Order Unit to Base Unit | Numerator for Conversion | NUMC | 5 | 1) Use the source value to update the target field AS-IS | Numerator for Conversion | Number | 5 | KONP | KUMZA | ||||
| 4.015 | KONP | ECC: KUMNE DCT: Denominator for Conversion of Order Unit to Base Unit | Denominator for Conversion | NUMC | 5 | 1) Use the source value to update the target field AS-IS | Denominator for Conversion | Number | 5 | KONP | KUMNE | ||||
| 4.016 | MARA | ECC: MEINS DCT: |
Base Unit of Measure | Base Unit of Measure ISO | CHA | 80 | Transformation Rule | Pulled from MARA | Base Unit of Measure ISO | Text | 80 | KONP | MEINS | |||||
| 4.017 | KONM | ECC/DCT: KONMS | Condition Scale Unit of Measure ISO | CHAR | 80 | Transformation Rule | Transformation Rule: 1) Use the source value to update the target field AS-IS | Condition Scale Unit of Measure ISO | Text | 80 | KONM | KONMS | |||
| Transformation Rule: NO RULE - send blanks | Condition Exclusion Indicator | Text | 80 | COND | EXCLUSION_IND | ||||||||||
| 5.001 | EINE | ECC: INFNR | Legacy Number of Purchasing Info Record | NUMC | 10 | Note: Transformation will be applied where Decision = 'PIR' or 'Pricing Conditions | - Mandatoryfor Migration Cockpit | Legacy Number of Purchasing Info Record | Text | 80 | EINE | INFNR | |||
| 5.002 | EINE | ECC: EKORG DCT: Purchasing Organization | Purchasing Organization | CHAR | 4 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG> | - Mandatoryfor Migration Cockpit | Purchasing Organization | Text | 80 | EINE | EKORG | ||
| 5.003 | EINE | ECC: ESOKZ DCT: Infotype | Purchasing Info Record Category | CHAR | 1 | Transformation Rule | Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatoryfor Migration Cockpit | Purchasing Info Record Category | Text | 80 | EINE | ESOKZ | ||
| 5.004 | EINE | ECC: WERKS DCT: Plant | Plant | CHAR | 4 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Plant <WERKS> | - Relevant for DataConversion (Mapping) | Plant | Text | 80 | EINE | WERKS | ||
| 5.005 | KONP | ECC/DCT: KOPOS | Condition Sequence Number | Number | 2 | 1) Use the source value to update the target field AS-IS | - Mandatoryfor Migration Cockpit | Condition Sequence Number | Number | 2 | KONP | KOPOS | |||
| 5.006 | KONP | ECC/DCT: KSCHL | Condition Type | Text | |||||||||||
| 4 | Transformation Rule | 1) Use the source value to update the target field AS-IS | - Mandatoryfor Migration Cockpit - Relevant for DataConversion (Mapping) | Condition Type | Text | 80 | KONP | KSCHL | |||||||
| 5.007 | KONH | ECC: DATAB DCT: Pricing Condition Start date | Valid From | Date | 1) Use the source value to update the target field AS-IS | - Mandatoryfor Migration Cockpit | Valid From | Date | KONH | DATAB | |||||
| 5.008 | KONH | ECC:DATBI DCT: Pricing condition End Date | Valid To | Date | 1) Use the source value to update the target field AS-IS | - Mandatoryfor Migration Cockpit | Valid To | Date | KONH | DATBI | |||||
| 5.009 | KONM | ECC/DCT: KLFN1 | Scale Item Number | Number | 4 | 1) ROW_NUMBER() OVER(PARTITION BY KONM-KNUMH, KONM-KOPOS ORDER BY KONM-KONMS) | - Mandatoryfor Migration Cockpit | Scale Item Number | Number | 4 | KONM | KLFN1 | |||
| 5. |
Scale Quantity
| 011 | KONM | ECC/DCT: KBETR | Scale Rate | Number | 31,3 | 1) Use the source value to update the target field AS-IS | Scale Rate | Number | 31,3 | KONM | KBETR | ||||
| 5.012 | KONW | ECC/DCT: |
| KSTBW | Scale Value | Number | 28,3 | 1) Use the source value to update the target field AS-IS | Scale Value | Number | 28,3 | KONW | KSTBM | ||||||
| 5.013 | KONM | ECC/DCT: KBETR | Scale Rate | Number | 31,3 | 1) Use the source value to update the target field AS-IS | Scale Rate | Number | 31,3 | KONW | KBETR | ||||
| 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 | ECC: TDOBJECT | Text Object | Text | 80 | 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./Not for Intercompany | - Mandatoryfor Migration Cockpit | Legacy Number of Purchasing Info Record | Text | 80 | STXL | TDOBJECT | |||
| 6.002 | STXL | ECC/DCT: EKORG | Purchasing Organization | Text | |||||||||||
| 4 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG>/Not for Intercompany | - Mandatoryfor Migration Cockpit - Relevant for DataConversion (Mapping) | Purchasing Organization | Text | 80 | STXL | EKORG | ||
| 6.003 | STXL | ECC/DCT: ESOKZ | Purchasing Info Record Category | Text |
| 1 | Transformation Rule | Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatoryfor Migration Cockpit | Purchasing Info Record Category | Text | 80 | STXL | ESOKZ | ||
| 6.004 | STXL | ECC/DCT: WERKS | Plant | Text |
| 4 | Transformation Rule | 1) Use the source value, and lookup on the mapping table for Plant <WERKS> | - Relevant for DataConversion (Mapping) | Plant | Text | 80 | STXL | WERKS | ||
| 6.005 | STXL | ECC/DCT: TDSPRAS | Language Key | Text |
| 1 | Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatoryfor Migration Cockpit | Language Key | Text | 80 | STXL | TDSPRAS | ||||||||
| 6.006 | STXL | ECC/DCT: TEXT | Text | Text | unrestricted | Copy source field value as-is to the target field (1:1 direct mapping). | - Mandatoryfor Migration Cockpit | Text | Text | unrestricted | STXL | TEXT | |||
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 | Map legacy field values to S/4HANA target values (including field-level mapping and technical names) | Data Team (S2P), Syniti team |
| 3 | Define value mapping rules for fields requiring standardization or harmonization across the two source systems WP2, PF2. | Functional Team (S2P)+ Data Team (S2P) |
| 4 | Identify and agree on default values where legacy data is incomplete or inconsistent | Business Team + Functional Team (S2P) |
| 5 | Configure transformation rules in Syniti Migrate (including calculated fields, formatting rules, etc.) | Syniti team |
| 6 | Review transformation logic and mappings with Business for confirmation | Business Team |
| 7 | Perform initial transformation run and generate draft target-ready dataset | Syniti team |
| 8 | Review draft target-ready data for structure and completeness | Data Team (S2P), Functional Team (S2P), Syniti |
| 9 | Share transformed data with Business for Pre-load Validation | Data Team (S2P) |
| 10 | Incorporate feedback from Business and refine mappings or transformation logic as needed | Data Team (S2P) |
| 12 | Syniti to transform the data | Syniti team |
| 13 | 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; | Syniti team |
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
LIFNR (LFA1-LIFNR) | <XREF-Vendor> |
MATNR (MARA-MATNR) | <XREF-Material> |
WERKS (T001W-WERKS_ | |
EKORG (T024E-EKORG) | |
EKGRP (T024-EKGRP) | |
MATKL (T023-MATKL) | |
MEINS (T006-MEINS) | |
MWSKZ (T007A-MWSKZ) | |
General Configuration for Info Records | |
Tax Jurisdiction Code |
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) |
| 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) |
| 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) |
| 019 | If Source is DCT (for Services or new records) then DCT should be completed by business before transformation. If Data is extracted from ECC (PF2 and WP2) then Business should complete approval of 'DCT for Business Decision' before transformation. | Data Owners/S2P Data Team |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.
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.
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 Cleansing 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) |
Duplicate Detection | Identify duplicate entries in the dataset |
Business Rule Compliance | Ensure compliance with agreed rules, for instance |
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 is ready to start
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
| 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 |
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.
Frequency of running reports
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).
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 |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach
- is in scope based on data design and any exception requested by business.
See also
| Object | Date | Link |
|---|---|---|
| Reference Document | 20251110 | Material is flagged as in scope according to MDS CNV-2019 Materials – Basic Data View |
| Reference Document | 20251110 | Vendor is flagged as in scope according to MDS CNV-3007 Business Partners – General (Role 000000) and CNV-3027 Business Partners - Plants / Intercompany Suppliers |
| Reference Document | 20251110 | Purchasing Organization (EINE.EKORG) is in scope based on enterprise structure mapping |
| Reference Document | 20251110 | Plant (EINE.WERKS) is in scope based on enterprise structure mapping. |
Change log
| Change History | ||
|---|---|---|
|
Workflow history
| Workflow Report | ||||||
|---|---|---|---|---|---|---|
|