Results for “oe_ak_objects_ext”

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

Overview

OE_AK_OBJECTS_EXT is a table owned by the ONT (Order Management) schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It functions as an extension table to the underlying AK_OBJECTS entity registry, providing a staged repository for additional metadata that describes the database objects, entities, and Order Management configuration artifacts used by the Oracle Order Management constraint, validation, and processing framework. The table holds the descriptive record that ties a physical database object (for example, a table or package) to the business entity code registered through FND_DOCUMENT_ENTITIES, and it is the target of referential integrity from a family of OE_PC_* configuration tables.

Under a heuristic Data Vault classification mined from its foreign key structure, OE_AK_OBJECTS_EXT behaves as a hub. It carries a surrogate primary key on ENTITY_ID and holds the grain of a single business entity, while downstream OE_PC_CONDITIONS, OE_PC_CONSTRAINTS, OE_PC_RSETS, OE_PC_VALIDATION_PKGS, and OE_PC_VTMPLTS reference it as the hub key. This classification is a modeling suggestion only; in the EBS implementation the table is a conventional normalized master record rather than a formally modeled Data Vault hub.

Key Information Stored

The documented physical schema exposes 36 columns. The most significant are:

• ENTITY_ID — the surrogate primary key (OE_AK_OBJECTS_EXT_PK) that uniquely identifies each registered entity and is propagated to all dependent OE_PC_* tables.
• ENTITY_CODE — the human-readable entity identifier used in validation packages and constraint definitions.
• DATABASE_OBJECT_NAME and DATABASE_OBJECT_TYPE — the physical object name and type that the entity resolves to, and the foreign key to AK_OBJECTS.
• DATA_OBJECT_CODE — the foreign key to FND_DOCUMENT_ENTITIES, linking the entity to the standard document entity registry.
• APPLICATION_ID — the owning application identifier within EBS.
• DEFAULTING_ENABLED_FLAG and CONSTRAINTS_ENABLED_FLAG — control flags that govern whether defaulting and constraint processing apply to the entity.
• WF_ITEM_TYPE and ITEMKEY_COLUMN1 through ITEMKEY_COLUMN4 with ITEMKEY_DELIMITER — Workflow item type and key composition columns used when the entity participates in a workflow process.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the descriptive flexfield (DFF) segment columns.
• ZD_EDITION_NAME — the editioning column supporting EBS online patching in 12.2.x.

Two additional unique indexes act as business-key candidates: OE_AK_OBJECTS_EXT_U1 (ENTITY_ID, ZD_EDITION_NAME) and OE_AK_OBJECTS_EXT_U2 (DATABASE_OBJECT_NAME, ZD_EDITION_NAME).

Common Use Cases and Queries

The table is queried during Order Management configuration and troubleshooting, particularly when diagnostics must trace a failing constraint or validation rule back to its registered entity. A typical resolution query joins the extension table to its parent registry:

• Resolve a constraint failure: SELECT c.CONSTRAINT_ID, o.ENTITY_CODE, o.DATABASE_OBJECT_NAME FROM OE_PC_CONSTRAINTS c, OE_AK_OBJECTS_EXT o WHERE c.ENTITY_ID = o.ENTITY_ID;
• List enabled validation packages: SELECT p.VALIDATION_PACKAGE_ID, o.ENTITY_CODE FROM OE_PC_VALIDATION_PKGS p, OE_AK_OBJECTS_EXT o WHERE p.VALIDATION_ENTITY_ID = o.ENTITY_ID;
• Enumerate entities with defaulting or constraints enabled for a given application using the DEFAULTING_ENABLED_FLAG and CONSTRAINTS_ENABLED_FLAG columns.
• Report the workflow item type and item key composition for entities that drive OM workflow, using WF_ITEM_TYPE and the ITEMKEY_COLUMN columns.

Because editioned rows exist in 12.2.x, queries against non-editioned views or direct table access should account for ZD_EDITION_NAME when historical edition data is present.

Related Objects

OE_AK_OBJECTS_EXT participates in a well-defined foreign key network:

• AK_OBJECTS — referenced via OE_AK_OBJECTS_EXT.DATABASE_OBJECT_NAME; the parent object registry.
• FND_DOCUMENT_ENTITIES — referenced via OE_AK_OBJECTS_EXT.DATA_OBJECT_CODE; the document entity registry.
• OE_PC_CONSTRAINTS — references this table through ENTITY_ID.
• OE_PC_CONDITIONS — references this table through VALIDATION_ENTITY_ID.
• OE_PC_RSETS — references this table through ENTITY_ID.
• OE_PC_VALIDATION_PKGS — references this table through both VALIDATING_ENTITY_ID and VALIDATION_ENTITY_ID.
• OE_PC_VTMPLTS — references this table through ENTITY_ID.

Together these relationships establish OE_AK_OBJECTS_EXT as the central hub for Order Management entity metadata, with the OE_PC_* constraint and validation objects acting as its dependent configuration satellites.