Results for “xdp_service_packages_tl”

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

Overview

XDP_SERVICE_PACKAGES_TL is the translation (language) table that accompanies the base table XDP_SERVICE_PACKAGES in the XDP – Provisioning product of Oracle E-Business Suite. The "_TL" suffix identifies it as a translated table in the standard Oracle EBS multilingual architecture, meaning it stores language-specific text attributes for the same logical entity held in the base table, while non-translatable attributes remain in the base table. The documentation metadata lists its description as "Not used," and its documented physical schema in ETRM 12.2.2 carries eleven columns. The table is owned by the XDP schema and is marked VALID.

From a modeling perspective, the FK structure — where XDP_SERVICE_PACKAGES_TL.PACKAGE_ID references XDP_SERVICE_PACKAGES and SECURITY_GROUP_ID references FND_SECURITY_GROUPS — suggests a satellite-leaning classification. In Data Vault terms, this table behaves as a satellite attached to the hub/link represented by the base package entity, carrying descriptive and translated attributes keyed by the parent identifier plus a language discriminator.

Key Information Stored

The primary key is defined by XDP_SERVICE_PACKAGES_TL_PK over (PACKAGE_ID, LANGUAGE), establishing the surrogate/compound key that uniquely identifies each language row for a given package. A separate unique index, XDP_SERVICE_PACKAGES_TL_U1, also covers (PACKAGE_ID, LANGUAGE), which is the documented business-key candidate reinforcing the same combination.

• PACKAGE_ID — foreign key to XDP_SERVICE_PACKAGES; identifies the parent service package.
• LANGUAGE — the language code for this translated row, part of the primary key.
• SOURCE_LANG — the source language from which the translation originated.
• DISPLAY_NAME — the translated, user-facing name of the service package.
• DESCRIPTION — the translated description text.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling row-level access.
• CREATED_BY, CREATION_DATE — standard audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the last modification user, timestamp, and login.

Common Use Cases and Queries

Because translated text is separated from the base entity, the primary use case is retrieving the correct display name and description for a package in a given language, typically by joining the translation table to the base table. A representative pattern:

• Language-specific lookup: SELECT t.DISPLAY_NAME, t.DESCRIPTION FROM XDP_SERVICE_PACKAGES_TL t WHERE t.PACKAGE_ID = :id AND t.LANGUAGE = USERENV('LANG');
• Listing all translations: SELECT t.LANGUAGE, t.DISPLAY_NAME FROM XDP_SERVICE_PACKAGES_TL t WHERE t.PACKAGE_ID = :id.
• Joined reporting: combine base and translation tables via PACKAGE_ID to produce multilingual catalog reports of service packages.
• Audit and reconciliation: query CREATED_BY/LAST_UPDATED_BY columns to track translation maintenance activity.

Related Objects

• XDP_SERVICE_PACKAGES — the base (non-translated) table; joined on XDP_SERVICE_PACKAGES_TL.PACKAGE_ID = XDP_SERVICE_PACKAGES.PACKAGE_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for row-level security filtering.
• XDP_SERVICE_PACKAGES_TL_PK and XDP_SERVICE_PACKAGES_TL_U1 — the primary key and unique index supporting language-keyed access.
• FND_LANGUAGES / FND_LANGUAGE — standard reference for interpreting the LANGUAGE and SOURCE_LANG values.
• Common translation views — reporting layers typically expose the "_TL" data through joined views rather than direct queries.