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’

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach. 

Data Cleansing

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

Extraction

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

1. The data exists. connects to the source and loads the data into . There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

No DCT for this object

Extraction Dependencies

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team.  This identifies the transformation activity required to allow to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in 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

Transformation Rules

Group Currency Calculation (reference from CS # 9013)

In legacy ECC, 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.

Note:  For AR balances, we will use the closing rate as of the cutover date. If the cutover is on 1st July, we will use the June closing rates, and these rates will be provided in a separate file.

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:

 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 )

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

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Source data for FI - Accounts receivable open item.xml

Load Run Sheet

Load Phase and Dependencies

Configuration

 Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load. 
• is in scope based on data design and any exception requested by business.

Change log

Workflow history