Search Results object_usage_id




Overview
Explore in AI Chat

Overview

APPS.JTF_OBJECT_USAGES_V is a reporting and integration view in the Oracle E-Business Suite Applications (APPS) schema. It exposes the full column set of the JTF_OBJECT_USAGES table, providing a stable, read-oriented interface for querying object usage definitions maintained by the Common Technology Foundation (JTF) layer. The view is available in both EBS 12.1.1 and 12.2.2, and is listed in the ETRM (E-Business Suite Technical Reference Manual) as a documented view owned by APPS.

In the context of EBS integration and reporting, the view abstracts direct access to the underlying base table. Consumers, including custom reports, OAF-based pages, and integration touchpoints, can select from JTF_OBJECT_USAGES_V rather than the base table, benefiting from a consistent column projection that includes the primary key OBJECT_USAGE_ID together with descriptive and audit attributes. This makes the view suitable for lookups, validation routines, and cross-module joins where object usage metadata is required.

Underlying Base Objects

The view is defined over a single base object: the synonym JTF_OBJECT_USAGES, which resolves to the physical table of the same name in the JTF schema. The view is a simple projection, not a join, and therefore introduces no aggregation or filtering logic. Every row returned by the view corresponds one-to-one with a row in the base table. The ETRM metadata records the referenced base object as: JTF_OBJECT_USAGES (SYNONYM). Because the view does not restrict columns or apply predicates, its cardinality and content are entirely determined by the base table.

Key Columns

  • OBJECT_USAGE_ID — the primary key and the identifier users most frequently search on. It uniquely identifies each object usage record.
  • OBJECT_CODE — the code of the object whose usage is being recorded.
  • OBJECT_USER_CODE — the code of the user or consumer associated with the usage of the object.
  • SEEDED_FLAG — indicates whether the record is seeded by Oracle (typically 'Y') or created by a customer.
  • OBJECT_VERSION_NUMBER — used for optimistic locking during DML operations.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording who created and last modified the record and when.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS flexible attribute (DDF) columns available for customer-defined extensions.

Common Use Cases and Queries

The most frequent scenario is looking up an object usage by its identifier, or determining which users reference a given object. The following queries reflect typical reporting patterns.

Retrieve a record by primary key:

SELECT object_usage_id, object_code, object_user_code, seeded_flag
FROM apps.jtf_object_usages_v
WHERE object_usage_id = :p_object_usage_id;

List all usages for a given object code:

SELECT object_usage_id, object_user_code, creation_date
FROM apps.jtf_object_usages_v
WHERE object_code = :p_object_code
ORDER BY object_user_code;

Identify customer-defined (non-seeded) records:

SELECT object_usage_id, object_code, object_user_code
FROM apps.jtf_object_usages_v
WHERE seeded_flag = 'N';

Because the view applies no filtering, queries should always include predicates to constrain result sets. For DML operations, the base table JTF_OBJECT_USAGES must be used directly; the view is intended for read access. The audit and version columns support reconciliation during data migration or interface error analysis.