Results for “attribute_code”

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

Overview

JTF_LOOKUPS_AK_ATTRIBUTE_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the CRM Foundation (JTF) product family and exposes descriptive metadata for extensible attributes registered in the Oracle Application Object Library (AK) attribute framework, restricted to those object types that have been registered as lookup values under the lookup type JTF_BRM_OBJECT_TYPE. The view is a metadata catalog: rather than presenting transactional CRM data, it resolves the relationship between a database object, its physical columns, and the associated attribute definitions and translated prompts.

In practice, the view answers the question "which extensible attributes are available on a given CRM business object, and what are their labels and descriptions?" This makes it valuable for building dynamic user interfaces, generating validation logic, and driving reporting layers that must remain synchronized with the underlying AK attribute setup rather than hard-coding attribute lists.

Underlying Base Objects

The view text is an inner join across four principal data sources, with the driving row set supplied by FND_LOOKUPS:

• FND_LOOKUPS — filtered inline to LOOKUP_TYPE = 'JTF_BRM_OBJECT_TYPE', with ENABLED_FLAG = 'Y' and an effective date window (START_DATE_ACTIVE <= SYSDATE, END_DATE_ACTIVE > SYSDATE, treating nulls as open-ended). This restricts the result to currently active business object types.
• AK_OBJECTS_TL — joined on DATABASE_OBJECT_NAME = FLU.LOOKUP_CODE, supplying the translated object name and description. The join is language-filtered by AOL.LANGUAGE = USERENV('LANG').
• AK_OBJECT_ATTRIBUTES — joined on DATABASE_OBJECT_NAME, providing the attribute code and attribute application identifier.
• AK_ATTRIBUTES_TL — joined on the composite key ATTRIBUTE_CODE + ATTRIBUTE_APPLICATION_ID, supplying the long attribute label (prompt) and attribute description, again language-filtered by USERENV('LANG').

The metadata confirms a dependency on the FND_GLOBAL package, which is the mechanism behind USERENV('LANG') language resolution. All base objects are referenced through APPS synonyms.

Key Columns

• DATABASE_OBJECT_NAME — the physical database object (table or view) associated with the business object type; the primary correlation key across the AK tables.
• DATABASE_COLUMN_NAME — the physical column in that object to which the attribute is mapped.
• APPLICATION_ID — the application identifier owning the attribute definition, forming part of the attribute's composite primary key.
• OBJECT_NAME and OBJECT_DESCRIPTION — the translated display name and description of the object, sourced from AK_OBJECTS_TL.
• ATTRIBUTE_CODE — the internal identifier of the attribute.
• ATTRIBUTE_PROMPT — the long label used for user interface display of the attribute.
• ATTRIBUTE_DESCRIPTION — explanatory text for the attribute.

Common Use Cases and Queries

Typical applications include dynamically rendering attribute entry fields, auditing which attributes exist per object, and reconciling AK setup with downstream configurations. A basic query filters by object name:

• SELECT object_name, attribute_code, attribute_prompt FROM jtf_lookups_ak_attribute_v WHERE database_object_name = 'JTF_...' ORDER BY attribute_code;
• SELECT database_object_name, COUNT(*) FROM jtf_lookups_ak_attribute_v GROUP BY database_object_name; — inventory of attribute counts per registered object.
• Joining to FND_LOOKUPS via DATABASE_OBJECT_NAME = LOOKUP_CODE allows reporting of the object type's meaning alongside its attributes, supporting metadata-driven configuration dashboards.

Because the view is language-aware and date-effective, results automatically reflect the session language and only currently active lookup registrations, reducing the need for custom filtering in consuming reports.