Value set associated to a parameter is not getting applied properly from a patch (Doc ID 971474.1)

Last updated on AUGUST 05, 2016

Applies to:

Oracle Receivables - Version 11.5.0 to 12.1.1 [Release 11.5.0 to 12.1]
Information in this document applies to any platform.
This issue could manifest in any concurrent program which has parameters controlled by value sets.

When a parameter value is entered and an error is encountered during validation of the value, the first line of investigation is to check the value set definition. If the value set definition provided via a .ldt file in the patch level customer is on, does not match the actual value set definition at the customer's instance then you may be hitting the issue wherein the value set is unable to override the definition in the database.


Symptoms

Symptoms are varied, some of which could be:

1) ORA-904: invalid identifier
2) ORA-04043: object does not exist
3) ORA-00942: table or view does not exist

Basically, the validation done by the value set at the customer site, does not match the validation defined in the .ldt file.

Example:
In SR#2-5884112, the following issue was noted:

In 12.0.6, When attempting to run Automatic Receipts Master Program, the following error occurs when clicking on the LOV for Receipt Class.

ERROR
-----------------------
ORA-904: "RMA"."BANK_ACCOUNT_ID" invalid identifier

The value set AR_AUTOREC_RECEIPT_CLASS_ID associated with this parameter is defined in ar12avs.ldt. However, when the value set definition at the customer's instance was reviewed, it was noted that it was still using the definition from Release 11i, instead of the one defined in the .ldt. Further, repeated applications of a patch containing the right .ldt did not fix the issue.

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