Budget Checking Error: FS_BP_STAO.GetPrior.GetPrior (SQL) -- RC = 8601 (108,524)

(Doc ID 1335756.1)

Last updated on AUGUST 11, 2017

Applies to:

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

Symptoms

Release 9.0Release 9.1
After applying SCM 9 Bundle 32 (Maintenance Pack 14) when budget checking a PO, received the following Budget Checking error: FS_BP_STAO.GETPRIOR.GETPRIOR

After applying SCM 9 Bundle 32 and FMS Financials 9 Bundle 32, application engine process PO_UPDEESEQ must be run to populate the new EE_SEQ_NUM field on the PO_HDR and PO_LINE_DISTRIB and KK_SOURCE_LN records.

This process does not populate the field for PO transactions that are closed or canceled, including such PO's that have non-valid budget status.

After running the process, when these PO's are budget checked, it causes FS_BP to abend at Step FS_BP_STAO.GetPrior.GetPrior with the error Subquery returned more than 1 value.

After applying SCM 9.1 Bundle 12, when budget checking a PO, received the following Budget Checking error: FS_BP_STAO.GETPRIOR.GETPRIOR.

After applying SCM 9.1 Bundle 12 and FMS Financials 9.1 Bundle 12, application engine process PO_UPDEESEQ must be run to populate the new EE_SEQ_NUM field on the PO_HDR and PO_LINE_DISTRIB and KK_SOURCE_LN records.

This process did not populate the field for PO transactions that were closed or canceled, including such PO's that have a non-valid budget status.

After running the process, when these PO's are budget checked, it causes FS_BP to abend at Step FS_BP_STAO.GetPrior.GetPrior with the error Subquery returned more than 1 value.

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