My Oracle Support Banner

EAR 9.2: AR Update Ignores All Transactions To Be Processed if One Customer Is Detected To Have Process Instance Different Than 0 Due to a Prior Abend, and Run Control ID Uses ‘Post All Business Units’ Option (Doc ID 2914554.1)

Last updated on DECEMBER 08, 2022

Applies to:

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


If an initial run of AR Update has ended up in No Success, the transactions and Customers that were being handled will be left with a Process Instance value different than 0 in the main Receivables Records. If this does not get addressed immediately, and new runs of AR Update are being launched with the 'Post All Business Units' check-box selected at the Run Control ID level, if the system detects one of those locked Customer instances, it will display in the Message Log an informative statement clarifying that for a particular Business Unit, a Customer was identified having a Process Instance value different than zero, and as such, their transactions were not handled, though other Customer's transactions, and Business Units should be fine.

However, AR Update does not post anything from non-affected Customers and Business Units.


    1.- Log into the FSCM Online Application as a Receivables User
    2.- Create a new Pending Item Group for Customer ID 1000, under Business Unit US003, and place the Post Action to Batch Standard
    3.- Launch AR Update for Business Unit US003, and option of 'Pending Items' selected
    4.- For whatever reason, the AR Update ends in Error Message, with a No Success
    5.- Create a new Pending Item Group for Customer ID 1005, under Business Unit US001, and place the Post Action to Batch Standard
    6.- Launch AR Update with a Run Control ID containing the 'Post All Business Units' check-box selected, including Business Units US001 and US003
    7.- AR Update PSJob has completed in Success, but nothing is posted with new Accounting Entries
    8.- Check the AR Update PSJob Message Log, and confirm the informative line regarding the locked Customer, but that all others should be processed fine

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.





To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.