EEX 9.1+: Double Encumbering Or Liquidating When Budget Checked Multiple Times (Doc ID 2288619.1)

Last updated on JULY 21, 2017

Applies to:

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

Symptoms

Double encumbering or liquidating when budget checked multiple times.

ACTUAL BEHAVIOR
---------------
Double encumbering or liquidating when budget checked multiple times.

EXPECTED BEHAVIOR
-----------------------
Double Encumbering Or Liquidating should not happen when budget checked multiple times.


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

(1) Create a Travel Authorization with one line, budget check, and approve it.
(2) Create an Expense by applying the Travel Authorization but delete the line brought in by the Travel Auth and instead enter a new line on the Expense (This is to trigger liquidation to occur on the Travel Auth).
(3) Submit for approval and budget check (use either FS_BP or EX_BCHK_ALL) - see KK_LIQUIDATION and KK_ACTIVITY_LOG on the Travel Auth pay attention to KK_FINAL flag and MONETARY_AMOUNT and AMOUNT on Activity. It will all look correct
(4) Login as approver and open the report, make sure not to approve the report. Make a change on the Expense by adding a line or increasing the current line amount and but this time use EX_BCHK_ALL to re-budget check. (DO NOT USE FS_BP) - see the change to KK_LIQUIDATION pay attention to KK_FINAL flag is changed back to N and MONETARY_AMOUNT goes from zero back to liquidation amount.
(5) Login as manager and Make another change to the Expense by adding a line or increasing the current line amount (do not approve) and re-budget check using EX_BCHK_ALL (DO NOT USE FS_BP)- see the change to KK_LIQUIDATION fields they will not change but see the liquidation that has occurred on the KK_ACTIVITY_LOG it will have doubled.
(6) Make a change to the Expense by adding a line or changing the amount and re-budget check again using EX_BCHK_ALL (DO NOT USE FS_BP) see the KK_ACTIVITY_LOG liquidation would have tripled.
Liquidation just keeps increasing incrementally every time EX_BCHK_ALL is used to re-budget check.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Liquidation just keeps increasing incrementally every time a re-budget check is required.

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