Results for “channel_name”

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

Overview

XDP_ADAPTER_ADMIN_REQS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the XDP – Provisioning product, which underpins the Oracle Telecommunications Service Order Management (TSOM) and provisioning framework used to orchestrate service activation across external network and adapter systems. The view presents adapter-specific pending jobs, exposing the administrative requests that have been submitted against provisioned adapters along with the scheduler information describing when those requests execute.

Because provisioning often depends on asynchronous, scheduled activity rather than immediate synchronous calls, administrators and integration specialists require a consolidated picture of outstanding work. XDP_ADAPTER_ADMIN_REQS_V serves that purpose by joining the adapter administration request queue to the database job scheduler and the adapter registration table. It is most commonly used for operational monitoring, troubleshooting stuck or failing provisioning jobs, and building administrative dashboards and extracts. The object is documented as VALID in ETRM metadata and is exposed as a standard APPS view, meaning it is accessible to any responsibility or concurrent program with the appropriate APPS-level privileges.

Underlying Base Objects

The view is defined over three primary objects plus a correlated sub-query reference, as documented in the view text. The driving table is XDP_ADAPTER_ADMIN_REQS, referenced through the APPS synonym XAA, which stores the pending adapter administration requests. It is joined to DBA_JOBS (alias DJ) on JOB_ID = JOB, which supplies the scheduler attributes for each request. It is further joined to XDP_ADAPTER_REG (alias XAR) on CHANNEL_NAME, which supplies the adapter type used to resolve the human-readable request type. A correlated scalar sub-query against XDP_ADAPTER_TYPE_REQ_TYPES_V retrieves the MEANING for the matching LOOKUP_CODE and ADAPTER_TYPE. The documented referenced base objects are FND_GLOBAL (PACKAGE), XDP_ADAPTER_ADMIN_REQS (SYNONYM), XDP_ADAPTER_REG (SYNONYM), XDP_ADAPTER_TYPE_REQ_TYPES_V (VIEW), and DBA_JOBS (SYNONYM). FND_GLOBAL is typically used by the underlying request framework to stamp the requesting user and session context.

Key Columns

• REQUEST_ID – Unique identifier for the adapter administration request.
• CHANNEL_NAME – The adapter channel against which the request was submitted; joins to XDP_ADAPTER_REG.
• REQUEST_TYPE – Resolved from XDP_ADAPTER_TYPE_REQ_TYPES_V using the request lookup code and adapter type, giving the descriptive request type.
• REQUEST_DATE – Date and time the request was created.
• REQUESTED_BY_USER – The user who submitted the request; this is the column users most often filter on when searching by submitter.
• REQUEST_FREQUENCY – The recurrence pattern associated with the scheduled job.
• JOB_ID – The database job identifier linking the request to DBA_JOBS.
• THIS_DATE, NEXT_DATE, LAST_DATE – Scheduler timestamps for the current, next, and previous execution.
• FAILURES – Number of consecutive job failures, a key indicator for troubleshooting.
• WHAT – The database job's WHAT column, showing the PL/SQL block or procedure invoked.

Common Use Cases and Queries

A frequent requirement is locating all pending adapter jobs submitted by a particular user. Because the view exposes REQUESTED_BY_USER directly, this filter is straightforward:

• SELECT request_id, channel_name, request_type, requested_by_user, next_date, failures FROM xdp_adapter_admin_reqs_v WHERE requested_by_user = :user_name ORDER BY next_date;
• SELECT channel_name, request_type, COUNT(*) FROM xdp_adapter_admin_reqs_v GROUP BY channel_name, request_type;
• SELECT request_id, job_id, failures, last_date FROM xdp_adapter_admin_reqs_v WHERE failures > 0 ORDER BY failures DESC;

These queries support operational monitoring of adapter queues, identification of failing or repeatedly retried jobs, and reconciliation of scheduled provisioning activity against adapter registrations. When diagnosing a specific submission, joining REQUEST_ID back to XDP_ADAPTER_ADMIN_REQS provides the full request payload, while the job columns reveal whether the scheduler is executing as expected.