Accounting Date Requested When Updating a Blanket Purchase Agreement in BWC with Encumbrance 'No'
(Doc ID 1353030.1)
Last updated on APRIL 23, 2019
Applies to:
Oracle Purchasing - Version 12.1.1 and laterInformation in this document applies to any platform.
Symptoms
On 12.1.1
Setup with :
- Primary and a Secondary Ledger
- Contract Commitment used with Dual budgetary control (BC against 2 Budgets)
- Enable Dual budgetary control for CC = Y
- Enable Dual budgetary control for PO = Y
While creating a new Blanket Purchase Agreement from Buyer Work Center > Agreements, can see incoherent defaulted information and controls :
Test A :
1) Create a BPA with one line
2) the reserve option is set to no
3) When Submitting the BPA, an accounting date is requested
But this is unexpected because in this case the contract should not be checked! The contract does get approved but will not have reservation.
Test B:
1) Create a BPA
2) Reserve option is set to yes.
This will require a budget account and a gl date
3) When Submitting the BPA, an accounting date is also requested
This is also unexpected because it already had to enter a gl date in the options tab. There will be a check and in this case the contract gets approved and also reserved.
ERROR
-----------------------
Accounting date requested
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Go to Purchasing responsibility
2. Navigate to Buyer Work Center > Agreement
3.Test A
- Create a BPA with one line
- the reserve option is set to No
- When Submitting the BPA, an accounting date is requested
3.Test B:
- Create a BPA
- Reserve option is set to Yes.
This will require a budget account and a gl date
- When Submitting the BPA, an accounting date is also requested
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |