Search Results validate_param_and_create

Overview

PA_CONTROL_API_PVT is the private implementation package for the Oracle Projects control item API layer in Oracle E-Business Suite 12.1.1 and 12.2.2. Control items represent project-level governance artifacts such as issues, risks, changes, action items, and similar tracked entities managed through the Project Control functionality. The package is owned by the APPS schema and carries the "PVT" classification, indicating that it is not intended for direct external invocation; the public interface is exposed through PA_CONTROL_API_PUB, which calls into this private package to perform validation, attribute assembly, and DML against the underlying control item tables.

In practice, PA_CONTROL_API_PVT encapsulates the core business logic that governs creation, retrieval, modification, and deletion of control items and their associated impacts, comments, and supplier details. Because it sits beneath the public API, it enforces internal business rules and referential integrity before any row is written.

Key Procedures and Functions

The ETRM 12.2.2 documentation lists ten documented procedures and functions in this package:

• UPDATE_IMPACTS — Maintains the impact records linked to a control item, synchronizing entries in the impact tables when an item's affected classifications change.
• ADD_SUPPLIER_DETAILS — Inserts or updates supplier-level detail records associated with a control item, used where the item involves vendor participation.
• CHECK_CREATE_CI_ALLOWED — Determines whether creation of a control item is permitted for the given context, forming the primary gatekeeper before insert processing.
• VALIDATE_PARAM_AND_CREATE — Validates incoming API parameters and proceeds to create the control item when validation succeeds.
• CHECK_CREATE_ACTION_ALLOW — Confirms that creation of an associated action is allowed against the parent control item.
• VALIDATE_ASSIGNEE_ID — Verifies the assignee supplied for an action is valid and eligible.
• VALIDATE_ACTION_ATTRIBUTES — Performs attribute-level validation on the action record prior to persistence.
• CREATE_ACTION — Inserts the action row and its dependent records once validation completes.
• VALIDATE_PRIV_AND_ACTION — Checks both privilege and action-level rules together, ensuring the caller is authorized for the requested operation.
• DELETE_CI — Removes a control item and manages the related cleanup of comments, impacts, and supplier details.

Tables Accessed

The package works across a defined set of APPS synonyms. The core transactional tables are PA_CONTROL_ITEMS and its translation/secure view PA_CONTROL_ITEMS_S, which hold the control item header records. Related child tables include PA_CI_ACTIONS, PA_CI_COMMENTS, PA_CI_IMPACTS, PA_CI_IMPACT_TYPE_USAGE, and PA_CI_SUPPLIER_DETAILS, which store actions, comments, impact assignments, impact type configuration, and supplier detail respectively. PA_CI_TYPES_B supplies control item type definitions.

Reference and validation data is drawn from PA_PROJECTS_ALL, PA_PROJECT_PARTIES, PA_PROJECT_STATUSES, PA_PROJ_ELEMENTS, PA_CLASS_CODES, PA_OBJ_STATUS_LISTS, and HZ_PARTIES, the latter used for party validation where suppliers are involved. These reads support assignee validation, status checks, and impact classification lookups.

Usage Notes

PA_CONTROL_API_PVT is invoked indirectly. The public package PA_CONTROL_API_PUB is its sole documented referrer among other packages, and both are typically called from the Project Management and Project Control forms, from concurrent programs that process control item data, and from custom extensions integrated through the public API. Direct calls to the PVT layer are not recommended and are unsupported in production.

The package depends on FND_API for the standard API error-handling framework and on PA_INTERFACE_UTILS_PUB for shared interface utilities. Custom code should invoke PA_CONTROL_API_PUB, allowing this private implementation to enforce validation, privilege checks, and multi-table DML consistently across all entry points.