Search Results af_rollback

Overview

The APPS.FND_CONCURRENT package is the core server-side utility library for Oracle E-Business Suite Concurrent Processing. It exposes public PL/SQL APIs that allow forms, concurrent programs, and custom code to interrogate and manipulate the lifecycle of concurrent requests, manager processes, and concurrent program definitions. The package header identifies its scope as "public" under product FND, with a display name of "Request Set" and an active lifecycle with a compatibility rating of "S". It was originally created in 1993 and has evolved through successive EBS releases, including 12.1.1 and 12.2.2.

Functionally, FND_CONCURRENT bridges the transactional tables of the Concurrent Manager subsystem with application logic. It provides translation-aware status reporting, request submission and initialization helpers, manager status queries, sub-request traversal, and lock-contention diagnostics. Because it is referenced by 638 other packages, it is one of the most load-bearing internal APIs in the EBS technology stack.

Key Procedures and Functions

The ETRM repository documents 38 procedures and functions in this package. The principal public entry points include:

• GET_REQUEST_STATUS — Returns the phase and status of a concurrent request, plus the completion message when the request has finished. It returns both user-displayable (translatable) and developer-comparable constant values for phase and status, allowing calling code to branch reliably on results.
• WAIT_FOR_REQUEST — Blocks the caller until a specified request reaches a terminal state, optionally with a timeout.
• GET_SUB_REQUESTS — Retrieves the child requests spawned by a parent request, typically used when processing request sets or multi-request workflows. This is the function most commonly sought when searching for "get_sub_requests".
• CHILDREN_DONE — Evaluates whether all child requests of a parent have completed, enabling orchestration logic in request-set processing.
• GET_MANAGER_STATUS — Reports the operational status of a concurrent manager.
• SET_COMPLETION_STATUS and SET_INTERIM_STATUS — Allow a running program to write its own completion or interim status back to the concurrent request record.
• INIT_REQUEST — Initializes a request record as part of submission processing.
• GET_REQUEST_PRINT_OPTIONS — Returns print-related settings (copies, print style, printer, save-output flag) defined by the Print_Options_Rec_Typ and Print_Options_Tbl_Typ public types.
• CHECK_LOCK_CONTENTION — Detects lock contention affecting concurrent processing.
• GET_PROGRAM_ATTRIBUTES — Returns attributes associated with a concurrent program definition.
• SET_PREFERRED_RBS and RESET_CONTEXT — Manage session context and rollback segment preferences.
• AF_COMMIT and AF_ROLLBACK — Commit and rollback wrappers used within the concurrent framework.
• SHUT_DOWN_PROCS — Terminates running concurrent manager processes.
• REGISTER_NODE — Registers a node with the concurrent processing infrastructure.
• GET_SERVICE_INSTANCES and GET_SERVICE_PROCESSES — Return information about service instances and their processes.
• MSC_MATCH — A specialized matching routine exposed publicly within the package.

Tables Accessed

The package reads and writes the principal Concurrent Processing tables through APPS synonyms:

• FND_CONCURRENT_REQUESTS — The central request repository; read and updated for status, phase, and completion results.
• FND_CONCURRENT_PROGRAMS and FND_EXECUTABLES — Program and executable definitions.
• FND_CONCURRENT_PROCESSES and FND_CONCURRENT_QUEUES — Manager process and queue configuration.
• FND_CONC_PP_ACTIONS — Program-to-queue assignment rules.
• FND_CP_SERVICES, FND_CP_SQL_REQUESTS, and FND_NODES/FND_NODES_S — Service, SQL, and node metadata used in manager and node operations.
• FND_APPLICATION, FND_RESPONSIBILITY, FND_USER, FND_LOOKUP_VALUES — Application, responsibility, user, and lookup metadata for resolving names and translating status codes.
• DBMS_APPLICATION_INFO — Session context set for auditing and monitoring.

Usage Notes

FND_CONCURRENT is invoked primarily from concurrent programs, request-set processing logic, and Oracle Forms-based concurrent manager screens. Custom PL/SQL—particularly programs that spawn or wait on dependent requests—commonly calls GET_SUB_REQUESTS together with WAIT_FOR_REQUEST and CHILDREN_DONE to coordinate multi-step jobs. Because it is a public package with active lifecycle status, it is supported for direct customer invocation in both 12.1.1 and 12.2.2. Its exceptional fan-in (638 dependent packages) means changes to its behavior can ripple broadly, so callers should treat its signatures as stable interfaces.