EAR 9.2: AR_UPDATE Reset Process Feature Not Clearing PS_WS_CONTROL.PROCESS_INSTANCE Record Field For Abended Maintenance Groups
(Doc ID 2486093.1)
Last updated on DECEMBER 01, 2020
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
It has been noted that after using the Reset Process functionality on abended ARUPDATE Jobs, the PROCESS_INSTANCE field gets properly cleared up on any stuck transactions such as Payment Worksheets, Transfer Worksheets, Pending Item Groups, Unpost Groups, and alike, with the only exception of Maintenance Groups. The Record Field PS_WS_CONTROL.PROCESS_INSTANCE does not get cleared up, when it should.
- Accounts Receivable > Receivables Update > Reset Process
This is because of all 13 delivered SQL Statement instructions in Record PS_AR_RESETSQL_TBL for Process ARUPDATE, none involves Table PS_WS_CONTROL.
1.- Log into the FSCM Online Application as a Receivables User
2.- Create a new Maintenance Worksheet to write off an existing Item
3.- Set the balanced Maintenance Worksheet into a Post Status of Batch Standard
4.- Launch AR Update with the Maintenance option selected
5.- Have ARUPDATE Job abend with an Error Message, and going to No Success
6.- Query Record PS_WS_CONTROL for the Maintenance Group ID, and confirm that the PROCESS_INSTANCE Field is not '0', and contains the value of the Process Instance abended in this AR Update run
7.- Go to the Reset Process page (Accounts Receivable > Receivables Update > Reset Process)
8.- Identify from the listed abends, the ARUPDATE in question that went into No Success
9.- Click on the available RESET button
10.- Query once again the Table PS_WS_CONTROL for the Maintenance Group ID, and notice that the Field PROCESS_INSTANCE still has a value different than the expected '0'
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word 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