Results for “oe_default_actions”

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

Overview

OE_DEFAULT_ACTIONS is a reference configuration table owned by the ONT schema within the Oracle E-Business Suite Order Management module. It stores information about all the actions that are applicable to a Sales Order, serving as the repository of action definitions that the order management engine and the user interface consult when presenting or executing operations against orders. In EBS 12.1.1 and 12.2.2, the table is documented as VALID with 11 physical columns, and it functions primarily as a metadata registry that drives action availability rather than storing transactional order data. The listed primary key is OE_DEFAULT_ACTIONS_PK, defined on ACTION_ID.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone. Following that heuristic, OE_DEFAULT_ACTIONS is best modeled as a hub-style reference table: its identity is a single surrogate key with no dependent child links or satellites documented through foreign keys. This is consistent with a lookup or code table whose rows define valid actions rather than record business events.

Key Information Stored

The documented columns capture the identity of each action, the object context in which it applies, presentation attributes, and standard audit stamping. The most significant columns are:

• ACTION_ID — the surrogate primary key (OE_DEFAULT_ACTIONS_PK) that uniquely identifies each action row. This is the column referenced by any dependent application logic that needs a stable identifier for an action.
• OBJECT — identifies the business object or context to which the action applies. Together with ACTION_NAME and ZD_EDITION_NAME it forms the business-key candidate.
• ACTION_NAME — the functional name of the action applicable to a sales order. This is the human-recognizable label used in menus, buttons, and action lists.
• ZD_EDITION_NAME — the edition designator used by the EBS 12.2.2 editioning and online patching infrastructure. Its presence in the unique index means business uniqueness is evaluated per edition.
• WIDTH — a presentation attribute governing the rendered width of the action, indicating that this table supports UI generation as well as back-end action resolution.
• DISPLAY_AS_BUTTON_FLAG — a flag determining whether the action is surfaced to users as a button. This is a key driver of user interface behavior in the Order Management forms.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-columns providing auditability for row creation and modification.

The documented unique index OE_DEFAULT_ACTIONS_U1 covers OBJECT, ACTION_NAME, and ZD_EDITION_NAME, establishing these three columns as the business-key candidate. The distinction is important: ACTION_ID is the technical primary key used for joins, while the composite of OBJECT, ACTION_NAME, and ZD_EDITION_NAME enforces business uniqueness.

Common Use Cases and Queries

The primary use cases center on resolving which actions apply to which objects and how they should be presented. A typical query retrieves the actions available for a given object context:

SELECT action_id, action_name, width, display_as_button_flag FROM ont.oe_default_actions WHERE object = :object_name ORDER BY action_name;

Reporting scenarios include auditing the configured action set for a specific edition, identifying actions exposed as buttons versus those invoked programmatically, and validating that no duplicate action names exist within an object. The edition column should always be constrained in 12.2.2 environments to avoid returning rows from multiple editions:

SELECT action_name, display_as_button_flag FROM ont.oe_default_actions WHERE object = :object_name AND zd_edition_name = :edition;

Because the table is configuration-oriented and relatively small, it is frequently joined to order-related tables at query time rather than being snapshotted into reporting extracts. Administrators also use it to verify the effect of patches or setups on the action set visible to order entry users.

Related Objects

OE_DEFAULT_ACTIONS is documented as standalone in the mined relationship data, meaning no foreign keys connect it to other ONT tables directly. Its relationships are therefore application-level rather than declarative. The most significant related objects include the Order Management action processing engine and the sales order entry forms, which read ACTION_NAME and DISPLAY_AS_BUTTON_FLAG to build the action menus presented on the order header and line. The unique index OE_DEFAULT_ACTIONS_U1 is the principal dependent object, enforcing the OBJECT, ACTION_NAME, and ZD_EDITION_NAME business key, while the primary key OE_DEFAULT_ACTIONS_PK on ACTION_ID defines the row identity used by any referencing logic.

In 12.2.2, the editioning infrastructure represented by ZD_EDITION_NAME ties the table to the patching and edition views used across the ONT schema. Tables in the ONT schema that store order-level action history or defaults reference action identifiers resolved through this table by application code rather than by enforced foreign keys. Consumers should therefore treat OE_DEFAULT_ACTIONS as an authoritative lookup for action definitions and join to it on OBJECT and ACTION_NAME, taking care to filter by edition in multi-edition environments.