Search Results get_pick_status




Overview
Explore in AI Chat

Overview

OE_LINE_STATUS_PUB is a public PL/SQL package in the APPS schema that centralizes the determination of order line status within Oracle Order Management. Rather than allowing each form, workflow utility, or integration program to re-implement status logic locally, this package exposes a consistent, governed interface for evaluating whether a given order line is closed, cancelled, shipped, picked, received, invoiced, or in a purchase-release state. Because the package is classified as a public API (PUB), it forms part of the supported extension surface for Oracle E-Business Suite 12.1.1 and 12.2.2.

The package is documented as VALID in the ETRM repository and depends only on SYS.STANDARD at the declared dependency level, while internally referencing several APPS synonyms. It is referenced by six other program units, including ASO_ORDER_INT, ASO_ORDER_STATUS_PVT, CTO_WORKBENCH_UTIL_PK, OE_LINE_STATUS_PUB itself (recursion or internal calling), OE_OE_FORM_LINE, and OE_WF_UPGRADE_UTIL, confirming its role as a shared status-evaluation utility across Order Management, Oracle Configurator, and Order Capture.

Key Procedures and Functions

The documented package interface exposes fifteen procedures and functions. Their purposes are as follows:

  • GET_CLOSED_STATUS — Evaluates and returns whether an order line has reached the closed status.
  • GET_CANCELLED_STATUS — Determines whether an order line is in a cancelled state.
  • GET_PURCHASE_RELEASE_STATUS — Returns the status relating to purchase release activity, used when lines flow to procurement.
  • GET_SHIP_STATUS — Determines whether the line has been shipped.
  • GET_PICK_STATUS — Determines whether the line has been picked in the warehouse.
  • GET_RECEIVED_STATUS — Determines whether the line has been received.
  • GET_INVOICED_STATUS — Determines whether the line has been invoiced.
  • GET_LINE_STATUS — Returns the overall status of the order line, typically serving as the primary entry point that consolidates the individual status checks above.

The metadata does not document parameter signatures for these routines; parameter lists should not be assumed. Each routine name indicates a single-purpose status predicate or accessor, and callers should consult the package specification in the target instance for exact arguments and return types.

Tables Accessed

The package operates against the following APPS synonyms:

Oracle ETRM does not classify these accesses as reads or writes in the supplied metadata; however, the surrounding dependency chain (including OE_WF_UPGRADE_UTIL and OE_OE_FORM_LINE) is consistent with a predominantly read-oriented status derivation, with possible status updates performed by dependent workflows.

Usage Notes

OE_LINE_STATUS_PUB is typically invoked when a form, workflow process, or concurrent program must establish the current state of an order line without directly querying OE_ORDER_LINES or duplicating business rules. The presence of OE_OE_FORM_LINE among its referencers indicates use from the Order Management forms layer; ASO_ORDER_INT and ASO_ORDER_STATUS_PVT indicate use from Order Capture integration and status processing; CTO_WORKBENCH_UTIL_PK indicates use from the Configurator workbench; and OE_WF_UPGRADE_UTIL indicates use during workflow upgrade processing.

Because the package is classified PUB, custom code may call it, but should do so through the documented specification and should avoid relying on undocumented behaviour. When troubleshooting status variances between Order Management forms, workflow notifications, and integration programs, OE_LINE_STATUS_PUB is the logical first point of investigation, as it is the shared authority those components consult.