| Status | Approved |
| Owner | Prasad Naidu |
| Stakeholders |
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, local currency and group 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:
- All AR Open items with posting dates on or before Migration cutoff date(BUDAT <=Cutover Date)
- One time customers are out of scope
- Open Customer Invoices with special GL Indicator are out of scope. These are covered in CNV-9009
- AR Open items clearing with future date is not applicable
| 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
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 | BELNR | BELNR_D | Legacy 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 | SHKZG | SHKZG | Debit / Credit Indicator | CHAR | 1 | 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 | MWSKZ | MWSKZ | Tax on sales/purchases code | CHAR | 2 | Optional |
| BSID | ZTERM | ZTERM | Payment Terms | CHAR | 4 | Optional |
| BSID | ZFBDT | ZFBDT | Baseline Date | DATS | 8 | Optional |
| 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 | BUZEI | BUZEI | Item number | NUMC | 3 | Required |
| 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 | FKBER | FKBER | Functional Area | CHAR | 16 | Optional |
| BSID | ZUORN | ZUONR | Assignment Number | CHAR | 18 | Optional |
| BSID | BKTXT | BKTXT | Document Header Text | CHAR | 25 | Optional |
| BSID | GJAHR | GJAHR | Year | NUMC | 4 | Required |
| BSID | BUZEI | BUZEI | Number of Line Item Within Account | NUMC | 3 | Required |
| BSID | KIDNO | KIDNO | Payment Reference | CHAR | 12 | Optional |
BSID | DMBE2 | DMBE2 | Amount in Group Currency | CURR | 23(2) | Optional |
BSID | MANSP | MANSP | Dunning block | CHAR | 1 | Optional |
BSID | MANST | MANST | Dunning level | NUMC | 2 | Optional |
BSID | GSBER | GSBER | Business Area | CHAR | 4 | Optional |
BSID | VBUND | VBUND | Trading Partner | CHAR | 10 | 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 > 1 years from Migration cutoff date | Report | PF2 / PI2 / WP2 |
Conversion Process
The high-level process:
- Extract data from source systems.
- Apply relevancy rules.
- Transform data based on field and value mappings.
- Create load files outputs.
- Load data in target system.
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:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- 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, BSID, BSAD 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
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
Data Collection Template (DCT)
The DCT will hold legacy data only. the necessary transformations will be applied at a later stage.DCT Rules
| Field | Field Description | Rule |
| BSID-BUKRS | Company Code | Drop down value from T001-BUKRS company code DCT (only with active for finance indicator) |
| BSID-KUNNR | Customer Number | Must exist in BP master and mapped correctly |
| BSID-GJAHR | Fiscal Year | Must be 4-digit valid year |
| BSID-BLART | Document Type | Must be defined in config |
| BSID-BLDAT | Document Date | Must be a valid past date |
| BSID-BUDAT | Posting Date | Must be in open posting period |
| BSID-WRBTR | Amount in Document Currency | Must match currency format |
| BSID-DMBTR | Local Currency Amount | Calculated based on exchange rate |
| BSID-WAERS | Currency | Valid ISO currency code (e.g., USD, EUR) |
| BSID-ZFBDT | Baseline Date | Required if ZTERM is used |
| BSID-XBLNR | Reference Number | Optional but recommended for audit traceability |
| BSID-ZUONR | Assignment | Used for matching or reporting |
| BSID-SGTXT | Text | Descriptive free text up to 50 chars |
| BSID-HKONT | Reconciliation Account | Must align with customer master |
| BSID-GSBER | Business Area | Optional, This is used in Legacy |
| BSID-ZTERM | Payment Terms | Must be configured and valid |
| BSID-PRCTR | Profit Center | Exist in Profit Centre DCT and assigned with the same company code |
Extraction Dependencies
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 to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- 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 | ECC or DCT | BKPF | BELNR | Document Number | S/4HANA | BKPF | BELNR | Document Number | Automatic 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 | Custom document type will be configured for Data Migration |
| 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 | S/4HANA | BKPF | WAERS | Currency Key | Copy as-is; validate against currency configuration. |
| 8 | ECC or DCT | BKPF | XBLNR | Reference | S/4HANA | BKPF | XBLNR | Reference | Takeover document number(BELNR) from source |
| 9 | ECC or DCT | BKPF | BKTXT | Document Header Text | S/4HANA | BKPF | BKTXT | Document Header Text | Copy as-is |
| 10 | ECC or DCT | BKPF | GJAHR | Fiscal Year | S/4HANA | BKPF | GJAHR | Fiscal Year | Automatic from Posting Date |
| 11 | ECC or DCT | BSID | KUNNR | Customer Number | S/4HANA | BSID | KUNNR | Business Partner Number | Map from source to target using Business Partner mapping table |
| 12 | ECC or DCT | BSID | NEWBKS | Posting Key | S/4HANA | BSID | NEWBKS | Posting Key | Map to S/4 Posting Key |
| 13 | ECC or DCT | BSID | HKONT | G/L Account Number | S/4HANA | BSID | HKONT | G/L Account Number | This is offsetting line and to be confirmed by R2R Team |
| 15 | ECC or DCT | BSID | SGTXT | Item Text | S/4HANA | BSID | SGTXT | Item Text | GJAHR + BUKRS+ BUZEI+ BELNR + KUNNR |
| 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 |
| 18 | ECC or DCT | BSID | MWSKZ | Tax on sales/purchases code | S/4HANA | BSID | MWSKZ | Tax on sales/purchases code | Automatic from Posting Date |
| 19 | ECC or DCT | BSID | ZTERM | Payment Terms | S/4HANA | BSID | ZTERM | Payment Terms | Map from source to target using Business Partner mapping table |
| 20 | ECC or DCT | BSID | ZFBDT | Baseline Date | S/4HANA | BSID | ZFBDT | Baseline Date | Map to S/4 Posting Key |
| 21 | ECC or DCT | BSID | ZLSCH | Payment Method | S/4HANA | BSID | ZLSCH | Payment Method | This is offsetting line and to be confirmed by R2R Team |
| 22 | ECC or DCT | BSID | ZLSPR | Payment Block | S/4HANA | BSID | ZLSPR | Payment Block | GJAHR + BUKRS+ BUZEI+ BELNR + KUNNR |
| 23 | ECC or DCT | BSID | MSCHL | Dunning Key | S/4HANA | BSID | MSCHL | Dunning Key | Copy as-is |
| 25 | ECC or DCT | BSID | KIDNO | Payment Reference | S/4HANA | BSID | KIDNO | Payment Reference | Convert using Exchange Rate |
| 26 | ECC or DCT | BSID | ZBD1T | Cash Discount Days 1 | S/4HANA | BSID | ZBD1T | Cash Discount Days 1 | Map Tax Code using Xref |
| 27 | ECC or DCT | BSID | ZBD1P | Cash Discount Percentage 1 | S/4HANA | BSID | ZBD1P | Cash Discount Percentage 1 | Payment Terms Mapping via Xref |
| 28 | ECC or DCT | BSID | ZBD2T | Cash Discount Days 2 | S/4HANA | BSID | ZBD2T | Cash Discount Days 2 | Copy as-is; ensure date format consistency. |
| 29 | ECC or DCT | BSID | ZBD2P | Cash Discount Percentage 2 | S/4HANA | BSID | ZBD2P | Cash Discount Percentage 2 | Payment Method Mapping via Xref |
| 30 | ECC or DCT | BSID | ZBD3T | Net Due Days | S/4HANA | BSID | ZBD3T | Net Due Days | Payment Block Mapping via Xref |
| 31 | ECC or DCT | BSID | SKFBT | Amount Eligible for Cash Disc. (Document Curr.) | S/4HANA | BSID | SKFBT | Amount Eligible for Cash Disc. (Document Curr.) | Dunning Key Mapping via Xref |
| 32 | ECC or DCT | BSID | BVTYP | Partner Bank Type | S/4HANA | BSID | BVTYP | Partner Bank Type | Copy as-is |
| 33 | ECC or DCT | BSID | KKBER | Credit Control Area | S/4HANA | BSID | KKBER | Credit Control Area | Copy as-is |
| 34 | ECC or DCT | BSID | RSTGR | Reason Code for Payments | S/4HANA | BSID | RSTGR | Reason Code for Payments | Reason Code Mapping via Xref |
| 35 | ECC or DCT | BSID | FILKD | Account Number of the Branch | S/4HANA | BSID | FILKD | Account Number of the Branch | Branch Mapping via Xref |
| 36 | ECC or DCT | BSID | LZBKZ | State Central Bank Indicator | S/4HANA | BSID | LZBKZ | State Central Bank Indicator | Central Bank Indicator Xref |
| 37 | ECC or DCT | BSID | LANDL | Supplying Country | S/4HANA | BSID | LANDL | Supplying Country | Country Mapping via ISO |
| 38 | ECC or DCT | BSID | XREF1 | Reference Key 1 | S/4HANA | BSID | XREF1 | Reference Key 1 | Copy as-is |
| 39 | ECC or DCT | BSID | XREF2 | Reference Key 2 | S/4HANA | BSID | XREF2 | Reference Key 2 | Copy as-is |
| 40 | ECC or DCT | BSID | XREF3 | Reference Key 3 | S/4HANA | BSID | XREF3 | Reference Key 3 | Copy as-is |
| 41 | ECC or DCT | BSID | PRCTR | Profit Center | S/4HANA | BSID | PRCTR | Profit Center | As per XREF table. |
| 42 | ECC or DCT | BSID | FKBER | Functional Area | S/4HANA | BSID | FKBER | Functional Area | Functional Area Mapping via Xref |
| 43 | ECC or DCT | BSID | ZUORN | Assignment Number | S/4HANA | BSID | ZUORN | Assignment Number | Copy as-is |
| 44 | ECC or DCT | BSID | BKTXT | Document Header Text | S/4HANA | BSID | BKTXT | Document Header Text | Copy as-is |
| 45 | ECC or DCT | BSID | GJAHR | Year | S/4HANA | BSID | GJAHR | Year | Derive from Posting Date |
| 46 | ECC or DCT | BSID | BUKRS | Company Code | S/4HANA | BSID | BUKRS | Company Code | Xref/Lookup Company Code |
| 47 | ECC or DCT | BSID | BUZEI | Number of Line Item Within Account | S/4HANA | BSID | BUZEI | Number of Line Item Within Account | Copy as-is |
| 48 | ECC or DCT | BSID | KIDNO | Payment Reference | S/4HANA | BSID | KIDNO | Payment Reference | Copy as-is |
| 49 | ECC or DCT | BSID | KSL | Amount in Group Currency | S/4HANA | BSID | KSL | Amount in Group Currency | Copy as-is |
| 50 | ECC or DCT | BSID | MSCHL | Dunning Key | S/4HANA | BSID | MSCHL | Dunning Key | Dunning Key Mapping via Xref |
| 51 | ECC or DCT | BSID | MANSP | Dunning block | S/4HANA | BSID | MANSP | Dunning block | Copy as-is |
| 52 | ECC or DCT | BSID | MANST | Dunning level | S/4HANA | BSID | MANST | Dunning level | Copy as-is |
| 53 | ECC or DCT | BSID | GSBER | Business Area | S/4HANA | BSID | GSBER | Business Area | Business Area Mapping via Xref |
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 |
Business Area | Mapping of legacy business 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
Completeness
Task | Action |
Generation of | Mandatory field check. Check Business Partners are extended to required company code Check if all mapped business partners exists in S/4HANA KNB1-KUNNR (Customer) and KNB1-BUKRS (Company Code), and KNB1-LOEVM |
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 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. |
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:
- 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
Source data for FI - Accounts receivable open item.xml
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
Configuration
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
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 |
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
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||