Status	Approved
Owner	Prasad Naidu
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to migrate AR open items without special GL indicator in 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.

Amounts in legacy involve document currency, local currency and group currency. All currencies will be loaded accordingly unless there is a change in company design where local / group currency changes. Rates are as per the historical postings unless specific requirement calls for a fixed rate eg. group currency rate for consolidation purposes. Offsetting gl accounts in legacy documents will not be considered in this migration scope, they will be migrated in other objects scope eg. GL open item or GL balances.

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.

The data from legacy system includes:

Open Customer Invoices
Unsettled credit or debit documents
Partial Payments / Residual Items
Clearing date > migration cutoff date
Posting date <= migration cutoff date

The data from legacy system excludes:

Parked item
Noted item

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
WP2	AR open item
PI2	AR open item

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
BKPF	BUKRS		Company Code	CHAR	4	Required
BKPF	GJAHR		Fiscal Year	NUMC	4	Required
BKPF	BLART		Document Type	CHAR	2	Required
BKPF	BUDAT		Posting Date	DATS	8	Required
BKPF	BLDAT		Document Date	DATS	8	Required
BKPF	MONAT		Posting Period	NUMC	2	Optional
BKPF	WAERS		Document Currency	CURR	5	Required
BKPF	BKTXT		Document Header Text	CHAR	25	Optional
BKPF	XBLNR		Reference Document Number	CHAR	16	Optional
BSEG	BUZEI		Line Item Number	NUMC	3	Auto
BSEG	BSCHL		Posting Key	NUMC	2	Required
BSEG	SHKZG		Debit/Credit Indicator	CHAR	1	Required
BSEG	HKONT		G/L Account	CHAR	10	Required
BSEG	KUNNR		Customer Number	CHAR	10	Required
BSEG	DMBTR		Amount in Local Currency	CURR	13,2	Required
BSEG	WRBTR		Amount in Document Currency	CURR	13,2	Required
BSEG	ZTERM		Payment Terms	CHAR	4	Optional
BSEG	ZFBDT		Baseline Date for Due Date	DATS	8	Required
BSEG	SGTXT		Line Item Text	CHAR	50	Optional
BSEG	ZUONR		Assignment Number	CHAR	18	Optional
BSEG	XREF1		Reference Key 1	CHAR	12	Optional
BSEG	UMSKS		Special G/L Indicator	CHAR	1	Optional
BSEG	REBZG		Reference Document Number (Clearing)	CHAR	10	Optional
BSEG	REBZJ		Fiscal Year of Reference Document	NUMC	4	Optional
BSEG	REBZZ		Line Item of Reference Document	NUMC	3	Optional

Data Cleansing

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 is 365 days or longer than current system date

Rule 3: Due Date is prior report execution date.

Report

PF2 / PI2 / WP2

2

Can load, but business process will fail

Parked Items need to be cleanse

Rule 1: Company must be in scope;

Rule 2: Document is parked (document status = “V”)

Report

PF2 / PI2 / WP2

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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

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

Req #	Requirement description	Team responsible
1.	Ensure source tables BKPF, BSEG, are extracted in tool according to the agreed cut-off date in the project plan	Data team
2.
3.
4.

Selection Screen

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 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.	Any period / year end close activities have been fully completed	Business
2.	Reconciliation for intercompany payables 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 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
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.	N/A	N/A	N/A	N/A	S/4HANA	BKPF	BELNR	Document Number	Automatic determination of the Document number in target system. Document Date from source system is migrated into field SGTXT – see transformation rule for Line Item text field below.
2.	Legacy	BKPF	BUKRS	Company Code	S/4HANA	BKPF	BUKRS	Company Code	Map from source to target using company code mapping table
3.	Legacy	BSIK	LIFNR	Vendor Account	S/4HANA	ACDOCA	LIFNR	Vendor Account	Map from source to target using Business Partner mapping table. For Vendors, identified as Employee vendors (using Employee Vendor DCT) – post to GL account xxxxxx without any vendor.
4.	Legacy	BSIK	HKONT	GL Account	S/4HANA	ACDOCA	HKONT	GL Account	Map from source to target using G/L Account mapping table
5.	Legacy	BKPF	XBLNR	Reference Document Number	S/4HANA	BKPF	XBLNR	Reference Document Number	Copy source value. For Vendors, identified as Employee vendors (using Employee Vendor DCT) – replace legacy value with constant “related”
6.	Legacy	BKPF	BLDAT	Document Date	S/4HANA	BKPF	BLDAT	Document Date	Copy source value
7.	Legacy	BKPF	BUDAT	Posting Date	S/4HANA	BKPF	BUDAT	Posting Date	Posting date = Conversion date (last day of month prior go-live)
8.	Legacy	BKPF	BKTXT	Header Text	S/4HANA	BKPF	BKTXT	Header Text	Copy source value. For Vendors, identified as Employee vendors (using Employee Vendor DCT) – replace legacy value with constant “Empl related”
9.	Legacy	BSIK	SGTXT	Item Text (For offset posting to conversion take-on G/L account)	S/4HANA	ACDOCA	SGTXT	Item Text	FY+CoCode+DocNumber (example – 2018ECAU3001102743) will be used as Prefix (SGTXT). If source SGTXT is longer than 32 chars, it’ll be cut to fit. Example in S4 will be posted with SGTXT= “2018ECAU3001102743MILLER MINING”. For Vendors, identified as Employee vendors(using Employee Vendor DCT) – replace legacy value with constant “Empl related”
10.	Legacy	BSIK	WRBTR	Amount in Document Currency	S/4HANA	ACDOCA	WSL	Amount in Document Currency	Copy source value, split by profit centers if required.
11.	Legacy	BSIK	DMBTR	Amount in Local Currency	S/4HANA	ACDOCA	HSL	Amount in Local Currency	Copy source value if source currency is equal to target currency,
12.	Legacy	BSIK	DMBE3	Amount in 3rd Local Currency	S/4HANA	ACDOCA	KSL		Copy source value as the group currency does not change.
13.	Legacy	BKPF	WAERS	Document Currency	S/4HANA	BKPF	WAERS	Document Currency	Mapping table - When conversion from ‘old’ Local currency to ‘new’ Local currency applies – refer to section 2. Conversion scope of this document for more details
14.	Legacy	T001	WAERS	Local Currency	S/4HANA	BKPF	HWAER	Local Currency	Mapping table - When conversion from ‘old’ Local currency to ‘new’ Local currency applies – refer to section 2. Conversion scope of this document for more details
15.	Legacy	BSIS	VALUT	Value Date	S/4HANA	ACDOCA	BZDAT	Value Date	Copy source value
16.	Legacy	BSIS	PRCTR	Profit Centre	S/4HANA	ACDOCA	PRCTR	Profit Centre	Profit centers should be populated on the offset item - conversion take-on G/L account
17.	Legacy	BSIS	VBUND	Company ID of Trading Partner	S/4HANA	ACDOCA	RASSC	Company ID of Trading Partner	Map from source to target using Trading Partner mapping table
18.	Legacy	BSIS	ZUONR	Assignment Number	S/4HANA	ACDOCA	ZUONR	Assignment Number	Copy source value. For Vendors, identified as Employee vendors(using Employee Vendor DCT) – replace legacy value with constant “Empl related”
19.	Legacy	BSIK	UMSKZ	Special G/L Indicator	S/4HANA	BSIK	UMSKZ	Special G/L Indicator	Map from source to target using Special G/L Indicator mapping table.
20.	Legacy	BSIK	ZLSPR	Payment Block Key	S/4HANA	BSIK	ZLSPR	Payment Block Key	Map from source to target using Payment Block Key mapping table
21	Legacy	BSIK	ZLSCH	Payment method	S/4HANA	BSIK	ZLSCH	Payment method	Map from source to target
22.		BSIK	ZTERM	Payment Term	S/4HANA	BSIK	ZTERM	Payment Term	Map from source to target using Payment term mapping table
23.	Legacy	BSIK	ZFBDT	Baseline Date	S/4HANA	BSIK	ZFBDT	Baseline Date	Copy source value
24.	Legacy	BSIK	KIDNO	Payment reference	S/4HANA	BSIK	KIDNO	Payment reference	Copy source value
25.	Legacyor DCT	BSIK	EBELN	Purchasing document	S/4HANA	BSIK	EBELN	Purchasing document	Map it to PO. Open PO cross reference table is used for mapping in both cases.
26.	Legacy or DCT	BSIK	EBELP	Purchasing document item	S/4HANA	BSIK	EBELN	Purchasing document item	Map it to PO item. Open PO cross reference table is used for mapping.

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 vendor 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
Special G/L Indicator	Mapping of legacy special GL indicator 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
Open Purchase order cross references	Mapping of legacy PO 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

Completeness

Task

Action

Generation of
Pre-load reports

Mandatory field check.
Based on S/4HANA target design fields, account field status groups and tax settings

Check if records have all mandatory fields filled and mapped, otherwise they should be flagged as error.

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 are consist of: Company Code, Customer

Check Amount in Document Currency and Local 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

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 AP 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:

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	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
6
7
8
9

Load Phase and Dependencies

Configuration

Item #	Configuration item
1.	Company code-related configuration (posting period variant).
2.	Finance posting (document types, document number ranges, special gl indicator)
3.	Currencies (currency keys, decimal places in currencies)
4.	Accounts Payable specific (payment term, payment method, payment block keys)

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

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

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

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.
is in scope based on data design and any exception requested by business.

Change log

Version	Published	Changed By	Comment
CURRENT (v. 7)	Apr 23, 2026 14:08	NAIDU-ext, Prasad
v. 101	Mar 26, 2026 17:52	NAIDU-ext, Prasad
v. 100	Mar 20, 2026 10:37	NAIDU-ext, Prasad
v. 99	Mar 20, 2026 10:25	NAIDU-ext, Prasad
v. 98	Mar 19, 2026 10:31	NAIDU-ext, Prasad	Reverted from v. 96
v. 97	Mar 13, 2026 12:36	NAIDU-ext, Prasad
v. 96	Jan 13, 2026 12:46	NAIDU-ext, Prasad
v. 95	Jan 13, 2026 12:43	NAIDU-ext, Prasad
v. 94	Jan 12, 2026 12:50	NAIDU-ext, Prasad
v. 93	Jan 09, 2026 12:51	NAIDU-ext, Prasad

Go to Page History

Workflow history

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

Apr 23, 2026	Actor	Type	Activity	Version
Approved	SHARMA-ext, Swati	State	changed state to Approved at 2:12 pm	v102
Revision under Review	SHARMA-ext, Swati	State	gave Minor change approval at 2:12 pm rephrased for LANDL mapping for better understanding
Revision under Review	SHARMA-ext, Swati	State	changed state to Revision under Review at 2:12 pm	v102
Revision in Progress	NAIDU-ext, Prasad	State	changed state to Revision in Progress at 2:08 pm	v102
Approved	NAIDU-ext, Prasad	Edit	updated the page at 2:08 pm
Mar 27, 2026
	SHARMA-ext, Swati	State	changed state to Approved at 1:06 pm	v101

Workflow history

Space shortcuts

Page tree

CNV- 9008 AR Open Items

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

Change log

Workflow history