Results for “fnd_lookup_assignments_u2”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPLSYS.FND_LOOKUP_ASSIGNMENTS is an Oracle E-Business Suite transactional data table that stores the assignment of lookup values to specific application object instances. While FND_LOOKUPS defines the universe of lookup codes available for a given lookup type, FND_LOOKUP_ASSIGNMENTS establishes which of those codes are actually attached to a particular entity — identified by an object name and up to five primary key values. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. Its design data object is FND.FND_LOOKUP_ASSIGNMENTS.

The heuristic Data Vault classification for this object is standalone, meaning it does not participate in a documented foreign-key hierarchy with other tables. A modeling suggestion, therefore, is to treat it as an independent hub-like reference table whose business key is the composite of lookup type, lookup code, object name, and the instance primary key values. Oracle explicitly marks this object as Internal Use Only, and supported access is expected through standard Oracle Applications programs rather than direct DML.

Key Information Stored

The table is defined with 16 columns. The most significant, as documented in the ETRM metadata, are:

• LOOKUP_ASSIGNMENT_ID — Surrogate primary key, generated from the sequence FND_LOOKUP_ASSIGNMENTS_S. It is the leading column of the unique index FND_LOOKUP_ASSIGNMENTS_U1, which is also the documented primary key FND_LOOKUP_ASSIGNMENTS_PK.
• LOOKUP_TYPE — The lookup type to which the assigned code belongs.
• LOOKUP_CODE — The specific lookup value code being assigned.
• OBJ_NAME — Identifies the object (entity) to which the lookup is assigned.
• INSTANCE_PK1_VALUE through INSTANCE_PK5_VALUE — Up to five 320-character columns holding the values of the primary key columns that uniquely identify the target instance.
• DISPLAY_SEQUENCE — Controls ordering of assigned values when presented.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ZD_EDITION_NAME — Editioning column supporting the 12.2 online patching / edition-based redefinition model.

Two unique indexes are documented: FND_LOOKUP_ASSIGNMENTS_U1 on LOOKUP_ASSIGNMENT_ID and ZD_EDITION_NAME, and FND_LOOKUP_ASSIGNMENTS_U2 on the composite business key of LOOKUP_TYPE, LOOKUP_CODE, OBJ_NAME, INSTANCE_PK1_VALUE through INSTANCE_PK5_VALUE, plus ZD_EDITION_NAME. The latter is the true business-key candidate. A non-unique index, FND_LOOKUP_ASSIGNMENTS_N1, mirrors the object-and-instance columns to support retrieval lookups.

Common Use Cases and Queries

Typical scenarios include retrieving the lookup values assigned to a specific entity instance, validating whether a code is valid for a given object, and reporting on assigned versus unassigned lookups. A straightforward query pattern is:

SELECT LOOKUP_TYPE, LOOKUP_CODE, OBJ_NAME, DISPLAY_SEQUENCE
FROM   APPLSYS.FND_LOOKUP_ASSIGNMENTS
WHERE  OBJ_NAME = :obj_name
AND    INSTANCE_PK1_VALUE = :pk1
ORDER  BY DISPLAY_SEQUENCE;

Joins to FND_LOOKUPS on LOOKUP_TYPE and LOOKUP_CODE enrich results with the lookup meaning. Reporting extracts frequently filter by LOOKUP_TYPE to enumerate all instance assignments for a given list of values.

Related Objects

Although classified as standalone, the object is functionally associated with the following:

• APPLSYS.FND_LOOKUPS — joined on LOOKUP_TYPE and LOOKUP_CODE for descriptive meaning.
• APPLSYS.FND_LOOKUP_TYPES — joined on LOOKUP_TYPE to resolve the underlying value set.
• APPLSYS.FND_LOOKUP_ASSIGNMENTS_S — sequence supplying LOOKUP_ASSIGNMENT_ID.
• FND_LOOKUP_ASSIGNMENTS_U1 / _U2 / _N1 — unique and non-unique indexes enforcing integrity and supporting access paths.
• Standard Oracle Applications APIs that maintain lookup assignments (substituting for direct DML, which is unsupported).