Search Results jtf_object_usages_v

Overview

JTF_OBJECT_USAGES_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 belongs to the JTF product family, collectively known as CRM Foundation, which supplies shared infrastructure components used across Oracle's CRM applications (Advanced Outbound, Interaction Center, iStore, TeleSales, and related modules). As documented in the ETRM metadata, the view exists to define the usage of an object code — that is, it associates a defined CRM object with the context or application in which that object is consumed.

The view is catalogued with a status of VALID, confirming that its definition compiles cleanly against the base objects in a supported release. Functionally, it provides a read-oriented projection of object usage metadata, allowing administrators, integrators, and reporting tools to enumerate which object codes are registered for use and to inspect their descriptive and descriptive-flexfield attributes without writing directly against the underlying transactional table.

Underlying Base Objects

The view is defined over a single documented base object: the synonym JTF_OBJECT_USAGES, which resolves to the base table of the same name in the APPS schema. There are no joins, unions, or aggregations in the view text. It is a straightforward column projection, which means row cardinality, data types, and value semantics are inherited one-to-one from the base table.

Because the view performs no filtering, no predicates are applied to exclude seeded or obsolete rows. All rows present in JTF_OBJECT_USAGES — including seeded reference data delivered by Oracle and customer-defined entries — are visible through the view. This distinguishes it from more curated CRM views that apply SEEDED_FLAG or language filters. Consumers should therefore expect the view to return the complete, unfiltered contents of the base table.

Key Columns

The column list reflects a standard Oracle EBS table shape with mandatory WHO columns, a versioning column, a flexible attribute block, and a small set of domain-specific keys.

• OBJECT_USAGE_ID — Surrogate primary key uniquely identifying each usage record.
• OBJECT_CODE — The logical object code whose usage is being defined; the core business identifier in the view.
• OBJECT_USER_CODE — A user-facing or application-level code associated with the usage, typically the value presented in setup and configuration screens.
• SEEDED_FLAG — Indicates whether the row was delivered as Oracle seed data (typically Y) or created by a customer (N).
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update provenance.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The DFF descriptive flexfield block, used for extensible, customer-defined metadata.

Note that the ETRM column listing includes OBJECT_ID, while the published view text selects OBJECT_USAGE_ID. In practice, both identifiers appear in the JTF object registry model, with OBJECT_ID referencing the parent object definition and OBJECT_USAGE_ID keying the usage row itself. The view text should be treated as authoritative for what the view exposes in a given patch level.

Common Use Cases and Queries

The most frequent application is diagnostic: confirming which object codes are registered for use before configuring a CRM component, replicating setup between environments, or troubleshooting a missing object reference.

• Enumerate seeded usages: SELECT object_code, object_user_code FROM jtf_object_usages_v WHERE seeded_flag = 'Y';
• Find customer-defined entries: SELECT object_usage_id, object_code, object_user_code FROM jtf_object_usages_v WHERE seeded_flag = 'N' ORDER BY object_code;
• Audit recent changes: SELECT object_code, last_updated_by, last_update_date FROM jtf_object_usages_v WHERE last_update_date > SYSDATE - 30;
• Inspect flexfield extensions: SELECT object_code, attribute_category, attribute1, attribute2 FROM jtf_object_usages_v WHERE attribute_category IS NOT NULL;
• Search a specific code: SELECT * FROM jtf_object_usages_v WHERE object_code = :p_object_code;

Because the view is unfiltered, integration extracts should always qualify results by OBJECT_CODE, SEEDED_FLAG, or date range to avoid loading the full registry. The absence of a language join also means no MLS filtering applies; multi-language consumers must resolve translated object names from the corresponding JTF translation entities.