Search Results execute_adapter_admin

Overview

XDP_CRON_UTIL is a utility package in the APPS schema that serves as the scheduled-job scheduling and orchestration layer for the Oracle E-Business Suite TeleService and Interaction Center (XDP) product family. Its name derives from "cron," the Unix concept of a time-based job scheduler, and the package performs an equivalent role inside the EBS database: it submits, updates, and executes background jobs registered in the DBMS_JOB queue. These jobs drive the adapter administration, campaign management (CMU), event manager, and data-quality/error (DQER) watchdog processes that keep the XDP runtime operational.

The package is classified as a UTIL API in the ETRM registry and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. It contains both a package specification and a package body, exposing eleven documented procedures. It depends on the SYS.STANDARD package and is referenced by APPS.XDP_ADAPTER_CORE_DB, indicating that the adapter core relies on the scheduler facilities provided here.

Key Procedures and Functions

The documented procedures partition into four functional groupings:

• Adapter administration: SUBMITADAPTERADMINJOB submits the adapter administration job to the job queue; EXECUTE_ADAPTER_ADMIN performs the actual execution of that administration logic when the scheduled job fires.
• CMU (campaign/communication) processing: SUBMITCMUJOB schedules the CMU job; EXECUTECMUCRONJOBS executes the set of scheduled CMU jobs; EXECUTECMUACTIVITY runs the CMU activity processing step.
• Watchdog processes: STARTUPWATCHDOGPROCESS initializes the watchdog mechanism; SUBMITWATCHDOGJOB schedules the standard watchdog job; SUBMITDQERWATCHDOGJOB schedules the data-quality/error watchdog variant.
• Event manager: SUBMITEVENTMGRJOB schedules the event manager job; EXECUTEEVENTMGRJOBS executes the pending event manager jobs. A further procedure, UPDATEDBJOB, performs maintenance on the DBMS_JOB rows themselves, updating job state or scheduling attributes.

Because the ETRM entry does not publish parameter lists, callers should consult the deployed package specification before invoking these routines directly.

Tables Accessed

The only documented table reference is DBMS_JOB, accessed through APPS synonyms. DBMS_JOB is the Oracle-supplied job queue that holds job numbers, next execution dates, intervals, and the PL/SQL block to be run. XDP_CRON_UTIL reads and writes DBMS_JOB to create new scheduled entries (SUBMIT* procedures), to modify existing entries (UPDATEDBJOB), and effectively to drive the submission loop for the CMU, watchdog, and event manager workloads. Persistent application state for adapters, campaigns, and events resides in other XDP tables; this package's transactional footprint is limited to job-queue maintenance. In 12.2.2 environments DBMS_SCHEDULER is the more common scheduler, but the documented dependency remains DBMS_JOB.

Usage Notes

XDP_CRON_UTIL is intended for background invocation rather than direct end-user execution. Typical call paths include:

• Concurrent programs and request sets: administrators schedule the submission procedures (for example, SUBMITWATCHDOGJOB or SUBMITEVENTMGRJOB) as concurrent programs so the runtime jobs are re-registered on the desired interval.
• Forms and OAF pages: XDP setup and administration screens can call the EXECUTE_* procedures indirectly when an administrator triggers a manual run of the adapter, event manager, or CMU processing.
• Custom and internal code: XDP_ADAPTER_CORE_DB references XDP_CRON_UTIL, so adapter runtime logic may re-schedule or refresh jobs programmatically. The package also references itself, reflecting internal helper calls between its own procedures.

Because the procedures manipulate the central job queue, changes should be limited to supported entry points, and any custom caller should supply the same arguments used by the standard XDP job registrations to avoid orphaned or duplicate DBMS_JOB entries.