Results for “copy_action”

10 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKE_DELIVERABLE_UTILS_PUB is a public PL/SQL package in the APPS schema that provides the core utility layer for the Oracle EBS Project Contracts (OKE) deliverable functionality. Deliverables represent tangible or intangible items that a project or contract must produce, such as hardware shipments, documents, or services. This package centralizes the business rules that determine whether a deliverable is initiated by a particular source system, whether the associated item is shippable, billable, or purchasable, and whether a deliverable, action, or demand record may be safely deleted. It also supplies pricing and currency conversion helpers, copy routines, and batch processing entry points for integration with Order Management (WSH) and Manufacturing (MDS). In EBS 12.1.1 and 12.2.2 the package holds a VALID status in the APPS schema and exposes an API classification of PUB, indicating it is intended for supported external invocation rather than internal-only use.

Key Procedures and Functions

The 24 documented procedures and functions fall into several functional groups.

Tables Accessed

The package reads and writes the OKE deliverables base and translation tables (OKE_DELIVERABLES_B, OKE_DELIVERABLES_TL) and their action and key-flexfield children (OKE_DELIVERABLE_ACTIONS, OKE_K_DELIVERABLES_S). It queries MTL_SYSTEM_ITEMS_B to validate item attributes and FND_LANGUAGES to resolve translated descriptions. It interacts with PO_REQUISITIONS_INTERFACE_ALL to support requisition-based demand creation, and uses DUAL for simple expression evaluation. These accesses allow the package to enforce data integrity and item-master consistency across deliverable lifecycle operations.

Usage Notes

OKE_DELIVERABLE_UTILS_PUB is referenced by six other packages, including OKE_AMG_GRP and several Project Accounting packages (PA_ACTIONS_PUB, PA_ACTIONS_PVT, PA_DELIVERABLE_PVT, PA_DELIVERABLE_UTILS, PA_TASK_UTILS). It is therefore invoked indirectly from the Project Contracts forms, from concurrent programs that process deliverable batches, and from custom extensions that require the same validation logic used by the standard application. Because it depends only on STANDARD and SYS, it is relatively self-contained. Oracle supports invocation through its public procedures and functions; internal implementation details are not exposed.