Results for “xdp_services”

42 results




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

Overview

XDP_SERVICES is a table residing in the XDP schema, belonging to the XDP – Provisioning product family within Oracle E-Business Suite. The ETRM reference documentation for this object carries a terse description of "Not used," which indicates that the table is retained in the physical schema for structural or historical reasons but is not actively referenced by supported provisioning business flows in release 12.1.1 or 12.2.2. Despite that annotation, the object remains VALID in the data dictionary, and its column set and foreign key topology reveal a service-definition catalog: a master list of provisionable services, their versioning, required-provisioning flags, and validity windows.

The object functions as the central anchor for a small cluster of dependent tables. Both XDP_SERVICES_TL (the translatable/MLS companion) and XDP_SERVICE_PKG_DET (service package detail) point back to it through SERVICE_ID, as does XDP_SERVICE_VAL_ACTS (service validation actions). This hub-and-spoke topology supports a heuristic Data Vault classification of hub-leaning. In a Data Vault model this table would naturally serve as a hub entity keyed on SERVICE_ID, with the descriptive and version attributes behaving like satellite or link artefacts around it. That classification is offered as a modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The table exposes fourteen documented columns in the 12.2.2 physical schema. The most significant are listed below.

Note that SERVICE_ID is also covered by unique index XDP_SERVICES_U1, alongside the primary key constraint, which is typical when a surrogate key is both the PK and an independently indexed unique column.

Common Use Cases and Queries

Because the table is documented as not used, its practical applicability is largely confined to investigative and reporting work: reconciling orphaned service definitions, auditing historical provisioning configuration, or supporting data migration and archival analysis. A representative query lists active service versions at a point in time:

  • SELECT service_id, service_name, version, prov_required_flag FROM xdp_services WHERE TRUNC(SYSDATE) BETWEEN valid_date AND NVL(invalid_date, TRUNC(SYSDATE)) ORDER BY service_name, version;
  • Join to the MLS companion to retrieve language-specific names: SELECT s.service_id, t.service_name FROM xdp_services s, xdp_services_tl t WHERE s.service_id = t.service_id AND t.language = USERENV('LANG');
  • Isolate rows by security group: SELECT service_id, service_name FROM xdp_services WHERE security_group_id = :p_security_group;
  • Detect duplicate business keys prior to migration: SELECT service_name, version, COUNT(*) FROM xdp_services GROUP BY service_name, version HAVING COUNT(*) > 1;

These patterns support provisioning configuration reviews, role-to-service mapping reports, and validation of version-controlled service catalogs.

Related Objects

The following objects reference XDP_SERVICES through documented foreign keys and are the primary candidates for join or dependency analysis.

  • XDP_SERVICES_TL — the translated/MLS child; joined on SERVICE_ID for language-specific service names.
  • XDP_SERVICE_PKG_DET — service package detail; joined on SERVICE_ID to link services to package composition.
  • XDP_SERVICE_VAL_ACTS — service validation actions; joined on SERVICE_ID for per-service validation logic.
  • FND_SECURITY_GROUPS — the parent of SECURITY_GROUP_ID, providing the security-group definition and partitioning context.

No public PL/SQL API specific to XDP_SERVICES is documented in the ETRM excerpt; the dependent tables above are the principal integration surface for this object in the XDP schema.