Results for “system_administrator”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_ADPATCH is an internal Oracle E-Business Suite utility package that supports the post-patch processing cycle for Oracle Applications, specifically the reloading of iRep (intelligent Repository) metadata into the database. Its single documented function, POST_PATCH, provides a guarded, idempotent mechanism for scheduling the iRep Loader concurrent program (FNDIRLOAD) after a patch session has completed. The package is part of the AD (Applications DBA) technology stack and is delivered under the APPS schema with an API classification of OTHER, indicating it is not a published public interface but rather an internal helper invoked by the patching infrastructure itself. Because it interacts with the concurrent manager and the FND security model, it functions as a bridge between patch driver execution and the standard concurrent request engine, ensuring that repository reloads do not proliferate unnecessarily and that the loader runs under a privileged, well-known security context.

Key Procedures and Functions

The package body exposes one documented function:

• POST_PATCH — Accepts an Autopatch session identifier and returns a character status indicator ("TRUE" or "FALSE"), with an output message describing the outcome. Its logic proceeds in two phases. First, it queries the concurrent request tables to determine whether an iRep Loader request referencing the same session is already pending, active, and unheld. If such a request exists, POST_PATCH short-circuits, reports success, and returns "TRUE" without submitting anything, thereby preventing duplicate reloads. Second, when no qualifying request is found, it resolves the SYSTEM_ADMINISTRATOR responsibility and the SYSADMIN user, initializes the FND global application context for that combination, and submits a new FNDIRLOAD concurrent request with the session identifier as its argument. If submission fails, the function returns "FALSE" together with the message returned by FND_MESSAGE; on success it returns "TRUE" with the new request ID embedded in the message text.

Tables Accessed

POST_PATCH reads five FND tables through APPS synonyms:

• FND_APPLICATION, FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUESTS — joined to detect existing pending FNDIRLOAD requests for the given Autopatch session, filtering on phase code "P", hold flag "N", and a requested start date within approximately fifteen minutes of the current time. This guards against redundant submissions.
• FND_RESPONSIBILITY — queried for the application, responsibility, and responsibility key corresponding to the SYSTEM_ADMINISTRATOR responsibility key, supplying the security context for the reload.
• FND_USER — queried for the user identifier and name of SYSADMIN, completing the identity tuple passed to FND_GLOBAL.APPS_INITIALIZE.

The package writes no application data directly; its only write operation is the submission of a concurrent request through FND_REQUEST.SUBMIT_REQUEST.

Usage Notes

FND_ADPATCH is not designed for direct invocation by end users. It is called by Oracle's patch infrastructure during the post-patch phase of an Autopatch or ADOP (Online Patching) run, after code objects have been applied and the iRep repository requires refresh. Administrators may encounter it when diagnosing why an iRep Loader did not start: the pending-request check means that a previously queued but unstarted FNDIRLOAD will suppress a second submission, which is normal and reported as a successful outcome. Because the function runs the loader as SYSADMIN under the SYSTEM_ADMINISTRATOR responsibility, any customization that removes that responsibility key or the SYSADMIN account will cause the function to raise an unhandled query exception rather than return a graceful failure. The package is referenced by one other package, reflecting its tightly scoped role. It remains a "noship" internal object in 12.1.1 and 12.2.2, and support for repository reload differs between the two releases' patching architectures, so it should be treated as Oracle-internal and not be called from custom forms or concurrent programs.