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 Approx

No. 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 Approx

No. 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-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 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

  1. Extract the data from Production.
  2. Prepare Excel reports to support the decision-making process.
  3. 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.
  4. 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 DescriptionUsage of the fieldSAP Fields
UNIQUE_IDUnique ID defined by Syniti
RELEASE NO.Release of the object
SOURCE SYSTEMSource System ID
TARGET SYSTEMTarget System ID
Purchase Info RecordInfo record CodeEINA-INFNR
Material NumberMaterial Code with leading zerosEINA-MATNR
Material (Golden record)

Material GroupMaterial GroupEINA-MATKL
Account Number of Supplier(Vendor)Account Number of SupplierEINA-LIFNR
Vendor (Golden record)

Short Text For Purchasing Info RecordShort Text For Purchasing Info RecordEINA-TXZ01
Order unitOrder UnitEINA-MEINS
Base UoMBase Unit of MeasureMARA-MEINS
Numerator for Conversion of Order Unit to Base UnitNumerator for Conversion of Order Unit to Base UnitMARM-UMREZ
Denominator for Conversion of Order Unit to Base UnitDenominator for Conversion of Order Unit to Base UnitMARM-UMREN
Vendor Material NumberMaterial Number Used by SupplierEINA-IDNLF
Purchasing OrganizationPurchasing OrganizationEINE-EKORG
InfotypePurchasing Info Record CategoryEINE-ESOKZ
Purchasing info record category DescriptionPurchasing info record category Description

DD07T-DDTEXT

Select Single DDTEXT
From DD07T
Where DOMNAME = ESOKZ and
            DDLANGUAGE = 'E'
            AS4LOCAL = 'A'
            DOMVALUE_L = EINE-ESOKZ

PlantPlantEINE-WERKS
Planned Delivery Time (in Days)Planned Delivery Time (in Days)EINE-PLIFZ
Available From DateDD/MM/YYYY

EINA-LIFAB

Available To date

DD/MM/YYYYEINA-LIFBI
CurrencyCurrencyEINE-WAERS
Minimum Order QuantityMin Order QuantityEINE-MINBM
Standard Purchase Order QuantityStandard Purchase Order QuantityEINE-NORBM
Net Price in Purchasing Info RecordNet PriceApply 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 UnitOrder Price Unit
Pricing Condition Start dateDD/MM/YYYY
Pricing condition End DateDD/MM/YYYY
Intercompany Flag<YES / NO>

If LFA1 = ZZR_SEGT_ATTR = 'G' Then 'Yes'

Info Record consignment flag<YES / NO>

IF EINE-ESOKZ = 2
   TargetField = 'YES'
ELSE.
   TargetField = 'NO'.
ENDIF.

Purchasing GroupPurchasing GroupEINE-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
ELSE = NO

---------------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
ELSE = NO

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
  1. For Intercompany Procurement only 'Pricing Condition' will be loaded. Please populate value = 'Pricing Condition required'
  2. IF Consignment PIR then PIR should be migrated then populate value = 'PIR is required'.                                                                                                                                                                                                    Exception (Consignment PIRs apply only to external suppliers. Intercompany processes do not use consignment)
  3. If an Open Contract exists at Material Level then populate = 'NO PIR'
  4. IF an Ariba Catalog exists for the Vendor | Material Grp | Purchasing Organisation, than populate = 'NO PIR'
  5. If Contract is at Material Grp level then we should check if PIR is created by Users then populate 'PIR is required' but if PIR is auto generated then populate 'TBC by Business' 
  6. IF condition 1 - 5 is not true then check:

      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 (Business_Decision)

Possible Values: Populate based on field 'Decision by Rule'
- Not Applicable

-TBC by Business
- PIR is required
- Pricing Condition required

- NO PIR


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 to be migrated




z Comment

<OPEN TEXT FIELD> 


BUSINESS INPUT ALLOWED



Additional Information

MDS Documents

Date

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/A


 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.


Target Design

The technical design of the target for this conversion approach.

Follow MDS for Governance Rules.

Technical Table-FieldField LabelDescriptionSyensqo RequirementData TypeLength
EINAMATNRMaterial number referenced by the Info Record.RequiredCHAR18
EINALIFNRSupplier (Business Partner/Vendor) for this Info Record.RequiredCHAR10
EINATXZ01Short text/description used for free-text PIRs.ConditionalCHAR40
EINAIDNLFSupplier’s material number/reference.ConditionalCHAR35
EINALTSNRSupplier subrange identifier.ConditionalNUMC10
EINAMFRNRManufacturer number.ConditionalCHAR10






EINEEKORGPurchasing organization responsible for this PIR.RequiredCHAR4
EINEESOKZInfo type (Standard, Subcontracting, Consignment, Pipeline).RequiredCHAR1
EINEWERKSPlant for which the PIR applies.ConditionalCHAR4
EINEEKGRPPurchasing group (buyer responsibility).ConditionalCHAR3
EINEWAERSCurrency for PIR pricing.ConditionalCUKY5
EINEMINBMMinimum order quantity.ConditionalQUAN13
EINENORBMStandard order quantity.ConditionalQUAN13
EINEAPLFZPlanned delivery time from supplier.ConditionalTIMS6
EINEUEBTOOverdelivery tolerance limit.ConditionalCHAR30
EINEUEBTKUnlimited overdelivery allowed.ConditionalCHAR30
EINEUNTTOUnderdelivery tolerance.ConditionalCHAR30
EINENETPRNet price.ConditionalCURR11
EINEPEINHPrice unit (per quantity).ConditionalDEC5
EINEBPRMEOrder price unit.ConditionalCURR11
EINEWEBREGR-Based Invoice Verification flag.ConditionalCHAR30
EINEKZABSAcknowledgment required from supplier.ConditionalCHAR40
EINEMWSKZTax code.ConditionalCHAR2
EINEBWTARValuation type (split valuation).ConditionalCHAR30
EINEEVERSShipping instructions.ConditionalCHAR30
EINEMEPRFPrice date category.ConditionalDATS8
EINEINCO1Incoterms.ConditionalCHAR30
EINEINCO2Incoterms location.ConditionalCHAR30
EINEXERSNNo ERS (Evaluated Receipt Settlement).ConditionalCHAR1
EINEVERIDProduction version (subcontracting).ConditionalCHAR30
EINEBSTMAMaximum order quantity.ConditionalQUAN13
EINERDPRFRounding profile.ConditionalCHAR30
EINEJ_1BNBMNCM code (Brazil).ConditionalCHAR30
EINEINCOVIncoterm version.ConditionalCHAR30
EINEINCO2_LExtended Incoterms location fields.ConditionalCHAR30
EINEINCO3_LExtended Incoterms location fields.ConditionalCHAR30
EINEINCO2_KEYIncoterms location keys.ConditionalCHAR30
EINEINCO3_KEYIncoterms location keys.ConditionalCHAR30
EINEAUT_SOURCEAutomatic sourcing flag.ConditionalCHAR30






A018KAPPLApplication (e.g., “M” for purchasing).ConditionalCHAR30
A018KSCHLCondition type key.ConditionalCHAR30
A018DATBIValid-to date.ConditionalDATS8
A018DATABValid-from date.ConditionalDATS8






KONPKSCHLCondition type (price, discount, surcharge, etc.).ConditionalCHAR30
KONPSTFKZScale type.ConditionalCHAR1
KONPKZBZGScale base type.ConditionalCHAR1
KONPKSTBMScale quantity.ConditionalQUAN13
KONPKONMSScale unit of measure.ConditionalCHAR30
KONPKSTBWScale value.ConditionalCURR11
KONPKONWSScale currency.ConditionalCUKY5
KONPKRECHCalculation type.ConditionalCHAR30
KONPKBETRCondition amount.ConditionalCURR11
KONPKONWACondition currency.ConditionalCUKY5
KONPKPEINPricing unit.ConditionalDEC5
KONPKMEINUnit of measure for condition.ConditionalUNIT3
KONPPRSCHScale group.ConditionalCHAR30
KONPKUMZANumerator for scale conversion.ConditionalCHAR30
KONPKUMNEDenominator for scale conversion.ConditionalCHAR30
KONPMEINSBase unit.ConditionalUNIT3
KONPMXWRTLower limit for validity.ConditionalCHAR30
KONPGKWRTUpper limit.ConditionalCHAR30
KONPPKWRTPlanned condition value.ConditionalCHAR30
KONPFKWRTCumulative value.ConditionalCURR11
KONPRSWRTCumulative accrual.ConditionalCHAR30
KONPKWAEHCondition currency key.ConditionalCUKY5
KONPUKBASPlanned basis.ConditionalCHAR30
KONPKZNEPExclusion indicator.ConditionalCHAR1
KONPLIFNRSupplier.ConditionalCHAR10
KONPMWSK1Tax code.ConditionalCHAR30
KONPBOMATMaterial for settlement.ConditionalCHAR30
KONPKBRUEAccrual.ConditionalCHAR30
KONPKSPAERetroactive pricing indicator.ConditionalCHAR30
KONPBOSTACondition record status.ConditionalCHAR30
KONPUMA_PIPromotion number.ConditionalCHAR30
KONPUMA_AGSales deal number.ConditionalCHAR30
KONPUMA_SQSales quotation number.ConditionalCHAR30
KONPVALTGAdditional value days.ConditionalCURR11
KONPVALDTFixed value date.ConditionalDATS8
KONPZTERMPayment terms.ConditionalCHAR30
KONPANZAUFNumber of orders.ConditionalNUMC10
KONPMIKBASMinimum condition base value.ConditionalCHAR30
KONPMXKBASMaximum condition base.ConditionalCHAR30
KONPOMXWRTMaximum condition value.ConditionalCURR11
KONPLF_STGIncrement scale.ConditionalCHAR30
KONPLF_KALPricing scale.ConditionalCHAR30
KONPVKKALRelevance to pricing.ConditionalCHAR30
KONPAKTNRPromotion number.ConditionalNUMC10
KONPUMA_BOAgreement number.ConditionalCHAR30
KONPMWSK2Withholding tax code.ConditionalCHAR30
KONPVERTTContract type.ConditionalCHAR30
KONPVERTNContract number.ConditionalNUMC10
KONPVBEWAFlow type.ConditionalCHAR30
KONPMDFLGMatrix maintenance flag.ConditionalCHAR30
KONPKFRSTRelease status.ConditionalCHAR30
KONPUASTACondition processing status.ConditionalCHAR30






KONHKVEWEApplication usage.ConditionalCHAR1
KONHKOTABNRCondition table number.ConditionalNUMC10
KONHKSCHLCondition type.ConditionalCHAR30
KONHDATABValid-from date.ConditionalDATS8
KONHDATBIValid-to date.ConditionalDATS8
KONHKOSRTSearch term.ConditionalCHAR30
KONHKZUSTResponsibility indicator.ConditionalCHAR30
KONHLICNOLicense number.ConditionalCHAR35
KONHLICDTLicense date.ConditionalDATS8
KONHREFERENCEReference text.ConditionalCHAR35
KONHPRICEAPPROVALREQUESTPrice approval request number.ConditionalCHAR30






A017KAPPLApplication for pricing (Purchasing = “M”).ConditionalCHAR30
A017KSCHLCondition type key (e.g., price, discount, freight).ConditionalCHAR30
A017LIFNRSupplier relevant for the condition record.ConditionalCHAR10
A017MATNRMaterial applicable to the condition.ConditionalCHAR18
A017EKORGPurchasing organization owning the condition.ConditionalCHAR4
A017WERKSPlant for which the condition is valid.ConditionalCHAR4
A017ESOKZInfotype (Standard, Subcontracting, Consignment).ConditionalCHAR1
A017DATBIValid-to date of the condition.ConditionalDATS8
A017DATABValid-from date of the condition.ConditionalDATS8






A025KAPPLApplication for pricing (Purchasing).ConditionalCHAR30
A025KSCHLCondition type for the condition record.ConditionalCHAR30
A025LIFNRSupplier associated with the condition.ConditionalCHAR10
A025EKORGPurchasing organization for the condition.ConditionalCHAR4
A025MATKLMaterial group applicable to the condition.ConditionalCHAR9
A025INFNRInfo record number (if condition tied to PIR).ConditionalNUMC10
A025WERKSPlant where the condition applies.ConditionalCHAR4
A025ESOKZInfotype used to classify procurement type.ConditionalCHAR1
A025DATBIValid-to date for the condition.ConditionalDATS8
A025DATABValid-from date.ConditionalDATS8






A028KAPPLApplication (Purchasing).ConditionalCHAR30
A028KSCHLCondition type.ConditionalCHAR30
A028LIFNRSupplier.ConditionalCHAR10
A028EKORGPurchasing organization.ConditionalCHAR4
A028MATKLMaterial group.ConditionalCHAR9
A028INFNRInfo record number.ConditionalNUMC10
A028ESOKZInfotype.ConditionalCHAR1
A028DATBIValid-to date.ConditionalDATS8
A028DATABValid-from date.ConditionalDATS8






A066KAPPLPricing application.ConditionalCHAR30
A066KSCHLCondition type.ConditionalCHAR30
A066LIFNRSupplier.ConditionalCHAR10
A066MATNRMaterial.ConditionalCHAR18
A066EKORGPurchasing organization.ConditionalCHAR4
A066ESOKZInfotype.ConditionalCHAR1
A066BSTMEOrder unit for pricing.ConditionalUNIT3
A066DATBIValid-to date.ConditionalDATS8
A066DATABValid-from date.ConditionalDATS8






A067KAPPLPricing application.ConditionalCHAR30
A067KSCHLCondition type.ConditionalCHAR30
A067LIFNRSupplier.ConditionalCHAR10
A067MATNRMaterial.ConditionalCHAR18
A067EKORGPurchasing organization.ConditionalCHAR4
A067ESOKZInfotype.ConditionalCHAR1
A067WERKSPlant.ConditionalCHAR4
A067BSTMEOrder unit.ConditionalUNIT3
A067DATBIValid-to date.ConditionalDATS8
A067DATABValid-from date.ConditionalDATS8






KONWKSTBWScale value threshold.ConditionalCURR11
KONWKBETRCondition amount for this scale level.ConditionalCURR11






KONMKSTBMQuantity threshold for scale.ConditionalCURR11
KONMKBETRCondition amount for this quantity level.ConditionalCURR11



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 ReportObjectiveComments

Report: Check PIRs where EINA-LIFBI [not DATBI] <= today’s date, however the Info Record is not deleted (EINA-LOEKZ is not set).
These cases should be reported to the business, as ideally such Info Records should not exist.



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 alignedNote: 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,00Objective: 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.



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/A


Extraction

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 DescriptionTeam Responsible
001Verify connectivity and authorizations to source ECC systems before execution.Syniti Team
002Confirm selection scope: Purchasing Organizations, Plants, Vendors, and Materials to be included in the extraction.Syniti Team
005Extract Info Records for Vendors that are not marked for deletion (LFM1-LOEVM ≠ ‘X’) and are within scope.Syniti Team
006Extract Info Records for active Vendors and Materials only – exclude entries with deletion or obsolete flags.Syniti Team
007Extract Info Records for Materials that are not marked for deletion and belong to valid Info Record combinations.Syniti Team
008Extract condition records (KONH/KONP, A017/A018/...) corresponding to valid Info Records, using non-overlapping validity dates.Syniti Team
009Extract long texts (STXH/STXL) for valid Info Records and ensure language completeness (including all ISO languages and excluding out of scope languages)Syniti Team
012Submit extraction output for validation to BusinessSyWay 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 ScreenParameter NameSelection TypeRequirementValue 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 1 – doesn’t depend from any other

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: - Basic Data Info

Field NameData TypeLengthDescriptionRule
INFNRCHAR10Info Record NumberRequired
EINA-MATNRCHAR18Material NumberRequired
EINA-MATKLCHAR9Material GroupConditional
EINA-LIFNRCHAR10Vendor NumberRequired
EINA-TXZ01CHAR40Sort term for Non-Stock Info RecordsConditional
EINA-TXZ01CHAR40Short TextConditional
EINA-MEINSUNIT3Order UnitConditional
EINA-UMREZNUMC5Numerator for ConversionConditional
EINA-UMRENNUMC5Denominator for ConversionConditional
EINA-IDNLFCHAR35Material Number Used by SupplierConditional
EINA-VERKFCHAR30Salesperson at vendorConditional
EINA-TELF1CHAR16Vendor’s telephone numberConditional
EINA-MAHN1CURR11Dunning amount limit (level 1)Conditional
EINA-MAHN2CURR11Dunning amount limit (level 2)Conditional
EINA-MAHN3CURR11Dunning amount limit (level 3)Conditional
EINA-LMEINUNIT3Base unit of measure.Conditional
EINA-VABMECURR13Total value of purchase order itemsConditional
EINA-WGLIFCHAR3Vendor country keyConditional
EINA-KOLIFCHAR10Collective number for vendorConditional
EINA-URZLACHAR3Terms of payment keyConditional
EINA-REGIOCHAR3Region (state, province, county)Conditional
EINA-MFRNRCHAR10Manufacturer numberConditional
EINA-LIFABDATS8Validity start date of vendor recordConditional
EINA-LIFBIDATS8Validity end date of vendor recordConditional
EINA-RELIFCHAR1Relevant for automatic release (indicator)Conditional


2 - DCT for PIR: - Purchase Organization Info

Field NameData TypeLengthDescriptionRule
INFNRCHAR10Info Record NumberRequired
EINE-EKORGCHAR4Purchasing OrganizationRequired
EINE-ESOKZCHAR1Info Category (Standard/Subcontracting/Consignment)Required
EINE-WERKSCHAR4PlantRequired
EINE-EKGRPCHAR3Purchasing GroupRequired
EINE-WAERSCUKY5Currency KeyRequired
EINE-MINBMQUAN

13,3

Minimum Order QuantityRequired
EINE-NORBMQUAN13,3Normal Order QuantityConditional
EINE-APLFZDEC3Planned Delivery Time (in Days)Conditional
EINE-UEBTODEC3Overdelivery Tolerance Limit (%)Conditional
EINE-UEBTKCHAR1Unlimited Overdelivery Allowed (Indicator)Conditional
EINE-UNTTODEC3Under delivery Tolerance Limit (%)Conditional
EINE-BWTARCHAR10Valuation TypeConditional
EINE-MTXNOCHAR20Material Text NumberConditional
EINE-WEBRECHAR1Goods Receipt-Based Invoice VerificationConditional
EINE-KZABSCHAR1Final Invoice IndicatorConditional
EINE-MWSKZCHAR2Tax CodeConditional
EINE-EVERSCHAR2Shipping InstructionsConditional
EINE-BSTAECHAR2Confirmation Control KeyConditional
EINE-XERSNCHAR1Reminder for Goods ReceiptConditional
EINE-MHDRZDEC3Minimum Remaining Shelf Life (in Days)Conditional
EINE-IPRKZCHAR1Info Record Update IndicatorConditional
EINE-BSTMAQUAN13Maximum Order QuantityConditional
EXPRF_LAND1CHAR3Country for Export/Import ProcessingConditional
EINE-EXPRFCHAR1Export/Import IndicatorConditional
EINE-RDPRFCHAR1Rounding ProfileConditional
EINE-VENDOR_RMA_REQCHAR1Vendor RMA (Return Material Authorization) RequiredConditional
EINE-AUT_SOURCECHAR1Automatic Source List Update IndicatorConditional
EINE-SKTOFCHAR1Cash Discount IndicatorConditional
EINE-MEPRFCHAR1Price Determination Schema (Pricing Profile)Conditional
EINE-INCOVCHAR3Incoterms VersionConditional
EINE-INCO1CHAR3Incoterms (Part 1)Conditional
EINE-INCO2_LCHAR70Incoterms Location 1 (Long Text)Conditional
EINE-INCO3_LCHAR70Incoterms Location 2 (Long Text)Conditional
EINE-NETPRCURR11Net price.Conditional
EINE-PEINHDEC5Price unit (per quantity).Conditional
EINE-BPRMECURR11Order price unit.Conditional
EINE-J_1BNBMCHAR30NCM code (Brazil)Conditional


3 - DCT for PIR: - Long Text

Field NameData TypeLengthDescriptionRule
INFNRCHAR10Info Record NumberRequired
EKORGCHAR4

Purchasing Organization


*To create a text for General Data, send the field empty

Required
ESOKZCHAR1

Purchasing Info Category (Standard, Subcontracting, Consignment, Pipeline)


*To create a text for General Data, send the field empty

Required
WERKSCHAR4PlantRequired
TDSPRASCHAR1Language KeyRequired
TEXTCHAR
TextRequired


4 - DCT for PIR: - Conditions

Field NameData TypeLengthDescriptionRule
INFNRCHAR10Info Record NumberRequired
COND-EKORGCHAR4Purchasing OrganizationRequired
COND-ESOKZCHAR1Purchasing Info Category (Standard, Subcontracting, Consignment, Pipeline)Required
COND-WERKSCHAR4PlantRequired
COND-KOPOSNUMC3Sequential Number of Condition RecordRequired
COND-COND_TYPECHAR4Condition Type (e.g., PB00, PBXX, RA01)Required
COND-VALID_FROMDATS8Validity Start Date for the ConditionConditional
COND-VALID_TODATS8Validity End Date for the ConditionConditional
KRECHCHAR1Calculation Type for Condition (e.g., Percentage, Amount)Conditional
COND-KBETR_EXTCURR11Condition Amount (External Representation)Conditional
COND-KONWACUKY5Currency Key for ConditionConditional
COND-KPEINDEC5Pricing Unit (Base Quantity for Condition)Conditional
COND-KMEINUNIT3Condition Unit (Unit of Measure for Condition)Conditional
COND-KUMZADEC5Numerator for Condition Conversion FactorConditional
COND-KUMNEDEC5Denominator for Condition Conversion FactorConditional
COND-MEINSUNIT3Base Unit of MeasureConditional
COND-KONMSUNIT3Condition Unit of Measure (Alternative)Conditional
COND-EXCLUSION_INDCHAR1Exclusion Indicator (for Condition Exclusion Logic)Conditional


5 - DCT for PIR: - Scales

Field NameData TypeLengthDescriptionRule
INFNRCHAR10Info Record NumberRequired - Field reference from above condition DCT
EKORGCHAR4Purchasing OrganizationRequired - Field reference from above condition DCT
ESOKZCHAR1Purchasing Info Category (Standard, Subcontracting, Consignment, Pipeline)Required - Field reference from above condition DCT
WERKSCHAR4PlantRequired - Field reference from above condition DCT
KOPOSNUMC3Sequential Number of Condition RecordRequired
COND_TYPECHAR4Condition Type (e.g., PB00, PBXX, RA01)Required
VALID_FROMDATS8Validity Start Date for ConditionConditional
VALID_TODATS8Validity End Date for ConditionConditional
LINE_NONUMC6Scale Line NumberConditional
KSTBM_QTYQUAN13Scale Quantity or Value Basis (threshold for scale)Conditional
KBETR_QTYCURR11Condition Rate (price or percentage)Conditional
SCALE_VALCURR13Scale Value (e.g., price value corresponding to KSTBM)Conditional
KBETR_VALCURR13Calculated Condition Amount for the Scale LevelConditional



Extraction Dependencies

Item #Step DescriptionTeam Responsible
001

ECC system access and table authorizations (connectivity)

Syniti team
002SQL access to Production DB or a copy of it's relevant tables  (connectivity)Syniti team
003Availability 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:

  1. Perform value mapping and data transformation rules.
    1. Legacy values are mapped to the to-be values (this could include a default value)
    2. Values are transformed according to the rules defined in
  2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation


Transformation Mapping/Rules (Source ECC / DCT)

Source Field InformationTransform RulesTarget Field Information
SequenceTechnical Source TableField NameTechnical Source FieldField TypeField LengthMapping TypeTransform Rule or Default Value

Validation Rule

Inline with Governance Rule



CommentsField DescriptionTypeLengthDecimalSap Table NameSap Field Name

1.001EINAINFNRLegacy Number of Purchasing Info RecordNUMC10

Not for Intercompany


IF DCT Intercompany Flag <> "", target structure is empty (skipt the record)

ELSE target field is empty


- Mandatory for Migration CockpitLegacy Number of Purchasing Info RecordNUMC10
EINAINFNR
1.002EINA/DCT

ECC/DCT: MATNR



(Material NumberCHAR18Transformation Rule1) 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 NumberCHAR18
EINAMATNR
1.003EINA

ECC/DCT: MATKL

Material Group - MATKL CHAR9Transformation Rule1) Use the source value, and lookup on the mapping table for <MATKL> and update the target field.

Dependent on Configuration

- Relevant for DataCleansing
- Relevant for DataConversion (Mapping)

Product GroupCHAR9
EINAMATKL
1.004EINA

ECC/DCT: LIFNR


Supplier's Account Number (Vendor Number - LIFNR)CHAR10Transformation Rule1) Use the source value, and lookup on the mapping table for Vendor <LIFNR> and update the target field.


- Mandatory for Migration Cockpit
- Relevant for
DataCleansing
- Relevant for DataConversion (Mapping)

Supplier's Account NumberCHAR10
EINALIFNR
1.005EINA

ECC/DCT: TXZ01


Short Text for Purchasing Info RecordCHAR40
1) Copy source field value as-is to the target field (1:1 direct mapping).

Short Text for Purchasing Info RecordCHAR40
 EINATXZ01
1.006EINAECC: SORTLSort Term for Non-Stock Info RecordsCHAR20
1) Copy source field value as-is to the target field (1:1 direct mapping).

Sort Term for Non-Stock Info RecordsCHAR20
 EINASORTL
1.007EINA

ECC/DCT: MEINS


Order Unit (ISO Format)UNIT3Transformation Rule1)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)UNIT3
 EINAMEINS
1.008EINA

ECC/DCT: UMREZ

Numerator for Conversion of Order UnitNUMC5
1) Copy source field value as-is to the target field (1:1 direct mapping).

Numerator for Conversion of Order UnitNUMC5
EINAUMREZ
1.009EINA

ECC/DCT: UMREN

Denominator for Conversion of Order UnitNUMC5
1) Copy source field value as-is to the target field (1:1 direct mapping).

Denominator for Conversion of Order UnitNUMC5
EINAUMREN
1.010EINA

ECC/DCT:: IDNLF


Material Number Used by SupplierCHAR35
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 SupplierCHAR35
EINAIDNLF
1.011EINAECC/DCT: VERKFSalesperson ResponsibleCHAR30
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 ResponsibleCHAR30
EINAVERKF
1.012EINAECC/DCT: TELF1Supplier's Telephone NumberCHAR16
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Supplier's Telephone NumberCHAR16
 EINATELF1
1.013EINAECC/DCT: MAHN1Days for First Reminder/ExpediterNUMC1
1) Use the source value to update the target field AS-IS

Days for First Reminder/ExpediterNUMC1
EINAMAHN1
1.014EINAECC/DCT: MAHN2Days for Second Reminder/ExpediterNUMC1
1) Use the source value to update the target field AS-IS

Days for Second Reminder/ExpediterNUMC1
 EINAMAHN2
1.015EINAECC/DCT: MAHN3Days for Third Reminder/ExpediterNUMC1
1) Use the source value to update the target field AS-IS

Days for Third Reminder/ExpediterNUMC1
EINAMAHN3
1.016EINAECC: URZNRChange NumberCHAR12
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structureChange NumberCHAR12
EINAURZNR
1.017EINAECC: URZDTValid toCHAR10
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structureValid toCHAR

EINAURZDT
1.018EINAECC: URZLA C/R. of OriginCHAR

1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structureC/R. of OriginCHAR

EINAURZLA
1.019EINAECC: URZTPCertif. Cat.CHAR

1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structureCertif. Cat.CHAR

EINAURZTP
1.020EINAECC: URZZTTime 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
EINAURZZT
1.021EINAECC/DCT: LMEINBase Unit of Measure (ISO Format)UNIT3Transformation Rule1)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)UNIT3
 EINALMEIN
1.022EINAECC/DCT: REGIORegionCHAR30
Copy source field value as-is to the target field (1:1 direct mapping).

RegionCHAR30
EINAREGIO
1.023EINAECC/DCT: VABMEVariable Purchase Order Unit ActiveUNIT3Transformation Rule1) Use the source value to update the target field AS-IS
- Relevant for DataConversion (Mapping)Variable Purchase Order Unit ActiveUNIT3
 EINAVABME
1.024EINAECC/DCT: WGLIFSupplier Material GroupCHAR30Transformation Rule1) Use the source value to update the target field AS-IS
ECC/DCT:Supplier Product GroupCHAR30
 EINAWGLIF
1.025EINA

ECC/DCT: LIFAB

Available (Deliverable) FromCHAR30
Copy source field value as-is to the target field (1:1 direct mapping).

Target field format: DD.MM.YYYY


Available (Deliverable) FromCHAR30
EINALIFAB
1.026EINA

ECC/DCT: LIFBI

Available (Deliverable) UntilCHAR30
Copy source field value as-is to the target field (1:1 direct mapping).

Target field format: DD.MM.YYYY


Available (Deliverable) UntilCHAR30
EINALIFBI
1.027EINAECC/DCT: KOLIFPrior SupplierCHAR10Transformation Rule1) Use the source value, and lookup on the mapping table for Vendor <LIFNR> and update the target fields.

- Relevant for DataCleansing
- Relevant for DataConversion (Mapping)

Prior SupplierCHAR10
EINAKOLIF
1.028EINAECC: ANZPUNumber of Price UnitsDEC (packed)5
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structure  Number of Price UnitsDEC (packed)5
EINAANZPU
1.029EINAECC/DCT:: PUNEIPrice UnitUNIT (char)3
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structure  Price UnitUNIT (char)3
EINAPUNEI
1.030EINAECC/DCT: RELIFIndicator: Regular SupplierCHAR10
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 SupplierCHAR10
 EINARELIF
1.031EINAECC/DCT: URZLACountry/Region of OriginCHAR30
Copy source field value as-is to the target field (1:1 direct mapping).

Country/Region of OriginCHAR30
 EINAURZLA
1.032EINAECC/DCT: MFRNRManufacturerCHAR10Transformation RuleUse 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)
ManufacturerCHAR10
 EINAMFRNR








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.001EINAECC: INFNRLegacy Number of Purchasing Info RecordNUMC10


- Mandatory for Migration CockpitLegacy Number of Purchasing Info RecordNUMC10
EINAINFNR
2.002STXL

ECC/DCT: TDSPRAS


Language KeyLANG1Transformation RuleAfter apply the data selection, use each line encountered in STXL-TDSPRAS//Not for Intercompany
- Mandatory for Migration Cockpit

Language KeyLANG1
EINATDSPRAS
2.003STXL

ECC: CLUSTD

DCT: TEXT

TextLRAW7902
Target field is equal to STXL-CLUSTD/Not for Intercompany
- Mandatory for Migration CockpitTextLRAW7902
EINATEXT

3.001EINEECC: INFNRLegacy Number of Purchasing Info RecordNUMC10

Not for Intercompany


IF DCT Intercompany Flag <> "", target structure is empty (skipt the record)

ELSE target field is empty


- Mandatory for Migration CockpitLegacy Number of Purchasing Info RecordNUMC10
EINEINFNR
3.002EINE

ECC/DCT: EKORG


Purchasing OrganizationCHAR4Transformation Rule1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG>
Dependent on Configuration

- Mandatory for Migration Cockpit
- Relevant for DataConversion (Mapping)


Purchasing OrganizationCHAR4
EINEEKORG
3.003EINE

ECC/DCT: ESOKZ


Purchasing Info Record CategoryCHAR1
Copy source field value as-is to the target field (1:1 direct mapping).
- Mandatory for Migration CockpitPurchasing Info Record CategoryCHAR1
EINEESOKZ
3.004EINE

ECC/DCT: WERKS


PlantCHAR4Transformation Rule1) 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
- Relevant for DataConversion (Mapping)


PlantCHAR4
EINEWERKS
3.005EINE

ECC/DCT: EKGRP

Purchasing GroupCHAR3Transformation Rule1) 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
- Relevant for DataConversion (Mapping)


Purchasing GroupCHAR3
EINEEKGRP
3.006EINE

ECC/DCT: WAERS


Currency Key(ISO Format)CUKY5Transformation Rule1) Use the source value, and lookup on the mapping table for Currency <WAERS>Dependent on Configuration

- Relevant for DataConversion (Mapping)

Currency Key(ISO Format)CUKY5
EINEWAERS
3.007EINE

ECC/DCT: MINBM


Minimum Purchase Order QuantityQUAN13
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 QuantityQUAN13
EINEMINBM
3.008EINE

ECC/DCT: NORBM

Standard Purchase Order QuantityQUAN13
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"

- Mandatory for Migration CockpitStandard Purchase Order QuantityQUAN13
EINENORBM
3.009EINE

ECC/DCT: APLFZ


Planned Delivery Time in DaysTIMS6
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Planned Delivery Time in DaysTIMS6
EINEAPLFZ
3.010EINEECC/DCT: UEBTOOverdelivery Tolerance LimitCHAR30
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Overdelivery Tolerance LimitCHAR30
EINEUEBTO
3.011EINEECC/DCT: UEBTKIndicator:Unlimited Overdelivery AllowedCHAR30
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Indicator:Unlimited Overdelivery AllowedCHAR30
EINEUEBTK
3.012EINEECC/DCT: UNTTOUnderdelivery Tolerance LimitCHAR30
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Underdelivery Tolerance LimitCHAR30
EINEUNTTO
3.013EINEECC: ANGNRQuotationCHAR10
1) Use the source value to update the target field AS-IS.  

20251127 *NOT PRESENT in Migration Cockpit structure. 

QuotationCHAR10
EINEANGNR
3.014EINEECC: ANGDTQuotation fromDATS10
1) Use the source value to update the target field AS-IS 20251127 *NOT PRESENT in Migration Cockpit structure.Quotation fromDATS10
EINEANGDT
3.015EINE

ECC: NETPR


DCT: Net Price in Purchasing Info Record

Net PriceDEC11,2
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structure.Net PriceDEC11,2
EINENETPR
3.016EINE

ECC: PEINH


DCT: Price unit (per quantity)

Price UnitDEC3
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structure.Price UnitDEC3
EINEPEINH
3.017EINEECC: TAX_COUNTRYCountry for Tax ReturnCHAR3
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structure.Country for Tax ReturnCHAR3
EINETAX_COUNTRY
3.018EINEECC/DCT: INCO2Incoterms (Part 2)CHAR28
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structure.Incoterms (Part 2)CHAR28
EINEINCO2
3.019EINEECC: MEGRUQuantity Conversion GroupCHAR4
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structure.Quantity Conversion GroupCHAR4
EINEMEGRU
3.020EINEECC/DCT: J_1BNBMNCM CodeCHAR16
1) Use the source value to update the target field AS-IS
20251127 *NOT PRESENT in Migration Cockpit structure.Nota Fiscal: Base Calculation IndicatorCHAR16
EINEJ_1BNBM
3.021EINEECC: BWTARValuation TypeCHAR30Transformation RuleUse the source value, and lookup on the mapping table for <VALUATION_TYPE) and update the target field.
- Relevant for DataConversion (Mapping)Valuation TypeCHAR30
EINEBWTAR
3.022EINEECC: MTXNOInd: Prod. Master Rec. PO Text Not Rele.NUMC10
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Ind: Prod. Master Rec. PO Text Not Rele.NUMC10
EINEMTXNO
3.023EINEECC/DCT: WEBREIndicator: GR-Based Invoice VerificationCHAR30
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier, region, or material category).
Indicator: GR-Based Invoice VerificationCHAR30
EINEWEBRE
3.024EINEECC: KZABSInd: Order Acknowledgment RequirementCHAR40
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Ind: Order Acknowledgment RequirementCHAR40
EINEKZABS
3.025EINEECC/DCT: MWSKZTax on Sales/Purchases CodeCHAR2Transformation RuleUse 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 CodeCHAR2
EINEMWSKZ
3.026EINEECC: TXDAT_FROMValid-From Date of the Tax RateCHAR30
1) Use the source value to update the target field AS-IS

Valid-From Date of the Tax RateCHAR30
EINETXDAT_FROM
3.027EINEECC: EVERSShipping InstructionsCHAR30Transformation Rule1) Use the source value to update the target field AS-IS applying Data ConversionApplies only if business condition is met (e.g. Supplier type, region, or material category).- Relevant for DataConversion (Mapping)Shipping InstructionsCHAR30
EINEEVERS
3.028EINEECC/DCT: BSTAEConfirmation Control KeyCHAR30Transformation RuleDefault value equal to '0001'Applies only if business condition is met (e.g. Supplier type, region, or material category).

- Relevant for DataConversion (Mapping)


Confirmation Control KeyCHAR30
EINEBSTAE
3.029EINEECC: XERSNInd: No Evaluated Receipt Settlem. (ERS)CHAR1
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Ind: No Evaluated Receipt Settlem. (ERS)CHAR1
EINEXERSN
3.030EINEECC/DCT: MHDRZMinimum Remaining Shelf LifeCHAR30
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Minimum Remaining Shelf LifeCHAR30
EINEMHDRZ
3.031EINEECC: IPRKZPeriod Ind. for Min. Remain. Shelf LifeCHAR2
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Period Ind. for Min. Remain. Shelf LifeCHAR2
EINEIPRKZ
3.032EINEECC/DCT: BSTMAMaximum Purchase Order QuantityQUAN13
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Maximum Purchase Order QuantityQUAN13
EINEBSTMA
3.033EINEECC: EXPRF_LAND1Foreign Trade: Country/RegionCHAR80Transformation RuleTransformation Rule:
1) Use the source value to update the target field AS-IS


Foreign Trade: Country/RegionCHAR 80
EINEEXPRF_LAND1
3.034EINEECC/DCT: EXPRFForeign Trade: ProcedureCHAR30Transformation Rule1) Use the source value to update the target field AS-ISApplies only if the PIR is linked to a specific Pgroup; Dependent on Configuration
Foreign Trade: ProcedureCHAR30
EINEEXPRF
3.035EINEECC/DCT: RDPRFRounding ProfileCHAR30Transformation Rule1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).- Relevant for DataConversionRounding ProfileCHAR30
EINERDPRF
3.036EINEECC: VENDOR_RMA_REQSupplier RMA Number RequiredCHAR30
1) Use the source value to update the target field AS-IS

Supplier RMA Number RequiredCHAR30
EINEVENDOR_RMA_REQ
3.037EINEECC: AUT_SOURCERelevant for Automatic SourcingCHAR30
1) Use the source value to update the target field AS-IS

Relevant for Automatic SourcingCHAR30
EINEAUT_SOURCE
3.038EINEECC: SKTOFInd: Item Does Not Qualify for Cash DiscCHAR30
1) Use the source value to update the target field AS-IS

Ind: Item Does Not Qualify for Cash DiscCHAR30
EINESKTOF
3.039EINEECC: MEPRFPrice Determinat. (Pricing) Date ControlDATS8
1) Use the source value to update the target field AS-IS

Price Determinat. (Pricing) Date ControlDATS8
EINEMEPRF
3.040EINEECC: INCOVIncoterms VersionCHAR30Transformation Rule1) Use the source value to update the target field AS-IS

Incoterms VersionCHAR30
EINEINCOV
3.041EINEECC: INCO1IncotermsCHAR30Transformation Rule1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).- Relevant for DataConversion (Mapping)IncotermsCHAR30
EINEINCO1
3.042EINEECC: INCO2_LIncoterms Location 1CHAR30
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Incoterms Location 1CHAR30
EINEINCO2_L
3.043EINEECC: INCO3_LIncoterms Location 2CHAR30
1) Use the source value to update the target field AS-ISApplies only if business condition is met (e.g. Supplier type, region, or material category).
Incoterms Location 2CHAR30
EINEINCO3_L



4.001EINEECC: INFNRLegacy Number of Purchasing Info RecordCHAR80

Note: Transformation will be applied where Decision = 'PIR' or 'Pricing Conditions'

IF DCT Intercompany Flag <> "", target structure is empty


- Mandatory for Migration CockpitLegacy Number of Purchasing Info RecordText80
EINEINFNR
4.002EINE

ECC: EKORG


DCT: Purchasing Organization

Purchasing OrganizationCHAR80Transformation Rule1) 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
- Relevant for DataConversion (Mapping)

Purchasing OrganizationText80
EINEEKORG
4.003EINE

ECC: ESOKZ


DCT: Infotype

Purchasing Info Record CategoryCHAR80Transformation RuleCopy source field value as-is to the target field (1:1 direct mapping).COND.ESOKZ ← EINE-ESOKZ- Mandatory for Migration CockpitPurchasing Info Record CategoryText80
EINEESOKZ
4.004EINE

ECC: WERKS


DCT: Plant

ECC: Plant



CHAR80Transformation Rule1) Use the source value, and lookup on the mapping table for Plant <WERKS>
COND.WERKS ← EINE-WERKS- Relevant for DataConversion (Mapping)PlantText80
EINEWERKS
4.005KONPECC: KOPOSCondition Sequence NumberNUMC2
1) Use the source value to update the target field AS-IS ELSE "1"COND.KOPOS ← KONP-KOPOS- Mandatory for Migration CockpitCondition Sequence NumberNumber2
KONPKOPOS
4.006KONPECC/DCT: KSCHLCondition TypeCHAR80Transformation Rule1) 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


COND.COND_TYPE ← KONP-KSCHL 


Mandatory to have PB00 or equivalent condition type for each record, but not limited to have only this condition type. Dependent on Configuration

- Mandatory for Migration Cockpit
- Relevant for DataConversion (Mapping)
Condition TypeText80
KONPKSCHL
4.007KONH

ECC: DATAB


DCT: Pricing Condition Start date

Valid FromDate

1) Use the source value to update the target field AS-ISCOND.VALID_FROM ← KONH-DATAB- Mandatory for Migration CockpitValid FromDate

KONHVALID_FROM
4.008KONH

ECC: DATBI


DCT: Pricing condition End Date

Valid ToDate

1) Use the source value to update the target field AS-ISCOND.VALID_TO ← KONH-DATBI- Mandatory for Migration CockpitValid ToDate

KONHVALID_TO
4.009KONMECC: KRECHCalculation TypeCHAR80Transformation Rule1) Use the source value to update the target field AS-IS

Calculation TypeText80
KONMKRECH
4.010KONP

ECC: KBETR


DCT: Net Price in Purchasing Info Record

AmountNUMC31,3
1) Use the source value to update the target field AS-IS

AmountNumber31,3
KONPKBETR
4.011KONP

ECC: KONWA


DCT: Currency

Condition Unit (Currency or Percentage)CHAR80
1) Use the source value to update the target field AS-IS

Condition Unit (Currency or Percentage)Text80
KONPKONWA
4.012KONP

ECC: KPEIN


DCT: Price unit (per quantity)

Condition Pricing UnitNUMC5
1) Use the source value to update the target field AS-IS

Condition Pricing UnitNumber5
KONPKPEIN
4.013KONP

ECC: KMEIN


DCT: Order Price Unit

Condition Unit of Measure ISOCHAR80Transformation Rule1)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 ISOText80
KONPKMEIN
4.014KONP

ECC: KUMZA


DCT: Numerator for Conversion of Order Unit to Base Unit

Numerator for ConversionNUMC5
1) Use the source value to update the target field AS-IS

Numerator for ConversionNumber5
KONPKUMZA
4.015KONP

ECC: KUMNE


DCT: Denominator for Conversion of Order Unit to Base Unit

Denominator for ConversionNUMC5
1) Use the source value to update the target field AS-IS

Denominator for ConversionNumber5
KONPKUMNE
4.016MARA

ECC: MEINS


DCT: Base Unit of Measure

Base Unit of Measure ISOCHA80Transformation RulePulled from MARA

Base Unit of Measure ISOText80
KONPMEINS
4.017KONMECC/DCT: KONMSCondition Scale Unit of Measure ISOCHAR80Transformation RuleTransformation Rule:
1) Use the source value to update the target field AS-IS


Condition Scale Unit of Measure ISOText80
KONMKONMS







Transformation Rule:
NO RULE - send blanks


Condition Exclusion IndicatorText80
CONDEXCLUSION_IND



5.001EINEECC: INFNRLegacy Number of Purchasing Info RecordNUMC10
Note: Transformation will be applied where Decision = 'PIR' or 'Pricing Conditions
- Mandatory for Migration CockpitLegacy Number of Purchasing Info RecordText80
EINEINFNR
5.002EINE

ECC: EKORG


DCT: Purchasing Organization

Purchasing OrganizationCHAR4Transformation Rule1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG>

- Mandatory for Migration Cockpit
- Relevant for DataConversion (Mapping)

Purchasing OrganizationText80
EINEEKORG
5.003EINE

ECC: ESOKZ


DCT: Infotype

Purchasing Info Record CategoryCHAR1Transformation RuleCopy source field value as-is to the target field (1:1 direct mapping).
- Mandatory for Migration CockpitPurchasing Info Record CategoryText80
EINEESOKZ
5.004EINE

ECC: WERKS 


DCT: Plant

PlantCHAR4Transformation Rule1) Use the source value, and lookup on the mapping table for Plant <WERKS>

- Relevant for DataConversion (Mapping)PlantText80
EINEWERKS
5.005KONPECC/DCT: KOPOSCondition Sequence NumberNumber2
1) Use the source value to update the target field AS-IS
- Mandatory for Migration CockpitCondition Sequence NumberNumber2
KONPKOPOS
5.006KONPECC/DCT: KSCHLCondition TypeText80Transformation Rule1) Use the source value to update the target field AS-IS
- Mandatory for Migration Cockpit
- Relevant for DataConversion (Mapping)
Condition TypeText80
KONPKSCHL
5.007KONH

ECC: DATAB


DCT: Pricing Condition Start date

Valid FromDate

1) Use the source value to update the target field AS-IS
- Mandatory for Migration CockpitValid FromDate

KONHDATAB
5.008KONH

ECC:DATBI


DCT: Pricing condition End Date

Valid ToDate

1) Use the source value to update the target field AS-IS
- Mandatory for Migration CockpitValid ToDate

KONHDATBI
5.009KONMECC/DCT: KLFN1Scale Item NumberNumber4
1) ROW_NUMBER() OVER(PARTITION BY KONM-KNUMH, KONM-KOPOS ORDER BY KONM-KONMS)
- Mandatory for Migration CockpitScale Item NumberNumber4
KONMKLFN1
5.011KONMECC/DCT: KBETRScale RateNumber31,3
1) Use the source value to update the target field AS-IS

Scale RateNumber31,3
KONMKBETR
5.012KONWECC/DCT: KSTBM 

Scale ValueNumber28,3
1) Use the source value to update the target field AS-IS

Scale ValueNumber28,3
KONWKSTBM
5.013KONMECC/DCT: KBETRScale RateNumber31,3
1) Use the source value to update the target field AS-IS

Scale RateNumber31,3
KONWKBETR















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.001STXLECC: TDOBJECTText ObjectText80
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
- Mandatory for Migration CockpitLegacy Number of Purchasing Info RecordText80
STXLTDOBJECT
6.002STXLECC/DCT: EKORGPurchasing OrganizationText80Transformation Rule1) Use the source value, and lookup on the mapping table for Purchasing Organization <EKORG>/Not for Intercompany

- Mandatory for Migration Cockpit
- Relevant for DataConversion (Mapping)
Purchasing OrganizationText80
STXLEKORG
6.003STXLECC/DCT: ESOKZPurchasing Info Record CategoryText80Transformation RuleCopy source field value as-is to the target field (1:1 direct mapping).
- Mandatory for Migration CockpitPurchasing Info Record CategoryText80
STXLESOKZ
6.004STXLECC/DCT: WERKSPlantText80Transformation Rule1) Use the source value, and lookup on the mapping table for Plant <WERKS>

- Relevant for DataConversion (Mapping)PlantText80
STXLWERKS
6.005STXLECC/DCT: TDSPRASLanguage KeyText80
Copy source field value as-is to the target field (1:1 direct mapping).
- Mandatory for Migration CockpitLanguage KeyText80
STXLTDSPRAS
6.006STXLECC/DCT: TEXTTextTextunrestricted
Copy source field value as-is to the target field (1:1 direct mapping).
- Mandatory for Migration CockpitTextTextunrestricted
STXLTEXT





Transformation Run Sheet

Item #Step DescriptionTeam Responsible
1Identify target S/4HANA fields and determine applicable legacy source fields from both ECC systems WP2, PF2Functional Team (S2P)+ Data Team (S2P)
2Map legacy field values to S/4HANA target values (including field-level mapping and technical names)Data Team (S2P), Syniti team
3Define value mapping rules for fields requiring standardization or harmonization across the two source systems WP2, PF2.Functional Team (S2P)+ Data Team (S2P)
4Identify and agree on default values where legacy data is incomplete or inconsistentBusiness Team + Functional Team (S2P)
5Configure transformation rules in Syniti Migrate (including calculated fields, formatting rules, etc.)Syniti team
6Review transformation logic and mappings with Business for confirmationBusiness Team
7Perform initial transformation run and generate draft target-ready datasetSyniti team
8Review draft target-ready data for structure and completenessData Team (S2P), Functional Team (S2P), Syniti
9Share transformed data with Business for Pre-load ValidationData Team (S2P)
10Incorporate feedback from Business and refine mappings or transformation logic as neededData Team (S2P)
12Syniti to transform the dataSyniti team
13Material 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 NameMapping Table Description

LIFNR (LFA1-LIFNR)

<XREF-Vendor>

MATNR (MARA-MATNR)

<XREF-Material>

WERKS (T001W-WERKS_

<Plant>

EKORG (T024E-EKORG) 

<Purchasing Organization> 

EKGRP  (T024-EKGRP)

<Purchasing Group>

MATKL (T023-MATKL)

<Material Group> 

MEINS (T006-MEINS)

<Unit of Measure>

MWSKZ (T007A-MWSKZ)

<1)Tax Code> 

< 2)Tax Code>

General Configuration for Info Records

<Info Records>

Tax Jurisdiction Code

<Tax Jurisdiction>

<Tax Jurisdiction Mapping>


Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
001Value Mapping Tables are completeFunctional Team (S2P) + Data Team (S2P)
002Info Record & Pricing configuration are completeFunctional Team (S2P) + Data Team (S2P)
003Org structure configuration is completeFunctional 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

TaskAction
Configuration

Ensure necessary configurations are in place in target system and field mapping is aligned with access sequence, condition types

Review Mapping TableEnsure all the source organization units are mapped with target values
Check ValuesValidate the pre-load data confirming the values are aligned with target system format and 
Validate template structure and required field populationEnsure 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
EINA-MATNR
EINE-EKORG
EINE-WERKS
EINE-WAERS
EINE-NETPR
EINE-BPRME
EINE-PEINH
EINE-WAERS
EINA-MEINS

Info Record Category

Check if the Info Record Category (EINE-ESOKZ) has been properly migrated and in case of conversion check the final result.
- Standard
- Subcontracting
- Consignment
- Pipeline

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

TaskAction

Conversion Accuracy

SyWay S2P Data Team to verify that all fields below meet pass the checks:
- Mandatory Fields
- Field and Value Mapping Correctness
- Null Checks
- Text Length Checks
- Check whether the all Business Rules proposed were respected

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:
- Material belongs to the Plant
- Configuration exists for UOM / Currency

Duplicate Detection

Identify and remove duplicate entries in the dataset

Business Rule Compliance

Ensure compliance with agreed rules, for instance
- material must have base UoM

Review Mapping TableEnsure 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 recordsExample: Run duplicate checks using key combinations (e.g., MATNR +  EKORG + WERKS)
Conduct dry runs using LTMC or BAPIs and review logsAnalyze load results and correct format or conversion errors

Business

 The following pre-load validations will be performed by the business. 

Completeness

TaskAction
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 coveredConfirm 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 PlantsVerify that all mapped EKORG and WERKS combinations exist for the expected materials and vendors.
Check that all relevant Condition Types are presentConfirm 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 textsEnsure 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 valuesReview mapped fields (e.g. Incoterms, Payment Terms, Currency) to ensure harmonization with approved master data mappings.
Validate deletion and blocking flagsEnsure no record is incorrectly marked as deleted or blocked unless explicitly confirmed by Syensqo Business.
Review price validity and activityConfirm that validity dates (DATAB, DATBI) cover the go-live date and that prices reflect the latest active vendor conditions

Accuracy

TaskAction

Conversion Accuracy

Verify that all fields below meet pass the checks: 
- Mandatory Fields
- Field and Value Mapping Correctness
- Null Checks
- Text Length Checks
- Check whether the all Business Rules proposed were respected

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
- material must have base UoM


Load

The loading process includes:

  1. 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
  2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

 

Load Run Sheet

Item #Step DescriptionTeam Responsible
001Confirm readiness of final approved data sets for each ECC source system WP2 and PF2Business / Functional Team
002Validate transformation rules and mappings in Syniti toolData Team (S2P-Data)
003Generate target-ready load files based on S/4HANA condition table formatData Team (Syniti)
004Review and approve load files before executionBusiness / Functional Team
005Execute automated data load using Syniti into the S/4HANA system (or generate manual load files if required)Data Team (Syniti)
006Monitor load progress and capture load statistics (records loaded, errors, duplicates, etc.)Data Team (Syniti) / Technical Team
007Extract loaded data from S/4HANA for post-load validationData Team (Syniti)
008Perform post-load data validation (compare target data with source/approved files) for all loaded pricing condition typesData Team (S2P-Data)
009Log and resolve any data load errors or mismatches identified during validationData Team (S2P-Data) + Functional Team
010Obtain business sign-off on successful load and validationBusiness Team
011Generate post load report is all steps are validatedData Team (S2P-Data) / Data Team (Syniti
012Archive load logs, error reports, and validation results for audit/complianceData Team (S2P-Data) / Data Team (Syniti) / PMO


Load Phase and Dependencies

Configuration

Configuration Document link

Item #Configuration Item
001ConfigurationsEnsure 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.
002Organization DataConfirm that all required Organizational Units (Purchasing Organizations, Plants, Company Codes, and Valuation Areas) are configured and available in the target system
003Vendor Master DataVendors (LIFNR) must be loaded and extended to the relevant Purchasing Organizations and Company Codes before Info Records are created
004Material Master DataMaterials (MATNR) must be loaded and extended to the relevant Plants and Purchasing Views before Info Record load execution
005Unit of Measure & CurrencyValidate that all UoM (MARM) and currency (TCUR*) configurations exist and match those used in the source Info Records and condition tables.
006Tax and Incoterm ConfigurationEnsure tax codes, Incoterm versions, and Incoterm values (INCO1/INCO2_L/INCOV) are configured in the target system
007Purchasing GroupsConfirm 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 TypeError DescriptionAction Taken
Invalid Date RangeValid From (DATAB) is after Valid To (DATBI)Corrected the date range to ensure DATAB < DATBI and in required date format
Duplicate RecordsIdentical key combinations found more than once in the load fileDuplicates removed or merged as per business rule. Aligned with Business and documented for future loads
Unmapped ValuesValues for fields like UoM, Currency, etc. not mapped in SynitiUpdated mapping tables; ensured value conversion aligned with S/4HANA settings
Invalid Currency FormatIncorrect currency formatting or unsupported currency codeStandardized to valid ISO currency codes (e.g., USD, EUR, JPY)
Invalid Number FormatKBETR or KPEIN contains special characters or comma separatorsCleaned formatting; ensured decimal values used with '.' as separator
Authorization ErrorsLack of access to execute load in target client/systemRaised access request; obtained necessary authorizations
Transformation MissRequired transformation logic not applied before loadRe-applied transformation rules and revalidated source-target mapping
Obsolete Master DataVendor or material master data no longer exists in target systemReplaced or removed based on business input
Technical Load FailureFile not processed due to syntax/format error or system issueReviewed 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

TaskAction
Ensure all required fields are properly coveredConfirm 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 PlantsVerify that all mapped EKORG and WERKS combinations exist for the expected materials and vendors.
Check that all relevant Condition Types are presentConfirm that each Info Record contains required pricing condition types (e.g. PBXX, FRA1, RA01) according to target Pricing Procedure.
Verify language coverage for textsEnsure 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 valuesReview mapped fields (e.g. Incoterms, Payment Terms, Currency) to ensure harmonization with approved master data mappings
Validate deletion and blocking flagsEnsure no record is incorrectly marked as deleted or blocked unless explicitly confirmed by business
Review price validityConfirm that validity dates (DATAB, DATBI) cover the go-live date and that prices reflect the latest active vendor conditions.

Accuracy

TaskAction
Compare uploaded data against source file values

Use Custom reconciliation tools to validate the following

  1. Number of records loaded against load file
  2. Any mismatch in condition value, unit , validity period against each input record at the KEY combination level
  3. Ensure field by field value match across all loaded records
Verify Key Field ValuesEnsure 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

TaskAction
Participate in Post-Load WalkthroughsJoin scheduled validation sessions with the migration and functional teams
Review Loaded Condition RecordsAccess the S/4HANA system to view loaded info records and purchasing price conditions
Check for Missing RecordsIdentify any missing records that were expected but not loaded

Accuracy

TaskAction
Compare Against Approved Load FileCross-check data in S/4HANA against the final business-approved load file used for migration
Validate Accuracy of Converted/Transformed DataReview any transformed fields (e.g., currency conversion, unit mappings) for correctness
Log and Report DiscrepanciesUse 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

ObjectDateLink
Reference Document20251110

Material is flagged as in scope according to MDS CNV-2019 Materials – Basic Data View

Reference Document20251110

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 Document20251110

Purchasing Organization (EINE.EKORG) is in scope based on enterprise structure mapping

Reference Document20251110

Plant (EINE.WERKS) is in scope based on enterprise structure mapping.

Change log

Version Published Changed By Comment
CURRENT (v. 644) Apr 22, 2026 13:47 SLOAN-ext, Anthony
v. 651 Mar 31, 2026 15:03 SLOAN-ext, Anthony
v. 650 Mar 31, 2026 14:55 SLOAN-ext, Anthony
v. 649 Mar 20, 2026 18:12 SLOAN-ext, Anthony
v. 648 Mar 20, 2026 17:11 SLOAN-ext, Anthony
v. 647 Mar 20, 2026 16:32 SLOAN-ext, Anthony
v. 646 Mar 20, 2026 14:54 SLOAN-ext, Anthony
v. 645 Feb 20, 2026 09:30 BUOSI-ext, Angelo
v. 644 Feb 17, 2026 10:48 MADHOK-ext, Jasleen
v. 643 Feb 07, 2026 10:55 MADHOK-ext, Jasleen

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

6 Comments

  1. For the Conversion Scope, “Active” is defined only by deletion flag + validity date.
    No reference to:

    • Usage frequency

    • Last PO date

    • Business criticality

    Can we introduce usage-based filter:

    • For example : No PO in last 36 months → review before migration.

    1. Reviewed and aligned with the Data Team during a call.

  2. For the "Relevancy Rules" section, I recommend adding :

    • Explicit uniqueness rule

    • Validity conflict resolution logic

    • Precedence hierarchy (Contract > PIR)

    1. Reviewed and aligned with the Data Team during a call.

  3. For the "Extraction Run Sheet" there is no mention of :

    • Delta extraction logic

    • Freeze window governance

    • Cutover sequencing

    That's may lead to late changes in ECC not synchronized.


    1. Reviewed and aligned with the Data Team during a call.