Search Results update_card_status

Overview

The APPS.PO_KANBAN_SV package body provides the server-side logic that synchronizes Oracle Purchasing documents with the Kanban card inventory records maintained by Oracle Inventory. Its central purpose is to reflect the lifecycle of a sourcing document — a purchase order, a blanket purchase agreement release, or an internal requisition — onto the Kanban card that originated the demand. When a document is created, approved, received, or closed, the corresponding Kanban card must move through its own replenishment statuses (for example, from Empty to In Process or Full). The procedures in this package perform that status transition by resolving the Kanban card identifier from the Purchasing distribution or requisition line and then delegating the actual status update to the Inventory Kanban API.

The package is classified as an OTHER API in the ETRM registry, indicating that it is an internal EBS component rather than a formally published public API. It exists to support the Kanban replenishment feature of Oracle Purchasing and is referenced by two other packages.

Key Procedures and Functions

• UPDATE_CARD_STATUS — The primary procedure associated with the common search term update_card_status. It accepts the target card status, the document type (for example PO or requisition), and the document identifier, and returns a status indicator to the caller. Based on the document type, it opens the appropriate cursor over the Purchasing distribution or requisition line to retrieve the Kanban card identifier, then invokes the Inventory Kanban API (INV_Kanban_PVT.Update_Card_Supply_Status) to move each affected card to the requested status. Its declaration appears at the head of the package body, reflecting its role as the original and most frequently called entry point.
• UPDATE_CARD_STATUS_FULL — A companion procedure that extends the status-update logic to the complete set of distribution and requisition lines associated with a document. It is documented alongside UPDATE_CARD_STATUS and is used where a document-wide synchronization of all linked Kanban cards is required rather than a single-card transition.

Tables Accessed

• PO_DISTRIBUTIONS — The package queries this table to resolve the KANBAN_CARD_ID for purchase order headers (PO_HEADER_ID) and for agreement releases (PO_RELEASE_ID). Only rows where the Kanban card identifier is not null are considered, ensuring that non-Kanban purchasing activity is ignored.
• PO_REQUISITION_HEADERS — Used to identify internal requisitions via TYPE_LOOKUP_CODE = 'INTERNAL', restricting processing to requisitions that represent an internal Kanban replenishment demand.
• PO_REQUISITION_LINES — Joined to the requisition header to obtain the requisition line identifier and its associated KANBAN_CARD_ID, which is then passed to the Inventory API.
• DBMS_OUTPUT — Referenced for diagnostic output during package execution, a legacy of the package's original development environment.

Usage Notes

PO_KANBAN_SV is not intended for direct invocation by end users or external integrations. It is called internally by Oracle Purchasing transaction flows and by the two dependent packages registered in ETRM, typically during document submission, approval, or receipt processing when a Purchasing document carries Kanban card references. Because the package delegates the physical status change to INV_Kanban_PVT, any custom code invoking UPDATE_CARD_STATUS must supply the correct document type and identifier and must be prepared to interpret the returned status string. Customizations should avoid modifying the package body in place; the version header (115.0) and the preserved dbms_output calls indicate that the code is seeded, and changes should be layered through supported extension mechanisms. The update_card_status procedure remains the entry point most frequently sought when diagnosing Kanban card status inconsistencies between Purchasing and Inventory in release 12.1.1 and 12.2.2.