Search Results fnd_nodes_s

Overview

FND_CONCURRENT is the core PL/SQL package body in the APPS schema that implements the Oracle E-Business Suite Concurrent Manager framework. It provides the programmatic interface through which concurrent requests are initialized, submitted to a manager, monitored, and reconciled with their completion status. Every concurrent program executed within Oracle EBS 12.1.1 or 12.2.2 — including standard Oracle reports, PL/SQL stored procedures, host scripts, and Java concurrent programs — relies on the services exposed by FND_CONCURRENT to register itself with the concurrent processing infrastructure and to communicate its state back to the FND_CONCURRENT_REQUESTS table.

The package also supports the multi-node architecture introduced with shared application tier file systems. It handles node registration, service instance discovery, and process shutdown coordination across the Concurrent Processing server topology. Its dependency list — which includes FND_GLOBAL, FND_FILE, FND_CP_SERVICES, DBMS_LOCK, and views such as V$SESSION and GV$SESSION — confirms its role as a low-level orchestration layer sitting between the Concurrent Manager executables and the FND dictionary tables.

Key Procedures and Functions

The documented API exposes 38 procedures and functions, of which the principal ones are:

• INIT_REQUEST — prepares a concurrent request record and session context prior to execution.
• GET_REQUEST_STATUS — returns the current phase and status of a submitted request.
• WAIT_FOR_REQUEST — blocks the calling session until a specified request reaches a terminal status, used by parent-child request chains.
• GET_MANAGER_STATUS — reports whether the Concurrent Manager is active and accepting work.
• SET_COMPLETION_STATUS / SET_INTERIM_STATUS — write phase and status transitions back to the request record.
• GET_PROGRAM_ATTRIBUTES — retrieves configuration attributes for a concurrent program definition.
• GET_REQUEST_PRINT_OPTIONS — resolves printer and print-style settings for the request output.
• CHECK_LOCK_CONTENTION — detects locking conflicts affecting concurrent processing.
• SET_PREFERRED_RBS / RESET_CONTEXT — manage the session's rollback segment and FND context.
• AF_COMMIT / AF_ROLLBACK — control transactional boundaries within the concurrent processing session.
• SHUT_DOWN_PROCS — terminates concurrent manager processes during an orderly shutdown.
• GET_SUB_REQUESTS / CHILDREN_DONE — traverse and evaluate the parent-child request hierarchy.
• REGISTER_NODE — registers a node with the FND_NODES table.
• GET_SERVICE_INSTANCES / GET_SERVICE_PROCESSES — enumerate running service instances and their OS processes.
• MSC_MATCH — supports matching logic used by the planning data collection integration.

Tables Accessed

FND_CONCURRENT reads and writes the FND_CONCURRENT_REQUESTS table, the central repository of request lifecycle data, and consults FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_PROGRAMS_VL, FND_EXECUTABLES, and FND_APPLICATION for program and executable definitions. Runtime state is tracked through FND_CONCURRENT_PROCESSES, FND_CONCURRENT_QUEUES, and FND_CONC_PP_ACTIONS. Node and service topology is maintained via FND_NODES, FND_NODES_S, FND_CP_SERVICES, and FND_CP_SQL_REQUESTS. Security and identity lookups draw on FND_USER, FND_RESPONSIBILITY, and FND_LOOKUP_VALUES. Session diagnostics use DBMS_APPLICATION_INFO and the V$SESSION, GV$SESSION, V$PROCESS, and V$LOCK dynamic views.

Usage Notes

FND_CONCURRENT is invoked indirectly by the Concurrent Manager executables and by every concurrent program wrapper at runtime. Oracle Forms such as the Submit Requests and View Requests screens call the package to submit work and to refresh request status. Custom PL/SQL concurrent programs frequently call WAIT_FOR_REQUEST and GET_REQUEST_STATUS to synchronize dependent child requests, and administrative utilities use SHUT_DOWN_PROCS and REGISTER_NODE during node maintenance. Because the package is not referenced by any database object and is classified as OTHER rather than a public API, direct custom calls should be limited to the documented entry points. With 638 dependent packages in 12.2.2, changes to its behavior have wide-reaching impact, and customizations should avoid wrapping or overriding the package body.