Status	Revision in Progress
Owner	LEW-ext, Chun Ming
Stakeholders

Purpose

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

Open sales orders are orders that are not fully delivered or billed and still require fulfillment or financial processing. This conversion ensures business continuity and data consistency for ongoing customer transactions. It should be a seamless migration, and business is able to continue working with open Sales Order in S/4 HANA.

Conversion Scope

The scope of this document covers the approach for converting Open Sales Orders, including relevant schedule lines and partner data, from legacy source systems into SAP S/4HANA.

From the current system landscape, open sales order data resides separately across legacy systems (WP2 and PF2), often with inconsistent formatting, incomplete references, and varying document structures. It is required to harmonize, cleanse, and validate the sales order data to ensure that only business-relevant, open orders are migrated to S/4HANA.

While WP2 and PF2 serve as the primary source systems, various transformation and mapping logic will be applied to generate load templates that conform to the target S/4HANA order structure, including header, item, schedule line, pricing, and partner functions. The conversion scope specifically includes orders that are not fully delivered or billed, with open quantities, future delivery dates, or billing schedules, and which remain critical to business continuity post go-live.

The data from legacy system includes:

The Sales Area of the Sales Orders are within the scope of S4 HANA.
Sales Orders with Open Quantities:
1. Orders with undelivered items, i.e., delivery quantity < order quantity.
2. Orders where the delivery status is not marked as complete.
3. Orders with open billing quantity, meaning not fully invoiced.
Special Sales Documents Still in Processing: XXX to be decided. Ideally all CN, DN and return should be closed in legacy.
1. Return orders or debit / credit memo requests not yet fully processed.
2. Partial deliveries or partial credit documents awaiting completion.

The data from legacy system excludes:

Fully Delivered and Billed Sales Orders:
1. Orders where all items are delivered (delivery complete) and invoiced (billing complete).
2. Orders archived in legacy system and no longer used operationally.
Rejected or Cancelled Orders:
1. Sales orders where header or item status indicates cancellation or rejection.
2. Orders marked with final rejection reason codes.
Out-of-Scope Sales Document Types or Sales Areas:
1. Document types not in use or excluded by process design (e.g., internal orders, sample/test).
2. Orders belonging to sales organizations, distribution channels, or divisions not part of S/4 scope.
Orders Without Business or Legal Justification:
1. Orders with no meaningful transactional history, or created erroneously.
2. Orders flagged by business for exclusion due to redundancy.

List of source systems and approximate number of records

Scenario No	Source	Scope (Legacy Scenario)	Supplying Entity Target System	Receiving Entity Target System	Source Approx No. of Records	Target System	Target Approx No. of Records
1	WP2	Standard Open Sales Orders	S/4HANA ROW	S/4HANA ROW	XXX	S/4HANA ROW	XXX
2	PF2	Standard Open Sales Orders	S/4HANA ROW	S/4HANA ROW	XXX	S/4HANA ROW	XXX
3	WP2	Standard Open Sales Orders	S/4HANA China	S/4HANA China	XXX	S/4HANA China	XXX
4	PF2	Standard Open Sales Orders	S/4HANA China	S/4HANA China	XXX	S/4HANA China	XXX
5	WP2	Standard Open Sales Orders	S/4HANA CUI	S/4HANA CUI	XXX	S/4HANA CUI
6	PF2	Standard Open Sales Orders	S/4HANA CUI	S/4HANA CUI	XXX	S/4HANA CUI
7	WP2	Direct Delivery Open Sales Orders	S/4HANA ROW	S/4HANA ROW	XXX	S/4HANA ROW	XXX
8	PF2	Direct Delivery Open Sales Orders	S/4HANA ROW	S/4HANA ROW	XXX	S/4HANA ROW	XXX
9	WP2	Direct Delivery Open Sales Orders	S/4HANA China	S/4HANA China	XXX	S/4HANA China	XXX
10	PF2	Direct Delivery Open Sales Orders	S/4HANA China	S/4HANA China	XXX	S/4HANA China	XXX
11	WP2	Direct Delivery Open Sales Orders	S/4HANA CUI	S/4HANA CUI	XXX	S/4HANA CUI
12	PF2	Direct Delivery Open Sales Orders	S/4HANA CUI	S/4HANA CUI	XXX	S/4HANA CUI
13	WP2	Direct Delivery Open Sales Orders	S/4HANA ROW	S/4HANA China	XXX	S/4HANA ROW - IC SO S/4HANA China - Customer SO
14	PF2	Direct Delivery Open Sales Orders	S/4HANA ROW	S/4HANA China	XXX	S/4HANA ROW - IC SO S/4HANA China - Customer SO
15	PF2	Direct Delivery Open Sales Orders	S/4HANA ROW	S/4HANA CUI	XXX	S/4HANA ROW - IC SO S/4HANA CUI - Customer SO
16	WP2	Direct Delivery Open Sales Orders	S/4HANA ROW	S/4HANA CUI	XXX	S/4HANA ROW - IC SO S/4HANA CUI - Customer SO
17	WP2	Direct Delivery Open Sales Orders	S/4HANA China	S/4HANA ROW	XXX	S/4HANA China - IC SO S/4HANA ROW - Customer SO
18	PF2	Direct Delivery Open Sales Orders	S/4HANA China	S/4HANA ROW	XXX	S/4HANA China - IC SO S/4HANA ROW - Customer SO
19	WP2	Direct Delivery Open Sales Orders	S/4HANA China	S/4HANA CUI	XXX	S/4HANA China - IC SO S/4HANA CUI - Customer SO
20	PF2	Direct Delivery Open Sales Orders	S/4HANA China	S/4HANA CUI	XXX	S/4HANA China - IC SO S/4HANA CUI - Customer SO
21	WP2 PF2	WP2 IC Purchase Order PF2 IC Sales Order	S/4HANA ROW	S/4HANA ROW	N/A	S/4HANA ROW - STO, Out of Scope	N/A
22	WP2 PF2	PF2 IC Purchase Order WP2 IC Sales Order	S/4HANA ROW	S/4HANA ROW	N/A	S/4HANA ROW - STO, Out of Scope	N/A
23	WP2 PF2	WP2 IC Purchase Order PF2 IC Sales Order	S/4HANA China	S/4HANA China	N/A	S/4HANA China - STO, Out of Scope	N/A
24	WP2 PF2	PF2 IC Purchase Order WP2 IC Sales Order	S/4HANA China	S/4HANA China	N/A	S/4HANA China - STO, Out of Scope	N/A
25	WP2 PF2	WP2 IC Purchase Order PF2 IC Sales Order	S/4HANA CUI	S/4HANA CUI	N/A	S/4HANA CUI - STO, Out of Scope	N/A
26	WP2 PF2	PF2 IC Purchase Order WP2 IC Sales Order	S/4HANACUI	S/4HANA CUI	N/A	S/4HANA CUI - STO, Out of Scope	N/A
27	WP2 PF2	WP2 IC Purchase Order PF2 IC Sales Order	S/4HANA ROW	S/4HANA China	XXX	S/4HANA ROW - IC SO
28	WP2 PF2	PF2 IC Purchase Order WP2 IC Sales Order	S/4HANA ROW	S/4HANA China	XXX	S/4HANA ROW - IC SO
29	WP2 PF2	WP2 IC Purchase Order PF2 IC Sales Order	S/4HANA ROW	S/4HANA CUI	XXX	S/4HANA ROW - IC SO
30	WP2 PF2	PF2 IC Purchase Order WP2 IC Sales Order	S/4HANA ROW	S/4HANA CUI	XXX	S/4HANA ROW - IC SO
31	WP2 PF2	WP2 IC Purchase Order PF2 IC Sales Order	S/4HANA China	S/4HANA ROW	XXX	S/4HANA China - IC SO
32	WP2 PF2	PF2 IC Purchase Order WP2 IC Sales Order	S/4HANA China	S/4HANA ROW	XXX	S/4HANA China - IC SO
33	WP2 PF2	WP2 IC Purchase Order PF2 IC Sales Order	S/4HANA China	S/4HANA CUI	XXX	S/4HANA China - IC SO
34	WP2 PF2	PF2 IC Purchase Order WP2 IC Sales Order	S/4HANA China	S/4HANA CUI	XXX	S/4HANA China - IC SO
35	WP2	WP2 STO	S/4HANA ROW	S/4HANA ROW	N/A	S/4HANA ROW - STO, Out of Scope	N/A
36	PF2	PF2 STO	S/4HANA ROW	S/4HANA ROW	N/A	S/4HANA ROW - STO, Out of Scope	N/A
37	WP2	WP2 STO	S/4HANA China	S/4HANA China	N/A	S/4HANA China - STO, Out of Scope	N/A
38	PF2	PF2 STO	S/4HANA China	S/4HANA China	N/A	S/4HANA China - STO, Out of Scope	N/A
39	WP2	WP2 STO	S/4HANA China	S/4HANA CUI	N/A	S/4HANA CUI - STO, Out of Scope	N/A
40	PF2	PF2 STO	S/4HANA China	S/4HANA CUI	N/A	S/4HANA CUI - STO, Out of Scope	N/A
41	WP2	WP2 STO	S/4HANA ROW	S/4HANA China	XXX	S/4HANA ROW - IC SO
42	PF2	PF2 STO	S/4HANA ROW	S/4HANA China	XXX	S/4HANA ROW - IC SO
43	WP2	WP2 STO	S/4HANA ROW	S/4HANA CUI	XXX	S/4HANA ROW - IC SO
44	PF2	PF2 STO	S/4HANA ROW	S/4HANA CUI	XXX	S/4HANA ROW - IC SO
45	WP2	WP2 STO	S/4HANA China	S/4HANA ROW	XXX	S/4HANA China - IC SO
46	PF2	PF2 STO	S/4HANA China	S/4HANA ROW	XXX	S/4HANA China - IC SO
47	WP2	WP2 STO	S/4HANA China	S/4HANA CUI	XXX	S/4HANA China - IC SO
48	PF2	PF2 STO	S/4HANA China	S/4HANA CUI	XXX	S/4HANA China - IC SO
49
50

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	Data Element	Field Description	Data Type	Length	Requirement
VBAK	VBELN	VBELN	Legacy Sales Document	Text	80	Mandatory
VBAK	AUART	AUART	Sales Document Type	Text	80	Mandatory
VBAK	VKORG	VKORG	Sales Organization	Text	80	Mandatory
VBAK	VTWEG	VTWEG	Distribution Channel	Text	80	Mandatory
VBAK	SPART	SPART	Division	Text	80	Mandatory
VBAK	VKBUR	VKBUR	Sales Office	Text	80
VBAK	VKGRP	VKGRP	Sales Group	Text	80
VBKD	BSTNK	BSTNK	Customer Purchase Order Number	Text	35
VBAK	VDATU	VDATU	Requested Delivery Date	Date		Mandatory
VBKD	BSTDK	BSTDK	Customer Purchase Order Date	Date
VBAK	FAKSK	FAKSK	Billing Block in SD Document	Text	80
VBAK	AUGRU	AUGRU	Order Reason	Text	80
VBKD	PRICE_DATE	PRICE_DATE	Pricing Date	Date
VBKD	EXCHG_RATE	EXCHG_RATE	Exchange Rate for Price Det.	Number	9
VBAK	AUDAT	AUDAT	Document Date	Date
VBAK	INCOV	INCOV	Incoterms Version	Text	80
VBAK	INCO1	INCO1	Incoterms (Part 1)	Text	80
VBAK	INCO2_L	INCO2_L	Incoterms Location 1	Text	70
VBAK	INCO2	INCO2	Incoterms (Part 2)	Text	28
VBAK	INCO3_L	INCO3_L	Incoterms Location 2	Text	70
VBAK	ZTERM	ZTERM	Terms of Payment Key	Text	80
VBKD	BILL_SCHED	BILL_SCHED	Invoicing Dates	Text	80
VBAK	WBS_ELEM	WBS_ELEM	WBS Element	Text	80
VBAK	NAME	NAME	Name	Text	35
VBAK	TELEPHONE	TELEPHONE	Telephone	Text	16
VBAK	KVGR1	KVGR1	Customer Group 1	Text	80
VBAK	KVGR2	KVGR2	Customer Group 2	Text	80
VBAK	KVGR3	KVGR3	Customer Group 3	Text	80
VBAK	KVGR4	KVGR4	Customer Group 4	Text	80
VBAK	KVGR5	KVGR5	Customer Group 5	Text	80
VBAK	NETWR	NETWR	Net value	Number	15
VBAK	WAERK	WAERK	Currency	Text	5
VBAK	BSTNK	BSTNK	Customer PO number	Text	20
VBAK	TAXK1	TAXK1	Alt.tax classific.	Text	1
VBAK	TAXK2	TAXK2	TaxClass2-Cust.	Text	1
VBAK	TAXK3	TAXK3	TaxClass3-Cust.	Text	1
VBAK	TAXK4	TAXK4	TaxClass4-Cust.	Text	1
VBAK	TAXK5	TAXK5	TaxClass5-Cust.	Text	1
VBAK	TAXK6	TAXK6	TaxClass6-Cust.	Text	1
VBAK	TAXK7	TAXK7	TaxClass7-Cust.	Text	1
VBAK	TAXK8	TAXK8	TaxClass8-Cust.	Text	1
VBAK	TAXK9	TAXK9	TaxClass9-Cust.	Text	1
VBAK	BSARK	BSARK	Purchase order type	Text	4
VBAK	BSTDK	BSTDK	Purchase Order Date	Date	8
VBAK	IHREZ	IHREZ	Your Reference	Text	12
VBAK	BNAME	BNAME	Name of the orderer	Text	35
VBAK	TELF1	TELF1	Telephone	Text	16
VBAK	KOSTL	KOSTL	Cost Center	Text	10
KONV	KNUMV	KNUMV	Switch for Condition Lines Handling	Text	1
VBAK	VBELN	VBELN	Legacy Sales Document	Text	80
KONV	KSCHL	KSCHL	Condition Type	Text	80
KONV	KBETR	KBETR	Amount	Number	31
KONV	WAERS	WAERS	Condition Unit (Currency or Percentage)	Text	80
KONV	KPEIN	KPEIN	Condition Pricing Unit	Number	5
KONV	KMEIN	KMEIN	Condition Unit of Measure	Text	80
VBAK	VBELN	VBELN	Legacy Sales Document	Text	80
STXH	TDID	TDID	Text ID	Text	80
STXH	TDSPRAS	TDSPRAS	Language Key	Text	80
STXH	TEXTLINE	TEXTLINE	Text	Text	unrestricted
VBAK	VBELN	VBELN	Legacy Sales Document	Text	80	Mandatory
VBAP	POSNR	POSNR	Sales Document Item	Number	6	Mandatory
VBAP	HG_LV_ITEM	HG_LV_ITEM	Higher-Level Item in Bill of Material	Number	6
VBAP	POSEX	POSEX	External Item Number	Text	6
VBAP	MATNR	MATNR	Product Number	Text	80	Mandatory
VBAP	ZIEME	ZIEME	Sales Unit	Text	80	Mandatory
VBAP	UMZIZ	UMZIZ	Numerator Conversion to Base Unit	Number	5
VBAP	UMZIN	UMZIN	Denominator Conversion to Base Unit	Number	5
VBAP	CHARG	CHARG	Batch Number	Text	10
VBAP	WERKS	WERKS	Plant	Text	80
VBAP	LGORT	LGORT	Storage Location	Text	80
VBAP	PSTYV	PSTYV	Sales Document Item Category	Text	80
VBAP	SHORT_TEXT	SHORT_TEXT	Item Description	Text	40
VBAK	INCOV	INCOV	Incoterms Version	Text	80
VBAK	INCO1	INCO1	Incoterms (Part 1)	Text	80
VBAK	INCO2_L	INCO2_L	Incoterms Location 1	Text	70
VBAK	INCO2	INCO2	Incoterms (Part 2)	Text	28
VBAK	INCO3_L	INCO3_L	Incoterms Location 2	Text	70
VBAK	ZTERM	ZTERM	Terms of Payment Key	Text	80
VBAK	KOKRS	KOKRS	Controlling Area	Text	80
VBAP	PROFIT_CTR	PROFIT_CTR	Profit Center	Text	80
VBAP	WBS_ELEM	WBS_ELEM	WBS Element	Text	80
VBAP	TAXM1	TAXM1	Tax classification	Text	1
VBAP	TAXM2	TAXM2	Tax classification	Text	1
VBAP	TAXM3	TAXM3	Tax classification	Text	1
VBAP	TAXM4	TAXM4	Tax classification	Text	1
VBAP	TAXM5	TAXM5	Tax classification	Text	1
VBAP	TAXM6	TAXM6	Tax classification	Text	1
VBAP	TAXM7	TAXM7	Tax classification	Text	1
VBAP	TAXM8	TAXM8	Tax classification	Text	1
VBAP	TAXM9	TAXM9	Tax classification	Text	1
VBAP	MWSBP	MWSBP	Tax amount	Number	13
VBAP	NETWR	NETWR	Net value	Number	15
VBAP	KOSTL	KOSTL	Cost Center	Text	10
VBAK	VBELN	VBELN	Legacy Sales Document	Text	80
VBAP	POSNR	POSNR	Sales Document Item	Number	6
KONV_ITEM	KSCHL	KSCHL	Condition Type	Text	80
KONV_ITEM	KBETR	KBETR	Amount	Number	31
KONV_ITEM	WAERS	WAERS	Condition Unit (Currency or Percentage)	Text	80
KONV_ITEM	KPEIN	KPEIN	Condition Pricing Unit	Number	5
KONV_ITEM	KMEIN	KMEIN	Condition Unit of Measure	Text	80
VBAK	VBELN	VBELN	Legacy Sales Document	Text	80
VBAP	POSNR	POSNR	Sales Document Item	Number	6
STXH	TDID	TDID	Text ID	Text	80
STXH	TDSPRAS	TDSPRAS	Language Key	Text	80
STXH	TEXTLINE	TEXTLINE	Text	Text	unrestricted
VBAK	VBELN	VBELN	Legacy Sales Document	Text	80
VBAP	POSNR	POSNR	Sales Document Item	Number	6
VBPA	PARVW	PARVW	Partner Function	Text	80
VBPA	KUNNR	KUNNR	Customer Number	Text	80
VBAP	EXTADDRNUMBER	EXTADDRNUMBER	External Address Number	Text	20
VBAP	STREET	STREET	Street and House Number	Text	35
VBAP	POSTL_CODE	POSTL_CODE	Postal Code	Text	10
VBAP	CITY	CITY	City	Text	35
VBAP	COUNTRY	COUNTRY	Country/Region	Text	80
VBAP	REGION	REGION	Region	Text	80
VBAP	TEL_NUMBER	TEL_NUMBER	Telephone Number	Text	16
VBAP	FAX_NUMBER	FAX_NUMBER	Fax Number	Text	31
VBAP	NAME1	NAME1	Name 1	Text	35
VBAK	VBELN	VBELN	Legacy Sales Document	Text	80	Mandatory
VBAP	POSNR	POSNR	Sales Document Item	Number	6	Mandatory
VBEP	ETENR	ETENR	Delivery Schedule Line Number	Number	4	Mandatory
VBEP	WMENG	WMENG	Order Quantity in Sales Units	Number	13	Mandatory
VBEP	ETDAT	ETDAT	Schedule Line Date/Delivery Date	Date

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Source System
9065-001	C-1	Sales order open for more than 3 years.	Orders created for more than 3 years ago.	PF2/WP2
9065-002	C-1	Missing sold-to data	If the sold-to is marked for deletion	PF2/WP2
9065-003	C-1	Missing ship-to data	If the ship-to is marked for deletion	PF2/WP2
9065-004	C-1	Missing bill-to data	If the bill-to is marked for deletion	PF2/WP2
9065-005	C-1	Missing payer data	If the payer-to is marked for deletion	PF2/WP2
9065-006	C-1	Missing material master	If the material master is marked for deletion	PF2/WP2
0065-007	C-3	Delivery note with planned PGI date beyond go-live date	If the DN PGI is beyond go-live date, delete the DN	PF2/WP2
0065-008	C-2	Invalid reference document	If the Credit Note, Debit Note and Return order was created with a reference document	PF2/WP2

Conversion Process

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

The ETL (Extract, Transform, Load) process is a structured approach to data migration and management, ensuring high-quality data is seamlessly transferred across systems. Here’s a breakdown of its key components:
1. Extraction
The process begins with extracting metadata and raw data from source systems, such as Syensqo ECC system (i.e., WP2/PF2) periodically. The extracted data is then staged for transformation.

2. Transformation
Once extracted, the data undergoes cleansing, consolidation, and governance. This step ensures data integrity, consistency, and compliance with business rules. The transformation process includes:
- Data validation to remove inconsistencies.
- Standardization to align formats across datasets.
- Business rule application to refine data for operational use.

3. Loading
The transformed data is then loaded into the target S4 Hana system.

Data Privacy and Sensitivity

N/A

Extraction

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

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.
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
Extraction Scope Definition	- Identify the source systems and databases involved. - Define the data objects (tables, fields, records) to be extracted. - Establish business rules for data selection.	Synithi
Extraction Methodology	- Specify the extraction approach (full, incremental, or delta extraction). - Determine the tools and technologies used. - Define data filtering criteria to exclude irrelevant records.	Synithi
Extraction Execution Plan	- Establish execution timelines and batch processing schedules. - Assign responsibilities for extraction monitoring. - Document dependencies on other migration tasks.	Synithi
Data Quality and Validation	- Define error handling mechanisms for extraction failures.	Synithi

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
SE16N	Standard Open Sales Order	To select: Standard or FOC Sales Order that is not fully billed	Scenario 1-20 under conversion scope	SELECT -- These are baseline fields only, extend according to needs vbak.vbeln AS sales_order, vbak.vbtyp AS doc_category, vbak.auart AS order_type, vbak.vkorg AS sales_org, vbap.posnr AS item_no, vbap.matnr AS material, vbap.arktx AS short_text, vbap.kwmeng AS order_qty, COALESCE(b.billed_qty, 0) AS billed_qty, -- (unbilled item) vbap.kwmeng - COALESCE(b.billed_qty, 0) AS open_by_billing_qty FROM vbak JOIN vbap ON vbak.vbeln = vbap.vbeln -- ensure item status indicates not completed (join VBUP) LEFT JOIN vbup ON vbup.vbeln = vbap.vbeln AND vbup.posnr = vbap.posnr -- sum billed quantity from billing items (VBRP) mapped to the order via AUBEL/AUPOS LEFT JOIN ( SELECT aubel AS order_vbeln, aupos AS order_posnr, SUM(fkimg) AS billed_qty FROM vbrp GROUP BY aubel, aupos ) b ON b.order_vbeln = vbap.vbeln AND b.order_posnr = vbap.posnr WHERE vbak.vbtyp = 'C' OR 'I" -- only sales orders and FOC orders(document category) -- not fully billed: AND (vbap.kwmeng - COALESCE(b.billed_qty,0)) > 0 AND vbup.absta <> 'C' - item is not rejected ORDER BY vbak.vbeln, vbap.posnr;
SE16N	IC Open Sales Order	To select: Standard or FOC Sales Order to affiliate that is not fully billed	Scenario 27-34 under conversion scope	SELECT -- These are baseline fields only, extend according to needs vbak.vbeln AS sales_order, vbak.vbtyp AS doc_category, vbak.auart AS order_type, vbak.vkorg AS sales_org, vbap.posnr AS item_no, vbap.matnr AS material, vbap.arktx AS short_text, vbap.kwmeng AS order_qty, COALESCE(b.billed_qty, 0) AS billed_qty, -- (unbilled item) vbap.kwmeng - COALESCE(b.billed_qty, 0) AS open_by_billing_qty FROM vbak JOIN vbap ON vbak.vbeln = vbap.vbeln -- ensure item status indicates not completed (join VBUP) LEFT JOIN vbup ON vbup.vbeln = vbap.vbeln AND vbup.posnr = vbap.posnr -- sum billed quantity from billing items (VBRP) mapped to the order via AUBEL/AUPOS LEFT JOIN ( SELECT aubel AS order_vbeln, aupos AS order_posnr, SUM(fkimg) AS billed_qty FROM vbrp GROUP BY aubel, aupos ) b ON b.order_vbeln = vbap.vbeln AND b.order_posnr = vbap.posnr WHERE vbak.vbtyp = 'C' OR 'I" -- only sales orders and FOC orders(document category) -- not fully billed: AND (vbap.kwmeng - COALESCE(b.billed_qty,0)) > 0 AND vbup.absta <> 'C' - item is not rejected AND it's IC sales XXXXXXXX to be updated with correct logic ORDER BY vbak.vbeln, vbap.posnr;
	IC Open Sales Order	To select: STO from legacy, converting to IC PO/SO scenario	Scenario 41-48 under conversion scope	Situation : Stock Transport Order in legacy will be converted to Purchase Order and Sales Order if the buying and selling entities are from different S4 Hana system To-be : Open STO quantity will be converted into a Purchase Order under buying entity The Purchase Order will be the base for the IC Sales order in the selling entity

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
1	Source System Availability Ensure that the source database or application is accessible. Confirm that necessary credentials and permissions are granted	Syensqo IT
2	Data Structure Identify relationships between tables, views, and stored procedures.	Synithi
3	Referential Integrity Ensure dependent records are extracted together.	Synithi
4	Extraction Methodology Define whether extraction is full, incremental, or delta-based. Establish batch processing schedules for large datasets.	Synithi
5	Performance and Scalability Considerations Optimize extraction queries to prevent system overload. Ensure network bandwidth supports data transfer volumes.	Synithi
6	Security and Compliance Adhere to regulatory standards for sensitive information if applicable	Synithi

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:

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
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
1	Transformation Scope Definition - Identify the source and target data structures. - Define business rules for data standardization. - Establish data cleansing requirements to remove inconsistencies.	Data Team
2	Data Mapping and Standardization - Align source fields with target fields. - Ensure unit consistency (e.g., currency, measurement units)	Data Team
3	Business Rule Application - Implement data enrichment/collection if applicable - Apply conditional transformations based on predefined logic/business rules	Data Team
4	Transformation Execution Plan - Define batch processing schedules. - Assign responsibilities for monitoring execution. - Establish error-handling mechanisms	Synithi

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic	Mapping Table
1	PF2/WP2	VBAK	VBELN	Legacy Sales Document	S4 HANA ROW/CUI/CHINA	VBAK	VBELN	Legacy Sales Document	1:1
2	PF2/WP2	VBAK	AUART	Sales Document Type	S4 HANA ROW/CUI/CHINA	VBAK	AUART	Sales Document Type	Mapping	MAP_AUART
3	PF2/WP2	VBAK	VKORG	Sales Organization	S4 HANA ROW/CUI/CHINA	VBAK	VKORG	Sales Organization	Mapping	MAP_VKORG
4	PF2/WP2	VBAK	VTWEG	Distribution Channel	S4 HANA ROW/CUI/CHINA	VBAK	VTWEG	Distribution Channel	Mapping	MAP_VTWEG
5	PF2/WP2	VBAK	SPART	Division	S4 HANA ROW/CUI/CHINA	VBAK	SPART	Division	Mapping	MAP_SPART
6	PF2/WP2	VBAK	VKBUR	Sales Office	S4 HANA ROW/CUI/CHINA	VBAK	VKBUR	Sales Office	Mapping	MAP_VKBUR
7	PF2/WP2	VBAK	VKGRP	Sales Group	S4 HANA ROW/CUI/CHINA	VBAK	VKGRP	Sales Group	Mapping	MAP_VKGRP
8	PF2/WP2	VBKD	BSTNK	Customer Purchase Order Number	S4 HANA ROW/CUI/CHINA	VBKD	BSTNK	Customer Purchase Order Number	1:1
9	PF2/WP2	VBAK	VDATU	Requested Delivery Date	S4 HANA ROW/CUI/CHINA	VBAK	VDATU	Requested Delivery Date	1:1
10	PF2/WP2	VBKD	BSTDK	Customer Purchase Order Date	S4 HANA ROW/CUI/CHINA	VBKD	BSTDK	Customer Purchase Order Date	1:1
11	PF2/WP2	VBAK	FAKSK	Billing Block in SD Document	S4 HANA ROW/CUI/CHINA	VBAK	FAKSK	Billing Block in SD Document	Mapping	MAP_FAKSK
12	PF2/WP2	VBAK	AUGRU	Order Reason	S4 HANA ROW/CUI/CHINA	VBAK	AUGRU	Order Reason	Mapping	MAP_AUGRU
13	PF2/WP2	VBKD	PRSDT	Pricing Date	S4 HANA ROW/CUI/CHINA	VBKD	PRICE_DATE	Pricing Date	1:1
14	PF2/WP2	VBKD	KURSK	Exchange Rate for Price Det.	S4 HANA ROW/CUI/CHINA	VBKD	EXCHG_RATE	Exchange Rate for Price Det.	1:1
15	PF2/WP2	VBAK	AUDAT	Document Date	S4 HANA ROW/CUI/CHINA	VBAK	AUDAT	Document Date	1:1
16	PF2/WP2	VBAK	INCOV	Incoterms Version	S4 HANA ROW/CUI/CHINA	VBAK	INCOV	Incoterms Version	1:1
17	PF2/WP2	VBAK	INCO1	Incoterms (Part 1)	S4 HANA ROW/CUI/CHINA	VBAK	INCO1	Incoterms (Part 1)	1:1
18	PF2/WP2	VBAK	INCO2_L	Incoterms Location 1	S4 HANA ROW/CUI/CHINA	VBAK	INCO2_L	Incoterms Location 1	1:1
19	PF2/WP2	VBAK	INCO2	Incoterms (Part 2)	S4 HANA ROW/CUI/CHINA	VBAK	INCO2	Incoterms (Part 2)	1:1
20	PF2/WP2	VBAK	INCO3_L	Incoterms Location 2	S4 HANA ROW/CUI/CHINA	VBAK	INCO3_L	Incoterms Location 2	1:1
21	PF2/WP2	VBAK	ZTERM	Terms of Payment Key	S4 HANA ROW/CUI/CHINA	VBAK	ZTERM	Terms of Payment Key	Mapping	MAP_ZTERM
22	PF2/WP2	VBKD	PERFK	Invoicing Dates	S4 HANA ROW/CUI/CHINA	VBKD	BILL_SCHED	Invoicing Dates	1:1
23	PF2/WP2	VBAK	PS_PSP_PNR	WBS Element	S4 HANA ROW/CUI/CHINA	VBAK	WBS_ELEM	WBS Element	Mapping	MAP_PS_PSP_PNR
24	PF2/WP2	VBAK	BNAME	Name	S4 HANA ROW/CUI/CHINA	VBAK	NAME	Name	1:1
25	PF2/WP2	VBAK	TELF1	Telephone	S4 HANA ROW/CUI/CHINA	VBAK	TELEPHONE	Telephone	1:1
26	PF2/WP2	VBAK	KVGR1	Customer Group 1	S4 HANA ROW/CUI/CHINA	VBAK	KVGR1	Customer Group 1	N/A
27	PF2/WP2	VBAK	KVGR2	Customer Group 2	S4 HANA ROW/CUI/CHINA	VBAK	KVGR2	Customer Group 2	N/A
28	PF2/WP2	VBAK	KVGR3	Customer Group 3	S4 HANA ROW/CUI/CHINA	VBAK	KVGR3	Customer Group 3	N/A
29	PF2/WP2	VBAK	KVGR4	Customer Group 4	S4 HANA ROW/CUI/CHINA	VBAK	KVGR4	Customer Group 4	N/A
30	PF2/WP2	VBAK	KVGR5	Customer Group 5	S4 HANA ROW/CUI/CHINA	VBAK	KVGR5	Customer Group 5	N/A
31	PF2/WP2	VBAK	NETWR	Net value	S4 HANA ROW/CUI/CHIN	VBAK	NETWR	Net value	1:1
32	PF2/WP2	VBAK	WAERK	Currency	S4 HANA ROW/CUI/CHIN	VBAK	WAERK	Currency	Mapping	MAP_WAERS
33	PF2/WP2	VBAK	BSTNK	Customer PO number	S4 HANA ROW/CUI/CHIN	VBAK	BSTNK	Customer PO number	1:1
34	PF2/WP2	VBAK	TAXK1	Alt.tax classific.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK1	Alt.tax classific.	1:1
35	PF2/WP2	VBAK	TAXK2	TaxClass2-Cust.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK2	TaxClass2-Cust.	1:1
36	PF2/WP2	VBAK	TAXK3	TaxClass3-Cust.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK3	TaxClass3-Cust.	1:1
37	PF2/WP2	VBAK	TAXK4	TaxClass4-Cust.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK4	TaxClass4-Cust.	1:1
38	PF2/WP2	VBAK	TAXK5	TaxClass5-Cust.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK5	TaxClass5-Cust.	1:1
39	PF2/WP2	VBAK	TAXK6	TaxClass6-Cust.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK6	TaxClass6-Cust.	1:1
40	PF2/WP2	VBAK	TAXK7	TaxClass7-Cust.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK7	TaxClass7-Cust.	1:1
41	PF2/WP2	VBAK	TAXK8	TaxClass8-Cust.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK8	TaxClass8-Cust.	1:1
42	PF2/WP2	VBAK	TAXK9	TaxClass9-Cust.	S4 HANA ROW/CUI/CHIN	VBAK	TAXK9	TaxClass9-Cust.	1:1
43	PF2/WP2	VBAK	BSARK	Purchase order type	S4 HANA ROW/CUI/CHIN	VBAK	BSARK	Purchase order type	1:1
44	PF2/WP2	VBAK	BSTDK	Purchase Order Date	S4 HANA ROW/CUI/CHIN	VBAK	BSTDK	Purchase Order Date	1:1
45	PF2/WP2	VBAK	IHREZ	Your Reference	S4 HANA ROW/CUI/CHIN	VBAK	IHREZ	Your Reference	1:1
46	PF2/WP2	VBAK	BNAME	Name of the orderer	S4 HANA ROW/CUI/CHIN	VBAK	BNAME	Name of the orderer	1:1
47	PF2/WP2	VBAK	TELF1	Telephone	S4 HANA ROW/CUI/CHIN	VBAK	TELF1	Telephone	1:1
48	PF2/WP2	VBAK	KOSTL	Cost Center	S4 HANA ROW/CUI/CHIN	VBAK	KOSTL	Cost Center	Mapping	MAP_KOSTL
49	PF2/WP2	KONV	KNUMV	Switch for Condition Lines Handling	S4 HANA ROW/CUI/CHINA	KONV	KNUMV	Switch for Condition Lines Handling	N/A
50	PF2/WP2	VBAK	VBELN	Legacy Sales Document	S4 HANA ROW/CUI/CHINA	VBAK	VBELN	Legacy Sales Document	1:1
51	PF2/WP2	KONV	KSCHL	Condition Type	S4 HANA ROW/CUI/CHINA	KONV	KSCHL	Condition Type	N/A
52	PF2/WP2	KONV	KBETR	Amount	S4 HANA ROW/CUI/CHINA	KONV	KBETR	Amount	N/A
53	PF2/WP2	KONV	WAERS	Condition Unit (Currency or Percentage)	S4 HANA ROW/CUI/CHINA	KONV	WAERS	Condition Unit (Currency or Percentage)	N/A
54	PF2/WP2	KONV	KPEIN	Condition Pricing Unit	S4 HANA ROW/CUI/CHINA	KONV	KPEIN	Condition Pricing Unit	N/A
55	PF2/WP2	KONV	KMEIN	Condition Unit of Measure	S4 HANA ROW/CUI/CHINA	KONV	KMEIN	Condition Unit of Measure	N/A
56	PF2/WP2	VBAK	VBELN	Legacy Sales Document	S4 HANA ROW/CUI/CHINA	VBAK	VBELN	Legacy Sales Document	1:1
57	PF2/WP2	STXH	TDID	Text ID	S4 HANA ROW/CUI/CHINA	STXH	TDID	Text ID	Mapping	MAP_TDID
58	PF2/WP2	STXH	TDSPRAS	Language Key	S4 HANA ROW/CUI/CHINA	STXH	TDSPRAS	Language Key	1:1
59	PF2/WP2	STXH	TEXTLINE	Text	S4 HANA ROW/CUI/CHINA	STXH	TEXTLINE	Text	1:1
60	PF2/WP2	VBAK	VBELN	Legacy Sales Document	S4 HANA ROW/CUI/CHINA	VBAK	VBELN	Legacy Sales Document	1:1
61	PF2/WP2	VBAP	POSNR	Sales Document Item	S4 HANA ROW/CUI/CHINA	VBAP	POSNR	Sales Document Item	1:1
62	PF2/WP2	VBAP	UEPOS	Higher-Level Item in Bill of Material	S4 HANA ROW/CUI/CHINA	VBAP	HG_LV_ITEM	Higher-Level Item in Bill of Material	1:1
63	PF2/WP2	VBAP	POSEX	External Item Number	S4 HANA ROW/CUI/CHINA	VBAP	POSEX	External Item Number	N/A
64	PF2/WP2	VBAP	MATNR	Product Number	S4 HANA ROW/CUI/CHINA	VBAP	MATNR	Product Number	Mapping	XREF_MATNR
65	PF2/WP2	VBAP	ZIEME	Sales Unit	S4 HANA ROW/CUI/CHINA	VBAP	ZIEME	Sales Unit	Mapping	MAP_MEINS
66	PF2/WP2	VBAP	UMZIZ	Numerator Conversion to Base Unit	S4 HANA ROW/CUI/CHINA	VBAP	UMZIZ	Numerator Conversion to Base Unit	N/A
67	PF2/WP2	VBAP	UMZIN	Denominator Conversion to Base Unit	S4 HANA ROW/CUI/CHINA	VBAP	UMZIN	Denominator Conversion to Base Unit	N/A
68	PF2/WP2	VBAP	CHARG	Batch Number	S4 HANA ROW/CUI/CHINA	VBAP	CHARG	Batch Number	1:1
69	PF2/WP2	VBAP	WERKS	Plant	S4 HANA ROW/CUI/CHINA	VBAP	WERKS	Plant	Mapping	MAP_WERKS
70	PF2/WP2	VBAP	LGORT	Storage Location	S4 HANA ROW/CUI/CHINA	VBAP	LGORT	Storage Location	Mapping	MAP_LGORT
71	PF2/WP2	VBAP	PSTYV	Sales Document Item Category	S4 HANA ROW/CUI/CHINA	VBAP	PSTYV	Sales Document Item Category	Mapping	MAP_PSTYV
72	PF2/WP2	VBAP	ARKTX	Item Description	S4 HANA ROW/CUI/CHINA	VBAP	SHORT_TEXT	Item Description	1:1
73	PF2/WP2	VBAK	INCOV	Incoterms Version	S4 HANA ROW/CUI/CHINA	VBAK	INCOV	Incoterms Version	1:1
74	PF2/WP2	VBAK	INCO1	Incoterms (Part 1)	S4 HANA ROW/CUI/CHINA	VBAK	INCO1	Incoterms (Part 1)	1:1
75	PF2/WP2	VBAK	INCO2_L	Incoterms Location 1	S4 HANA ROW/CUI/CHINA	VBAK	INCO2_L	Incoterms Location 1	1:1
76	PF2/WP2	VBAK	INCO2	Incoterms (Part 2)	S4 HANA ROW/CUI/CHINA	VBAK	INCO2	Incoterms (Part 2)	1:1
77	PF2/WP2	VBAK	INCO3_L	Incoterms Location 2	S4 HANA ROW/CUI/CHINA	VBAK	INCO3_L	Incoterms Location 2	1:1
78	PF2/WP2	VBAK	ZTERM	Terms of Payment Key	S4 HANA ROW/CUI/CHINA	VBAK	ZTERM	Terms of Payment Key	Mapping	MAP_ZTERM
79	PF2/WP2	VBAK	KOKRS	Controlling Area	S4 HANA ROW/CUI/CHINA	VBAK	KOKRS	Controlling Area	N/A
80	PF2/WP2	VBAP	PRCTR	Profit Center	S4 HANA ROW/CUI/CHINA	VBAP	PROFIT_CTR	Profit Center	N/A
81	PF2/WP2	VBAP	PS_PSP_PNR	WBS Element	S4 HANA ROW/CUI/CHINA	VBAP	WBS_ELEM	WBS Element	Mapping	MAP_PS_PSP_PNR
82	PF2/WP2	VBAP	TAXM1	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM1	Tax classification	1:1
83	PF2/WP2	VBAP	TAXM2	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM2	Tax classification	1:1
84	PF2/WP2	VBAP	TAXM3	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM3	Tax classification	1:1
85	PF2/WP2	VBAP	TAXM4	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM4	Tax classification	1:1
86	PF2/WP2	VBAP	TAXM5	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM5	Tax classification	1:1
87	PF2/WP2	VBAP	TAXM6	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM6	Tax classification	1:1
88	PF2/WP2	VBAP	TAXM7	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM7	Tax classification	1:1
89	PF2/WP2	VBAP	TAXM8	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM8	Tax classification	1:1
90	PF2/WP2	VBAP	TAXM9	Tax classification	S4 HANA ROW/CUI/CHIN	VBAP	TAXM9	Tax classification	1:1
91	PF2/WP2	VBAP	MWSBP	Tax amount	S4 HANA ROW/CUI/CHIN	VBAP	MWSBP	Tax amount	1:1
92	PF2/WP2	VBAP	NETWR	Net value	S4 HANA ROW/CUI/CHIN	VBAP	NETWR	Net value	1:1
93	PF2/WP2	VBAP	KOSTL	Cost Center	S4 HANA ROW/CUI/CHIN	VBAP	KOSTL	Cost Center	Mapping	MAP_KOSTL
94	PF2/WP2	VBAK	VBELN	Legacy Sales Document	S4 HANA ROW/CUI/CHINA	VBAK	VBELN	Legacy Sales Document	1:1
95	PF2/WP2	VBAP	POSNR	Sales Document Item	S4 HANA ROW/CUI/CHINA	VBAP	POSNR	Sales Document Item	1:1
96	PF2/WP2	KONV_ITEM	KSCHL	Condition Type	S4 HANA ROW/CUI/CHINA	KONV_ITEM	KSCHL	Condition Type	N/A
97	PF2/WP2	KONV_ITEM	KBETR	Amount	S4 HANA ROW/CUI/CHINA	KONV_ITEM	KBETR	Amount	N/A
98	PF2/WP2	KONV_ITEM	WAERS	Condition Unit (Currency or Percentage)	S4 HANA ROW/CUI/CHINA	KONV_ITEM	WAERS	Condition Unit (Currency or Percentage)	N/A
99	PF2/WP2	KONV_ITEM	KPEIN	Condition Pricing Unit	S4 HANA ROW/CUI/CHINA	KONV_ITEM	KPEIN	Condition Pricing Unit	N/A
100	PF2/WP2	KONV_ITEM	KMEIN	Condition Unit of Measure	S4 HANA ROW/CUI/CHINA	KONV_ITEM	KMEIN	Condition Unit of Measure	N/A
101	PF2/WP2	VBAK	VBELN	Legacy Sales Document	S4 HANA ROW/CUI/CHINA	VBAK	VBELN	Legacy Sales Document	1:1
102	PF2/WP2	VBAP	POSNR	Sales Document Item	S4 HANA ROW/CUI/CHINA	VBAP	POSNR	Sales Document Item	1:1
103	PF2/WP2	STXH	TDID	Text ID	S4 HANA ROW/CUI/CHINA	STXH	TDID	Text ID	Mapping	MAP_TDID
104	PF2/WP2	STXH	TDSPRAS	Language Key	S4 HANA ROW/CUI/CHINA	STXH	TDSPRAS	Language Key	1:1
105	PF2/WP2	STXH	TEXTLINE	Text	S4 HANA ROW/CUI/CHINA	STXH	TEXTLINE	Text	1:1
106	PF2/WP2	VBAK	VBELN	Legacy Sales Document	S4 HANA ROW/CUI/CHINA	VBAK	VBELN	Legacy Sales Document	1:1
107	PF2/WP2	VBAP	POSNR	Sales Document Item	S4 HANA ROW/CUI/CHINA	VBAP	POSNR	Sales Document Item	1:1
108	PF2/WP2	VBPA	PARVW	Partner Function	S4 HANA ROW/CUI/CHINA	VBPA	PARVW	Partner Function	Mapping	MAP_PARVW
109	PF2/WP2	VBPA	KUNNR	Customer Number	S4 HANA ROW/CUI/CHINA	VBPA	KUNNR	Customer Number	Mapping	XREF_KUNNR
110	PF2/WP2	VBAP	EXTADDRNUMBER	External Address Number	S4 HANA ROW/CUI/CHINA	VBAP	EXTADDRNUMBER	External Address Number	N/A
111	PF2/WP2	VBAP	STREET	Street and House Number	S4 HANA ROW/CUI/CHINA	VBAP	STREET	Street and House Number	N/A
112	PF2/WP2	VBAP	POSTL_CODE	Postal Code	S4 HANA ROW/CUI/CHINA	VBAP	POSTL_CODE	Postal Code	N/A
113	PF2/WP2	VBAP	CITY	City	S4 HANA ROW/CUI/CHINA	VBAP	CITY	City	N/A
114	PF2/WP2	VBAP	COUNTRY	Country/Region	S4 HANA ROW/CUI/CHINA	VBAP	COUNTRY	Country/Region	N/A
115	PF2/WP2	VBAP	REGION	Region	S4 HANA ROW/CUI/CHINA	VBAP	REGION	Region	N/A
116	PF2/WP2	VBAP	TEL_NUMBER	Telephone Number	S4 HANA ROW/CUI/CHINA	VBAP	TEL_NUMBER	Telephone Number	N/A
117	PF2/WP2	VBAP	FAX_NUMBER	Fax Number	S4 HANA ROW/CUI/CHINA	VBAP	FAX_NUMBER	Fax Number	N/A
118	PF2/WP2	VBAP	NAME1	Name 1	S4 HANA ROW/CUI/CHINA	VBAP	NAME1	Name 1	N/A
119	PF2/WP2	VBAK	VBELN	Legacy Sales Document	S4 HANA ROW/CUI/CHINA	VBAK	VBELN	Legacy Sales Document	1:1
120	PF2/WP2	VBAP	POSNR	Sales Document Item	S4 HANA ROW/CUI/CHINA	VBAP	POSNR	Sales Document Item	1:1
121	PF2/WP2	VBEP	ETENR	Delivery Schedule Line Number	S4 HANA ROW/CUI/CHINA	VBEP	ETENR	Delivery Schedule Line Number	1:1
122	PF2/WP2	VBEP	WMENG	Order Quantity in Sales Units	S4 HANA ROW/CUI/CHINA	VBEP	WMENG	Order Quantity in Sales Units	1:1
123	PF2/WP2	VBEP	EDATU	Schedule Line Date/Delivery Date	S4 HANA ROW/CUI/CHINA	VBEP	ETDAT	Schedule Line Date/Delivery Date	1:1

Transformation Mapping

Mapping Table Name	Mapping Table Description
MAP_AUART	Sales Order Type
MAP_VKORG	Sales Organization Mapping
MAP_VTWEG	Distribution Channel Mapping
MAP_SPART	Division Mapping
MAP_VKBUR	Sales Office Mapping
MAP_VKGRP	Sales Group Mapping to new partner fucntion
MAP_FAKSK	Billing Block in SD Document
MAP_AUGRU	Order Reason
MAP_ZTERM	Payment term Mapping
MAP_PS_PSP_PNR	WBS Element
MAP_TDID	Text ID Mapping
MAP_MEINS	Unit of Measure Mapping
MAP_WERKS	Plant Mapping
MAP_LGORT	Storage Location
MAP_PSTYV	Sales Document Item Category
MAP_PARVW	Partner function Mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Source Data Integrity - Ensure extracted data is complete, accurate, and consistent. - Validate that data types and formats align with transformation requirements.	Synithi
2	Referential Integrity - Ensure dependent records are transformed together or in advance	Synithi
3	Transformation Logic and Mapping - Define data mapping rules between source and target schemas.	Data Team
4	Performance and Scalability Considerations - Optimize transformation processes for large datasets. - Ensure system resources can handle transformation workloads	Synithi
5	Logging and Error Handling - Maintain detailed logs of transformation activities. - Define error-handling procedures for failed transformations	Synithi

Pre-Load Validation

Project Team

Completeness

Task

Action

Validate mandatory and key fields

Mandatory field check.
Based on S/4HANA target design fields, sales order type configuration, item category determination and schedule line category.

Check if records have all mandatory fields filled and mapped (e.g. Sales Document Type, Sales Organization, Distribution Channel, Division, Sold-to Party, Ship-to Party, Material, Quantity, Requested Delivery Date, Pricing Conditions, etc.).
Records missing any mandatory fields must be flagged as error.

Check Business Partners Master Data

Verify that Sold-to Party, Ship-to Party, Bill-to Party, and Payer exist as Business Partners in S/4HANA (tables: BUT000, KNA1, KNVV).
Ensure the BP is extended to the required Sales Organization, Distribution Channel, and Division.
Check BP deletion flags: KNVV-LOEVM (Deletion flag for sales area data) must not be set.

Check Material Master Data

Confirm that Material Numbers exist in S/4HANA Material Master (MARA, MVKE and MARC).
Validate that materials are extended to relevant Sales Org and Distribution Channel.
Check that the material is not flagged for deletion (MARA-LVORM must not be set).

Check Sales Order Item Consistency

Validate item category and schedule line category are mapped accordingly
Ensure quantity fields are populated and non-zero.
Check schedule lines have valid requested delivery dates.

Check Currency and Pricing Data

Validate pricing conditions are correctly mapped and exist in condition master data.
Check currency fields: Sales Order currency and pricing currency must be populated and valid (against TCURC / currency customizing).
Ensure that net values and tax amounts are correctly calculated and populated.

Reconciliation check

Record Count

Check that the total number of open sales order records in the load file matches the source system.
The record count will be reconciled on a group basis. The grouping fields are:
- Sales Organization
- Sales Document Type
- Sold-to Party
- Sales Document Number
Any mismatch in record count between source and load file must be flagged for investigation.

Check Amount in Document Currency and Local Currency

Sum the total Net Value (Document Currency) for Sales Orders in the load file and compare with the total from the source system.
Sum the Tax (Document Currency) for Sales Orders in the load file and compare with the total from the source system.
Any difference in sum between source and load file must be flagged as an error.

Check Total Quantity

Sum the ordered quantity matching with open quantities in the source system.
If there is a UOM changes, the quantity must be converted with the correct conversion rate.
Compare aggregated quantities per Material and Sales Organization to ensure data consistency.
Any mismatches must be flagged for investigation.

Accuracy

Task	Action
Validate the transformation	Make sure all fields with transformation are populated with S/4 HANA values according to the mapping file.
Check Data Consistency	Sold-to Party Verify that the Sold-to Party (Customer Number) in the pre-load file matches the corresponding value in the legacy system. Validate customer master mapping if applicable. Ship-to Party Verify that the Ship-to Party in the pre-load file matches the corresponding value in the legacy system. Validate partner function assignments if applicable. Customer PO Date Verify that the Customer Purchase Order Date (VBAK-BSTDK) matches between legacy system and pre-load file. Pricing Validate that key pricing condition values (e.g. base price, discounts, surcharges) are consistent between legacy system and pre-load file. Compare condition type values (e.g. KONV-KBETR) where feasible. Number of Line Items Verify that the total number of open line items per sales order matches between legacy system and pre-load file. Open Quantities Validate that open quantities (Ordered Quantity minus Delivered Quantity) match between legacy system and pre-load file.

Business

Completeness

Task

Action

Conversion check

In legacy system, execute report Open Sales Orders List (e.g. via transaction code VA05 or equivalent custom report).

Group the output of the report by Sales Organization and Sold-to Party using the subtotal function and compare the count in this report against the Open Sales Orders count in the pre-load file.

The record count for Open Sales Orders may also be done at a more granular level. The recommended granular level or subtotal fields can consist of:

Sales Organization
Sales Document Type
Sold-to Party
Material Number

If any of the count is different, raise a defect and flag the relevant record as error.

Accuracy

Task

Action

Key fields check

Perform the following checks on a selected sample of open sales orders:

Total Net Value Check
- Compare the total Net Value (VBAK-NETWR) per Sales Organization and Sold-to Party between legacy system and pre-load file.
Total Tax Amount Check
- Compare the total Tax Amount (if applicable, e.g. from pricing conditions or summarized tax amount) between legacy system and pre-load file.
Material Number and Open Quantity Check
- For each Sales Order Item (VBAP):
  - Verify that Material Numbers match between legacy system and pre-load file.
  - Verify that Open Quantities (Ordered Quantity minus Delivered Quantity) are accurate.

Validate the transformation

Make sure all fields with transformation are populated with S/4 HANA values according to the mapping file.

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
1	Load Scope Definition - Identify the target system and database structure. - Define data objects (tables, fields, records) to be loaded. - Establish business rules for data validation.	Data team
2	Load Methodology - Specify the loading tools and technologies (Migration Cockpit, LSMW, custom loading program).	Synithi
3	Data Quality and Validation - Ensure data integrity checks (null values, duplicates, format validation). - Perform pre-load validations to verify completeness. - Define error handling mechanisms for load failures	Synithi
4	Load Execution Plan - Establish execution timelines and batch processing schedules. - Assign responsibilities for monitoring execution. - Document dependencies on other migration tasks	Synithi
5	Logging and Reporting - Maintain detailed logs of loading activities. - Generate summary reports on loaded data volume and quality. - Define escalation procedures for errors	Synithi

Load Phase and Dependencies

Open Sales Orders will be loaded in the pre-cutover or cutover phase, depending on business cut-off.

Configuration

Item #	Configuration Item
1	Order type
2	Item categories
3	Schedule lines categories
4	Pricing procedure
5	Number range settings for orders

Conversion Objects

Object #	Preceding Object Conversion Approach
1046	Classes Type: 023 ( Batch)
1047	Batch Characteristics of Class Type: 023
1048	Batch Master
1058	Batch Classification Data
1051	TM - Locations
1052	TM - Transportation Zones
1042	TM - Transportation Lanes
1053	TM - Default Routes
1062	Batch Search Strategy
1034	Sales Pricing Conditions
2001	Material Listing and Exclusions
2002	Material Substitution
1036	Customer Material Information Records(CMIR)
1135	Z tables (variant table)
1134	Output determination for application V1/V3
3007	Business Partners - General (Role 000000)
3017	Business Partners - FI Customer (FLCU00)
3019	Business Partners - Credit Management (UKM000)
3022	Business Partners - Collection Management (UDM000)
3039	Business Partners - GTS Master
3003	Business Partners - Customer (Sales and Service) - FLCU01
3010	Business Partners - Relationship for contact person
3011	Business Partners - Contact Persons (BUP001)
3027	Business Partners - Plants/Intercompany Suppliers
2019	Materials - Basic View
2012	Materials - Accounting 1
2014	Materials - Accounting 2
2013	Materials - Costing 1
2015	Materials - Costing 2
2005	Materials - MRP view (4 views)
2027	Materials - Foreign Trade Views
2011	Materials - WM Execution ( EWM )
2003	Materials - Sales view with sales long text
3040	Business Partners - Treasury

Error Handling

Error Type	Error Description	Action Taken
Configuration / Data Transformation	The value XXX for field XXX doesn't exist	Check the mapping/conversion is done properly in the loading file Validate the target value is configured/transported in the target system Reach out to function team to validate the configuration
Configuration	There is mandatory field XXX missing	Validate MDS if the fields are set as mandatory Validate if there is value in the pre-loading file Validate if the configuration for the mandatory fields are done properly

Post-Load Validation

Project Team

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

Completeness

Task

Action

Validate Record count

Total number of records loaded for Open Sales Orders will be generated in the post-load reports in the tool based on the target tables and fields mentioned in section target design.

The reconciliation needs to be executed on the total number of 'valid' records and amounts per Sales Organization in the source compared to total number of records and amounts in S/4HANA.

Record Count

Check that the total record count of Open Sales Orders in the pre-load file matches the number of records loaded into S/4HANA.
The record count will be validated on a group basis. The recommended grouping fields are:
- Sales Organization
- Sold-to Party
- Sales Document Type
Any mismatch in record count between pre-load file and S/4HANA must be flagged for investigation.

Check Amount in Document Currency and Local Currency

At the line item level, sum the Net Value amounts in both Document Currency and Local Currency from the pre-load file and compare to the values posted in S/4HANA.
Any mismatches in totals must be flagged as errors for investigation.

Accuracy

Task

Action

Validate Key Fields

Post-load reports will have the same structure as the Open Sales Order load file, with additional columns as required to support post-load validation.
Utilize the migration tool to generate a Post-Load Report that displays S/4HANA loaded records alongside the corresponding legacy system values. This side-by-side comparison will enable a 100% field-level validation of all key fields in the shortest possible time.
Key fields for comparison include (but are not limited to):
1. Sales Document Number
2. Sales Document Type
3. Sales Organization
4. Sold-to Party
5. Ship-to Party
6. Customer PO Number and PO Date
7. Material Number
8. Ordered Quantity and Open Quantity
9. Pricing values (Net Value, Tax, Conditions)
10. Document Currency and Local Currency amounts
Any mismatches identified will be captured in the Post Load - Error Report for further investigation and resolution.

Business

Post-load validation is a critical step in data migration, ensuring that transferred data is accurate, complete, and functional within the target system.

1. Ensuring Data Integrity
After migration, data must be consistent with its original structure. Post-load validation checks for missing records, incorrect mappings, and formatting errors to prevent discrepancies.
2. Business Continuity
Faulty data can disrupt operations, leading to financial losses and inefficiencies. Validating post-load data ensures that applications function as expected, preventing downtime.
3. Error Detection and Resolution
By validating data post-migration, businesses can detect anomalies early, reducing the cost and effort required for corrections

Completeness

Task	Action

Accuracy

Task	Action
Display Records	Pick up few random sales document number numbers, display with Tcode VA03 and validate the details

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	Comment
CURRENT (v. 16)	Apr 20, 2026 06:39	LEW-ext, Chun Ming	Update VTWEG logic to derive from Sales Org country
v. 83	Apr 14, 2026 12:45	LEW-ext, Chun Ming	Update report 9065-010 to not applicable
v. 82	Apr 02, 2026 17:33	LEW-ext, Chun Ming
v. 81	Apr 02, 2026 16:36	LEW-ext, Chun Ming	Update EQART to not used
v. 80	Apr 01, 2026 19:04	LEW-ext, Chun Ming	fine tune rule 215
v. 79	Apr 01, 2026 18:01	LEW-ext, Chun Ming	Fine tune rule 88
v. 78	Mar 30, 2026 08:06	LEW-ext, Chun Ming	Update transformation rule 88 to consider VBRK-VBTYP
v. 77	Mar 06, 2026 08:36	LEW-ext, Chun Ming	Added M2 order type in exclusion criteria
v. 76	Feb 23, 2026 14:02	LEW-ext, Chun Ming	Correction after approved
v. 75	Feb 23, 2026 13:58	LEW-ext, Chun Ming

Go to Page History

Workflow history

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

Apr 20, 2026	Actor	Type	Activity	Version
Revision in Progress	LEW-ext, Chun Ming	Edit	updated the page at 6:39 am Update VTWEG logic to derive from Sales Org country
Apr 14, 2026
	LEW-ext, Chun Ming	State	changed state to Revision in Progress at 12:45 pm	v83
From Apr 02, 2026 to Apr 14, 2026
Approved	LEW-ext, Chun Ming	Edit	updated the page at 4:36 pm
	TAMRAKAR-ext, Pooja	State	changed state to Approved at 4:19 pm	v82
Revision under Review	TAMRAKAR-ext, Pooja	State	gave Minor change approval at 4:19 pm

Workflow history

Space shortcuts

Page tree

CNV-9065 Open Sales Order

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

Workflow history