Results for “fnd_concurrent_request”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.ONT_ACTIVITY_SUM_ORDER_PURGE package body is a component of the Oracle Order Management (ONT) module's activity summarization and purge framework. Its principal business function is to gather operational statistics concerning the Order Purge concurrent program (short name ORDPUR, application identifier 660) and to publish those statistics into the concurrent manager summarizer, where they become visible to administrators through the Concurrent Requests diagnostics interface. In effect, the package quantifies how often order purge activity has been executed, both system-wide and by the currently logged-in user, and exposes these counts as named summarizer rows.

The package is owned by APPS and is classified under the ETRM "OTHER" API category rather than as a formal public API. Its source header (OEXACSUB.pls 120.2) indicates it belongs to the Order Management purge subsystem and was maintained under the noship flag, meaning it is not shipped as a standalone supported interface but rather as part of the ONT schema's internal infrastructure.

Key Procedures and Functions

The package exposes a single documented procedure:

• ACTIVITY_SUMMARIZER — The sole procedure in the package. It performs the core summarization work: it declares a cursor over FND_CONCURRENT_REQUESTS to count completed (phase_code = 'C') Order Purge requests, retrieves the display labels for each statistic via FND_MESSAGE.GET_STRING using the ONT message dictionary (for example ONT_CONC_REQUESTS and ONT_PURGE_ORD_USER_COUNT), and then writes each name/value pair to the summarizer through FND_CONC_SUMMARIZER.INSERT_ROW. Two distinct measures are produced: the total number of Order Purge concurrent requests for the entire system, and the number of those requests submitted by the session user (resolved through FND_GLOBAL.USER_ID). No parameter list is documented for this procedure; it operates entirely on environment context and internal cursors.

Tables Accessed

The ETRM metadata identifies the following tables referenced through APPS synonyms:

• FND_CONCURRENT_REQUESTS — The primary data source. The procedure filters this table by phase_code, program_application_id (660), the resolved concurrent_program_id, and requested_by to compute the two purge counts.
• FND_CONCURRENT_PROGRAMS — Used in a subquery to resolve the concurrent_program_id for the ORDPUR program within application 660.
• FND_CONCURRENT_PROCESSES — Referenced to summarize the number of concurrent processes submitted, complementing the request-level statistics.
• FND_CRM_HISTORY — Consulted in the broader summarizer logic for activity history context.
• FND_TM_EVENTS — Referenced for transaction manager event tracking associated with orders undergoing purge.

The package writes only indirectly, via FND_CONC_SUMMARIZER.INSERT_ROW, which persists results in the summarizer storage underlying the concurrent manager diagnostics UI; no direct DML against the referenced tables is documented.

Usage Notes

ONT_ACTIVITY_SUM_ORDER_PURGE is invoked in the context of the Oracle EBS "Activity Summarizer" diagnostics framework, typically from the Concurrent Requests form or the System Administrator's concurrent manager screens. When a user requests statistics for a program such as ORDPUR, the summarizer invokes this package to populate the counters, and the resulting rows appear as labeled metrics in the diagnostics output.

Because the procedure relies on FND_GLOBAL.USER_ID, meaningful per-user results require an initialized FND session; it should therefore be called from within a runtime session rather than from ad hoc scripts that bypass FND initialization. Typical invocation patterns include EBS Forms diagnostics, concurrent program registration, or custom monitoring code that calls ACTIVITY_SUMMARIZER directly. The package is not referenced by other PL/SQL packages (referenced by 0 objects), confirming its role as a terminal consumer of FND data rather than a shared dependency. Standard cautions apply: compile it in the APPS schema, ensure the ORDPUR program is registered under application 660, and account for the noship status when planning customizations or upgrades across 12.1.1 and 12.2.2.