Results for “oke_deliverable_utils_pub”

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

Overview

OKE_DELIVERABLE_UTILS_PUB is a public PL/SQL utility package in the APPS schema that centralizes validation, inquiry, copy, and deletion logic for Oracle Deliverables within Oracle E-Business Suite. Deliverables in the Oracle Procurement and Projects (OKE/PA) module represent contract line items that must be shipped, procured, billed, or otherwise fulfilled; the utilities package provides a single, reusable entry point for the business rules that govern those activities. The package is classified as a public API (PUB), meaning it is intended for invocation from forms, concurrent programs, workflows, and external integration code rather than being a private helper.

Its scope spans Oracle Shipping (WSH), Manufacturing and Distribution (MDS), and Purchasing/Requisitioning flows, as reflected in procedures such as WSH_INITIATED_YN, MDS_INITIATED_YN, and REQ_INITIATED_YN. These determine the origin of a deliverable action so downstream processing can branch appropriately. The package also underpins user exit-style validation and deletion behavior for deliverables and their actions, and it is referenced by six other database objects, indicating it is an established dependency in the OKE deliverable architecture.

Key Procedures and Functions

• MDS_INITIATED_YN / WSH_INITIATED_YN / REQ_INITIATED_YN — Boolean-style checks returning whether a deliverable or action was initiated by Manufacturing/Distribution, Shipping, or Requisitioning respectively.
• ITEM_DEFINED_YN / ITEM_EXIST_YN — Confirm that the inventory item associated with a deliverable is defined and exists in the item master.
• READY_TO_SHIP_YN / READY_TO_PROCURE_YN / ITEM_SHIPPABLE_YN / ITEM_BILLABLE_YN / ITEM_PURCHASABLE_YN — Evaluate item attributes and deliverable status to determine whether a given action (ship, procure, bill, purchase) is permitted.
• ACTION_DELETABLE_YN — Determines whether a deliverable action can be safely removed given its current state and origin.
• COPY_ITEM / COPY_ACTION — Duplicate deliverable item and action records, supporting rapid entry of similar deliverable lines.
• UNIT_PRICE / CURRENCY_CODE — Retrieve pricing and currency information for a deliverable or its actions.
• DELETE_DELIVERABLE / DELETE_ACTION / DELETE_DEMAND — Housekeeping procedures that remove deliverables, their actions, or associated demand records, applying the package's validation rules first.
• BATCH_MDS / BATCH_WSH — Batch processing entry points that reconcile deliverables initiated from Manufacturing/Distribution and Shipping.

Tables Accessed

The package reads and writes the core OKE deliverable base tables: OKE_DELIVERABLES_B, OKE_DELIVERABLES_TL (translated descriptions), OKE_DELIVERABLE_ACTIONS, and the OKE_K_DELIVERABLES_S key-flexfield definition used by the Deliverables form. It queries MTL_SYSTEM_ITEMS_B (via the OKE_SYSTEM_ITEMS_V view) to validate item attributes and FND_LANGUAGES to support multilingual descriptions. PO_REQUISITIONS_INTERFACE_ALL is used when requisition-originated actions are validated or created. OKE_DELIVERABLE_REQUISITIONS_V supplies requisition context. The package leverages FND_API, FND_MSG_PUB, and FND_GLOBAL for standard API error handling and session context, and calls OKE_API, OKE_ACTION_VALIDATIONS_PKG, OKE_DELIVERABLE_ACTIONS_PKG, OKE_UTILS, and PA_DELIVERABLE_UTILS for shared business logic. DUAL and STANDARD are used for trivial and built-in constructs.

Usage Notes

OKE_DELIVERABLE_UTILS_PUB is typically invoked from the Oracle Deliverables and Contracts forms, from concurrent programs that batch-process shipping or manufacturing demand, and from custom extensions that need to check deliverable readiness or perform safe deletion. Because it is a PUB package, it is the supported public interface for these operations; custom code should call it rather than manipulating OKE_DELIVERABLES_B directly. The presence of OKE_K_DELIVERABLES_S among its dependencies confirms tight integration with the descriptive flexfield used by the Deliverables window, and callers should initialize FND_MSG_PUB message stacks before invoking procedures that may raise API errors.