Results for “package_version”

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

Overview

The XDP_SERVICE_PACKAGES table resides in the XDP schema and belongs to the XDP – Provisioning product module within Oracle E-Business Suite. It functions as the master definition table for service packages, storing the header-level identity, versioning, and validity of each package that the provisioning engine can assign or activate for a subscriber. In the ETRM 12.2.2 documentation, the object-level description is recorded as "Not used," and the table is marked VALID with twelve documented columns. This indicates that, although the table remains physically present and structurally sound, it is a legacy or dormant object within the provisioning data model and is not actively maintained by current application flows in 12.1.1 or 12.2.2.

From a Data Vault modeling perspective, the metadata's heuristic classification is hub-leaning. This suggests the table best serves as a hub entity: its primary key PACKAGE_ID provides a stable, non-volatile business key, while version and validity attributes describe the descriptive context of each package. Analysts modeling this data into a warehouse should therefore treat XDP_SERVICE_PACKAGES as a hub and route the timeline-oriented attributes into a satellite.

Key Information Stored

The surrogate primary key is PACKAGE_ID, enforced by the constraint XDP_SERVICE_PACKAGES_PK and by the unique index XDP_SERVICE_PACKAGES_U1. A second unique index, XDP_SERVICE_PACKAGES_U2, defines the composite business key of PACKAGE_NAME and PACKAGE_VERSION, guaranteeing that a given package name cannot repeat at the same version number. Together with the primary key constraint XDP_SERVICE_PACKAGES_UK1, these indexes establish both the technical and the business identity of each row.

The most significant columns include:

• PACKAGE_ID — surrogate primary key and the join column referenced by all child tables.
• PACKAGE_NAME — the functional name of the service package; part of the business key.
• PACKAGE_VERSION — the version identifier that distinguishes successive revisions of the same package name.
• VALID_DATE and INVALID_DATE — the effective dating window that governs when a package definition is usable.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS that controls row-level access by operating unit or responsibility.
• MIGRATED_PACKAGE_NAME — a migration-tracking field that records the pre-conversion name of the package.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO audit columns maintained for every row.

Common Use Cases and Queries

Because the table is documented as not actively used, the primary practical scenarios are data migration audits, historical reconciliation, and diligence on legacy provisioning configurations. A typical query retrieves the current valid package definition for a given name:

• Filter rows where VALID_DATE <= SYSDATE and (INVALID_DATE IS NULL OR INVALID_DATE > SYSDATE) to return only currently effective packages.
• Join PACKAGE_ID to XDP_SERVICE_PKG_DET to expand a package into its constituent detail lines.
• Join PACKAGE_ID to XDP_SERVICE_PACKAGES_TL to obtain translated PACKAGE_NAME values for multilingual reporting.
• Aggregate by PACKAGE_NAME and order by PACKAGE_VERSION to reconstruct a version history for migration validation.
• Filter by SECURITY_GROUP_ID to restrict output to the security groups relevant to a specific operating unit.

Reporting use cases center on confirming that no orphaned or duplicate package versions exist prior to an upgrade from 12.1.1 to 12.2.2.

Related Objects

The following objects participate in direct foreign key relationships with XDP_SERVICE_PACKAGES:

• XDP_SERVICE_PACKAGES_TL — the translation table, joined on PACKAGE_ID.
• XDP_SERVICE_PKG_DET — the package detail table, joined on PACKAGE_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID to enforce access control.

These relationships place XDP_SERVICE_PACKAGES at the center of the provisioning package hierarchy, with the translation and detail tables acting as dependent children keyed by the same PACKAGE_ID surrogate value.