Search Results p_actual_completion_date

Overview

FND_CONC is a core Oracle E-Business Suite package body owned by the APPS schema and classified as an OTHER API. It encapsulates the internal diagnostics and liveness-checking logic used by the Concurrent Manager infrastructure. Rather than exposing a public business interface, FND_CONC provides the low-level routines that determine whether the concurrent processing tier is healthy, whether a specific manager or service is alive, and whether in-flight requests should be cancelled during patching or shutdown. The package maintains a set of private status constants representing internal states — STATUS_INACTIVE_RUNALONE ('1'), STATUS_INACTIVE_WKSHIFT ('2'), STATUS_INACTIVE_MGR_DOWN ('3'), STATUS_INACTIVE_MGR_TROUBLE ('4'), STATUS_INACTIVE_CP_DOWN ('5'), and STATUS_INACTIVE_PATCH_ED ('6') — which are used to distinguish why a pending request is inactive. These internal codes are never returned externally; they are all mapped outward to the single "Inactive/No Manager" state presented to end users.

Key Procedures and Functions

• DIAGNOSE — Produces diagnostic output for a concurrent request, assembling descriptive context. Notably, the private buffer P_PROGRAM was widened to varchar2(483) to accommodate the concatenation of request description and concurrent program name, a fix associated with Bug 4097622.
• PROCESS_ALIVE — Determines whether a given concurrent process (typically identified by concurrent process/request identifiers) is still running and responsive.
• ICM_ALIVE — Reports whether the Internal Concurrent Manager (ICM) is up and reachable, a prerequisite for normal request scheduling.
• SERVICE_ALIVE — Checks the health of a concurrent manager service (a named set of managers), used to confirm the service layer of the concurrent tier is functioning.
• MANAGER_CHECK — Validates the status of a specific concurrent manager, forming part of the manager-monitoring and restart logic.
• GET_PHASE — Returns the phase associated with a concurrent request, derived from the internal phase code stored on the request record.
• GET_STATUS — Returns the status of a concurrent request. Together with GET_PHASE, these functions translate internal code values into the externally visible phase/status pair familiar from the "View Requests" forms.
• CANCEL_PATCH_REQUESTS — Cancels outstanding concurrent requests in preparation for patching or shutdown, using the STATUS_INACTIVE_PATCH_ED internal state to reflect the patch-induced cancellation reason.

The package references several private package-level variables — P_USER_STATUS_CODE, P_PHASE_CODE, P_REQUEST_ID, P_ACTUAL_START_DATE, P_ACTUAL_COMPLETION_DATE, P_COMPLETION_TEXT, and others — that carry request state between its internal calls.

Tables Accessed

Through APPS synonyms, FND_CONC reads and writes the fundamental concurrent-processing tables:

• FND_CONCURRENT_PROCESSES — the registry of running processes and managers; central to the *_ALIVE and MANAGER_CHECK routines.
• FND_CONCURRENT_REQUESTS — the request ledger; read for phase/status and updated during cancellation.
• FND_CONCURRENT_PROGRAMS — supplies the concurrent program name used in DIAGNOSE.
• FND_CONC_PP_ACTIONS — the process/phase action definitions that anchor phase and status semantics.
• FND_CONC_STAT_SUMMARY — aggregated concurrency statistics read during diagnostics.
• FND_CONFLICTS_DOMAIN — conflict domain membership consulted for scheduling/termination logic.
• FND_USER — resolves the requestor and updater names surfaced in diagnostic output.
• DATABASE_PROPERTIES — consulted for environment-level settings such as edition name (P_EDITION_NAME).

Usage Notes

FND_CONC is not intended as a public, supported API for custom development. It is invoked primarily by the Concurrent Manager tier itself and by Oracle-supplied maintenance screens — particularly the Concurrent Managers and Administer Concurrent Managers forms, and the concurrent manager diagnostics/restart facilities. Administrators effectively trigger the *_ALIVE and MANAGER_CHECK routines whenever they review the status of the Internal Concurrent Manager or a service. CANCEL_PATCH_REQUESTS is invoked during patch application and controlled shutdown, ensuring pending requests are terminated cleanly and marked with an internal patch-edition state. The package is referenced by four other APPS packages, confirming its role as a shared low-level dependency. Because the procedures operate on internal state codes and are subject to change between releases, custom code should avoid calling them directly and should instead rely on supported concurrent manager administration interfaces.