Last updated on MARCH 21, 2016
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 8.9 to 9.1 [Release 8.9 to 9]
Information in this document applies to any platform.
***Checked for relevance on 31-JAN-2011***
***Checked for relevance on 26-SEP-2012***
***Checked for relevance on 28-AUG-2014***
***Checked for relevance on 21-MAR-2016***
When source transactions that are budget checked, pass budget checking with a status of 'V' for valid, a row for each source transaction accounting line gets written to KK_SOURCE_HDR, then KK_SOURCE_LN, then KK_ACTIVITY_LOG and finally LEDGER_KK.
When source transactions that are budget checked get a status of 'E' for error, a row for each source transaction accounting line gets written only to KK_SOURCE_HDR and does not get written to the remaining 3 KK log tables.
If a situation occurs in which a source transaction has been budget checked and you find rows only in KK_SOURCE_HDR and KK_SOURCE_LN, not in KK_ACTIVITY_LOG nor LEDGER_KK, there is a delivered workaround to get rows generated to KK_ACTIVITY_LOG and LEDGER_KK.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms