Search Results get_action_set_lines

Overview

PA_ACTION_SET_UTILS is a utility PL/SQL package in the Oracle EBS Projects (PA) module that centralizes the logic required to define, retrieve, and evaluate "action sets" used by Oracle Project Management and Oracle Project Resource Management. An action set is a reusable, ordered collection of actions that the application triggers automatically when a specific business event occurs against a project, such as a status change, a staffing event, or a workflow-driven approval. The package supports the configuration and runtime interpretation of these rule-based definitions by exposing lookup routines and validation helpers that other Project modules invoke.

Because the source carries the "noship" designation (Header PARASUTS.pls 120.1), PA_ACTION_SET_UTILS is an internal, non-shipped utility rather than a public, documented open interface. It is nonetheless a foundational dependency: the ETRM metadata records that it is referenced by twelve other packages, confirming that action set resolution is a shared service across the Projects suite.

Key Procedures and Functions

• GET_ACTION_SET_ID — Returns the identifier of an action set for a given action set type code and object. This is the entry point most commonly sought by integrators and form-level code that must resolve a configuration to a concrete action set.
• GET_ACTION_SET_LINES — Retrieves the collection of line records belonging to an action set.
• GET_ACTION_SET_LINE — Retrieves a single action set line by its identifier.
• GET_ACTION_LINE_CONDITIONS — Returns the condition rows associated with an action set line, which determine whether the line is applicable.
• GET_ACTION_SET_DETAILS — Returns header-level attribute information for an action set.
• GET_ACTIVE_AUDIT_LINES — Retrieves the currently active audit lines for an action set, supporting the audit/traceability requirements of action execution.
• ADD_MESSAGE — Appends a message to the package's message buffer; the package defines a G_ERROR_EXISTS flag and encoded-error columns for this purpose.
• IS_NAME_UNIQUE_IN_TYPE — Validates that a proposed action set name is unique within its action set type.
• IS_ACTION_SET_A_SOURCE — Determines whether a given action set is used as a source (for example, when copying or referencing definitions).
• DO_LINES_EXIST and DO_AUDIT_LINES_EXIST — Existence checks for configuration lines and audit lines respectively.
• GET_LAST_PERFORMED_DATE — Returns the date on which an action set was last executed.
• CHECK_ACTION_SET_NAME_OR_ID — Resolves and validates an action set by either name or numeric identifier.
• GET_LINE_INFORMATION_MESSAGES — Returns informational messages generated while processing action set lines.

Tables Accessed

• PA_ACTION_SETS — base table storing action set headers, keyed by action set type and object.
• PA_ACTION_SET_LINES — the ordered actions within each set.
• PA_ACTION_SET_LINE_COND — conditions that gate line execution.
• PA_ACTION_SET_LINE_AUD — audit rows capturing performed, reversed, or updated actions; the package constants G_PERFORMED_ACTIVE through G_UPDATED_CUSTOM_AUDIT map to these reasons.
• PA_ACTION_SET_TYPES — the taxonomy of action set types used by GET_ACTION_SET_ID and IS_NAME_UNIQUE_IN_TYPE.
• PLITBLM — the standard EBS PL/SQL table-to-message utility used by ADD_MESSAGE.

The package also declares record and table types (number_tbl_type, action_set_lines_tbl_type, action_line_cond_tbl_type, insert_audit_lines_tbl_type, and others) matching these tables' %ROWTYPE definitions.

Usage Notes

PA_ACTION_SET_UTILS is normally invoked implicitly. Oracle Project Management setup forms call it to validate and persist action set definitions, while runtime action-processing logic calls GET_ACTION_SET_ID and GET_ACTION_SET_LINES to determine which actions apply to an event. Workflow and concurrent program logic rely on GET_LAST_PERFORMED_DATE and the audit-line routines for idempotency and traceability. Custom extensions should treat this package as an internal API: reuse the documented functions rather than querying the underlying tables directly, and avoid dependency on the "noship" source, which may change without public notice. The ETRM classification "OTHER" reinforces that it is not a supported public API.