EAP 9.2: Single Payment Voucher Placed In Entry Status Recycle Disabling Submit For Approval Button Once FSCM 9.2 Image #25 Is Implemented
Last updated on DECEMBER 15, 2017
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
After completing a systems upgrade to PeopleSoft Enterprise FSCM 9.2 Image #25, it has been detected by the Payables Functional Team that upon creating a brand new Single Payment Voucher transaction in the system, once saved into the system, the Entry Status is placed automatically into Recycle. This prevents the system from displaying the 'Submit For Approval' button at the Invoice Information and Voucher Attributes tabs, in the eventuality that approval workflow is required.
1.- Have an environment patched up to FSCM 9.2 Image #25
2.- Log into the FSCM Online Application as User ID VP1
3.- Navigate to: Account Payable > Vouchers > Add/Update > Regular Entry
4.- Go to the Add A New Value tab, and define the below values:
- Business Unit = US003
- Voucher ID = NEXT
- Voucher Style = Single Payment Voucher
- Supplier ID = SINGLE
- Invoice Number = SINGLEVCHRTEST
- Invoice Date = Today's Date
- Gross Invoice Amount = 100 USD
5.- Click on the ADD button
6.- Proceed to fill in the tab 'Single Payment Supplier' as follows:
- Supplier Name = OSS Test
- Country = USA
- Address 1 = Fifth Avenue 100
- City = New York City
- County = New York County
- Postal = 10010
- State = NY
7.- Click on the SAVE FOR LATER button
8.- Go to the 'Invoice Information' tab
9.- At the Invoice Distribution Line section, define the below values:
- GL Unit = US003
- Account = 610000
10.- Click on the SAVE button
11.- Notice that the 'Submit For Approval' button is not being displayed in the Invoice Information tab, next to the Print button, as it should
12.- At the Voucher Attributes tab, the 'Submit For Approval' button is also not available
13.- Checking the Summary tab, the Voucher's Entry Status is 'Recycle'
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.
As long as the Single Payment Voucher is stored in the system with an Entry Status of 'Recycle', the transaction will not be eligible for submission in approvals. The Users are forced to modify something on the transaction, and re-save it, so that the Entry Status becomes Postable.
The transaction's Entry Status of such Single Payment Voucher should be placed in Postable from the beginning, if there are no issues found upon saving it during the time of its creation.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms