My Oracle Support Banner

List Of Code Fixes - Encumbrance - Setup And Usage (Doc ID 1198703.1)

Last updated on AUGUST 23, 2017

Applies to:

Oracle Purchasing - Version 11.5.10.2 to 12.1.2 [Release 11.5 to 12.1]
Information in this document applies to any platform.

Details

This document is a 'Master Code Fix Note' which consolidates all the code fixes done in the problem category "Encumbramce - Setup And Usage".

For similar such notes refer to the Master Note matrix,
Note 1138043.1 Master Note For Oracle EBS Procurement Suite - Encumbrance And Receipt Accounting

Code fix note lists the following details for the fix in a tabular format.

* Release version applicable to
* Symptom for the issue fixed
* Bug number
* Root cause
* Patch number released
* Relevant file versions upgraded in the patch
* Post patch behaviour

This document will be updated with all these details whenever a new code fix is done in the problem category.

Actions

Whenever you get an issue related to the problem category 'Encumbrance - Setup and Usage',

1) Match your issue with the symptoms listed in the table below. The patch mentioned in the column, ' Patch number', for the record will fix the symptom mentioned.
Apply the patch in a test instance first and verify if this resolves your issue.

2) The note also contains the latest code fixes/ file versions available for the problem area discussed.
If you are unable to match your problem with the symptoms listed on the table below, verify your file versions with the versions available on the table given in the end for the respective application release. Apply the latest fix patch(es) mentioned on the table in a test instance and check if this resolves your issue.
It is always recommended that customer upgrade to lastest versions of code when ever possible to avoid running into issues already fixed.

3) If the above actions do not resolve your issue, please log a Service Request with Oracle Support for assistance.

S. NoReported Release VersionSymptoms      Bug numberBug AbstractRoot CausePatch numberFixed file version / File version upgraded by the patch suggestedBehavior after patch application
1 12 & 12.1 GL date is enabled for PO distributions having Shopfloor destination. While changing the GL date, system throws the error "The accounting date is not in an
open encumbrance period". But system should not validate the GL period when the destination
type is Shop floor as shop floor destination POs do not support
encumbrance as per the intended design
<Bug.8326256> GL DATE IS ENABLED FOR PO WITH SHOP FLOOR DESTINATION Code limitation in files POXPODIS.pld and POXVDCKB.pls <Patch.8326256:R12.PO.A> for R12 & <Patch.8326256:R12.PO.B> for 12.1

(Patches not distributed in Metalink. Please raise one off to get standalone patch)
POXPODIS.pld -120.23.12000000.26;
POXVDCKB.pls 120.48.12000000.26 for R12 & POXPODIS.pld - 120.34.12010000.8; POXVDCKB.pls -120.64.12010000.14
GL date cannot be entered and will not be validated if the PO has Shopfloor destination
2 12.1 When the 'Reserve at Completion' flag is enabled in the Financial Options, the user should be able to reserve a Requisition or Purchase Order after it is created.  However, if the 'Owner Can Approve' flag is disabled in the Document Types form, the user is unable to reserve the document before submitting it for approval.  The 'Reserve' box is not enabled.

<Bug.8520350>

'RESERVE AT COMPLETION' DOES NOT WORK IF 'OWNER CAN APPROVE' IS DISABLED

This was previously considered to be the standard functionality as documented in the Oracle Purchasing User's Guide Release 12, p. 1-68 Development has changed this, as some customers have business requirements to reserve funds at the time of submission and not at the time of approval. This was addressed by Oracle Development in <Bug 8520350> - "'RESERVE AT COMPLETION' DOES NOT WORK IF 'OWNER CAN APPROVE' IS DISABLED".

<Patch.8520350:R12.PO.B> for 12.1 & <Patch. 8658242:R12.PRC_PF.A> for R12

[POXAPAPC.pld 120.18.12010000.6
POXWPA1B.pls 120.56.12010000.8] for 12.1 & [POXAPAPC.pld -120.11.12000000.10
POXWPA1B.pls - 120.46.12000000.25] for R12
Reserve at completion flag will not depend on the 'owner can approve' flag setting

3 11.5.10.2,
R12 &12.1
While attempting to change the GL date to re-approve the PO with Shop floor destination , the following error occurs:

ERROR
-----------------
Please Enter a valid Date.
cause: Budget Account is not valid for this new GL Encumbered Date
.
Action: Please Enter a valid GL Encumbered Date , Budget Account Combination

It is not possible to alter the GL date on a PO or release with SHOP FLOOR
destination type due to budget account validation.

<Bug.8254650>

UNABLE TO APPROVE BLANKET PURCHASE ORDER RELEASES

In POXPODIS.pld, there was a validation on budget account when ever the GL date was changed irrespective of the destination type

<Patch.7189206> for 11.5.10 & <Patch.8254650:R12.PO.A> for R12 & <Patch.8222606:R12.PO.B> for 12.1


POXPODIS.pld - 115.152.11510.36 for 11.5.10 & POXPODIS.pld - 120.23.12000000.22 for R12 &
POXPODIS.pld - 120.34.12010000.5 for 12.1


It is possible to alter the GL date in a PO or release with SHOP FLOOR destination type without this error

4 11.5.10.2 System is not allowing to change the GL Date in an unreserved PO, which was Billed and Invoiced.

<Bug.7302701>

PATCH 6840188 HAS MISSED DEPENDENCIES.

The call to the function PO_DISTRIBUTIONS_C14.IS_CHARGE_ACCOUNT_ALTERABLE in the procedure PO_DISTRIBUTIONS_C20.GL_ENCUMBERED_DATE is disabling the GL Date field in PO distributions, for an unreserved PO, which was received and Invoiced.

<Patch.8555411> - PRC Rollup 11

POXPOEPO.fmb -115.445.11510.44
POXPOERL.fmb - 115.243.11510.40
POXPOEPO.pld - 115.217.11510.14
POXPOPOS.pld - 115.232.11510.10
POXPODIS.pld - 115.152.11510.33
POXRQDIS.pld - 115.80.11510.11
pomsg.ldt - 115.222.11510.54
popch80.sql - 115.4.11510.2

GL Date in PO Distributions will be editable

5 11.5.10.2 When creating a Purchase Order, if the buyer populates project information under the Project tab of the Distributions form and then performs a Save, the GL Date field under the Destination tab (which was previously populated) goes null. If the buyer has not entered multiple distributions, he/she is able to re-populate the GL Date field and save. However, if the buyer enters multiple distributions, the GL Date fields are grayed out and are not updateable.
If, prior to accessing the Project tab, the buyer clicks in the GL Date field and then proceeds to the Project tab and populates the project information, the GL Date field does not go null upon performing a Save

<Bug.7275529>


PO ENTRY SCREEN BLANKS OUT GL_DATE WHILE SAVING PROJECT RELATED DISTRIBUTIONS.

Code limitation in file POXPODIS.pld <Patch.8555411> - PRC Rollup 11

POXPOEPO.fmb - 115.445.11510.44
POXPOERL.fmb - 115.243.11510.40
POXPOEPO.pld - 115.217.11510.14
POXPOPOS.pld - 115.232.11510.10
POXPODIS.pld - 115.152.11510.33
POXRQDIS.pld - 115.80.11510.11
pomsg.ldt - 115.222.11510.54
popch80.sql - 115.4.11510.2

System allows to change the GL Date in an Autocreated PO, which has Project related distributions.

6 12.0.4 Reservation is happening for the Requisition lines sourced to a BPA, for the
requisitions created from Req Import

<Bug.7234465>

TST1204: RESERVATION IS NOT HAPPENING CORRECTLY WHILE RUNNING THE REQ IMPORT.

In the procedure PO_AUTOSOURCE_SV.reqimport_sourcing, we are not setting the Prevent Encumbrance Flag on the Req distributions based on whether the Source Document is already Encumbered or Not.

<Patch.8427508:R12.PO.A>

POXSRCDB.pls - 120.17.12000000.14

Requisitions sourced to an Encumbered Blanket Purchase Agreement won't be Reserved.

7 11.5.10.2 Try to approve partially received, unreserved POs having GL date on them not within an open period it shows error. GL date field is greyed out. POs remain stuck in requires reapproval state

<Bug.6492476>

CAN UNRESERVE RECEIVED POS, CAUSE PO STUCK IN REQUIRE REAPPROVE STATUS

The check present in po_distributions_c14.is_charge_account_alterable rule 5 causes the gl date field to be greyed out when received quantity>0.

<Patch.6840188>

POXPOEPO.fmb - 15.445.11510.44
POXPODIS.pld - 115.152.11510.28

GL date field will not be grayed out

8 11.5.10.2 & R12 Funds check and encumbrance accounting validates the accounting period to be in "open" or "future
enterable"

<Bug.5206339>

GL FUNDS CHECK AND ENCUMBRANCE ACCOUNTING SHOULD NOT REQUIRE OPEN GL PERIOD

Enhancement implementation

<Patch.5702204> for 11.5.10.2 & <Patch.5498063:R12.PO.A> for R12

[POXCOC1B.pls 115.43.11510.6
POXCOC1S.pls 115.20.11510.2
POXCOPEB.pls 115.7.11510.2
POXENC1B.pls 115.54.11510.4
POXVDCOB.pls 115.29.11510.8
POXWPA9B.pls 115.8.11510.4
POXDOCON.pld 115.108.11510.8
poxrmc.lpc 115.15.11510.5
pocis.opc 115.68.11510.8
pocca.lpc 115.59.11510.9
poprf.ldt 115.17.11510.13] for 11.5.10 & [poprf.ldt - 120.9.12000000.7
POXCOPEB.pls - 120.0.12000000.2
POXENC1B.pls - 120.15.12000000.2
POXVDCOB.pls - 120.30.12000000.9
POXWPA9B.pls - 120.0.12000000.4
POXDOCON.pld - 120.6.12000000.7
poxrmc.lpc - 120.2.12000000.13
pocis.opc - 120.14.12000000.14
pocca.lpc - 120.35.12000000.11
POXPORMC.pld - 120.0.12000000.2] for R12

New Validation changes for GL period in Purchasing: If the profile option "PO:Validate GL Period" is set to Yes only then
the GL period will be validated to be in "Open" or "future enterable" status.

9 11.5.10.2 Final close/Unreserve of PO/Release was allowed even when an invoice/debit memo was not validated

<Bug.5109231>

FCLOSE A PO BEFORE INV IS VALIDATED, DOES NOT RELIEVE PROJECT COMMITM--SR 29210

Unreserve/Finally Close Action on a Document was allowed, even when there are some unvalidated debit memos and/or Invoices related to that document.

<Patch.5109231> POXPOSCS.pls - 115.3.11510.2
POXPOSCB.pls - 115.10.11510.2
POXPOACB.pls - 115.32.11510.9
POXVDCKB.pls - 115.83.11510.19
poccc.lpc - 115.23.11510.2

Final close /Unreserve action will not be allowed if there is an unvalidated invoice.

10 11.5.10.2 The requisition failed funds check but gets forwarded to the next approver with status 'IN PROCESS'/'Pre-approved'.
The requisition should stay in status 'INCOMPLETE' due to the message 'Failed funds reservation'.

<Bug.4468933>

REQUISITION THAT FAILED FUNDS NOT REMAINING INCOMPLETE

The approval Check box was not unchecked after the funds check failure In procedure 'po_approve_c8.approve_doc' need to modify'if' condition so that the 'po_approve.approve' will be unchecked for the funds failure case.

<Patch.4468933> POXPOEPO.fmb - 115.445.11510.12
POXPOERL.fmb -  115.243.11510.15
POXRQERQ.fmb - 115.198.11510.8
POXAPAPC.pld - 115.156.11510.3

Purchasing documents will remain in INCOMPLETE status without getting forwarded to next level for approval if funds reservation fails

 

Release VersionLatest file versionPatch
11.5.10

POXPODIS.pld - 115.152.11510.36

POXAPAPC.pld - 115.156.11510.3

POXPOEPO.fmb - 115.445.11510.44
POXPOEPO.pld - 115.217.11510.14

POXPOERL.fmb - 115.243.11510.40
POXPOPOS.pld - 115.232.11510.10
POXPODIS.pld - 115.152.11510.33
POXRQDIS.pld - 115.80.11510.11

POXRQERQ.fmb - 115.198.11510.8 
pomsg.ldt - 115.222.11510.54
popch80.sql - 115.4.11510.2

POXCOC1B.pls 115.43.11510.6
POXCOC1S.pls 115.20.11510.2
POXCOPEB.pls 115.7.11510.2
POXENC1B.pls 115.54.11510.4
POXVDCOB.pls 115.29.11510.8
POXWPA9B.pls 115.8.11510.4
POXDOCON.pld 115.108.11510.8
poxrmc.lpc 115.15.11510.5
pocis.opc 115.68.11510.8
pocca.lpc 115.59.11510.9
poprf.ldt 115.17.11510.13

POXPOSCS.pls - 115.3.11510.2
POXPOSCB.pls - 115.10.11510.2
POXPOACB.pls - 115.32.11510.9
POXVDCKB.pls - 115.83.11510.19
poccc.lpc - 115.23.11510.2

<Patch.7189206>

<Patch.4468933>

<Patch.8555411> PRC Rollup 11

<Patch.4468933>

<Patch.5702204>

<Patch.5109231>

12.0.4

a) POXPODIS.pld - 120.23.12000000.26

b) POXAPAPC.pld -120.11.12000000.10 

b) POXWPA1B.pls - 120.46.12000000.25

c) POXSRCDB.pls - 120.17.12000000.14

d) poprf.ldt - 120.9.12000000.7 

d) POXCOPEB.pls - 120.0.12000000.2

d) POXENC1B.pls - 120.15.12000000.2 

d) POXVDCOB.pls - 120.30.12000000.9

d) POXWPA9B.pls - 120.0.12000000.4 

d) POXDOCON.pld - 120.6.12000000.7 

d) poxrmc.lpc - 120.2.12000000.13 

d) pocis.opc - 120.14.12000000.14 

d) pocca.lpc - 120.35.12000000.11 

d)POXPORMC.pld - 120.0.12000000.2

a) <Patch.8326256:R12.PO.A>

b) <Patch. 8658242:R12.PRC_PF.A>

c) <Patch.8427508:R12.PO.A>

d) <Patch.5498063:R12.PO.A>

12.1

a) POXPODIS.pld - 120.34.12010000.8

b) POXAPAPC.pld 120.18.12010000.6
b) POXWPA1B.pls 120.56.12010000.8

 

a) <Patch. 8326256:R12.PO.B>

b) <Patch.8520350:R12.PO.B>

Contacts

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
Details
Actions
Contacts
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.