Status
Owner	Prasad Naidu
Stakeholders	NG-ext, Bernard PILLAY-ext, Lawrence GARCIA-ext, Angel Luis SHARMA-ext, Swati KUMAR-ext, Kamal

Purpose

The purpose of this document is to define the conversion approach to migrate AR open items from Legacy systems to S/4 HANA.

AR open items refer to customer invoices, credit memos, or other receivables that have not yet been cleared (i.e., not paid or settled). These are key transactional data required for financial continuity post-go-live.

AR special GL open items are covered under CNV-9009

Conversion Scope

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

Amounts in legacy involve document currency and local currency . All currencies will be loaded accordingly unless there is a change in company design where local / group currency changes. 

For each customer open item, We must have:

• A customer line item (in BSID)
• An offsetting GL account line item (so that the document balances in FI).
• For every open item migrated, we debit the customer account and post the opposite entry to a temporary clearing account (a GL account created for migration).
• Later, once all AR open items are loaded, we clear the migration clearing account with a single offsetting entry to reconcile balances. 

Relevancy Criteria:

1. All AR Open items with posting dates on or before Migration cutoff date(BUDAT <=Cutover Date)
2. One time customers are out of scope
3. Open Customer Invoices with special GL Indicator are out of scope. These are covered in CNV-9009 
4. AR Open items clearing with future date is not applicable

Read all the records from table BSIS for the company codes as listed in the source column of the mapping file of company codes .  ( Source company codes can be referred to   where check the worksheet 10. Company Code with filter on column "In Scope as S/4 Company Code?" as in "In-Scope")  

As the month-end closing can take some time and therefore, data extraction takes few more days well into the next month, it is important to select right data for each mock cycle for migrating true month-end AR Open items. 

As example, For MC1, MC2 and MC3, the conversion Cut-Over date will be prior to extraction date.  e.g. If conversion date is March 31^st 2026, then the extraction date may take place several days later. Between conversion date and extraction date the open items may have been cleared or new AR Open items can appear. 

Therefore, 

• Select documents from BSID where document posting date is less than or equal to Mock cycle conversion Cut-Over date.
• Select documents from BSAD where the clearing date is greater than the  conversion Cut-Over date and the document posting date is less than or equal to the  conversion Cut-Over date.

This should not be applicable for Production Cut-Over since there will be a data freeze between the conversion date and extraction date. so, for production cut-over, there is no need to extract data from BSAD and only BSID is sufficient.

Example for MC1, MC2, MC3:

BSID.BUDAT <= ‘ conversion Cut-Over date’

BSAD.BUDAT <= ‘ conversion Cut-Over date’ and BSAD.AUGDT > ‘ conversion Cut-Over date’.

Example for Production Cut-Over:

BSIS.BUDAT <= ‘Production Cut-Over Date’

List of source systems and approximate number of records 

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	AR open item	4200	S4	4200
WP2	AR open item	24000	S4	24000
PI2	AR open item

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	Data Element	Field Description	Data Type	Length	Requirement
BKPF	BELNR	BELNR_D	Document Number	CHAR	10	Required
BKPF	BLDAT	BLDAT	Document Date in Document	DATS	8	Required
BKPF	BUDAT	BUDAT	Posting Date in the Document	DATS	8	Required
BKPF	BLART	BLART	Document Type	CHAR	2	Required
BKPF	BUKRS	BUKRS	Company Code	CHAR	4	Required
BKPF	MONAT	MONAT	Fiscal Period	NUMC	2	Optional
BKPF	WAERS	WAERS	Currency Key - Document Currency	CUKY	5	Required
BKPF	HWAER	HWAER	Local Currency/ Co Code currency (T001)	CUKY	5	Required
BKPF	XBLNR	XBLNR1	Reference Document Number	CHAR	16	Optional
BKPF	BKTXT	BKTXT	Document Header Text	CHAR	25	Optional
BKPF	GJAHR	GJAHR	Year	NUMC	4	Required
BSID	KUNNR	KUNNR	Business Partner Number	CHAR	10	Required
BSID	HKONT	HKONT	General Ledger Account Number (Reconciliation Account)	CHAR	10	Required
BSID	GKONT	GKONT	Account Number of Offsetting Account	CHAR	10	Optional
BSID	SGTXT	SGTXT	Item Text	CHAR	50	Optional
BSID	WRBTR	WRBTR	Document Currency Amount	CURR	13	Required
BSID	DOCLN	DOCLN	Line Item Number in Accounting Document	NUMC	3	Required
BSID	DMBTR	DMBTR	Local Currency Amount	CURR	13	Required
BSID	ZTERM	ZTERM	Payment Terms	CHAR	4	Optional
BSID	ZFBDT	ZFBDT	Baseline Date	DATS	8	Required
BSID	ZLSCH	ZLSCH	Payment Method	CHAR	1	Optional
BSID	ZLSPR	ZLSPR	Payment Block	CHAR	1	Optional
BSID	MSCHL	MSCHL	Dunning Key	CHAR	1	Optional
BSID	KIDNO	KIDNO	Payment Reference	CHAR	12	Optional
BSID	ZBD1T	ZBD1T	Cash Discount Days 1	DEC	3	Optional
BSID	ZBD1P	ZBD1P	Cash Discount Percentage 1	DEC	3	Optional
BSID	ZBD2T	ZBD2T	Cash Discount Days 2	DEC	3	Optional
BSID	ZBD2P	ZBD2P	Cash Discount Percentage 2	DEC	3	Optional
BSID	ZBD3T	ZBD3T	Net Due Days	DEC	3	Optional
BSID	SKFBT	SKFBT	Amount Eligible for Cash Disc. (Document Curr.)	CURR	13	Optional
BSID	BVTYP	BVTYP	Partner Bank Type	CHAR	1	Optional
BSID	KKBER	KKBER	Credit Control Area	CHAR	4	Optional
BSID	RSTGR	RSTGR	Reason Code for Payments	CHAR	3	Optional
BSID	FILKD	FILKD	Account Number of the Branch	CHAR	5	Optional
BSID	LZBKZ	LZBKZ	State Central Bank Indicator	CHAR	2	Optional
BSID	LANDL	LANDL	Supplying Country	CHAR	3	Optional
BSID	XREF1	XREF1	Reference Key 1	CHAR	12	Optional
BSID	XREF2	XREF2	Reference Key 2	CHAR	12	Optional
BSID	XREF3	XREF3	Reference Key 3	CHAR	20	Optional
BSID	PRCTR	PRCTR	Profit Center	CHAR	10	Optional
BSID	ZUORN	ZUONR	Assignment Number	CHAR	18	Optional
BSID	HWAE2	HWAE2	Group Currency	CUKY	5	Optional
BSID	DMBE2	DMBE2	Amount in Group Currency	CURR	23(2)	Optional
BSID	MSCHL	MSCHL	Dunning Key	CHAR	1	Optional
BSID	MANSP	MANSP	Dunning block	CHAR	1	Optional
BSID	MANST	MANST	Dunning level	NUMC	2	Optional
BSID	VBUND	VBUND	Trading Partner	CHAR	10	Optional

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
1	Can load, but business process will fail	Open Item is overdue and aged	Rule 1: Company must be in scope Rule 2: Posting Date > 1 years from Migration cutoff date	Report	PF2 / PI2 / WP2

Conversion Process 

The high-level process:

1. Extract data from source systems.
2. Apply relevancy rules.
3. Transform data based on field and value mappings.
4. Create load files outputs.
5. Load data in target system.

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
1.	Ensure source tables BKPF, BSID are extracted in tool according to the agreed cut-off date in the project plan	Data team
2.	Perform preliminary completeness check	Data team
3.	Raise issues as defects if Req # 1 to 2 are not met	Data team
4.	Repeat Req # 1 to 3 if required	Data team
5	Report extraction result to person in charge of AR Open items conversion	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)

No DCT for this object

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step description	Team responsible
1.	Any period / year end close activities have been fully completed	Business
2.	Reconciliation for intercompany receivables have been completed, and adjustment made in legacy SAP system	Business

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 ETL tool
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
1.	Ensure all the fields that require value mapping, as stipulated  Mapping tables, have the latest signed-off mapping files imported into toolMigrate.	Data team
2.	In tool, select the AR Open Items object.	Data team
3.	Go to Process Area Launch and Process the Object - AR Open Items - R3 AR Open Items.	Data team
4.	Launch the Objects to execute transformation.	Data team
5.	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
6.	Generate Pre-Load reports .	Data team
7.	Generate data load count.	Data team
8.	Log errors as defects, if any and address resolutions. Close defects.	Data team
9.	Re-transform and re-validate the Pre-load reports if necessary.	Data team
10.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
11.	Analyse and resolve any pre-load defects logged by business.	Data team
12.	Repeat steps 6 to 11 if necessary	Data team
13.	Proceed to pre-load validations	Data team

Transformation Rules

Rule #	Source  System	Source Table	Source  Field	Source  Description	Target  System	Target Table	Target  Field	Target  Description	Transformation Logic
1	ECC or DCT	BKPF	BELNR	Document Number	S/4HANA	BKPF	BELNR	Document Number	Automatically Generated
2	ECC or DCT	BKPF	BLDAT	Document Date	S/4HANA	BKPF	BLDAT	Document Date	Copy as-is; ensure date format consistency.
3	ECC or DCT	BKPF	BUDAT	Posting Date	S/4HANA	BKPF	BUDAT	Posting Date	As per planned Go-Live data
4	ECC or DCT	BKPF	BLART	Document Type	S/4HANA	BKPF	BLART	Document Type	9D
5	ECC or DCT	BKPF	BUKRS	Company Code	S/4HANA	BKPF	BUKRS	Company Code	Map from source to target using company code mapping table
6	ECC or DCT	BKPF	MONAT	Fiscal Period	S/4HANA	BKPF	MONAT	Fiscal Period	Automatic from Posting Date
7	ECC or DCT	BKPF	WAERS	Currency Key - Document Currency	S/4HANA	BKPF	WAERS	Currency Key - Document Currency	Copy as-is; validate against currency configuration.
8	ECC or DCT	BKPF	HWAER	Local Currency/ Co Code currency (T001)	S/4HANA	BKPF	HWAER	Local Currency/ Co Code currency (T001)	Copy as-is
9	ECC or DCT	BKPF	XBLNR	Reference	S/4HANA	BKPF	XBLNR	Reference	Copy as-is
10	ECC or DCT	BKPF	BKTXT	Document Header Text	S/4HANA	BKPF	BKTXT	Document Header Text	Copy as-is
11	ECC or DCT	BKPF	GJAHR	Fiscal Year	S/4HANA	BKPF	GJAHR	Fiscal Year	Automatic from Posting Date
12	ECC or DCT	BSID	KUNNR	Customer Number	S/4HANA	BSID	KUNNR	Business Partner Number	Map from source to target using Business Partner mapping table
13	ECC or DCT	BSID	SHKZG	Debit / Credit Indicator	S/4HANA	BSID	SHKZG	Debit / Credit Indicator	Automatically derived by the system
15	ECC or DCT	BSID	SGTXT	Item Text	S/4HANA	BSID	SGTXT	Item Text	Copy as-is
16	ECC or DCT	BSID	WRBTR	Document Currency Amount	S/4HANA	BSID	WRBTR	Document Currency Amount	Copy as-is
17	ECC or DCT	BSID	DMBTR	Local Currency Amount	S/4HANA	BSID	DMBTR	Local Currency Amount	Copy as-is
19	ECC or DCT	BSID	ZTERM	Payment Terms	S/4HANA	BSID	ZTERM	Payment Terms	Payment Terms Mapping via Xref . Payment term is required for all AR open items. If a payment term is missing, it can still be migrated with some dummy payment terms but a separate report is required for the missing payment terms.
20	ECC or DCT	BSID	ZFBDT	Baseline Date	S/4HANA	BSID	ZFBDT	Baseline Date	Copy as-is
21	ECC or DCT	BSID	ZLSCH	Payment Method	S/4HANA	BSID	ZLSCH	Payment Method	Payment Method Mapping via Xref
22	ECC or DCT	BSID	ZLSPR	Payment Block	S/4HANA	BSID	ZLSPR	Payment Block	Payment Block Mapping via Xref
23	ECC or DCT	BSID	MSCHL	Dunning Key	S/4HANA	BSID	MSCHL	Dunning Key	Copy as-is
24	ECC or DCT	BSID	KIDNO	Payment Reference	S/4HANA	BSID	KIDNO	Payment Reference	Copy as-is
25	ECC or DCT	BSID	ZBD1T	Cash Discount Days 1	S/4HANA	BSID	ZBD1T	Cash Discount Days 1	Copy as-is
26	ECC or DCT	BSID	ZBD1P	Cash Discount Percentage 1	S/4HANA	BSID	ZBD1P	Cash Discount Percentage 1	Copy as-is
27	ECC or DCT	BSID	ZBD2T	Cash Discount Days 2	S/4HANA	BSID	ZBD2T	Cash Discount Days 2	Copy as-is
28	ECC or DCT	BSID	ZBD2P	Cash Discount Percentage 2	S/4HANA	BSID	ZBD2P	Cash Discount Percentage 2	Copy as-is
29	ECC or DCT	BSID	ZBD3T	Net Due Days	S/4HANA	BSID	ZBD3T	Net Due Days	Copy as-is
30	ECC or DCT	BSID	SKFBT	Amount Eligible for Cash Disc. (Document Curr.)	S/4HANA	BSID	SKFBT	Amount Eligible for Cash Disc. (Document Curr.)	Copy as-is
31	ECC or DCT	BSID	BVTYP	Partner Bank Type	S/4HANA	BSID	BVTYP	Partner Bank Type	Copy as-is
32	ECC or DCT	BSID	KKBER	Credit Control Area	S/4HANA	BSID	KKBER	Credit Control Area	Copy as-is
33	ECC or DCT	BSID	RSTGR	Reason Code for Payments	S/4HANA	BSID	RSTGR	Reason Code for Payments	Reason Code Mapping via Xref
34	ECC or DCT	BSID	FILKD	Account Number of the Branch	S/4HANA	BSID	FILKD	Account Number of the Branch	Customer Mapping via Xref .  Map from source to target using Business Partner mapping table. Branch is also a customer in Legacy.
35	ECC or DCT	BSID	LZBKZ	State Central Bank Indicator	S/4HANA	BSID	LZBKZ	State Central Bank Indicator	Central Bank Indicator Xref
36	ECC or DCT	BSID	LANDL	Supplying Country	S/4HANA	BSID	LANDL	Supplying Country	Country Mapping via ISO
37	ECC or DCT	BSID	XREF1	Reference Key 1	S/4HANA	BSID	XREF1	Reference Key 1	Copy as-is
38	ECC or DCT	BSID	XREF2	Reference Key 2	S/4HANA	BSID	XREF2	Reference Key 2	Copy as-is
39	ECC or DCT	BSID	XREF3	Reference Key 3	S/4HANA	BSID	XREF3	Reference Key 3	Copy as-is
40	ECC or DCT	BSID	PRCTR	Profit Center	S/4HANA	BSID	PRCTR	Profit Center	The logic is mentioned below notes.
42	ECC or DCT	BSID	ZUORN	Assignment Number	S/4HANA	BSID	ZUORN	Assignment Number	Copy as-is
44	ECC or DCT	BSID	MSCHL	Dunning Key	S/4HANA	BSID	MSCHL	Dunning Key	Dunning Key Mapping via Xref
45	ECC or DCT	BSID	MANSP	Dunning block	S/4HANA	BSID	MANSP	Dunning block	Dunning Block Mapping via Xref
46	ECC or DCT	BSID	MANST	Dunning level	S/4HANA	BSID	MANST	Dunning level	Based on the current understanding, the field is mapped as copy as-is
48	ECC or DCT	BSID	VBUND	Trading Partner	S/4HANA	BSID	VBUND	Trading Partner	Trading Partner Mapping via Xref
49	ECC or DCT	BSID	GKONT	Account Number of Offsetting Account	S/4HANA	BSID	GKONT	Account Number of Offsetting Account	2210999
50	ECC or DCT	BSID	DOCLN	Line Item Number in Accounting Document	S/4HANA	BSID	DOCLN	Line Item Number in Accounting Document	Copy as-is
51	ECC or DCT	BSID	HWAE2	Local Currency 2 - Group Currency	S/4HANA	BSID	HWAE2	Local Currency 2 - Group Currency	EUR
52	ECC or DCT	BSID	DMBE2	Amount in Group Currency	S/4HANA	BSID	DMBE2	Amount in Group Currency	Group Currency 1 This is for currency type 30 Based on SHKZG  = 'S' posting key is '40' or else posting key is '50' Refer to Note Below this table 'Legal/Group Currency Calculation' Copy as is with Signage as '-' if the posting key is 50 or else '+' Also consider Currency Adjustment During Migration (TCURX Consideration) below this table Life-to-Date (YTD) Periodic Movements by combining opening balance and Year-to-date balances which will be derived by accumulating all transactional postings (BSEG) for each period up to and including the target migration period.

Group Currency Calculation

During the migration of GL balances from SAP ECC to S/4HANA, it was identified that group currency balances are missing. To address this, the plan is to derive group currency amounts by reading the relevant exchange rates from the BFC consolidation system for each period within the migration scope.

For each period:

• The local currency trial balance will be extracted from ECC.
• The corresponding period’s exchange rate will be retrieved from BFC.
• The group currency balance will be calculated by converting the local currency amounts using the BFC exchange rates.
• The calculated group currency balances will then be loaded into S/4HANA as part of the migration process.

This approach ensures consistency between the group currency balances in S/4HANA and the consolidation system.

Currency Adjustment During Migration (TCURX Consideration)

In SAP, the TCURX table defines the number of decimal places used for each currency.
This impacts how amounts are stored internally in database tables versus how they are displayed externally in user interfaces or reports.

Currencies such as JPY (Japanese Yen), KRW (Korean Won), or VND (Vietnamese Dong) are typically configured with no decimal places (TCURX-CURRDEC = 0).

Understanding and correctly applying the TCURX rules is essential during data migration to ensure financial consistency between ECC and S/4HANA.

Internal vs External Currency Representation example:

External Amount	The amount value as displayed to users in SAP screens and reports.	96015 JPY	Multiplied by factor = 10² if target has 2 decimals
Internal Amount	The amount value stored in database tables for computation.	960.15

 During data migration, these internal (technical) amounts must be converted to external amounts to ensure accuracy and consistency in the target S/4HANA system.

Conversion Formula:

External Amount =  Internal Amount * 10 to the power ( 2 - Number of decimal for the currency in TCURX table )

Profit Centre

PF2:
1)The Business Area will be used to derive the corresponding Profit Centre to which the Business Area is assigned, for the AR Open Item data.
2)AR Open Items will be aggregated at the Company Code and Profit Centre levels.
3)The aggregated data will then be used to allocate the AR Take-on GL Account balances by Profit Centre, ensuring reconciliation and alignment between subledger and general ledger balances at the profit centre level during migration.

WP2: the profit center will be derived from the offset line of the AR open item document.

PI2:  AR open items transferred to PI2 from PF2 will include the business area, and the profit center derivation process for these items will follow the approach outlined in the PF2 section. Similarly, AR open items transferred to PI2 from WP2 will include the business area, and the profit center derivation process will follow the approach detailed in the WP2 section.

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Mapping Table Name	Mapping Table Description
Company Code	Mapping of legacy company codes to target system value
GL Account	Mapping of legacy GL accounts to target system value
Profit Centre	Mapping of legacy Profit Center to target system value
Business Partner	Mapping of legacy Customer accounts to target system value
Trading Partner	Mapping of legacy trading partners to target system value
Currency Key	Mapping of legacy currency keys to target system value
Payment Block Key	Mapping of legacy payment block key to target system value
Payment Method	Mapping of legacy payment method to target system value
Document type	Default doc type for this object OPEN AR
Payment Terms	Mapping of legacy Payment terms to target system value
Dunning Key	Mapping of legacy Dunny key to target system value
Reason Code for Payments	Mapping of legacy reason codes to target system value
Account Number of the Branch	Mapping of legacy Branch accounts to target system value
Supplying Country	Mapping of legacy supplying country to target system value
Functional Area	Mapping of legacy functional area to target system value

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool.	Data team

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Generation of Pre-load reports	Mandatory field check. Based on S/4HANA target design fields, Check if records have all mandatory fields filled and mapped, otherwise they should be flagged as error. Check Business Partners are extended to required company code Check if all mapped business partners exist in S/4HANA KNB1-KUNNR (Customer) and KNB1-BUKRS (Company Code), and KNB1-LOEVM (Deletion Flag) must not be X
Reconciliation of total	Record Count Check the sum of record count of the AR open items in the load file is the same as source. The record count for AR Open Items will be done on the group basis. The fields in the group consist of: Company Code, Customer Check Amount in Document Currency and Local Currency and Group Currency Check the sum of the amount in Document Currency and Local Currency in load file is the same as source. If any of the sum is different, flag the record as error.

Accuracy

Task	Action
Mandatory field mapping and transformation	Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.  Review the data report to ensure mapping value is not missing in tool. Capture errors in the Data Error report.

Business

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

Completeness

Task

Action

Verify record count in Pre-load reports by region

In legacy system, execute report AR Line Item Display (t/code: FBL5N)  Group the output of the report by Company Code and Customer Account using subtotal function and compare the count in this report against the AR open items count in the pre-load file. The record count for AR Open Items may also be done on the more granular level. The recommended granular level or the subtotal fields can consist of: Company Code, Customer, Profit Centre. If any of the count is different, raise defect and flag the relevant record as error.

Accuracy

Task	Action
Conversion accuracy	Verify AR open items are transformed accurately as per endorsed transformation/mapping rules. Review error reports in tool for any mismatch or missing transformed values. In legacy system, execute report AR Line Item Display (t/code: FBL5N) with selection parameters. If any of the sum is different, raise defect and flag the relevant record as error.
Business partner balance on Company code and profit center level	Check the total open item amount on Business partner at Company Code and Profit center level, against the total in legacy by Document, Local and Group currency. Apply currency rules where applicable

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
1	Ensure the load tools are transported into the correct tool instance.	Data team
2	Ensure DCTs and all required mappings are submitted and complete	Data team
3	Ensure Pre-load sign-offs are obtained.	Data team
4	Execute tool AR Open items	Data team
5	Generate the post load reports in tool.	Data team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
8	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
9	Repeat steps 5 to 7 if necessary.	Data team

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
1.	Company code-related configuration (posting period variant).
2.	Finance posting (document types, document number ranges)
3.	Currencies (currency keys, decimal places in currencies)
4.	Accounts Receivable specific (payment term, payment method)

 Conversion Objects

Object #	Preceding Object Conversion Approach
1067	GL Account Operational CoA (incl. secondary CE)
3017	Business Partners - FI Customer (FLCU00)
1073	Profit center

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
Posting Period Error	Posting period is blocked for posting	Review project / cutover plan and ensure posting periods can be opened for postings
Business partner does not exist	Business Partner record for the line item doesn’t exist	Create the relevant Business Partner in the S/4HANA System
Profit Centre does not exist	Profit centre does not exist in company code	Ensure the profit centre mapping is correct and or create the profit centre if it is valid

Post-Load Validation

Project Team

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

Completeness

Task

Action

Reconciliation of Record Count

Total number of records loaded for AR Open Items will be generated in the Post-load reports in tool based on the target table and fields mentioned in section 3. The reconciliation needs to be executed on the total number of ‘valid’ records and currency amount per company code in the source compared to total number of records and currency amount in S/4HANA Record Count Check the sum of record count of the open items in the load file is the same as S/4HANA. The record count for AR Open Items will be done on the group basis. The fields in the group are consist of: Company Code, Customer Account Check Amount in Document Currency and Local Currency Check on line item level that the sum of the amount in Document Currency and Local Currency in the load file is the same as posted in S/4HANA. If any of the sum is different, flag the record as error.

Accuracy

Task

Action

Check values in key fields for accuracy

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation. Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. Any mismatch will be reported under the Post Load - Error report.

Business

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

Completeness

Task	Action
Record Count Check	Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations Business may also run transaction code FBL5N – Customer Line Item Display or equivalent report in Fiori App to display loaded AR Open Items in S/4HANA and compare results against the pre-load reports generated from tool.

Accuracy

Task	Action
Open items totals	Check business partner open item totals by Business partner, Company code, profit centre. Totals should be checked in Document, Local and Group currency.
Spot check	Business should choose some business partners and perform comprehensive check of open items, payment terms etc Such partners should have huge number of open items or be critical for payment runs in S4 or have certain complexity in conversion.

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.

Change log

Workflow history