Results for “attachments_enabled_flag”

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

Overview

OE_AK_OBJ_ATTR_EXT is a table owned by the ONT (Order Management) schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. As its name indicates, it is an extension table to the Oracle Application Framework (AK) object attribute repository. While the base AK_OBJECT_ATTRIBUTES table records the generic definition of descriptive flexfield and attribute metadata, OE_AK_OBJ_ATTR_EXT stores Order Management-specific behavioral controls and configuration flags that govern how individual order attributes are defaulted, validated, secured, priced, and displayed within the order capture flow. The table therefore acts as the Order Management customization layer over the shared AK attribute dictionary.

With respect to Data Vault modeling heuristics, the mined relationship structure classifies this object as satellite-leaning. Its primary key is a surrogate identity column (ATTRIBUTE_ID), and its principal foreign key relationship points outward to AK_OBJECT_ATTRIBUTES via the composite of DATABASE_OBJECT_NAME, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID. This pattern—a surrogate-keyed table carrying descriptive and flag data keyed to a parent business key—is characteristic of a satellite attached to the AK attribute hub rather than an independent hub or a link table.

Key Information Stored

The documented physical schema contains 43 columns. The most consequential are:

• ATTRIBUTE_ID — surrogate primary key, enforced by OE_AK_OBJ_ATTR_EXT_PK.
• DATABASE_OBJECT_NAME, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID — the composite business key identifying the attribute, enforced by unique index OE_AK_OBJ_ATTR_EXT_UK1 (also present as OE_AK_OBJ_ATTR_EXT_U2 alongside ZD_EDITION_NAME in 12.2.2).
• DEFAULTING_SEQUENCE, DEFAULTING_ENABLED_FLAG, DEFAULTING_CONDN_REF_FLAG, DEFAULTING_SOURCE_FLAG — control the order of defaulting rules and whether conditional or source-based defaulting applies.
• CONSTRAINTS_ENABLED_FLAG, CONSTRAINT_CONDN_REF_FLAG — govern validation constraint activation for the attribute.
• PRICING_RULE_ENABLED_FLAG, DISCOUNTS_ENABLED_FLAG — determine whether the attribute participates in pricing and discounting logic.
• HOLDS_ENABLED_FLAG, NOTES_ENABLED_FLAG, ATTACHMENTS_ENABLED_FLAG, STATE_ATTRIBUTE_FLAG — functional enablement switches for holds, notes, attachments, and state-driven behavior.
• SECURITY_API_PKG, SECURITY_API_PROC, DEPENDENT_API_PKG, DEPENDENT_API_PROC — identify the PL/SQL routines invoked for attribute-level security and dependent value processing.
• COLUMN_TYPE_CODE — classifies the underlying column type.
• ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — the DFF-style descriptive extension columns.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• ZD_EDITION_NAME — the editioning column introduced for online patching in 12.2.

Common Use Cases and Queries

The table is queried primarily to determine the configured behavior of order attributes, to trace which API governs defaulting or security, and to audit customizations that deviate from seeded metadata. A typical join resolves the full attribute context:

SELECT e.DATABASE_OBJECT_NAME, e.ATTRIBUTE_CODE, a.ATTRIBUTE_NAME, e.DEFAULTING_ENABLED_FLAG, e.SECURITY_API_PKG, e.SECURITY_API_PROC
FROM ONT.OE_AK_OBJ_ATTR_EXT e, AK.AK_OBJECT_ATTRIBUTES a
WHERE e.DATABASE_OBJECT_NAME = a.DATABASE_OBJECT_NAME
AND e.ATTRIBUTE_CODE = a.ATTRIBUTE_CODE
AND e.ATTRIBUTE_APPLICATION_ID = a.ATTRIBUTE_APPLICATION_ID;

Reporting scenarios include identifying all attributes with defaulting enabled for a given order entity, isolating attributes whose security is driven by a packaged procedure (a common source of unexpected field behavior), and validating that pricing-enabled attributes align with pricing setup. In 12.2.2 environments, queries should constrain or account for ZD_EDITION_NAME when comparing across editions.

Related Objects

• AK_OBJECT_ATTRIBUTES — parent table; joined on DATABASE_OBJECT_NAME, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID. This is the documented foreign key relationship.
• AK_OBJECTS / AK_ATTRIBUTES — supporting AK dictionary tables that define objects and attribute metadata consumed alongside this extension.
• OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — the transactional entities whose attributes this metadata describes.
• OE_AK_OBJ_ATTR_EXT_PK / _UK1 / _U1 / _U2 — the primary, unique, and edition-aware indexes that enforce identity and business-key integrity.
• Order Management attribute defaulting, constraint, and security PL/SQL APIs — referenced dynamically through DEPENDENT_API_PKG/PROC and SECURITY_API_PKG/PROC columns.