Search Results process_replenishment_po

Overview

JMF_SHIKYU_PO_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PVT (private) API within the ETRM repository. It forms part of the Oracle Process Manufacturing (OPM) shop floor and subcontracting component of the EBS application stack, and its responsibility is narrowly focused: it encapsulates the purchasing-related calls that the Interlock logic requires when SHIKYU transactions are processed. SHIKYU is the Japanese term for subcontracting, and within ETRM it denotes the processing of subcontracting orders in which components are supplied to a supplier and finished goods are received back. The package header dates to May 2005 and carries a source revision header from July 2008 for release 12.1.0, and it remains present in the 12.2.2 code line. It is not a public or customer-facing API; it is invoked internally by the subcontracting interlock process to reconcile purchase order data with SHIKYU shipment line activity.

Key Procedures and Functions

The documented package exposes a single public procedure: PROCESS_REPLENISHMENT_PO. Per the source commentary, this procedure populates data in the purchasing interface tables and creates a replenishment purchase order or shipment for the subcontracting order shipment line. It accepts an action indicator that governs the operating mode — create, delete, or update — together with identifying information for the subcontracting purchase order shipment line, the quantity, and the item. On completion it returns the resulting purchase order line location identifier and a return status value that callers inspect to determine success or failure. Because the procedure works through the PO interface tables rather than writing directly to the base purchasing tables, it adheres to the standard EBS pattern of staging records for the purchasing interface concurrent programs. No other procedures or functions are documented in the ETRM metadata for this package.

Tables Accessed

The package reads and writes a defined set of purchasing and manufacturing tables through APPS synonyms. On the transactional side it references JMF_SUBCONTRACT_ORDERS and JMF_SHIKYU_COMPONENTS, which supply the subcontracting order and component context that drives replenishment. It references MTL_SYSTEM_ITEMS_B to resolve item master attributes such as the item identifier and its purchasing characteristics. The purchasing interface tables form the primary write target: PO_HEADERS_INTERFACE and PO_HEADERS_INTERFACE_S, PO_LINES_INTERFACE and PO_LINES_INTERFACE_S, and PO_DISTRIBUTIONS_INTERFACE and PO_DISTRIBUTIONS_INTERFACE_S. These staged rows are subsequently processed by the standard Purchasing interface programs. The package also consults the base purchasing tables PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL, the latter supplying the line location identifier returned to the caller. Finally, it references FND_USER, HR_ALL_ORGANIZATION_UNITS, and HR_ORGANIZATION_INFORMATION, which are used to derive the operating unit and user context required when stamping interface records.

Usage Notes

JMF_SHIKYU_PO_PVT is an internal, private API and should not be called directly from custom code without a clear understanding of the SHIKYU processing flow; Oracle does not guarantee its signature across releases and may change it in patches or upgrades. It is invoked from within the OPM subcontracting interlock logic that processes SHIKYU transactions, typically in response to shop floor material or receipt movements that trigger component replenishment. The ETRM metadata records that one other package references it, confirming its role as a subordinate utility in the subcontracting call chain. Customers requiring equivalent functionality should prefer the public OPM subcontracting or purchasing APIs. Where the package is exercised indirectly through a concurrent program or an OPM-manufacturing form, the standard purchasing interface programs must run afterwards to convert the staged PO_HEADERS_INTERFACE, PO_LINES_INTERFACE, and PO_DISTRIBUTIONS_INTERFACE rows into live purchase orders. Trace files and interface errors should be reviewed when the returned status indicates failure.