Search Results get_ci_open_actions




Overview
Explore in AI Chat

Overview

PA_CI_ACTIONS_UTIL is a utility package in the Oracle E-Business Suite Projects (PA) module that supports the Control Items (CI) action framework. Control Items represent issues, change requests, or action items tracked against a project, and each control item carries a lifecycle of actions that must be created, numbered, assigned, monitored, and closed. PA_CI_ACTIONS_UTIL provides the shared PL/SQL logic that forms and concurrent programs use to query and manipulate those actions without duplicating business rules. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema and relies on APPS synonyms for data access. The specification header dates to release 11i (115.9), and the package remains available in 12.1.1 and 12.2.2 as an internal utility rather than a public, supported API. It is classified as a UTIL object and is referenced by five other packages, confirming its role as a shared dependency within the Control Items subsystem.

Key Procedures and Functions

The documented specification exposes eight callable units:

  • ACTION_WITH_REPLY — A function that indicates whether a given control item action has an associated reply, used to drive display or workflow decisions.
  • CHECKHZPARTYNAME_OR_ID — A procedure that validates a resource against Oracle Receivables party data (HZ), accepting either a party name or an identifier and returning the resolved party identifier, resource type, and standard return status/message outputs.
  • GET_NEXT_CI_ACTION_NUMBER — A function returning the next sequential action number for a control item, ensuring action numbering remains unique and contiguous.
  • GET_PARTY_ID — A function that resolves the party identifier associated with a given FND user.
  • GET_CI_OPEN_ACTIONS — The function the user searched for. It returns a count of open actions for a control item, optionally scoped to a specific control item identifier; a NULL argument implies a broader scope.
  • GET_MY_ACTIONS — A function returning a count of actions filtered by action status and, optionally, by control item, supporting personal worklist views.
  • CHECK_OPEN_ACTIONS_EXIST — A function returning a status indicator that reports whether any open actions remain for a control item, typically used to block closure of the parent control item.
  • GET_TOP_PARENT_ACTION — A function that walks the action hierarchy to return the top-level parent action for a given action identifier.

Tables Accessed

Through APPS synonyms the package reads and writes the Control Items tables and their supporting reference data:

  • PA_CI_ACTIONS — The primary action table; source of open-action counts, action numbers, statuses, and parent-child relationships.
  • PA_CI_COMMENTS — Comment records attached to control item actions, consulted when evaluating replies.
  • PA_CONTROL_ITEMS — The parent control item definition that scopes action queries.
  • FND_USER and PER_ALL_PEOPLE_F — Used to resolve the current user to a person and thence to a party identifier, and to support "my actions" filtering.

Party validation logic may also touch Oracle Receivables (HZ) party tables depending on the resource type supplied.

Usage Notes

PA_CI_ACTIONS_UTIL is an internal utility, not a documented public API with guaranteed upward compatibility. It is most commonly invoked from Control Items and Issue Tracking forms through the OA Framework or Forms-based UI layer, and from the concurrent programs and workflow activities that generate and monitor control item actions. The open-action functions (GET_CI_OPEN_ACTIONS, CHECK_OPEN_ACTIONS_EXIST, GET_MY_ACTIONS) are typically called before permitting a control item to be closed or to populate action dashboards. Developers extending Control Items functionality should call these functions rather than querying PA_CI_ACTIONS directly, since the package encapsulates the status and hierarchy rules. Because the package runs AUTHID CURRENT_USER, callers must have appropriate grants on the underlying tables, and any custom code should be regression-tested across 12.1.1 and 12.2.2, where the package is delivered but may be patched independently of the public APIs.