My Oracle Support Banner

E1: 03B: Statistical History Refresh (R03B16A) Incorrectly Includes Paid Late Negative Amount Invoices and Paid Late Chargebacks, and Any Standalone Chargebacks in the Amount Paid Late (AIPL) Calculation (Doc ID 2893954.1)

Last updated on FEBRUARY 28, 2023

Applies to:

JD Edwards EnterpriseOne Accounts Receivable - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When Statistical History Refresh (R03B16A) is run, it incorrectly includes standalone chargebacks and negative amount invoices and negative amount chargebacks in the calculation of the Paid Late Amount (AIPL) field.

Credit memos should not be included in the Paid Late Amount calculation, as per Chapter 32/Appendix C in the Accounts Receivable Implementation Guide for release 9.2, section ‘Mapping Fields in the A/R Statistical History Table (F03B16)’:

 

Field Name

Alias

Definition

Paid Late Amount

AIPL

Sum of receipt pay item payment amounts where the G/L date of the receipt pay item is greater than the due date of the invoice it is paying. Invoice credit memos are not included in these calculations.

Standalone chargebacks are not specifically mentioned but it does state that it is about invoices being paid. Standalone chargebacks are not invoices at the time when they are created, so they should not be included. See also the final dispositions of the following bugs:

See also the following in KM article E1: 03B: How To Calculate Statistical History Update Fields (P03B16, R03B16, R03B16A) (Doc ID 656325.1):

Paid Late Amount (AIPL) 

A/R Statistical History table (F03B16) - This is the sum of the F03B14 Payment Amount (PAAP) field for records where:

 

STEPS TO REPRODUCE

  1. P03B11: create invoices and credit memo as follows:
    1. 1st invoice (RI) for 1,000,00 with date in March.
    2. 2nd invoice (RI) for 500.00 with date in April.
    3. 3rd invoice (RI) for 500.00 with date in June.
    4. 4th invoice (RI) for 250.00 with date in May.
    5. 5th invoice (RI) for 100.00 with date in June.
    6. 6th invoice (RI) for 300.00 with a date in June.
    7. create a credit memo (doc type RM) for -250 with a date in March.
    8. create a negative invoice (doc type RI) for -125.00 with a date in February.
  2. R09801: post the invoices and credit memo.
  3. P03B102: create a receipt in March for the March invoice for 1200, create negative 200 chargeback for the overpayment.
  4. R09801: post the receipt.
  5. P03B102:
    1. create a receipt in June for 400 and match it to the two June invoices (3 and 5). Create a standalone positive 200 chargeback for the difference.
    2. create another receipt in June for 300 and match it to the April invoice to it as well as the neg. 200.00 chargeback.
    3. create a zero-amount receipt with a date in June and match the May invoice to the credit memo.
    4. Create a receipt in June for 175.00 and match the negative RI from February and the 3rd June invoice (no. 6) to the receipt.
  6. R09801: post the receipts.
  7. P03B08: make sure that C&C patterns are set up for at least company 00000
  8. BV: set up a version of R03B16A with following PO settings:
    1. DSO tab:
      1. 1
      2. 3
    2. Calculations tab:
      1. 1
      2. 1
    3. Summary Record tab:
      1. 0/blank
      2. 0/blank
  9. Run the new R03B16A version
  10. Databrowser: get the records for the customer from the following tables:
    1. F03012
    2. F03B11
    3. F03B13
    4. F03B14
    5. F03B08
    6. F03B16
    7. F03B16S
  11. Note that the F03B16 value for June for AIPL is 225.00- which means it includes the negative RI from February, the negative RB from March, and the standalone RB created in June.

  

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.