Results for “xdp_service_packages_vl”

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

Overview

The view XDP_SERVICE_PACKAGES_VL belongs to the XDP – Provisioning product/module within Oracle E-Business Suite (valid in both the 12.1.1 and 12.2.2 release levels). It is a "VL" (View with Language) construct, which combines a base transactional table with its associated translation table so that language-sensitive descriptive columns are surfaced without requiring the calling application to explicitly join the *_TL table. The view therefore presents service package definitions — the top-level provisioning constructs that group service offerings and configuration data — together with their language-dependent display names and descriptions.

In EBS reporting, this view serves as a simplified, user-friendly read layer over the base service packages table. Because it resolves the translation row for the current runtime language, it is well suited to concurrent-program extracts, Oracle Reports, Discoverer/BIP data models, and integration interfaces that need to present service package metadata consistently to end users.

Underlying Base Objects

Per the ETRM metadata, the view is defined over two base objects:

• XDP_SERVICE_PACKAGES (aliased as B) — the primary table holding package identifiers, names, versions, and the VALID_DATE / INVALID_DATE effective-dating columns, along with standard auditing columns.
• XDP_SERVICE_PACKAGES_TL (aliased as T) — the translation table holding the language-specific DISPLAY_NAME and DESCRIPTION.

The two are joined on B.PACKAGE_ID = T.PACKAGE_ID, with the translation table additionally constrained by T.LANGUAGE = USERENV('LANG'). This predicate restricts the result to the single translation matching the session language, so the view returns exactly one row per package (subject to other filters). Note that the ETRM metadata records this view as "not implemented in this database" and lists no documented referenced base objects beyond the join text above, so object availability can vary by instance depending on whether the XDP Provisioning module objects have been deployed.

Key Columns

• ROW_ID — the ROWID of the base XDP_SERVICE_PACKAGES row, useful for row-level addressing and updates.
• PACKAGE_ID — primary key linking the base and translation records.
• PACKAGE_NAME — the internal (non-translated) package name.
• PACKAGE_VERSION — the version identifier of the service package definition.
• VALID_DATE / INVALID_DATE — the effective-dating window; the package is considered active when the current date falls between these values. This is the column referenced in the user's "valid_date" search and is the primary driver for date-based filtering.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns maintained by the concurrent manager and forms framework.
• DISPLAY_NAME, DESCRIPTION — language-dependent descriptive text sourced from the _TL table.

Common Use Cases and Queries

The most common use case is to enumerate currently effective service packages. Because VALID_DATE and INVALID_DATE are exposed directly, filters can be applied to return only active definitions:

SELECT package_id,
       package_name,
       package_version,
       display_name,
       valid_date,
       invalid_date
FROM   xdp_service_packages_vl
WHERE  TRUNC(SYSDATE) BETWEEN valid_date AND NVL(invalid_date, TRUNC(SYSDATE));

Analysts also use the view to reconcile translation completeness, retrieve the version history of a given package, or feed provisioning data into downstream integration tables. A version-oriented extract might look like:

SELECT package_name, package_version, display_name
FROM   xdp_service_packages_vl
WHERE  package_name = :p_package_name
ORDER  BY package_version;

Because DISPLAY_NAME and DESCRIPTION are already resolved for the session language (USERENV('LANG')), reporting tools need not perform an additional join to the translation table, simplifying data models and improving performance in multilingual deployments.