Results for “jmf_process_shikyu_rcv_trx_pvt”

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

Overview

The APPS.JMF_PROCESS_SHIKYU_RCV_TRX_PVT package is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite Process Manufacturing (OPM) and Supply Chain Execution stack. Its name reflects its role: "Shikyu" is the Japanese term for "delivery" or "supply," which in Oracle EBS terminology corresponds to the subcontracting replenishment and consumption flow. The package processes receiving transactions associated with shikyu-style subcontract manufacturing, where a supplier performs work on components supplied by the manufacturer, and the resulting assemblies, returns, and component movements must be reflected in Oracle Inventory and Purchasing.

Under the ETRM 12.2.2 documentation, the package is classified as a private API, indicating it is intended for internal invocation by Oracle's own concurrent programs and other packages rather than for direct customer use. It is schema-owned by APPS and is currently VALID. Its principal consumer is the concurrent program package JMF_SHIKYU_RCV_TRANSACTIONS_CP, which drives the batch processing of shikyu receiving transactions. The package is self-referencing in the dependency tree and depends only on SYS.STANDARD in the documented excerpt, though its transactional logic relies on the APPS synonyms listed below.

Key Procedures and Functions

• PROCESS_SHIKYU_RCV_TRX — The primary driver procedure. It accepts and processes shikyu receiving transactions, orchestrating validation, staging, and posting to the receiving and inventory interfaces. It is the entry point invoked by the concurrent program package.
• PROCESS_OSA_RECEIPT — Handles the receipt leg of an OSA (Outsourced Assembly / outside processing) transaction, ensuring the assembled or processed item is received back into inventory against the appropriate sourcing document.
• PROCESS_OSA_RETURN — Manages the return of items previously received under an OSA arrangement, applying reversal logic to receiving and inventory balances.
• PROCESS_COMPONENT_RETURN — Processes the return of components issued to a supplier for subcontract work, adjusting component consumption and supply records accordingly.

No parameter signatures are documented in ETRM; the procedures should be treated as internal and invoked only through their supported calling wrapper, JMF_SHIKYU_RCV_TRANSACTIONS_CP.

Tables Accessed

The package reads and writes through APPS synonyms across purchasing, receiving, order management, and shikyu-specific tables:

• RCV_STAGING_TABLE, RCV_TRANSACTIONS_INTERFACE — staging and interface tables for inbound receiving transactions.
• RCV_SHIPMENT_LINES, RCV_SUPPLY, RCV_TRANSACTIONS — shipment, supply, and posted receiving transaction records.
• PO_HEADERS_ALL, PO_LINE_LOCATIONS_ALL — purchase order and shipment schedule context for subcontract receipts.
• OE_ORDER_LINES_ALL — sales order line linkage where receipts originate from order-driven flows.
• JMF_SHIKYU_COMPONENTS, JMF_SHIKYU_REPLENISHMENTS, JMF_SHIKYU_ADJUSTMENTS, JMF_SUBCONTRACT_ORDERS — shikyu component, replenishment, adjustment, and subcontract order data specific to the shikyu process.
• MTL_PARAMETERS, MTL_UNITS_OF_MEASURE_TL — inventory organization defaults and unit-of-measure validation.
• HR_ORGANIZATION_INFORMATION — organization classification and attribute lookups.

Usage Notes

Because JMF_PROCESS_SHIKYU_RCV_TRX_PVT is a private API, Oracle does not publish a supported public signature. It is invoked in the context of the shikyu receiving concurrent program JMF_SHIKYU_RCV_TRANSACTIONS_CP, which submits batches of transactions for processing. Custom code should not call this package directly; instead, developers should raise transactions through the standard receiving open interface (RCV_TRANSACTIONS_INTERFACE) or through the concurrent program, allowing this package and its wrapper to perform the shikyu-specific logic. Any direct dependency risks breakage during patching, since private APIs are not covered by Oracle's compatibility guarantees.