Search Results set_notification_attr

Overview

FND_CONC_PRIVATE_UTILS is an internal helper package in the Oracle E-Business Suite Applications (APPS) schema that supports the Concurrent Processing subsystem. It is classified as an "OTHER" API, meaning it is not intended as a public, supported programming interface, but rather as a repository of private utility routines used by Oracle's own concurrent manager and related infrastructure code. Its responsibilities span several distinct areas: resolving file-sharing service names and generating secured output-file URLs, computing request resubmission timing, dispatching completion notifications, managing the tracking of temporary files, invoking PL/SQL via the parallel processing (PP) mechanism, managing concurrent manager reconfiguration, and establishing multi-org session context.

The package body header identifies the source file as AFCPSCRB.pls, with the header comment referencing an early 2005 revision. The documented metadata for 12.2.2 lists ten procedures and functions, indicating the package evolved across the 12.1.1 and 12.2.2 releases while retaining its role as a low-level concurrent processing utility layer.

Key Procedures and Functions

• GET_FS_SVC_NAME — Derives the file-sharing service name for a given node. It consults the FS_SVC_PREFIX profile option to build the service identifier, defaulting to the "FNDFS_" prefix when the profile is undefined or null.
• GET_RESUB_TIME — Determines the appropriate time at which a concurrent request should be resubmitted, supporting scheduling and period-based release logic.
• SEND_SIMPLE_DONE_MSG — Sends a simple completion message, typically interacting with the Workflow notification tables (WF_NOTIFICATIONS) to inform users when a request finishes.
• RECORD_TEMP_FILE_USE, ERASE_TEMP_FILE_USE, CHECK_TEMP_FILE_USE — A related trio that registers the use of a temporary file, removes that registration, and verifies whether a temporary file is currently in use, all against FND_TEMP_FILES. These support orderly cleanup and reuse decisions.
• CALL_PP_PLSQL — Invokes a PL/SQL routine through the parallel processing infrastructure, allowing packaged logic to be executed in a managed processing context.
• SET_MGR_RCG — Sets concurrent manager reconfiguration information, referred to as the MGR_RCG value, used by the concurrent manager to track restart or reconfiguration state.
• SET_MULTIORG_CONTEXT — Establishes the multi-organization session context, ensuring application logic reads the correct operating unit and organization identifiers for the session.

Note: the ETRM excerpt also shows the internal function GENERATE_REQ_OUT_URL, which builds a secured, time-limited URL for a request output file using APPS_WEB_AGENT and the FS_SVC_PREFIX profile options. This routine illustrates the package's URL-generation and file-securing behavior, though it is not among the ten listed procedures.

Tables Accessed

The package reads and writes via APPS synonyms. FND_CONCURRENT_REQUESTS and FND_CONCURRENT_QUEUES are used to resolve request, output file, and queue information, including the URL-generation query that joins output file name, node name, and MIME type. FND_CONC_RELEASE_CLASSES, FND_CONC_RELEASE_PERIODS, FND_CONC_REL_CONJ_MEMBERS, and FND_CONC_REL_DISJ_MEMBERS support release and resubmission scheduling logic. FND_TEMP_FILES backs the temporary file use-tracking routines. FND_USER resolves user identity for notifications, while WF_NOTIFICATIONS holds the completion messages. DBMS_SESSION, DUAL, and V$SESSION are referenced for session-context and diagnostic purposes.

Usage Notes

FND_CONC_PRIVATE_UTILS is invoked implicitly by Oracle's concurrent manager, notification, and parallel processing infrastructure rather than by end users. Because it is a private package, custom code should not call it directly; the set_notification_attr-related search interest reflects its role in surfacing notification and completion information. The metadata records that it is referenced by one other package, confirming its narrow internal footprint. Customers on 12.1.1 and 12.2.2 should treat it as read-only and rely on supported concurrent processing APIs for any extension requirements.