Search Results oke_deliverable_actions_pkg




Overview
Explore in AI Chat

Overview

OKE_DELIVERABLE_ACTIONS_PKG is a PL/SQL package owned by APPS and declared with AUTHID CURRENT_USER, meaning its database objects are resolved against the privileges of the invoking user rather than the package owner. It belongs to the Oracle E-Business Suite Project Contracts (OKE) module family, which manages contract deliverables — contractual commitments such as shipments, demands, and requisitions tied to a project or contract line.

The package acts as a control layer that converts a deliverable action into a downstream execution artifact. A deliverable action represents an intent recorded against a deliverable (for example, "ship these goods" or "raise a demand"). The package interprets that action and creates the corresponding transactional record, then reports success or failure through a standard message-list interface. It is classified as an OTHER API, not a public, supported open interface, which means Oracle does not commit to its signature or behavior across releases.

Key Procedures and Functions

  • CREATE_SHIPMENT — The procedure the user searched for. It takes an action identifier and an initial message list, and returns an identifier, a return status, a message count, and message data. It reads a deliverable action and creates the shipment-side execution record for that action, writing back the new record ID and any error context.
  • CREATE_DEMAND — Same call pattern as CREATE_SHIPMENT. Generates a demand for the deliverable action, typically feeding planning or scheduling so the requirement is visible to MRP.
  • CREATE_REQUISITION — Same call pattern. Creates a purchasing requisition through the requisition interface, translating a contract deliverable action into a sourcing document.
  • DELETE_ROW — Removes a single deliverable action row using only the action ID.
  • DELETE_ACTION — Removes the action and its associated effects, taking only the action ID.
  • DELETE_DELIVERABLE — Removes a deliverable by its deliverable ID.

The three create procedures share a uniform OUT parameter contract: an ID, a return status, a message count, and a concatenated message data string. Callers must always inspect X_Return_Status and X_Msg_Count rather than assuming success from the absence of an exception.

Tables Accessed

The package reads and writes OKE_DELIVERABLES_B and OKE_DELIVERABLES_TL, the base and translation tables holding the deliverable definition, and OKE_DELIVERABLE_ACTIONS, which stores the action to be processed. BOM_PARAMETERS, MTL_PARAMETERS, MRP_SCHEDULE_ITEMS, MRP_SCHEDULE_DATES, MRP_SCHEDULE_DATES_S, and MRP_SCHEDULE_CONSUMPTIONS provide the planning and item-validation context needed to build demands and shipments correctly, including schedule dates and consumption records. MTL_SYSTEM_ITEMS validates the item master, and FND_USER resolves the acting user. PO_REQUISITIONS_INTERFACE_ALL is the staging table for the requisition interface used by CREATE_REQUISITION. DUAL supports trivial single-row queries. Two other packages reference this package, confirming it is invoked programmatically rather than only from the UI.

Usage Notes

In EBS 12.1.1 and 12.2.2 this package is normally called indirectly, from the Project Contracts deliverable action form or from a concurrent program that processes pending actions. The form passes the action ID and the caller's message list; the package then delegates to the appropriate creation path and returns diagnostics for display.

Because it is an internal, unsupported API, custom code invoking CREATE_SHIPMENT directly should be treated as a customization risk: capture X_ID and X_Return_Status, always initialize the message list, and validate that the action row is in a processable state before the call. Avoid calling delete procedures without first confirming the action has no dependent downstream documents, since the delete routines accept only an ID and perform no interactive confirmation.