EGL9.2:When Budget Check (either FS_BP, FS_STREAMLINE, or EX_BCHK_ALL) is Run in Parallel with Base Tables, There are Ledgers that are Being Skipped or Missed. (Doc ID 2284536.1)

Last updated on AUGUST 09, 2017

Applies to:

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

Symptoms

Issue:

Commitment Control 'skipping' or 'missing' Ledgers when updating KK
When running budget check (either FS_BP, FS_STREAMLINE, or EX_BCHK_ALL, when they are running in parallel with Base Tables, there are ledgers that are being skipped/missed.
Note:  This is an issue exclusively when running in parallel, and hitting base tables. 
This is causing the program to proceed down different paths when base tables, and multiple processes running at the same time.

-- 13:09:46.261 ................(FS_BP_XLAT.Process.KeyCFs) (Do Select)
%SelectInit(FS_BP_XLAT_AET.SUBTYPE) SELECT DISTINCT SUBTYPE FROM
PS_BP_XCF_TAO XCF1 WHERE PROCESS_INSTANCE = 3813653 AND NOT EXISTS ( SELECT
'X' FROM PS_BP_XCF3_TAO XCF3 WHERE XCF1.SUBTYPE = XCF3.SUBTYPE)

There is no binding in this step for the "NOT EXISTS" based on the process instance number.


What's working:

If it's not hitting base tables, then it is not an issue.


Steps to replicate:

Running budget check (either FS_BP, FS_STREAMLINE, or EX_BCHK_ALL)
When they are running in parallel with Base Tables, there are ledgers that are being skipped/missed.

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