EAP 9.2: Two Consecutive AP_PSTVCHR Runs From AP WorkCenter On Same Voucher Set It As Posted, Although No Accounting Entries Are Created
(Doc ID 2196061.1)
Last updated on OCTOBER 01, 2018
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
It has been detected that at the Accounts Payable WorkCenter level, a User can select a Voucher ID that is ready for posting, and consecutively launch two different Voucher Post runs (AE Program AP_PSTVCHR) for the same transaction. This seems to corrupt the transaction, as while it places the Voucher Post Status into a value of 'P' (Posted), the system does not generate any Accrual Accounting Entries at all.
1.- Log into the FSCM Online Application as User ID VP1
2.- Navigate to: Accounts Payable > Vouchers > Add/Update > Regular Entry
3.- Create a brand new Voucher transaction, and save it, so its Status is Postable
4.- Navigate to: Accounts Payable > Accounts Payable WorkCenter
5.- In the 'My Work' section, click on the link named: Vouchers Ready for Posting
6.- Search for the Voucher ID just created, and select it
7.- At this stage, follow the below sequence of steps, as quickly as possible: (make use of one hand with the mouse, and the other with the ENTER key from the Keyboard, to speed through the steps)
a) Position the Mouse right on top of the RUN VOUCHER POSTING button, and click it
b) Click the ENTER key on the keyboard for the pop-up message displayed: " Voucher Posting Request has been launched with Process Instance Number XXXXXX (7055,58) "
c) Having the Mouse cursor still on top of the RUN VOUCHER POSTING button, select it once again.
d) Finally, again press the ENTER key, to ok the second pop-up message: " Voucher Posting Request has been launched with Process Instance Number ZZZZZZ (7055,58) "
8.- Navigate to: PeopleTools > Process Scheduler > Process Monitor
9.- Notice that there will be 2 AP_PSTVCHR AE Program runs, with each its own Process Instance number (XXXXXX, and ZZZZZZ)
10.- Once completed, one of the Process Instances will have a status of WARNING, with the following message: " Some Vouchers were not posted because they were being processed by other process. "
11.- The other Process Instance would have a Status of SUCCESS, with a normal Message Log, as if everything went fine
12.- Navigate to: Accounts Payable > Vouchers > Add/Update > Regular Entry
13.- Open the Voucher ID in question
14.- At the Voucher Summary page (VCHR_SUMMARY_PG), confirm that the Voucher Post Status is POSTED (PS_VOUCHER.POST_STATUS_AP = 'P')
15.- From the View Related drop down list, select the value of: Accounting Entries Inquiry
16.- Click on GO link
17.- This opens a new Window for the Voucher Accounting Entries page (VCHR_ACTG_ENTRIES)
18.- While the Voucher ID and Business Unit values are automatically pre-populated, there are no Accounting Entries being generated
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.
The Voucher Post Status is set to Posted (PS_VOUCHER.POST_STATUS_AP = 'P'), as such, the Voucher Post action can no longer be triggered for this transaction whether On Demand, or via the Voucher Posting Run Control ID batch process. The Voucher Accrual Accounting Entries are missing, and the transaction is corrupted at this stage.
If a User launches the Voucher Post Application Engine Program (AP_PSTVCHR) multiple times for the same Voucher ID from the Accounts Payable WorkCenter, the system should at least have one of the Process Instances complete properly, and generate the needed Accounting Entries, and place all remaining Process Instance requests in Warning, or issue an Error Message at WorkCenter level just after lunching the second Voucher Post run informing the User that one of the selected Vouchers is already being processed, identifying which one, so it can be un-selected.
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