Search Results process_misc_issue




Overview
Explore in AI Chat

Overview

APPS.JMF_SHIKYU_INV_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Process Manufacturing (OPM) module, specifically associated with the SHIKYU subcontracting interlock functionality. The package header, dated 2005, declares that it "contains INV related calls that the Interlock accesses when processing SHIKYU transactions." Its role is to bridge SHIKYU subcontracting events and standard Oracle Inventory transactions by wrapping the core inventory transaction engine and invoking it with the appropriate transaction types. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking session rather than the defining schema. Because it is classified as a private package, it is intended for internal consumption by Oracle's SHIKYU interlock code rather than as a public extension API.

Key Procedures and Functions

The package exposes seven documented procedures that map distinct inventory and WIP transaction scenarios to the underlying inventory transaction engine:

  • PROCESS_TRANSACTION — The central internal engine routine. Other procedures in the package delegate to it, passing the appropriate transaction type so that a specific inventory movement is processed. It forms the common entry point for all transaction types handled by the package.
  • PROCESS_MISC_RCPT — Processes a miscellaneous receipt transaction into Inventory. Its documented comment states that it invokes Process_Transaction with the appropriate transaction type for a miscellaneous receipt, and it is parameterized by subcontract PO shipment identifier, quantity, unit of measure, and a return status out parameter.
  • PROCESS_MISC_ISSUE — Processes a miscellaneous issue transaction out of Inventory. Like Process_Misc_Rcpt, it delegates to Process_Transaction after supplying the correct transaction type for an issue.
  • PROCESS_WIP_COMPLETION — Handles the WIP completion transaction, recording finished goods receipt against a discrete job as part of the SHIKYU processing flow.
  • PROCESS_WIP_ASSY_RETURN — Handles the return of an assembly from WIP, reversing or reducing a prior completion.
  • PROCESS_WIP_COMPONENT_RETURN — Handles the return of components previously issued to a discrete job, returning material to inventory.
  • PROCESS_WIP_COMPONENT_ISSUE — Handles the issue of components to a WIP discrete job.

All seven procedures ultimately funnel into the common transaction-processing path, ensuring consistent validation, transaction type selection, and return status handling across SHIKYU-driven inventory and WIP movements.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • JMF_SUBCONTRACT_ORDERS — Stores subcontracting order information for SHIKYU processing; the package reads it to identify the subcontracting context (including the subcontract PO shipment) for which a transaction is being processed.
  • MTL_MATERIAL_TRANSACTIONS_S — The Inventory transaction base table; the package writes processed transaction records here, or reads them to validate prior activity.
  • MTL_TRANSACTIONS_INTERFACE — The inventory transaction interface table. The package populates this table so that the standard Inventory transaction manager can process the SHIKYU-related movements.
  • WIP_DISCRETE_JOBS — Provides discrete job context for the WIP-related procedures (completion, assembly return, component issue and return).
  • WIP_PARAMETERS — Supplies WIP system parameter settings that govern transaction behavior and validation.
  • WIP_REQUIREMENT_OPERATIONS — Records component requirements against discrete job operations, used when issuing or returning WIP components.

Usage Notes

JMF_SHIKYU_INV_PVT is a private package, and Oracle does not publish it as a supported public API. It is typically invoked indirectly: the SHIKYU interlock, running as part of process manufacturing subcontracting flows, calls the appropriate procedure to push a subcontracting transaction into Inventory or WIP. ETRM metadata indicates the package is referenced by two other packages, confirming that callers are other Oracle internal packages rather than forms or concurrent programs directly. Custom code should not call these procedures directly, as parameter signatures and behavior are subject to change without notice; supported integration should use the standard Inventory transaction interface (MTL_TRANSACTIONS_INTERFACE) and the public transaction managers instead.