Results for “prov_required_flag”

22 results




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

Overview

XDP_SERVICE_PKG_DET is a table in the XDP schema (Provisioning module) within Oracle EBS 12.1.1 and 12.2.2. The ETRM documentation labels the object "Not used," indicating that Oracle does not publicly document a functional business purpose for it beyond its structural definition. Despite this designation, the table remains VALID and physically present, and it participates in a defined foreign-key topology that suggests it is an association or detail table linking service packages to individual services. Its composite primary key, XDP_SERVICE_PKG_DET_PK (PACKAGE_ID, SERVICE_ID), confirms its role as a many-to-many resolution between packages and services, with additional attributes layered on top.

From a data-modeling standpoint, the mined Data Vault classification is satellite-leaning. This heuristic reflects that the table's key structure is not a simple standalone hub; it carries descriptive and operational attributes (such as flags and sequencing) tied to the combination of a package and a service. Modelers should treat it as a candidate satellite keyed to a hub/link combination rather than as an independent hub, though this remains a modeling suggestion derived from FK structure rather than an Oracle-stated classification.

Key Information Stored

The table contains 11 documented columns. The most significant include:

The surrogate/business key distinction is notable: the primary key constraint uses only (PACKAGE_ID, SERVICE_ID), while the unique index XDP_SERVICE_PKG_DET_U1 spans (PACKAGE_ID, SERVICE_ID, ZD_EDITION_NAME). The edition column's inclusion in the unique index is characteristic of 12.2 editioning and reinforces that the business key operates per-edition.

Common Use Cases and Queries

Because the table is documented as "Not used," direct application queries are unlikely in standard provisioning flows; however, the table supports diagnostic and integration reporting where package-to-service composition must be reconstructed. A typical join pattern resolves package and service names:

  • Joining to XDP_SERVICE_PACKAGES and XDP_SERVICES on PACKAGE_ID and SERVICE_ID to list services per package.
  • Filtering by PROV_REQUIRED_FLAG to isolate services requiring provisioning.
  • Ordering by ACTIVATION_SEQUENCE to validate activation order configuration.
  • Filtering by SECURITY_GROUP_ID to respect data access in multi-org environments.
  • Optionally joining XDP_SERVICE_PKG_DET_TL on (PACKAGE_ID, SERVICE_ID) for translated (MLS) descriptions.

A representative query would select PACKAGE_ID, SERVICE_ID, PROV_REQUIRED_FLAG, and ACTIVATION_SEQUENCE from XDP_SERVICE_PKG_DET, then join outward to the package and service masters. Reporting use cases include auditing package composition, verifying activation sequencing, and reconciliation during upgrades or migrations.

Related Objects

The following objects are most significant given the documented FK relationships:

  • XDP_SERVICE_PACKAGES — Parent of PACKAGE_ID; defines the provisioning package master.
  • XDP_SERVICES — Parent of SERVICE_ID; defines the individual service master.
  • XDP_SERVICE_PKG_DET_TL — Translation (MLS) table referencing XDP_SERVICE_PKG_DET on PACKAGE_ID and SERVICE_ID.
  • FND_SECURITY_GROUPS — Parent of SECURITY_GROUP_ID; governs security-group based data access.

Together these objects form the package-service provisioning association, with XDP_SERVICE_PKG_DET acting as the connective detail and its _TL counterpart supplying language-specific text.