Search Results access_key

Overview

The OE_CUSTOM_ACTIONS table, owned by the ONT schema in Oracle E-Business Suite 12.1.1 and 12.2.2, is an Order Management configuration object that stores information about all custom actions assigned to a folder. In the context of the Order Management HTML user interface and the folder-based personalization framework, this table functions as the persistence layer for the user-defined actions that appear on a folder, including their prompts, display attributes, and access keys. It allows administrators and users to define which buttons or menu actions are exposed on a given folder within the Orders, Quotes, and Returns workbenches.

From a heuristic Data Vault modeling perspective, this table is classified as a standalone structure — that is, the mining of its foreign-key structure identified no parent dependencies, which suggests treating it as an independent hub or a self-contained reference entity rather than a link or satellite in a strict Data Vault model. This classification is a modeling suggestion only; in practice the table is a configuration table that may be joined functionally to folder definitions and user identifiers even where referential constraints are not declared in the database.

Key Information Stored

The table is documented with 15 columns. The most significant are:

• ACTION_ID — the surrogate primary key, enforced by the OE_CUSTOM_ACTIONS_PK constraint. Every row is uniquely identified by this generated identifier.
• FOLDER_ID — identifies the folder to which the action is assigned; this is the principal organizing business attribute.
• ACTION_NAME — the internal name of the custom action.
• OBJECT — the object or entity against which the action operates.
• USER_ENTERED_PROMPT and DEFAULT_PROMPT — the display label supplied by the user and the system default label, respectively.
• DISPLAY_AS_BUTTON_FLAG — controls whether the action renders as a button rather than a menu item.
• WIDTH — the display width of the action control.
• ACCESS_KEY — the keyboard access key or mnemonic associated with the action.
• USER_ID — the owning user for the action definition.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

No unique business-key index is documented beyond the primary key; ACTION_ID remains the only documented uniqueness constraint.

Common Use Cases and Queries

Typical scenarios include auditing which custom actions are configured on a folder, diagnosing missing buttons on an Order Management folder, and migrating personalization definitions between environments. A representative query lists actions for a given folder:

• SELECT action_id, folder_id, action_name, object, user_entered_prompt, display_as_button_flag FROM ont.oe_custom_actions WHERE folder_id = :p_folder_id;
• SELECT a.* FROM ont.oe_custom_actions a WHERE a.user_id = :p_user_id ORDER BY a.action_name;
• Reporting: count of button-displayed actions versus menu-displayed actions per folder using GROUP BY on FOLDER_ID and DISPLAY_AS_BUTTON_FLAG.
• Audit queries filtering on LAST_UPDATE_DATE to detect recent personalization changes.

Related Objects

Given the documented standalone classification, no foreign keys are mined. Functional relationships to consider include:

• OE_CUSTOM_ACTIONS_PK — the primary-key constraint on ACTION_ID.
• FOLDER_ID joins to folder-definition tables in the ONT schema that describe Order Management folders.
• USER_ID joins to FND_USER for identifying the owning user.
• CREATED_BY / LAST_UPDATED_BY join to FND_USER for audit attribution.
• OBJECT relates to the entity names used by the Order Management folder framework.