Search Results start_watch




Overview
Explore in AI Chat

Overview

APPS.MRP_PRINT_PK is a Oracle E-Business Suite PL/SQL package body residing in the APPS schema. It belongs to the Oracle Materials Planning (MRP) product family and is classified under the ETRM "OTHER" API category, indicating that it is an internal utility package rather than a public, transactional API. Its principal business function is to instrument and support the printing of MRP planning output by recording message-generation activity into a temporary staging table. Each procedure or function call creates or updates a "watch" record that captures the message name, the concurrent request that produced the output, the user who initiated it, substitution tokens for runtime message text, and start/end timestamps. The package therefore serves as the logging and message-composition layer used when MRP planning results, exception messages, and descriptive text are formatted for printed or report-based delivery. It is embedded in the standard MRP print workflow and is referenced by four other packages within the application.

Key Procedures and Functions

  • START_WATCH — A function that creates a new transaction record in the message staging table. It obtains a transaction identifier from a sequence, inserts a row capturing the message name, request identifier, user identifier, creation and update audit columns, and up to two token/value pairs with translation indicators, and returns the new transaction identifier for later use by STOP_WATCH.
  • STOP_WATCH — Overloaded procedure that closes out a previously started watch. One form accepts a request identifier, transaction identifier, and an optional row count and updates the corresponding staging record with the ending timestamp and processed row count. The second form delegates to the first, passing a null row count.
  • MRPRINT — A driver procedure that accepts a message name, request identifier, and user identifier. It invokes the watch-start logic and discards the returned transaction identifier, providing a simplified entry point for callers that do not need to track the transaction handle themselves.
  • CLEAR_MESSAGES — The procedure most relevant to the user's search term. It is responsible for removing or purging stale entries from the message staging area, ensuring that prior request output does not bleed into a subsequent print run.

Tables Accessed

The package operates exclusively against the MRP temporary message tables. MRP_MESSAGES_TMP is the primary target: START_WATCH inserts rows into it, STOP_WATCH updates the end_date and row_count columns for the matching request and transaction, and CLEAR_MESSAGES removes rows from it. MRP_MESSAGES_TMP_S is the sequence that supplies unique transaction identifiers for each watch record. DUAL is used solely to retrieve the sequence's next value into a local variable before the insert.

Usage Notes

MRP_PRINT_PK is not intended for direct end-user invocation. It is called from the MRP printing and reporting flow, typically within concurrent program logic or from the report-generation code that assembles planning exception messages for output. Customizations that extend MRP printed output can call START_WATCH and STOP_WATCH around their message-emission blocks to preserve performance and row-count telemetry, and should rely on CLEAR_MESSAGES to reset the staging table between logical runs. Because the package writes to MRP temporary tables tied to a specific request, callers must supply a valid request identifier and commit appropriately within their own transaction context.