Results for “xdp_action_codes_v”

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

Overview

XDP_ACTION_CODES_V is a VALID Oracle EBS view owned by the APPS schema within the XDP – Provisioning product, typically deployed in 12.1.1 and 12.2.2 environments. It exists to expose a consolidated, unified list of "action codes" that downstream provisioning, order-capture, and integration logic can reference without hardcoding source-specific identifiers. The view is a UNION ALL-style construct that merges two distinct catalogues: sales-related transaction types sourced from Oracle Order Management, and generic lookup values sourced from the application's flexfield lookup infrastructure.

Its core role in Oracle EBS reporting and integration is normalization. Rather than joining OE_TRANSACTION_TYPES_ALL and FND_LOOKUPS separately, a consumer can query this single view to retrieve a homogeneous set of ACTION_CODE and DISPLAY_NAME pairs, each tagged with an ACTION_SOURCE discriminator ('SALES' or 'XDP'). This makes the view particularly useful in provisioning workflows where the origin of an action code matters less than its presence and its display label.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following objects:

• OE_TRANSACTION_TYPES_ALL (synonym) — supplies the sales-side transaction type rows.
• OE_TRANSACTION_TYPES_TL (synonym) — supplies the translated NAME values for those transaction types.
• FND_LOOKUPS (view) — supplies XDP lookup rows where LOOKUP_TYPE = 'XDP_ACTIONS'.
• FND_GLOBAL (package) — referenced through Oracle EBS session context (e.g., USERENV('LANG')) to resolve the active language.

The first branch of the UNION restricts OE_TRANSACTION_TYPES_ALL to rows where TRANSACTION_TYPE_CODE = 'LINE' and ORDER_CATEGORY_CODE = 'ORDER', and where the row is currently active (START_DATE_ACTIVE <= SYSDATE and NVL(END_DATE_ACTIVE, SYSDATE) >= SYSDATE). The second branch reads lookup values from FND_LOOKUPS for the XDP_ACTIONS lookup type. Because the view resolves translation via USERENV('LANG'), the DISPLAY_NAME returned reflects the session's language setting.

Key Columns

• ACTION_CODE — the identifier used to reference the action. For sales rows this is TO_CHAR(TRANSACTION_TYPE_ID); for XDP rows it is the FND_LOOKUPS LOOKUP_CODE.
• DISPLAY_NAME — the user-facing label. Sourced from OE_TRANSACTION_TYPES_TL.NAME for sales rows, and from FND_LOOKUPS.MEANING for XDP lookup rows.
• LOOKUP_TYPE — populated with the lookup type for XDP-sourced rows (XDP_ACTIONS) and returned as NULL for sales rows, preserving the distinction between the two origins.
• ACTION_SOURCE — a literal discriminator, either 'SALES' (Order Management) or 'XDP' (Provisioning lookup), indicating which catalogue the row was drawn from.
• ORG_ID — the operating unit for sales rows (taken from OTT.ORG_ID); for XDP rows this is returned as TO_NUMBER('') → NULL.

Common Use Cases and Queries

The view is typically consumed when provisioning or order-processing logic needs a normalized list of available action codes. A straightforward listing of all available actions, grouped by origin, is:

• SELECT ACTION_SOURCE, ACTION_CODE, DISPLAY_NAME FROM XDP_ACTION_CODES_V ORDER BY ACTION_SOURCE, ACTION_CODE;

To isolate only the sales-order line transaction types available in the current operating unit:

• SELECT ACTION_CODE, DISPLAY_NAME, ORG_ID FROM XDP_ACTION_CODES_V WHERE ACTION_SOURCE = 'SALES';

To retrieve the provisioning lookup-based actions specifically:

• SELECT ACTION_CODE, DISPLAY_NAME, LOOKUP_TYPE FROM XDP_ACTION_CODES_V WHERE ACTION_SOURCE = 'XDP';

Because the OE branch is time-filtered, the view always reflects transaction types active as of the query date, which makes it suitable for dynamic integration endpoints that must not offer expired action codes to upstream systems.