Status	Lead Approval
Owner	SICONOLFI-ext, Michael
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create in S/4 HANA.

Conversion Scope

The scope of this document covers the approach for converting active from Legacy Source Systems into S/4HANA following the Master Data Design Standard.

The material and vendor in the quote are in the migration scope.
The contract is still within the validity period.
If multiple records exist for the same material and vendor, select only the one with the most recent effective date.

Sequence:

Material Master → Purchasing Info Record → Purchasing Contracts

The data from legacy system includes:

The data from legacy system excludes:

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2			S4H
WP2			S4H

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Field Description	Check Table	Data Type	Length	Requirement
EKKO	LIFNR	Vendor Account Number	LFA1	C	3	Internal
EKKO	SPRAS	Language Key	T002	X	16	Internal
EKKO	ZTERM	Terms of Payment Key	T052	C	10	Mandatory
EKKO	ZBD1T	Cash (Prompt Payment) Discount Days		C	70	Mandatory
EKKO	ZBD2T	Cash (Prompt Payment) Discount Days		C	32	Mandatory
EKKO	ZBD3T	Cash (Prompt Payment) Discount Days		C	2	Mandatory
EKKO	ZBD1P	Cash Discount Percentage 1		C	70	Internal
EKKO	ZBD2P	Cash Discount Percentage 2		C	32	Internal
EKKO	EKORG	Purchasing Organization	T024E	C	2
EKKO	EKGRP	Purchasing Group	T024	C	10	Not in use
EKKO	WAERS	Currency Key	TCURC	C	1	Not in use
EKKO	WKURS	Exchange Rate		C	10	Not in use
EKKO	KUFIX	Indicator: Fixing of Exchange Rate		C	1	Not in use
EKKO	BEDAT	Purchasing Document Date		P	8	Internal
EKKO	KDATB	Start of Validity Period		C	10	Not in use
EKKO	KDATE	End of Validity Period
EKKO	IHREZ	Your Reference
EKKO	VERKF	Responsible Salesperson at Vendor's Office
EKKO	TELF1	Vendor's Telephone Number
EKKO	LLIEF	Supplying Vendor	LFA1
EKKO	INCO1	Incoterms	TINC
EKKO	INCO2	Incoterms Location 1
EKKO	KTWRT	Target Value for Header Area per Distribution
EKKO	UNSEZ	Legacy Number
EKPO	EBELP	Item Number of Purchasing Document
EKPO	TXZ01	Short Text
EKPO	MATNR	Material Number	MARA
EKPO	WERKS	Plant	T001W
EKPO	LGORT	Storage Location	T001L
EKPO	BEDNR	Legacy Contract Line Number
EKPO	MATKL	Material Group	T023
EKPO	KTMNG	Target Quantity
EKPO	MEINS	Purchase Order Unit of Measure	T006
EKPO	BPRME	Order Price Unit (Purchasing)	T006
EKPO	BPUMZ	Numerator for Conversion of Order Price Unit into Order Unit
EKPO	BPUMN	Denominator for Conv. of Order Price Unit into Order Unit
EKPO	NETPR	Net Price in Purchasing Document (in Document Currency)
EKPO	PEINH	Price Unit
EKPO	MWSKZ	Sales Tax Code	T007A
EKPO	INSMK	Stock Type
EKPO	SPINF	Indicator: Update Info Record
EKPO	MAHN1	Number of Days for First Reminder/Expediter
EKPO	MAHN2	Number of Days for Second Reminder/Expediter
EKPO	MAHN3	Number of Days for Third Reminder/Expediter
EKPO	UEBTO	Overdeliver Tolerance Limit
EKPO	UEBTK	Indicator: Unlimited Overdeliver Allowed
EKPO	UNTTO	Underdelivery Tolerance Limit
EKPO	PSTYP	Item Category in Purchasing Document	T163
EKPO	KNTTP	Account Assignment Category	T163K
EKPO	REPOS	Invoice Receipt Indicator
EKPO	WEBRE	Indicator: GR-Based Invoice Verification
EKPO	ABMNG	Standard release order quantity
EKPO	PLIFZ	Planned Delivery Time in Days
EKPO	BSTAE	Confirmation Control Key	T163L
EKPO	LBLKZ	Subcontracting vendor
EKPO	KANBA	Kanban Indicator
EKPO	WEORA	Acceptance At Origin

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

Extraction

Extract data from a source into . There are 2 possibilities:

The data exists. connects to the source and loads the data into . There are 3 methods:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #	Requirement Description	Team Responsible

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

Item #	Step Description	Team Responsible

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

Perform value mapping and data transformation rules.
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
Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible

Transformation Rules

Source Table	Source Field	Source Description
EKKO	EBELN	Purchasing Document Number
EKKO	BUKRS	Company Code
EKKO	BSTYP	Purchasing Document Category
EKKO	BSART	Purchasing Document Type
EKKO	PINCR	Item Number Interval
EKKO	LPONR	Last Item Number
EKKO	LIFNR	Vendor Account Number
EKKO	SPRAS	Language Key
EKKO	ZTERM	Terms of Payment Key
EKKO	ZBD1T	Cash (Prompt Payment) Discount Days
EKKO	ZBD2T	Cash (Prompt Payment) Discount Days
EKKO	ZBD3T	Cash (Prompt Payment) Discount Days
EKKO	ZBD1P	Cash Discount Percentage 1
EKKO	ZBD2P	Cash Discount Percentage 2
EKKO	EKORG	Purchasing Organization
EKKO	EKGRP	Purchasing Group
EKKO	WAERS	Currency Key
EKKO	WKURS	Exchange Rate
EKKO	KUFIX	Indicator: Fixing of Exchange Rate
EKKO	BEDAT	Purchasing Document Date
EKKO	KDATB	Start of Validity Period
EKKO	KDATE	End of Validity Period
EKKO	IHREZ	Your Reference
EKKO	VERKF	Responsible Salesperson at Vendor's Office
EKKO	TELF1	Vendor's Telephone Number
EKKO	LLIEF	Supplying Vendor
EKKO	INCO1	Incoterms
EKKO	INCO2	Incoterms Location 1
EKKO	KTWRT	Target Value for Header Area per Distribution
EKKO	UNSEZ	Legacy Number
EKPO	EBELP	Item Number of Purchasing Document
EKPO	TXZ01	Short Text
EKPO	MATNR	Material Number
EKPO	WERKS	Plant
EKPO	LGORT	Storage Location
EKPO	BEDNR	Legacy Contract Line Number
EKPO	MATKL	Material Group
EKPO	KTMNG	Target Quantity
EKPO	MEINS	Purchase Order Unit of Measure
EKPO	BPRME	Order Price Unit (Purchasing)
EKPO	BPUMZ	Numerator for Conversion of Order Price Unit into Order Unit
EKPO	BPUMN	Denominator for Conv. of Order Price Unit into Order Unit
EKPO	NETPR	Net Price in Purchasing Document (in Document Currency)
EKPO	PEINH	Price Unit
EKPO	MWSKZ	Sales Tax Code
EKPO	INSMK	Stock Type
EKPO	SPINF	Indicator: Update Info Record
EKPO	MAHN1	Number of Days for First Reminder/Expediter
EKPO	MAHN2	Number of Days for Second Reminder/Expediter
EKPO	MAHN3	Number of Days for Third Reminder/Expediter
EKPO	UEBTO	Overdeliver Tolerance Limit
EKPO	UEBTK	Indicator: Unlimited Overdeliver Allowed
EKPO	UNTTO	Underdelivery Tolerance Limit
EKPO	PSTYP	Item Category in Purchasing Document
EKPO	KNTTP	Account Assignment Category
EKPO	REPOS	Invoice Receipt Indicator
EKPO	WEBRE	Indicator: GR-Based Invoice Verification
EKPO	ABMNG	Standard release order quantity
EKPO	PLIFZ	Planned Delivery Time in Days
EKPO	BSTAE	Confirmation Control Key
EKPO	LBLKZ	Subcontracting vendor
EKPO	KANBA	Kanban Indicator
EKPO	WEORA	Acceptance At Origin

Transformation Mapping

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible

Load Phase and Dependencies

Configuration

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

Error Handling

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
is in scope based on data design and any exception requested by business.

Change log

Version	Published	Changed By
CURRENT (v. 4)	Apr 16, 2026 13:21	MADHOK-ext, Jasleen
v. 35	Apr 15, 2026 15:16	BATTINI-ext, Srinivasarao
v. 34	Apr 15, 2026 12:56	BATTINI-ext, Srinivasarao
v. 33	Apr 02, 2026 08:33	BATTINI-ext, Srinivasarao
v. 32	Mar 24, 2026 13:14	BATTINI-ext, Srinivasarao
v. 31	Mar 24, 2026 12:03	BATTINI-ext, Srinivasarao
v. 30	Mar 24, 2026 11:38	BATTINI-ext, Srinivasarao
v. 29	Mar 24, 2026 07:00	BATTINI-ext, Srinivasarao
v. 28	Mar 24, 2026 06:46	BATTINI-ext, Srinivasarao
v. 27	Mar 24, 2026 06:33	BATTINI-ext, Srinivasarao

Go to Page History

Apr 23, 2026	Actor	Type	Activity	Version
Lead Approval	TILBEE-ext, Amanda	Comment	commented 2:38 pm This document should cover validation of agreements against ICertis contracts so we have end to end alignment on legal contracts and purchase contracts. We need rules for when an OA / SA is created and how the ICertis contract references is included.
		Comment	commented 2:36 pm Shouldnt this be part of validation rules?
		Comment	commented 2:36 pm What does this mean? 'your SAP Solution"??
		Comment	commented 2:36 pm Shouldn't this be covered in inclusions?
		Comment	commented 2:31 pm This doesnt contain any rules.
		Comment	commented 2:29 pm Shouldnt we know what this is?
		Comment	commented 2:20 pm Rewrite as a conversion spec. there should be no 'make sure' but a clear rule set of field mapping - legacy to target; transformation - legacy to target; relevancy rules; conditional logic
		Comment	commented 2:17 pm This is missing conditional importance / logic.
		Comment	commented 2:16 pm This is very hard to read. Please restructure the table. Is this source based on only the inclusions? Why are we ending up with the same number in target? Where are the mapping or transformation rules?
		Comment	commented 2:12 pm Are these exclusions in use? Include additional info on this so impacts are understood.
		Comment	commented 2:11 pm Why are these being excluded?
		Comment	commented 2:09 pm This needs a mapping activity as both are likely to be changing.
		Comment	commented 2:08 pm This should be a mapping activity from legacy to new, not filter criteria to exclude details.
	ROWLINSON-ext, Kerry	Comment	commented 1:04 pm As part of R2 ECC developments implemented are fields: EKKO-ZZICMAGREEMENTCODE which will hold the Icertis agreement number filled by the user on new OA creation or in change OA post R2 go live. EKKO-ZZOAVERIFICATION which is a verification status which can be set by the user post R2 go live. If Icertis number is filled above, leave this blank - expect OA needs to be migrated. 01 - Verified without ICM contract (is required to be migrated, but there is no ICM agreement currently to map to) 02 - Do not migrate Ideally, every OA to migrate would have one or the other of these fields set, plus any other 'rules' met - validity date, open target value, target qty etc.
		Comment	commented 12:07 pm As above, the diagrams need to be drawn in confluence for everyone to be able to see them.
		Comment	commented 12:03 pm Clarify which specific blocking statuses, for both this client level check and the plant level below.
		Comment	commented 12:01 pm If the valid to date is in the past, then the OA is expired. Can just be excluded. But the types of invalid dates which should be reported for cleansing are 31.12.9999 31.12.nn99 - anything more than nn(to be defined) years in the future.
		Comment	commented 11:57 am Clarify what we are trying to achieve with this report. If the header is marked for deletion, the OA is not valid. Considering the account assignment data is not relevant. Same as below for the items marked for deletion. No cleansing is required for the account assignment data.
		Comment	commented 11:55 am This is not possible in SAP. The header deletion is set automatically only when all items are marked for deletion. There will never be any entries in this report.
		Comment	commented 11:47 am In SAP the can be OA items with blank account assignment category meaning the item is coming into stock - there will be no EKKN data. If an account assignment category is selected that requires account assignment data it has to be entered, an OA cannot exist without it. It is also feasible for account assignment to be 'unknown' on the OA, SAP will force it to be entered on the purchase order or requisition. So can we clarify what problem we are looking for with this report?
		Comment	commented 11:43 am This is not possible in SAP and there will be no entries found
		Comment	commented 11:41 am Unable to see or open the diagram. In confluence, the diagrams need to be drawn in the tool so that everyone can see them. I can help you with that, if required.
		Comment	commented 11:39 am Typo
		Comment	commented 11:39 am Can this be explained further? If there is an OA for a material it is going to have a price? Is this saying always to take the price from the info record instead?
		Comment	commented 11:35 am Can this be clarified exactly which date? Valid from? Would you use the source list to determine which one they are actually using? Or look at the release history? Or ask Syensqo to confirm? The dates might not enough to make an automated choice.
		Comment	commented 11:30 am Can this also exclude OAs where there is no remaining target value or no remaining quantity. This may not be exactly zero, but if only a small percentage of the total remains the contract is no longer useable in terms of raising further POs. Exclude any OAs which are not released.
		Comment	commented 11:28 am This is not possible in SAP
	TILBEE-ext, Amanda	Comment	commented 7:00 am Please clarify what this means 'verified with the one year consumption'
		Comment	commented 6:59 am The attribute design has been provided previously, please advise what is needed.
		Comment	commented 6:59 am Please specify the source of this when using the word 'contract'
Apr 16, 2026
	JAIN-ext, Gaurav	State	changed expiry date to '23 Apr, 2026 02:11 pm' at 2:11 pm
	JAIN-ext, Gaurav	State	changed state to Lead Approval at 2:11 pm	v36
Tech Review of Updates	JAIN-ext, Gaurav	State	gave Minor change approval at 2:11 pm

Workflow history

Space shortcuts

Page tree

CNV-9040 Operational Contracts

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log