You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Status

  Revision in Progress

OwnerBernard Ng
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to post AP open items without special GL indicator in S/4 HANA.

AP open items are related to vendor line items that have not been cleared and remains as open status during migration cut-off date.

  • 3rd party vendors
  • Intercompany vendors
  • Employees
  • Others

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 AP open items from Legacy Source Systems into S/4HANA following the AP open items Master Data Design Standard. 


The data from legacy system includes:

  1. All open items with no special GL indicator, exclude parked item and noted item
  2. Clearing date > migration cutoff date
  3. Posting date <= migration cutoff date

The data from legacy system excludes:

  1. Parked item
  2. Noted item


List of source systems and approximate number of records 
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2AP open item1000
1000
WP2AP open item1000
1000
PI2AP open item500
500





Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements




Target Design

The technical design of the target for this conversion approach. 

TableFieldData ElementField DescriptionData TypeLengthRequirement






















Table

Field

Data Element

Field Description

Data Type

Length (Decimals)

Requirement

BKPF

BUKRS


Company Code

CHAR

4

Mandatory

ACDOCA

LIFNR


Vendor

CHAR

16

Mandatory

BKPF

XBLNR


Reference Document Number

CHAR

16

Mandatory

BKPF

BLDAT


Document Date

DATE

10

Mandatory

BKPF

BUDAT


Posting Date

DATE

10

Mandatory

BKPF

BKTXT


Header Text

CHAR

50

Conditional Based on Source Data

BKPF

SGTXT


Item Text

CHAR

50

Conditional Based on Source Data

BSIK

UMSKZ


Special G/L Indicator

CHAR

1

Conditional Based on Source Data

ACDOCA

WSL


Amount in Document Currency

CURR

23(2)

Mandatory

ACDOCA

HSL


Amount in Local Currency

CURR

23(2)

Mandatory

ACDOCA

KSL


Amount in Group Currency

CURR

23(2)

Mandatory

BKPF

WAERS


Document Currency

Text

4

Mandatory

BKPF

HWAER


Local Currency

Text

4

Mandatory

ACDOCA

BZDAT


Value Date

Date

8

Conditional Based on Source Data

ACDOCA

PRCTR


Profit Centre

Text

10

Mandatory

BSIK

ZLSPR


Payment Block Key

Text

1

Conditional Based on Source Data

BSIK

ZLSCH


Payment Method

Text

1

Conditional Based on Source Data

BSIK

ZTERM


Payment Term

Text

4

Conditional Based on Source Data

BSIK

ZFBDT


Baseline Date

Date

8

Mandatory

ACDOCA

RASSC


Company ID of Trading Partner

Text

6

Conditional based on Intercompany account used in source and target

ACDOCA

ZUONR


Assignment Number

Text

18

Conditional Based on Source Data

BSEG

LZBKZ


SCB Indicator

CHAR

3

Conditional Based on Source Data

BKPF

XREF1_HD


Reference field 1 (header)

CHAR

20

Conditional Based on Source Data

BKPF





20

Conditional Based on Source Data

BSIK

KIDNO


Payment reference

CHAR

30

Conditional Based on Source Data

BSIK

EBELN


Purchasing document

CHAR

10

Required if BSIK-UMSKZ = “A”

BSIK

EBELP


Purchasing document item

NUMC

5

Required if BSIK-UMSKZ = “A”



Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System


























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:

  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

Req #Requirement DescriptionTeam Responsible













Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue 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 NameField DescriptionRule












Extraction Dependencies

Item #Step DescriptionTeam Responsible













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
  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 DescriptionTeam Responsible













Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































Transformation Mapping

Mapping Table NameMapping Table Description 








Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible













Pre-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





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 DescriptionTeam Responsible













Load Phase and Dependencies

Configuration

Item #Configuration Item






 Conversion Objects

Object #Preceding Object Conversion Approach

list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)




Error Handling

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





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. 5) Apr 08, 2026 15:01 NG-ext, Bernard
v. 81 Apr 06, 2026 11:42 NG-ext, Bernard
v. 80 Mar 18, 2026 08:24 NG-ext, Bernard
v. 79 Jan 23, 2026 11:36 NG-ext, Bernard
v. 78 Dec 18, 2025 07:46 NG-ext, Bernard Reverted from v. 76
v. 77 Dec 18, 2025 07:23 NG-ext, Bernard
v. 76 Dec 04, 2025 07:23 NG-ext, Bernard
v. 75 Dec 04, 2025 07:21 NG-ext, Bernard
v. 74 Dec 04, 2025 07:15 NG-ext, Bernard
v. 73 Dec 04, 2025 02:06 NG-ext, Bernard

Go to Page History

Workflow history

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

  • No labels