EAP: Supplier Contract Release Amounts not updated after Contract Voucher is Closed (Doc ID 1919616.1)

Last updated on MARCH 18, 2016

Applies to:

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

Symptoms

The Release Amount of a Supplier Contract is not adjusting back to the original value after the Released Contract Voucher generated from it is Closed in the Accounts Payable module. Additionally, the closed Contract Voucher remains listed as Completed in the Supplier Contract, which prevents the users from staging a new Release for the same date since a Warning Message is triggered:

WARNING MESSAGE
Release dated YYYY-MM-DD already exists for Business Unit XXXXX. (10400,304)

Similar scenarios have been raised in <Bug 12345599> and <Bug 17396381>, for Release Contract Vouchers being deleted. In this scenario though, the Voucher, which could be initially paid and later on voided, got eventually closed.

STEPS
1.  Log into the FSCM Online Application as User ID VP1
2.  Navigate to: Supplier Contracts > Create Contracts and Documents > Contract Entry
3.  Create a new General Contract for an amount of 10,000 USD
4.  Add all the needed values in the Voucher Contract Options section, for 5,000 USD amount, and proceed to complete the Line Items data
5.  Save the changes
6.  At the Create Release tab, select the Release Option of 'Create Voucher', and fill in the needed remaining values
7.  Click on the STAGE button to create the Release Voucher data
8.  Navigate to: Accounts Payable > Batch Processes > Vouchers > Voucher Build
9.  Run the process, having at the Run Control ID the data from Business Unit, Contract ID, and the build the released Voucher
10.  Navigate to: Supplier Contracts > Create Contracts and Documents > Contract Entry
11.  Go to the 'Review Releases' tab, and confirm that the Voucher ID is in Complete status
12.  Navigate to: Accounts Payable > Batch Processes > Voucher > Voucher Post
13.  Run Voucher Post for the created transaction, to generate the ACCRUAL Accounting Entries
14.  Navigate to: Accounts Payable > Payments > Pay Cycle Processing > Payment Selection Criteria
15.  Create a new Pay Cycle to target the newly created AP Voucher
16.  Navigate to: Accounts Payable > Payments > Pay Cycle Processing > Pay Cycle Manager
17.  Open the newly created Pay Cycle ID, and run Payment Selection, Payment Creation, Printing of Checks, until the Pay Cycle is Complete
18.  Navigate to: Accounts Payable > Batch Processes > Payment > Payment Posting
19.  Run the Payment Post process for the newly generated Voucher Payment, to create the PAYMENT Accounting Entries
20.  Navigate to: Accounts Payable > Payments > Cancel/Void Payments > Payment Cancellation
21.  Open the generated Payment, and select VOID and Do Not Reissue/Close Liability options
22.  Navigate to: Accounts Payable > Batch Processes > Payment > Payment Posting
23.  Run the Payment Post process for the newly generated Voucher Payment, to create the CANCEL Accounting Entries
24.  Navigate to: Accounts Payable > Vouchers > Add/Update > Close Voucher
25.  Open the affected Release Voucher, mark it for Closure, and save the changes
26.  Navigate to: Accounts Payable > Batch Processes > Voucher > Voucher Post
27.  Run Voucher Post for the created transaction, to generate the CLOSURE Accounting Entries
28.  Navigate to: Supplier Contracts > Create Contracts and Documents > Contract Entry
29.  Open the Supplier Contract created
30.  In the Contract tab, the Line Released and Total Released Amount fields still show 5,000 USD, when it should be 0 USD
31.  In the Review Releases tab, the closed Voucher ID is still displayed as Completed

EXPECTED RESULT:
The AMT_LINE_RELEASED field value in PS_CNTRCT_LIN_RLS table should become zero, where the value should be reduced to the extent of the Amount on the closed Voucher. Also, the Released Voucher ID should change its status from Completed to Closed, and thus allowing the Users to stage a new Contract Voucher for the same period of time if need to be.
 

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