Results for “user_entered_prompt”

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

Overview

OE_ACTIONS is an Oracle E-Business Suite internal Forms view owned by the APPS schema within the Order Management (ONT) product family. It is documented as VALID in the ETRM for both release 12.1.1 and 12.2.2. The view exists to expose, in a single result set, both the default actions shipped with Oracle Order Management and the customized actions that an individual user has defined for order entry and related folders. Because it is described in Oracle's documentation as an "Internal Forms View," its primary consumer is the Oracle Forms-based Order Management user interface rather than external reporting or integration layers.

The view resolves which actions are presented to a given user by unioning customized actions with default actions that the current user has not overridden. This behavior makes the view user-context sensitive: its contents depend on the value returned by FND_PROFILE.VALUE('USER_ID'), so two different users querying the same view may legitimately receive different rows. Because it is a view and not a table, no data is stored against it; all content is derived at query time from the underlying action definition objects.

Underlying Base Objects

As documented in the ETRM metadata, OE_ACTIONS is defined over three referenced objects: the package FND_PROFILE and the synonyms OE_CUSTOM_ACTIONS and OE_DEFAULT_ACTIONS.

• OE_CUSTOM_ACTIONS — supplies user-defined actions and their prompts, folder assignment, width, access key, and display-as-button flag.
• OE_DEFAULT_ACTIONS — supplies Oracle-seeded default actions. The view selects from this source only where the action name is not already present in OE_CUSTOM_ACTIONS for the current user, enforcing user customization precedence over system defaults.
• FND_PROFILE — the profile option package, invoked as FND_PROFILE.VALUE('USER_ID') to determine the effective user for the customization check.

The union assigns a literal FOLDER_ID of -1 and null values for USER_ENTERED_PROMPT, ACCESS_KEY, and DEFAULT_PROMPT on the default-actions branch, distinguishing system defaults from customized entries.

Key Columns

• ACTION_ID — identifier of the action record.
• OBJECT — the object or entity to which the action applies.
• ACTION_NAME — name of the action; used in the view text as the join key preventing duplication of customized actions.
• USER_ENTERED_PROMPT — user-supplied prompt text; null for default actions.
• FOLDER_ID — folder assignment; -1 indicates a default action.
• WIDTH — display width of the action control.
• ACCESS_KEY — keyboard access key; null for default actions.
• DISPLAY_AS_BUTTON_FLAG — controls whether the action is rendered as a button.
• DEFAULT_PROMPT — seeded prompt text; null for default actions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The view is typically referenced when diagnosing which actions a user should see in the Order Management Forms interface, when troubleshooting missing or duplicated action buttons, and when validating that a customization has been applied correctly for a specific user. Administrators may also use it to audit whether a customized action is masking a seeded default.

To list all actions visible to the currently connected user:

SELECT action_id, object, action_name, user_enterred_prompt, folder_id, width, display_as_button_flag FROM apps.oe_actions ORDER BY object, action_name;

To isolate customized entries only, filter on the distinguishing literals applied by the union:

SELECT action_id, object, action_name, user_enterred_prompt, folder_id FROM apps.oe_actions WHERE folder_id <> -1;

Because results vary by session user, queries intended for administrative review should be run under the relevant user's responsibility context, or the profile value must be accounted for explicitly in any comparison. Given its internal, Forms-oriented purpose, OE_ACTIONS should not be treated as a stable integration interface; custom reports and interfaces are better served by the underlying OE_CUSTOM_ACTIONS and OE_DEFAULT_ACTIONS objects directly.