1.      

Can load, but business process will fail

Open Item is overdue and aged

Rule 1: Company must be in scope;

Rule 2:

Rule 3: ;Posting Date is 365 days or longer than current system date;

Rule 4: Due Date is prior report execution date.

Due Date calculation:

o    Credit posting to vendor account (BKPF.GLVOR = RFBU and BSIK.SHKZG = H)

Due Date = Baseline Date + Number Days as per specified in payment terms defined in line item

o    Debit posting to vendor account (BKPF.GLVOR = RFBU and BSIK.SHKZG = S)

Due Date = Baseline Date

2.      

Can load, but business process will fail

Open Items for Employees Vendors

Rule 1: Company must be in scope;

Rule 2: Line item is not having a clearing date;

Rule 3:  Vendors is with Employee Vendor Account

3.      

Can load, but business process will fail

Open items posted to alternative GL

Rule 1: Company must be in scope;

Rule 2: Line item is not having a clearing date;

Rule 3:  The Special GL Indicator field is not initial

4.      

Cannot load

Open Items posted for One-Time Vendor

Rule 1: Company must be in scope;

Rule 2: Line item is not having a clearing date;

Rule 3:  Vendors is with One-time Vendor account

5.      

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”)

6.      

Can load, but business process will fail

Unapproved Noted Items to cleanse

Rule 1: Company must be in scope;

Rule 2: Document is noted (document status = “S”)

7.      

Can load, but business process will fail

Monitor documents without payment terms and payment method

Rule 1: Company must be in scope;

Rule 2: Document is missing payment terms and / or payment method 

1.      

Ensure source tables BKPF, BSIK, BSAK, BFOK_A are extracted in DSP according to the agreed cut-off date in the project plan

Data team

2.      

Perform preliminary completeness check documented in section 5.2.8.1.1

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 APOI conversion

Data team

region_group

ORICA region of operation

Region code derived from Company code DCT based on entered Company code. No user input required.

BKPF-BUKRS

Company Code

Drop down value from company code DCT (only with active for finance indicator)

ACDOCA-LIFNR

Vendor Account

Drop down value from Business Partner DCT as FI Vendor on required company code level

ACDOCA-UMSKZ

Special G/L Indicator

Business to determine if document should be reflected as sn special G/L transaction. Special G/L indicator is provided in the mapping table.

BKPF-XBLNR

Reference Document Number

Business to enter content as per data type and length permitted

BKPF-BLDAT

Document Date

Business to enter content as per data type and length permitted

BKPF-BUDAT

Posting Date

Default to Conversion date as per section 2

BKPF-BKTXT

Header Text

Business to enter content as per data type and length permitted

ACDOCA-SGTXT

Item Text

Business to enter content as per data type and length permitted

BKPF-WAERS

Document Currency Key

Drop down value. Exist as valid 4S Currency Key (TCURT.WAERS)

ACDOCA-WSL

Amount in Document Currency

BKPF-HWAER

Local Currency Key

Default to target Company Code Currency (T001-WAERS)

ACDOCA-HSL

Amount in Local Currency

Business to enter content. Values should be checked with decimal points for Local currency (TCURX-CURDEC)

ACDOCA-BZDAT

Value Date

Business to enter content as per data type and length permitted

ACDOCA-PRCTR

Profit Centre

Drop down value. Exist in Profit Centre DCT and assigned with the same company code

BSIK-ZLSPR

Payment Block Key

Default value to be used.

BSIK-ZLSCH

Payment Method

Drop down value. Exist as valid 4S Payment Method (T042Z-ZLSCH where T042Z-LAND1 = T001-LAND1)

BSIK-ZTERM

Payment Term

Drop down value. Exist as valid 4S Payment Term (T052-ZTERM where T052-KOART = Blank or ‘K’)

BSIK.ZFBDT

Baseline Date

Business to enter content as per data type and length permitted as per section 3. The Baseline Date will determine the calculation of Payment Due Date (Days in Payment Term + Baseline Date = Payment Due Date)

ACDOCA-RASSC

Company ID of Trading Partner

Drop down value. Exist as valid 4S Trading Partner (T880-RCOMP)

ACDOCA-ZUONR

Assignment Number

Business to enter content as per data type and length permitted

BSEG-LZBKZ

SCB Indicator

Business to enter content as per data type and length permitted

BKPF- XREF1_HD

Reference field 1 (header)

Business to enter content as per data type and length permitted

BKPF- XREF2_HD

Reference field 2 (header)

 Business to enter content as per data type and length permitted

BSIK – KIDNO

Payment reference

Business to enter content as per data type and length permitted

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

3.      

Reconciliation of migrated Purchase Order is completed before the extraction of Accounts Payable Open Items

Business and Data

1.      

Ensure all the fields that require value mapping, as stipulated  Mapping tables, have the latest signed-off mapping files imported into dspMigrate.

Data team

2.      

In tool, select the AP Open Items object.

Data team

3.      

Go to Process Area Launch and Process the Object - AP Open Items - R3 AP 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