Search Results pa_dlvr_action_function




Overview
Explore in AI Chat

Overview

APPS.PA_ACTION_FUNCTIONS_AMG_V is a lightweight Oracle E-Business Suite view that exposes the set of valid "action functions" used within the Oracle Projects delivery management and deliverables functionality. It presents the lookup values registered under the lookup type PA_DLVR_ACTION_FUNCTION in a denormalized, query-friendly form. Rather than requiring integration or reporting code to filter the generic PA_LOOKUPS view directly, this view isolates the specific lookup type and returns only the relevant rows.

The view belongs to the APPS schema and is documented in ETRM 12.2.2 with APPS as the owner and PA_LOOKUPS as the sole referenced base object. It plays a supporting role in reporting and integration: it is typically consumed when a report, concurrent program, OAF page, or interface needs to translate a stored lookup code for a deliverable action function into its user-facing meaning and description. Because it is defined over a lookup view rather than a transactional table, it carries no transactional data and is effectively a controlled reference or value-set style view.

Underlying Base Objects

The view is defined with a simple projection and filter over a single referenced object, PA_LOOKUPS, which itself is a view. The documented definition is:

Because the referenced object is PA_LOOKUPS rather than the underlying FND_LOOKUP_VALUES table directly, the relationship is one hop removed from the base lookup values. PA_LOOKUPS resolves the Projects-specific lookup values, and this view narrows that result to a single lookup type. Any change to the seeded or user-maintained lookup values for PA_DLVR_ACTION_FUNCTION — such as adding, disabling, or re-meaning a code — is immediately reflected when the view is queried. No joins, aggregations, or computations are performed, so the view is a straightforward filtered projection.

Key Columns

Three columns are exposed, all inherited directly from PA_LOOKUPS:

  • LOOKUP_CODE — the internal, stored code for the action function. This is the value persisted in Projects deliverable/action records and is the key used for programmatic comparisons and joins.
  • MEANING — the translatable, user-facing label for the action function, suitable for display in reports, LOVs, and page prompts.
  • DESCRIPTION — an optional longer explanation providing additional context for the action function.

The view does not expose enabled/disabled flags, start and end dates, or language-specific attributes that might be present in the underlying lookup source; consumers needing those attributes must query PA_LOOKUPS or the underlying lookup values directly.

Common Use Cases and Queries

Typical uses include populating a selection list of valid deliverable action functions, resolving a stored code to its display meaning on a report, and validating inbound interface values before insert. The following query lists all available action functions:

  • SELECT lookup_code, meaning, description FROM apps.pa_action_functions_amg_v ORDER BY lookup_code;

To resolve a single code to its meaning:

  • SELECT meaning FROM apps.pa_action_functions_amg_v WHERE lookup_code = :p_action_function;

To validate that an inbound value is a recognized action function:

  • SELECT COUNT(*) FROM apps.pa_action_functions_amg_v WHERE lookup_code = :p_inbound_code;

Because the predicate on LOOKUP_TYPE is fixed inside the view, callers never need to supply it themselves, which reduces the risk of miscoding the lookup type in downstream SQL. The view is read-only and is most valuable as a stable, self-documenting interface to the PA_DLVR_ACTION_FUNCTION lookup set.