Search Results release_new_iro

Overview

MSC_SRP_RELEASE is an APPS-owned PL/SQL package in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that supports the release of supply chain planning recommendations into Oracle's execution systems. The package name and its documented constants, notably IRO_LOAD CONSTANT NUMBER := 256, tie it directly to the Item Replenishment / Order Release (IRO) process managed by Oracle Advanced Supply Chain Planning (ASCP). Its role is to take planning output — recommendations for internal requisitions, external requisitions, and order releases — and push them downstream so that execution-level documents such as requisitions, purchase orders, and discrete jobs are created or updated.

The package is declared AUTHID CURRENT_USER, which means it executes with the privileges of the calling schema (typically APPS), a standard pattern in EBS concurrent processing where security is enforced through the invoking user's responsibility and organization context. The metadata classifies it as "OTHER", indicating it is neither a supported public API nor a pure utility; it is an internal processing engine accessed primarily by ASCP's release framework. It is referenced by zero other packages according to the ETRM metadata, underscoring its role as a top-level release driver rather than a shared library.

Key Procedures and Functions

The ETRM documentation lists four procedures for this package: LOG_MESSAGE, MSC_RELEASE_IRO, RELEASE_NEW_IRO, and RELEASE_NEW_ERO.

• LOG_MESSAGE — Accepts user context information and writes diagnostic or audit output. It is the logging routine used by the other procedures to record release activity and errors, typically directed to a temporary or debug table during concurrent processing.
• MSC_RELEASE_IRO — The core release routine for IRO processing. It accepts user, responsibility, and application context together with a batch identifier and load type, and returns an IRO load identifier through an IN OUT parameter. It is the internal engine invoked to raise requisitions and related supply documents from planning recommendations.
• RELEASE_NEW_IRO — A concurrent-program-callable wrapper (errbuf/retcode signature typical of EBS concurrent managers) that releases new IRO recommendations for a given batch identifier.
• RELEASE_NEW_ERO — The analogous wrapper for External Requisition / Order release (ERO), releasing new external recommendations for a specified batch identifier.

Tables Accessed

The package reads and writes across planning execution staging and transactional tables:

• MRP_IRO_RELEASE, MRP_ERO_RELEASE, MRP_ORG_TRANSFER_RELEASE — planning release staging tables holding the recommendations to be processed.
• WIP_JOB_SCHEDULE_INTERFACE and WIP_JOB_NUMBER_S — used to feed and number work order jobs generated from planning releases.
• CSD_REPAIRS, CSD_REPAIR_TYPES_B, CSD_PRODUCT_TRANSACTIONS, CSP_REPAIR_PO_HEADERS — depot repair and repair order information used when planning recommendations relate to repair activity.
• HZ_CUST_ACCOUNTS_ALL, HZ_PARTIES, HZ_RELATIONSHIPS — Trading Community Architecture tables resolving customer, party, and relationship detail for external requisitions.
• HR_ORGANIZATION_INFORMATION, GL_LEDGERS — organization and ledger context used to validate the target execution entity.
• FND_USER — user identity for logging and responsibility context.

Usage Notes

MSC_SRP_RELEASE is not a documented public API and should not be called from custom code without careful validation. In practice it is invoked by ASCP's release framework, often triggered by the "Release Plan" or "Release Recommended Orders" concurrent programs or by Planner Workbench actions that submit release requests. The RELEASE_NEW_IRO and RELEASE_NEW_ERO procedures follow the standard EBS concurrent program interface, so they can be registered as concurrent executables where a batch ID is supplied as a parameter. Because the package operates as AUTHID CURRENT_USER and depends on APPS synonyms, any direct call must run under a responsibility whose organization and ledger context are correctly initialized, and all activity should be monitored through LOG_MESSAGE output. The presence of the string "msc_release_iro" in search terms confirms it is most frequently encountered when diagnosing IRO release failures, batch hangs, or missing requisition generation in ASCP-to-execution integrations.