Purpose

The purpose of this document is to define the conversion approach for migrating Purchasing Info Records into S/4HANA from multiple SAP ECC source systems. The migration of Purchasing Requisitions (PRs) aims to ensure business continuity by transferring relevant and open requisition data from one or more legacy systems into the SAP S/4HANA environment. This process is essential for preserving in-flight procurement processes, avoiding disruption in material and service availability, and maintaining traceability of internal purchasing demands.

---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 specified Execution 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
•  (ABUOS)
  •  Rules for Data Merging (all systems)
  •  
  Mapping Rules & Conversion Rules
  • Conversion Scope
  •  Data Loading Details

Conversion Scope

The scope of this document covers This document outlines the approach for converting migrating active and relevant Purchase Requisitions (PR) from Purchasing Requisitions from Syensqo's legacy SAP ECC systems (PF2 and WP2) into SAP S/4HANA following , in alignment with the Procurement Master Data Design Standard.

Purchasing Requisitions will be migrated to support operational procurement, sourcing strategies, and Ariba integration. All requisitions will be validated, cleansed, and centrally loaded using standardized templates and mapped fields, ensuring consistency with the target S/4HANA data model.

Due to the decentralized nature of the current system landscape—where requisition data is stored across PF2 and WP2—discrepancies in materials, vendors, and organizational data may exist. As a result, data harmonization, cleansing, and mapping are critical to ensure accurate and reliable information in the target system. These efforts will also ensure that load templates are properly formatted and aligned with the S/4HANA requirements.

The data from legacy system includes:

1. Requisitions from multiple source systems referring to the same Vendor and Material
2. Valid combinations of Material (MATNR), Plant, and Purchasing Group
3. Requisitions with active Purchasing Organization and account assignment details
4. Open requisitions or those converted into Purchase Orders in the last 2 years
5. Requisitions with key control data

1. (e.g.,

1. Delivery Date,

1. Quantity,

1. Account Assignment)

1. Requisitions relevant for open sourcing processes or planned purchases

The data from legacy system excludes:

1. Requisitions flagged for deletion or already fully processed (PO/Item received or deleted)
2. Requisitions with blocked or deleted materials or vendors
3. Requisitions referencing Plants, Vendors, or Materials that are Out of Scope (OOS)
4. Draft or incomplete requisitions missing essential data (e.g., Material, Quantity)
5. Requisitions created solely for test or training purposes

6.  Obsolete PRs marked for deletion

7. PRs not used within last 3 years (unless flagged for business exception)

8. PRs with incomplete vendor or material references

*The figures described above, are restricted to one 1W Period.
**The objective is to reduce the data volume to be migrated by 80%, retaining only manually created Purchase Requisitions.

Additional Information

Multi-language Requirement

Long Texts must be migrated in all languages relevant to global purchasing defined in the Source System (when availableon source system/PurchReq)

Data Deduplication

For this data object, deduplication rules are not applicable. This is due to the fact that the object represents a transactional entity exclusively created and maintained within the target system. As such, there is no risk of duplicate records originating from external sources or legacy systems. The object’s lifecycle is fully controlled within the system, ensuring uniqueness by design.

Therefore, no deduplication logic or validation needs to be implemented for this object in the data migration or integration processes.

Document Management

N/A

Legal Requirement

Legal Requirement: Retention of pricing data history should comply with local audit regulations.N/A

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Data Merging Strategy

Purchasing Requisitions (PRs) typically do not require data merging like master data does for the reason they are related to transactional and historical records. However this topic can be considered as Not Applicable (N/A).

Data Cleansing

Conversion Process

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

Image Added

Image Added

Data Privacy and Sensitivity

Extraction

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

1. 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.
2. 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

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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:

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

Transformation Rules

Transformation Mapping

Tables are not yet available to be mentioned here.

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Processing Details:

Image Added

Load Method:  We are using LSMW (Legacy System Migration Workbench) to perform the data migration for this object.

Tool: LSMW (Legacy System Migration Workbench)

Technical Approach: Utilization of BAPI BAPI_REQUISITION_CREATE (or BAPI_PR_CREATE) to create Purchasing Requisitions.

 Load Run Sheet

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also

Change log