Search Results jmf_shikyu_batch_s

Overview

JMF_SUBCONTRACT_ORDERS_PVT is the private implementation package body behind the Oracle E-Business Suite Process Manufacturing (OPM) subcontracting feature. It belongs to the family of JMF_SHIKYU objects that support the "Shikyu" (subcontracting) settlement process, in which a manufacturing organization issues components to a supplier, receives the processed output back, and settles the supplier's charges against the resulting production or purchase transactions.

In Oracle EBS 12.1.1 and 12.2.2, this package acts as the engine that drives the JMF Subcontract Orders concurrent request. It reads subcontract order definitions, expands them into individual batch and component allocation records, validates those records against purchasing, inventory, and item master data, and then drives allocation, replenishment, and settlement activity through the lower-level JMF_SHIKYU API layer. The PVT (private) classification indicates that the package is not part of the public, committed API surface and is intended for internal use by the application's concurrent programs and by other APIs within the same family.

The object is registered with status VALID in the APPS schema and depends on a broad set of Oracle modules, including FND (Concurrent, File, Global, Log, Message, Profile, MSG_PUB), BOM, WIP, INV, MTL, PO, OE, and HR. No database object references this package body directly, confirming its role as a top-level driver rather than a reusable public interface.

Key Procedures and Functions

The package exposes two documented entry points. Their names follow the standard Oracle worker/manager pattern, in which a single manager procedure is invoked from the concurrent program and dispatches work to the worker.

• SUBCONTRACT_ORDERS_MANAGER — The controlling routine for the subcontract orders process. It is the entry point called by the concurrent program. It initializes the environment (through FND_GLOBAL, FND_CONCURRENT, and FND_MSG_PUB), opens output and log files via FND_FILE, iterates over the set of eligible subcontract orders, and invokes SUBCONTRACT_ORDERS_WORKER for each order or batch range. It also handles message accumulation and the final completion status of the concurrent request.
• SUBCONTRACT_ORDERS_WORKER — The processing routine that performs the substantive work for a single subcontract order. It reads order lines and shipment details from the purchasing tables, resolves the associated item and unit-of-measure information, creates or updates allocation and replenishment records, and calls the JMF_SHIKYU_PVT utilities (JMF_SHIKYU_ALLOCATION_PVT, JMF_SHIKYU_ONT_PVT, JMF_SHIKYU_WIP_PVT) to generate the corresponding inventory and WIP transactions. It also manages the temporary staging table JMF_SUBCONTRACT_ORDERS_TEMP and applies error handling through FND_MESSAGE and FND_LOG.

Tables Accessed

The package reads and writes a broad cross-module table set, using APPS synonyms throughout. The main tables include:

• JMF_SUBCONTRACT_ORDERS and JMF_SUBCONTRACT_ORDERS_TEMP — the persistent and staging structures that hold the subcontract order definition and the intermediate results of processing.
• JMF_SHIKYU_BATCH_S, JMF_SHIKYU_ALLOCATIONS, JMF_SHIKYU_COMPONENTS, and JMF_SHIKYU_REPLENISHMENTS — the Shikyu allocation, component, and replenishment records that the worker creates and consumes.
• PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_RELEASES_ALL, and PO_ASL_ATTRIBUTES — used to resolve purchase order, shipment, distribution, and approved supplier list details for the subcontracting supplier.
• MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_PARAMETERS, MTL_INTERORG_PARAMETERS, MTL_UNITS_OF_MEASURE, and MTL_UNITS_OF_MEASURE_VL — used for item master, organization, inter-organization transfer, and unit-of-measure validation and conversion (via INV_CONVERT).
• BOM_OPERATIONAL_ROUTINGS and WIP_REQUIREMENT_OPERATIONS — used to associate the subcontract operation with the routing and WIP requirement operations of the parent manufacturing order.
• OE_ORDER_LINES_ALL and HR_ORGANIZATION_INFORMATION — used to link to the sales order line driving the subcontract demand and to resolve organization classification details.

Oracle's own dictionary object and collection types (PLITBLM, STANDARD, WIP_COMPONENT_OBJ_T, WIP_COMPONENT_TBL_T) are also referenced for bulk processing.

Usage Notes

JMF_SUBCONTRACT_ORDERS_PVT is invoked primarily from the Oracle Process Manufacturing Subcontract Orders concurrent program. In a typical run, the request parameters select the operating unit, supplier, and date range, and the manager procedure processes the qualifying subcontract orders in the background, writing output to the concurrent request log and output file through FND_FILE.

Because the package is classified as PVT and is documented as not being referenced by any database object, it should not be called directly from custom forms, triggers, or third-party extensions. Customizations that require subcontract order processing should instead invoke the public JMF_SHIKYU APIs (JMF_SHIKYU_ALLOCATION_PVT, JMF_SHIKYU_ONT_PVT, JMF_SHIKYU_WIP_PVT, JMF_SHIKYU_UTIL) or use the standard concurrent program. Where troubleshooting is required, DBMS_OUTPUT and FND_LOG messages emitted by the package, together with the contents of JMF_SUBCONTRACT_ORDERS_TEMP, provide the primary diagnostic trail.

Note that the user's search term jmf_shikyu_batch_s is not this object but one of its documented dependencies. JMF_SHIKYU_BATCH_S is the Shikyu batch staging table that JMF_SUBCONTRACT_ORDERS_PVT reads and writes while processing subcontract orders; the dependency reported above reflects that relationship.