Results for “oe_attachment_object_refs_v”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_ATTACHMENT_OBJECT_REFS_V is a view owned by the APPS schema within the ONT (Order Management) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view joins attachment object reference metadata from Order Management with document entity definitions maintained by the Oracle Application Object Library. Its columns expose the physical table and column location in which a given attachment/document category is stored, together with standard audit columns.
The ETRM documentation explicitly states that this view is "No longer used," and it is registered with a VALID status solely because the underlying DDL persists in the database. Oracle has historically retained such views to preserve backward compatibility for customizations, reports, and extensions that may reference them, even after the functional code path that originally consumed them has been retired. Consequently, the view should be treated as a legacy, read-only compatibility object rather than an actively supported integration point. When evaluated against the newer FND Attachment framework introduced around EBS 12.1.x, this view reflects the earlier pattern of resolving document entities through FND_DOCUMENT_ENTITIES at query time.
Underlying Base Objects
The view is defined by an inner join between two base objects, both referenced in the ETRM metadata as synonyms:
- OE_ATTACHMENT_OBJECT_REFS — the ONT-owned table that holds registration rows describing each attachment object reference, keyed by OBJECT_REF_ID. It contributes the DATA_OBJECT_CODE that identifies the document entity and the COLUMN_NAME, COLUMN_DATATYPE, and audit attributes.
- FND_DOCUMENT_ENTITIES — the Application Object Library table that maps a DATA_OBJECT_CODE to the database TABLE_NAME in which the corresponding document or attachment records reside.
The join predicate is O.DATA_OBJECT_CODE = FDE.DATA_OBJECT_CODE, so only object references that have a matching row in FND_DOCUMENT_ENTITIES are returned. This is a straightforward equijoin with no outer join, meaning orphaned object reference rows without a corresponding document entity definition are excluded from the result set. The view adds no aggregation, filtering, or DML capability; it is a pure projection of the two joined sources.
Key Columns
- OBJECT_REF_ID — Primary identifier for the attachment object reference row, sourced from OE_ATTACHMENT_OBJECT_REFS.
- OBJECT_REF_TYPE — Classifies the type of object reference being described.
- DATA_OBJECT_CODE — The document entity code that links the attachment reference to the FND_DOCUMENT_ENTITIES definition; this is the join key.
- TABLE_NAME — The physical database table in which the referenced document entity is stored, resolved through FND_DOCUMENT_ENTITIES. This is the most operationally significant column in the view.
- COLUMN_NAME — The specific column within that table that carries the document content or reference.
- COLUMN_DATATYPE — The datatype of the COLUMN_NAME target, useful for interpreting or validating attachment storage.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns recording insert and update audit information.
Common Use Cases and Queries
The primary supported use is diagnostic: resolving where Order Management attachment or document references are physically stored. A typical query filters by object reference type or data object code:
SELECT object_ref_id,
object_ref_type,
data_object_code,
table_name,
column_name,
column_datatype
FROM apps.oe_attachment_object_refs_v
WHERE data_object_code = :p_data_object_code;
A second pattern joins the view back to FND_DOCUMENT_ENTITIES to confirm that the table mapping remains consistent after patching:
SELECT v.data_object_code,
v.table_name,
fde.data_object_code
FROM apps.oe_attachment_object_refs_v v,
apps.fnd_document_entities fde
WHERE v.data_object_code = fde.data_object_code;
Because the view is documented as no longer used, new development should rely on the current FND_ATTACHMENT / FND_DOCUMENT_ENTITIES APIs instead. Existing custom reports referencing this view should be inventoried and migrated, and no application logic should depend on the view returning rows for newly created attachment objects.
-
No longer used
APPS.OE_ATTACHMENT_OBJECT_REFS_V·↳ FND_DOCUMENT_ENTITIES·↳ OE_ATTACHMENT_OBJECT_REFS·Explore ONT module →
-
No longer used
APPS.OE_ATTACHMENT_OBJECT_REFS_V·↳ FND_DOCUMENT_ENTITIES·↳ OE_ATTACHMENT_OBJECT_REFS·Explore ONT module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.