EAR9.1: Unposting of a Payment That Encountered a Budget Error not Deleting Lines From Child Tables. (Doc ID 1937521.1)

Last updated on OCTOBER 24, 2014

Applies to:

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

Symptoms

On : 9.1 version, Revenue Estimate & Commit Control

ACTUAL BEHAVIOR
---------------
If the budget error is not rectified prior to the unpost of the payment, code during the revenue estimate AR_REV_EST process will delete the KK_SOURCE_HDR record for the original payment, leading the payment to have a "No Effect" status, but the unpost to be in Error.

EXPECTED BEHAVIOR
-----------------------
If the row has been deleted from KK_SOURCE_HDR it should also get deleted from child record KK_SHDR_ARRVEST and KK_SOURCE_LN.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

  1. Create an item and post it and make sure commitment control is active.
  2. Now close the budget and create payment and apply it.
  3. System will give budget status as error.
  4. Unpost the payment worksheet.
  5. The rows gets deleted from KK_SOURCE_HDR but it is present in KK_SHDR_ARRVEST and KK_SOURCE_LN.


BUSINESS IMPACT
-----------------------
The issue is that the revenue estimate that is in error is now going to be out in the system forever as an error on the AR_CC_TRAN_ERROR component search page until both lines are fixed through a manual SQL updated. Once that happens, when data is loaded into the Oracle Business Intelligence (OBIEE) solution, rows on tables are missing, namely KK_SOURCE_HDR. If these were really "no effect," shouldn't they then not show up as an error under the Revenue Estimate?

Also, why would any database delete a header row and leave the children and sibling rows behind? Because that is what is happening - KK_SHDR_ARRVEST and KK_SOURCE_LN table information is still present AFTER the delete of the associated KK_SOURCE_HDR row. Maybe my understanding of the table structure here is incorrect, but it seems that the SOURCE_HDR is the Parent table, KK_SHDR_ARRVEST is a subordinate sibling, and the KK_SOURCE_LN is the child.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms