Search Results g_conc_request_pending




Overview
Explore in AI Chat

Overview

BIS_CONCURRENT_MANAGER_PVT is a private PL/SQL package in the APPS schema that provides the internal API layer for managing concurrent requests on behalf of Oracle EBS alerting and business intelligence service components. It is declared with AUTHID CURRENT_USER, meaning its unqualified database references resolve against the privileges of the invoking session rather than the package owner. The package was originally created in June 2000 and carries a header revision dated 15 December 2003 (BISVCONS.pls, version 115.19), reflecting enhancements introduced for change-based and target-based alerting (enhancement 3148615). Its central responsibility is to control the submission, monitoring and scheduling of the BIS_ALERT_SERVICE concurrent program and its Java successor, BIS_ALERT_SERVICE_PVT_JAVA. The package encapsulates request lifecycle states through the constants G_CONC_REQUEST_RUNNING, G_CONC_REQUEST_COMPLETE, G_CONC_REQUEST_SCHEDULED and G_CONC_REQUEST_PENDING, and defines the alert program names G_ALERT_PROGRAM and G_ALERT_PROGRAM_PVT. Because the package is classified as PVT (private), it is not part of Oracle's supported public API surface; it is intended for internal consumption by other BIS packages and Java service components.

Key Procedures and Functions

  • SUBMIT_CONCURRENT_REQUEST — the primary entry point for launching an alert service request; this is the procedure that responds to the "submit_concurrent_request" search and is the mechanism through which alerting jobs are dispatched to the concurrent manager.
  • MANAGE_ALERT_REGISTRATIONS — handles registration and lifecycle handling of alerting subscriptions, including the logic that prevents an alert from being scheduled again while it is already running (fix for bug 2834155).
  • GET_ALL_REQUESTS — retrieves concurrent request records, used to enumerate alert-related requests for status inspection.
  • GET_REQUEST_SCHEDULE_INFO — returns scheduling information attached to a given concurrent request.
  • GET_FREQ_DISPLAY_UNIT and FORMAT_SCHEDULE_FREQ_UNIT — translate internal frequency values into their user-facing display units for schedule presentation.
  • SET_REPEAT_OPTIONS — configures the repeat/regeneration attributes applied when a request is scheduled.
  • GET_PMF_CONCURRENT_PROGRAM_ID — resolves the concurrent program identifier, typically for the alert service program referenced by the package constants.

Tables Accessed

The package operates against the core concurrent processing tables through APPS synonyms. FND_CONCURRENT_REQUESTS is the principal table, holding submitted request rows and their phase and status values that the package reads and updates. FND_CONCURRENT_PROGRAMS and FND_APPLICATION supply program and application definitions used when resolving the alert service executable and its owning application. PLITBLM is referenced for temporary string buffer manipulation used in building and formatting request or schedule data. All access is read/write where request state transitions are involved and read-only for program and application lookups.

Usage Notes

BIS_CONCURRENT_MANAGER_PVT is referenced by five other packages and is invoked indirectly rather than through end-user forms. Typical callers are the alert service packages (including BISVCONB.pls, which passes dimension-level parameters to the Java concurrent program) and Java service layers introduced during the SONAR conversion. A developer searching for "submit_concurrent_request" should treat this procedure as the internal dispatch point for alert scheduling, not as a general-purpose concurrent submission API — public request submission in EBS uses FND_REQUEST.SUBMIT_REQUEST. Direct custom calls are possible from PL/SQL but are unsupported and should be validated against the exact signature in the deployed 12.1.1/12.2.2 instance.