My Oracle Support Banner

EAR: Collected Amount Is Overstated in the AR_CC_TRAN_TBL Table When a Payment Is Applied (Doc ID 2654718.1)

Last updated on JULY 22, 2020

Applies to:

PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Collected Amount Is Overstated in AR_CC_TRAN_TBL When a Payment Is Applied

This scenario is for transactions in Project Costing (PC) that are sent to Billing (BI) and Accounts Receivable (AR). If no revenue has been posted to GL from Contracts for those transactions, the user cannot apply a payment for the billed item in AR but instead gets an error. However, if there are multiple distributions for the transactions and some but not all have revenue recognized, journal generated and posted from Contracats, the payment can be applied in AR. The problem is that this then allows the total collected amount to be applied with though only some of the distribution lines have been recognized. If there are multiple projects, then amounts can be applied to a single project instead of being spread across multiples so some projects may be overstated and others understated.

The fix for Bug 28777322 - COLLECTED AMOUNT IS OVERSTATED IN AR_CC_TRAN_TBL WHEN A PAYMENT IS APPLIED should have resulted in a warning message when applying a payment in this scenario but this scenario was not considered.

Replication Steps

  1. Configure the Billing BU to use AR Level = Header and AR Option = Line for Distribution. Commitment control is enabled for BI, AR, PC
  2. Create a contract with a rate-based line. Assign two different projects to the line.
  3. Add cost transactions to each project.
  4. Run As-incurred billing in contracts to bill the transactions.
  5. Go through billing cycle to generate a single invoice for the transactions.
  6. Update the contract to remove a project from the line (use case would be to assign to a different contract line).
  7. Run As-incurred revenue recognition PSA_ACCTGGL for the contract. This generates CA_ACCTG_LN_PC entries for transactions for only one of the two projects.
  8. Run journal generator and post the accounting lines for CAPCDEFN.
  9. Run ARUPDATE for the invoice from Billing.
  10. Create a deposit for the invoice.
  11. Create a worksheet and apply payment.
  12. Run ARUPDATE.

 

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.