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

Purpose

This document outlines the conversion strategy for migrating Source List data from SAP ECC systems to SAP S/4HANA.

In the legacy systems, Source List entries may be duplicated, outdated, or inconsistently maintained across plants and purchasing organizations. Some entries reference inactive vendors or materials and contain obsolete validity dates. As per SyWay standards, Source List data will be rationalized and aligned to the new S/4HANA data model.

---CHECKLIST---

• Logical Source and Target Systems are identified. 
• Processing Type is specified (i.e. Direct Input, BAPI, IDoc, Web Service, OData API, etc.)
• Standard or custom load program name/BAPI/IDoc is specified to support this functionality.
• Data Mapping is provided for mappings which are not obvious to a suitably-skilled and experienced developer
• All translation requirements are clearly defined (including data validation rules, data derivation/calculation and default values, if applicable)Input and/or Output file layouts are provided for all record types possible
• Transaction volume is specifiedExecution frequency is specifiedRestart/Recovery requirements have been defined
• Error handling requirements are specified, including alerting requirement and expected action on failure. 
• Application log requirement if applicable to be specified. 

--- Additional topics to check---

• Update the Data Volume with a actual figures
• Rules for Data Merging (all systems)
• Mapping Rules & Conversion Rules

Conversion Scope

The objective is to convert active and relevant Source List entries from legacy systems (PF2, WP2) into S/4HANA in accordance with the Source List Master Data Design.

The Source List in SAP defines the approved supply source(s) for a specific material over a given timeframe and plant. It plays a critical role in the Source-to-Pay process, particularly in automatic sourcing and purchase requisition conversion.

The legacy systems already use Source List functionality, but the structure, completeness, and business relevance vary. A cleansing and standardization process will be undertaken to ensure only valid, non-redundant records are transitioned.

The data from legacy system includes:

1. Valid Source List entries with active Vendor and Material

2. Entries with current or future Validity Period

3. Plant (when applicable) and Purchasing Organization combinations relevant to the business scope

4. Fixed vendor flags and quota arrangements, if maintained

The data from legacy system excludes:

1. Entries with deletion indicators

2. Expired entries with no future relevance

3. Entries referring to blocked materials or vendors

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
P2F		217.793	S4H	180.000
WP2		139.062	S4H	90.000

Data will be extracted via Syniti Migrate and formatted into DCTs (Data Collection Templates). Business users will validate and confirm the relevance of each entry.

Additional Information

Multi-language Requirement

Descriptions are not applicable for Source List records, but Plant and Purchasing Organization descriptions may be presented in English and logon language if available.

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

Source List data will be loaded into SAP S/4HANA tables EORD and EINE (if applicable for quota and vendor assignment) according to the standard structure:

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
EORD	MATNR	MATNR	Material Number	CHAR	18
EORD	WERKS	EWERK	Plant	CHAR	4
EORD	ZEORD	DZEORD	Number of Source List Record	NUMC	5	Mandatory
EORD	ERDAT	ERDAT	Record Created On	DATS	8
EORD	ERNAM	ERNAM	Name of Person Responsible for Creating the Object	CHAR	12
EORD	VDATU	ORDAB	Source List Record Valid From	DATS	8
EORD	BDATU	ORDBI	Source List Record Valid To	DATS	8
EORD	LIFNR	ELIFN	Supplier's Account Number	CHAR	10
EORD	FLIFN	FLIFN	Indicator: Fixed Supplier	CHAR	1
EORD	EBELN	EVRTN	Agreement Number	CHAR	10
EORD	EBELP	EVRTP	Agreement Item	NUMC	5
EORD	FEBEL	FEBEL	Fixed Outline Purchase Agreement Item	CHAR	1
EORD	RESWK	BEWRK	Plant from Which Material is Procured	CHAR	4
EORD	FRESW	FRESW	Fixed issuing plant in case of stock transport order	CHAR	1
EORD	EMATN	EMATN	Material Number Corresponding to Manufacturer Part Number	CHAR	40
EORD	NOTKZ	ORDSP	Blocked Source of Supply	CHAR	1
EORD	EKORG	EKORG	Purchasing Organization	CHAR	4
EORD	VRTYP	BSTYP	Purchasing Document Category	CHAR	1
EORD	EORTP	EORTP	Category of Source List Record	CHAR	1
EORD	AUTET	AUTET	Source List Usage in Materials Planning	CHAR	1
EORD	MEINS	BSTME	Purchase Order Unit of Measure	UNIT	3
EORD	LOGSY	LOGSYSTEM	Logical System	CHAR	10

Data Cleansing

Standardization activities include:

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1097-001	C1	Removal of duplicates	Since we may have multiple source systems, is possible to
1097-002	C1	Elimination of expired entries	Remove expired dates before upload the date
1097-003	C1	Alignment with valid vendor-material combinations	Identify whether the info record exists
1097-004	C1	Standardizing date formats and flags	Check whether the date format is correct according to the users language

Conversion Process

The conversion process begins with the extraction of Source List records from ECC systems based on relevancy criteria. These records are pre-validated to ensure referenced materials and vendors are active and valid. The validated data is then loaded into the DCT where cleansing, standardization, and transformation activities are performed. Once complete, the business reviews the entries and confirms readiness. Following this, load files are prepared and test loads are executed for validation. If successful, a full data load is carried out into S/4HANA, followed by a post-load validation to confirm completeness and accuracy.

Data Privacy and Sensitivity

N/A

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
001	Extract data from source system based on relevancy rule	SyWay Data Team
002	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team
003	Only extract data that is NOT marked for deletion Where: EINA-LOEKZ = ””	SyWay Data Team
004	Only extract records that are still valid Where: EINA-LIFBI >= Today’s date	SyWay Data Team
005	Extract Info Records for Vendors that are NOT marked for deletion and are part of an Info Record	SyWay Data Team
006	Extract Info Records for Vendors that are in scope	SyWay Data Team
007	Extract Info Records for Materials that are NOT marked for deletion and are part of the respective Info Record	SyWay Data Team
008	Extract Info Records for Materials that are in scope	SyWay Data Team
009	Extract Info Records for Plants that are in scope. Do this check when EINE-WERKS is different than initial	SyWay Data Team

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
001	Vendor - The Info Record is created for a specific vendor, therefore the vendor must exist and be active	S2P
002	Material - The Info Record is for a specific material, therefore the material must exist and be active	S2P
003	Purchasing Organization - Mandatory organizational level (configuration). Must be valid for both the vendor and material	S2P
004	Plant (optional) - If a plant-specific Info Record is used, the plant must be valid (included on scope) and maintained	FICO
005	Currency & UoM - Must align with vendor master and material master data	S2P
006	Tax Code - Should exist in system and be consistent with vendor's country and plant region	S2P
007	Conditions - Purchasing conditions (price, discounts, scales) are typically stored in condition records. Linked to Info Records via condition tables	S2P
008	Vendor Master Settings - The vendor must have the purchasing organization maintained in purchasing view	S2P

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow 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
001	Identify target S/4HANA fields and determine applicable legacy source fields from both ECC systems WP2, PF2	Functional Team (S2P)+ Data Team (S2P)
002	Review condition types and access tables used in each ECC source systems WP2, PF2.Those have to be translated into the new S/4Hana Conditions	Business Team + Functional Team (S2P)
003	Map legacy field values to S/4HANA target values (including field-level mapping and technical names)	Data Team (S2P), Data Team (Syniti)
004	Define value mapping rules for fields requiring standardization or harmonization across the two source systems WP2 and PF2.	Functional Team (S2P)+ Data Team (S2P)
005	Identify and agree on default values where legacy data is incomplete or inconsistent	Business Team + Functional Team (S2P)
006	Configure transformation rules in Syniti Migrate (including calculated fields, formatting rules, etc.)	Data Team (Syniti), Data Team (S2P)
007	Review transformation logic and mappings with Business for confirmation	Business Team + Functional Team (S2P)
008	Perform initial transformation run and generate draft target-ready dataset	Data Team (Syniti),
009	Review draft target-ready data for structure and completeness	Data Team (S2P), Functional Team (S2P)
010	Share transformed data with Business for Pre-load Validation	Business Team
011	Incorporate feedback from Business and refine mappings or transformation logic as needed	Data Team (S2P)
012	Finalize and approve transformed data as Target Ready Load File	Business + Functional (S2P) + Data Team (S2P)
013	Handover final file to Load Team or trigger the load via Syniti Load Workbench	Data Team (Syniti), Data Load Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
001	Legacy	EINA	INFNR	Legacy Number of Purchasing Info Record	S/4HANA	EINA	INFNR	Legacy Number of Purchasing Info Record	Generate the Info Record number and keep this mapping in a reference table (this will might be used for Transactional Data
002	Legacy	EINA	MATNR	Material	S/4HANA	EINA	MATNR	Material	Select the new Material Code from the mapping table and update the corresponding target structure accordingly
003	Legacy	EINA	MATKL	Material Group	MATKL	Material Group	MATKL	Material Group	Select the new Material Group from the mapping table and update the corresponding target structure accordingly
004	Legacy	EINA	LIFNR	Vendor	S/4HANA	EINA	LIFNR	Vendor	Select the new Vendor Code from the mapping table and update the corresponding target structure accordingly
005	Legacy	EINA	INCO1	Incoterm	S/4HANA	EINA	INCO1	Incoterm	Select the Incoterm Code from the mapping table and update the corresponding target structure accordingly
006	Legacy	EINA	MEINS	Order Unit	S/4HANA	EINA	MEINS	Order Unit	Select the new Order Unit Code from the mapping table and update the corresponding target structure accordingly
007	Legacy	EINA	MFRNR	Manufacturer	S/4HANA	EINA	MFRNR	Manufacturer	Select the new Manufacturer Code from the mapping table and update the corresponding target structure accordingly
008	Legacy	EINE	WERKS	Plant	S/4HANA	EINE	WERKS	Plant	Select the new Plant Code from the mapping table and update the corresponding target structure accordingly
009	Legacy	EINE	WAERS	Currency	S/4HANA	EINE	WAERS	Currency	Select the new Currency Code from the mapping table and update the corresponding target structure accordingly

Transformation Mapping

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

Mapping Table Name	Mapping Field Name	Mapping Table Description
LIFNR	LIFNR	<Vendor>
MATNR	MATNR	<Material>
WERKS	WERKS	<Plant>
EKORG	EKORG	<Purchasing Organization>
EKGRP	EKGRP	<Purchasing Group>
MATKL	MATKL	<Material Group>
MEINS	MEINS	<Unit of Measure>
WAERS	WAERS	<Currency>

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
001	Org structure configuration is complete	Functional Team (S2P) + Data Team (S2P)
002	Configuration for Purchasing Conditions is complete	Functional Team (S2P) + Data Team (S2P)
003	Value Mapping Tables are complete	Functional Team (S2P) + Data Team (S2P)
004	Dependent Master Data records for Materials / Vendors are loaded	Functional Team (S2P) + Data Team (S2P)

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Configuration	Ensure necessary configurations are in place in target system and field mapping is aligned with access sequence, pricing condition types
Review Mapping Table	Ensure all the source organization units are mapped with target values
Check Values	Validate the pre-load data confirming the values are aligned with target system format and
Validate template structure and required field population	Ensure mandatory fields like VKORG, VTWEG, MATNR, KUNNR, KSCHL, valid dates are filled

Accuracy

Task	Action
Review Mapping Table	Ensure all the source organization units are mapped with target values
Check mapping rules against configuration (access sequences, condition tables)	Cross-check mapping sheet with customizing entries in V/03, V/04, V/05, V/08
Set up validation rules based on condition tables and field catalog	Use rule-based validation and lookups against master data (e.g., MARA, KNA1)
Perform format validation (date, currency, decimal separators)	Standardize format to match SAP accepted input (e.g., YYYYMMDD for dates)
Implement logic to detect duplicate condition records	Example: Run duplicate checks using key combinations (e.g., VKORG + MATNR + KUNNR)
Conduct dry runs using LTMC or BAPIs and review logs	Analyze load results and correct format or conversion errors

Business

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

Completeness

Task	Action
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

Workflow history