Search Results create_ci_action

Overview

APPS.PA_CI_ACTIONS_PUB is a public PL/SQL API package in Oracle E-Business Suite that exposes the business logic governing CI Actions (Collection/Issues and Actions records) within Oracle Projects. In the Oracle Projects suite, a "CI" record represents a collection of issues, deliverables, or action items tracked against a project, and each discrete task or follow-up against that record is persisted as a CI Action. PA_CI_ACTIONS_PUB is the supported, externally callable interface through which forms, concurrent programs, and custom extensions may create, modify, cancel, close, reassign, and comment upon those actions without directly manipulating the underlying base tables.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer. Its header comment identifies it as a published API (the _PUB suffix and the $Header tag referencing PACIACPS.pls). Because it is classified as a PUB API in the ETRM/12.2.2 metadata, it is intended for external consumption and is the correct entry point for programmatic manipulation of CI actions. All procedures follow the Oracle Application Object Library PL/SQL API conventions: they accept p_api_version, p_init_msg_list, p_commit, p_validate_only, and p_max_msg_count control parameters and return status through x_return_status, x_msg_count, and x_msg_data.

Key Procedures and Functions

The documented interface comprises six procedures:

• CREATE_CI_ACTION — Creates a new CI Action record. This is the procedure the user's search term create_ci_action targets. It accepts identifying and descriptive attributes for the action, including the parent CI identifier, action type, assignee, resource type, required/sign-off dates and flags, comment text, and optional source action for copying. The generated action identifier is returned through P_CI_ACTION_ID, and standard audit columns default to the current user and system date.
• CANCEL_CI_ACTION — Cancels an existing action identified by P_CI_ACTION_ID. It requires a record version number for optimistic locking and accepts a cancellation comment, with audit columns defaulted from the session.
• CLOSE_CI_ACTION — Closes a CI Action, marking it complete and removing it from the active worklist.
• REASSIGN_CI_ACTION — Transfers ownership of an existing action to a different assignee or resource.
• ADD_CI_COMMENT — Appends a new comment to an existing CI Action.
• UPDATE_CI_COMMENT — Modifies an existing comment attached to a CI Action.

Tables Accessed

The ETRM metadata for this package does not enumerate the base tables it references through APPS synonyms. Functionally, the procedures operate against the CI action and CI comment entity tables owned by Oracle Projects, writing new action rows on create, updating status and assignment columns on cancel/close/reassign, and inserting or updating comment records for the comment procedures. The audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are populated from fnd_global.user_id and sysdate, ensuring the standard Oracle EBS who-columns remain consistent across all calls.

Usage Notes

PA_CI_ACTIONS_PUB is typically invoked from the Oracle Projects issue and action tracking forms, from concurrent programs that process or close actions in bulk, and from custom PL/SQL extensions that need to raise or maintain CI actions outside the standard UI. Because the package is a public API, customizations should call these procedures rather than performing direct DML on the underlying tables.

Callers should observe the following conventions. p_validate_only defaults to FND_API.g_true, so a call performs validation only unless explicitly set to false; callers performing the real transaction must pass FND_API.g_false to commit changes. p_init_msg_list defaults to true, initializing the message stack at entry. Return status must always be inspected against FND_API.g_ret_sts_success, with x_msg_count and x_msg_data used to retrieve error detail. p_commit governs whether the API issues its own commit, allowing callers to include the call in a larger transactional unit. The package is referenced by one other package in the ETRM inventory, confirming it is a shared, reused interface component within Oracle Projects.