Search Results create_and_schedule_iso

Overview

The APPS.MRP_CREATE_SCHEDULE_ISO package body is a component of the Oracle E-Business Suite manufacturing and supply chain execution layer, specifically supporting the creation and scheduling of inter-organization (ISO) supply and transfer activity. In the Oracle EBS 12.1.1 and 12.2.2 environments, this package operates within the MRP schema family and is classified as an "OTHER" API, meaning it is not part of a formally versioned public API set but is instead invoked internally by concurrent programs and dependent package logic. Functionally, the package orchestrates the submission of concurrent requests that release inter-organization transfer demand generated by planning runs. The module naming convention (MRPCISOB.pls) and the ISO prefixes on its procedures link it directly to the Oracle Advanced Supply Chain Planning and MRP inter-org sourcing flows, where planned DRP (Distribution Requirements Planning) transfers must be translated into executable ISO release and re-scheduling requests. The header line reference 120.12.12010000.3 indicates the file was last updated in 2008 and remains the shipped version across the 12.1.1 and 12.2.2 code lines.

The package provides both logging utilities and core processing procedures. The logging procedures wrap FND_FILE calls to write diagnostic output to the concurrent request log and output files, while a debug procedure conditionally emits messages based on the MRP_DEBUG profile option. The business-critical procedures submit and manage the ISO release concurrent requests that propagate planned transfer orders into the transactional supply chain.

Key Procedures and Functions

The documented procedures number four and reflect a narrow, focused responsibility set:

• LOG_MESSAGE — Writes informational and error text to the concurrent program log file via FND_FILE.PUT_LINE. It is used throughout the package to record request IDs and status messages.
• MSC_RELEASE_ISO — The central procedure that submits the MSC_RELEASE_ISO concurrent program in the MSC application. Based on an incoming load type parameter, it distinguishes between an ISO load and an ISO re-schedule, populating the appropriate IN OUT NOCOPY argument with the returned concurrent request ID and writing that ID to the log.
• CREATE_AND_SCHEDULE_ISO — The procedure corresponding to the user's search term create_and_schedule_iso. It drives the creation and scheduling of inter-organization transfer supply, coordinating the release flow managed by the package.
• CREATE_IR_ISO — Compared to the other procedures, this one handles the creation of internal requisition-based ISO activity, bridging the transfer mechanics with the requisition and order tables referenced by the package.

The absence of explicit parameter lists in the package body excerpt means only the purposes above should be relied upon; callers must obtain exact signatures from the shipped source.

Tables Accessed

The package reads and writes several core EBS tables (via APPS synonyms), consistent with its role in supply creation and order release:

• OE_ORDER_HEADERS_ALL — accessed for internal sales order activity generated when ISO supply results in an order.
• PO_SYSTEM_PARAMETERS_ALL and FINANCIALS_SYSTEM_PARAMS_ALL — read to resolve purchasing and financial system defaults governing sourcing and requisition behavior.
• MRP_ORG_TRANSFER_RELEASE — the primary ISO release table linking planned transfer information to executable releases.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — accessed to resolve customer and party information for internal order creation.
• FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — read to retrieve profile settings such as the debug flag.
• PLITBLM — a PL/SQL internal table used for name-value pairs during processing.

Usage Notes

This package is invoked primarily from concurrent programs and from other packages rather than from user-facing forms directly. The ETRM metadata indicates it is referenced by one other package, confirming its role as a subordinate utility in the planning-to-execution flow. The MSC_RELEASE_ISO procedure demonstrates the standard pattern: it calls FND_REQUEST.SET_MODE(TRUE) and then FND_REQUEST.SUBMIT_REQUEST to fire the release program, returning the request ID for tracking. Customizations should not call these procedures directly unless the exact shipped signatures are validated against the 12.1.1 or 12.2.2 source, because the "OTHER" classification means Oracle does not guarantee backward-compatible interfaces. Where diagnostics are required, setting the MRP_DEBUG profile option to Y enables verbose logging.