Search Results log_message

Overview

The APPS.MSC_SRP_RELEASE package body forms part of the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) and Enterprise Resource Planning infrastructure, specifically around the release of repair and transfer transactions generated by planning. Its central business purpose is to take staged release records produced by planning engines — repair orders, internal requisitions, enterprise repair orders and organisation transfer releases — and push them into their downstream execution systems so that purchase requisitions, repair purchase orders, work orders and shipment documents are created automatically. The package is classified as OTHER in the ETRM repository, indicating it is a supporting internal package rather than a formally published public API, and the ETRM metadata confirms that no other packages reference it, so it is effectively a terminating point in the dependency chain, invoked by concurrent processing rather than by peer PL/SQL code.

Key Procedures and Functions

The ETRM metadata documents four callable units in this package. LOG_MESSAGE is a utility logging routine that writes caller supplied text to the concurrent program log file via FND_FILE.PUT_LINE, and is reused throughout the body to record trace and diagnostic output. MSC_RELEASE_IRO and RELEASE_NEW_IRO are the release drivers for internal requisition related material, operating on records held in the release staging tables and converting them into requisition and demand records for the executing operating unit. RELEASE_NEW_ERO is the enterprise repair order release routine; the supplied source excerpt shows it declares a cursor over MRP_ERO_RELEASE for a given batch identifier and loops across the staged rows, resolving source and destination organisations, repair supplier identity, repair program, inventory item, quantity and promise date before submitting each transaction downstream. All four units are procedural; no functions returning values are documented.

Tables Accessed

The package reads and writes across a wide set of ASCP, service and trading-partner tables. MRP_ERO_RELEASE and MRP_IRO_RELEASE are the primary staging tables that hold pending enterprise repair order and internal requisition release rows, keyed by batch and transaction identifiers. MRP_ORG_TRANSFER_RELEASE performs the equivalent role for inter-organisation transfer releases. Service and repair detail is drawn from CSD_REPAIRS, CSD_REPAIR_TYPES_B, CSD_PRODUCT_TRANSACTIONS and CSP_REPAIR_PO_HEADERS, and the supplied source confirms the use of the CSP_REPAIR_PO_GRP.DEFECTIVE_PARTS_TBL_TYPE record type to describe defective parts and quantities. Trading partner context is resolved through HZ_PARTIES, HZ_CUST_ACCOUNTS_ALL and HZ_RELATIONSHIPS. Organisational and security context comes from HR_ORGANIZATION_INFORMATION, FND_USER and GL_LEDGERS, while work order numbering and scheduling uses WIP_JOB_NUMBER_S, WIP_JOB_S and WIP_JOB_SCHEDULE_INTERFACE.

Usage Notes

MSC_SRP_RELEASE is not intended for direct end-user invocation. In Oracle EBS 12.1.1 and 12.2.2 it is driven by ASCP planning concurrent programs that process release batches; the P_BATCH_ID parameter visible in the source ties an execution run to a set of staged rows previously populated by the planning engine. Because the procedures use FND_FILE.LOG and FND_FILE.OUTPUT, any diagnostic information — including the header text “Repair Purchase Order Release Report” — is only visible in the concurrent request log and output files, and the search term log_message corresponds to this logging utility. Custom code should call this package only with caution, since the ETRM record shows no published signature documentation and no dependent packages; the supported integration route for externally releasing planned repair and transfer demand remains the standard ASCP release concurrent programs, with this package acting as the internal engine behind them.