Status
Owner	SICONOLFI-ext, Michael
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

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

Summarise how the data is currently utilized and set up in the legacy system/s and how object is intended to be represented in S/4, and any other relevant information

Conversion Scope

The scope of this document covers the approach for converting active <Data Object> from Legacy Source Systems into S/4HANA following the <Data Object> 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:

1. Relevancy Criteria 1
2. Relevancy Criteria 2
3. Relevancy Criteria n

The data from legacy system excludes:

1. Exclusion Criteria 1
2. Exclusion Criteria 2
3. Exclusion Criteria n

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

Summarize Multi-language Requirement/s, if any

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

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

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

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

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

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

Data Collection Template (DCT)

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

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

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 Syniti Migrate to make the data Target ready:

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 Syniti Migrate
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 Run Sheet

Item #	Step Description	Team Responsible

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
		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

Use the exact name and reference this section in the “Transformation rules” above

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

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
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 Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

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

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log