Results for “umx_reg_services_tl”

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

Overview

UMX_REG_SERVICES_TL is the translation table for UMX_REG_SERVICES_B, owned by the APPLSYS schema and delivered as part of the FND — Application Object Library product family. In Oracle EBS 12.1.1 and 12.2.2, this object stores the language-specific, translated attributes of registered services managed by the User Management (UMX) infrastructure. Every base row in UMX_REG_SERVICES_B is paired with one or more translated rows in this table, one per installed language, enabling the service registry to present locale-appropriate display text without duplicating the operational definition of each service.

The table carries a heuristic Data Vault classification of satellite-leaning. Under that modeling suggestion, UMX_REG_SERVICES_TL behaves as a descriptive satellite attached to its parent hub-like entity, UMX_REG_SERVICES_B, keyed by the business identifier REG_SERVICE_CODE and qualified by LANGUAGE. It contains descriptive, context-dependent attributes rather than relationships between business entities, which is consistent with the satellite pattern.

Key Information Stored

The documented physical schema contains 13 columns. The most operationally significant are listed below.

• REG_SERVICE_CODE — the business identifier of the registered service; part of the composite primary key and the FK join column to UMX_REG_SERVICES_B.
• LANGUAGE — the NLS language code of the translated row; the second component of the composite primary key.
• SOURCE_LANG — the language in which the source text was originally authored, used by the translation (TL) framework for reconciliation.
• DISPLAY_NAME — the user-visible, localized name of the registered service.
• DESCRIPTION — the localized description of the service's purpose.
• USAGE — localized usage text associated with the service.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording row creation and last modification metadata.
• SECURITY_GROUP_ID — the security group to which the translated row belongs; an FK to FND_SECURITY_GROUPS supporting multi-organization data partitioning.
• ZD_EDITION_NAME — the edition identifier used by the Edition-Based Redefinition (EBR) framework in 12.2.x.

The primary key constraint is UMX_REG_SERVICES_TL_PK, defined on (REG_SERVICE_CODE, LANGUAGE). A unique index, UMX_REG_SERVICES_TL_U1, is documented on (REG_SERVICE_CODE, LANGUAGE, ZD_EDITION_NAME), making that combination the business-key candidate that accommodates editioned rows.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios involve joining the translation table to its base table to retrieve localized display text for a given language, or auditing which services lack a translation in a particular installed language.

• Retrieving localized service names: SELECT b.reg_service_code, tl.display_name, tl.description FROM umx_reg_services_b b, umx_reg_services_tl tl WHERE b.reg_service_code = tl.reg_service_code AND tl.language = USERENV('LANG');
• Identifying missing translations: comparing UMX_REG_SERVICES_B rows against UMX_REG_SERVICES_TL entries filtered by language.
• Security-group-scoped reporting: filtering on SECURITY_GROUP_ID when validating data visibility in multi-organization deployments.
• Post-upgrade verification in 12.2.x: validating ZD_EDITION_NAME values to confirm editioned rows resolve correctly.

Because this is a TL table, queries should always constrain on LANGUAGE to avoid blending translations across installed languages.

Related Objects

UMX_REG_SERVICES_TL participates in a small, well-defined set of relationships within the FND and User Management schemas.

• UMX_REG_SERVICES_B — the base table; joined on REG_SERVICE_CODE. This is the primary dependency and the source of untranslated service definitions.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, defining the security partitioning of translated rows.
• UMX_REG_SERVICES_TL_PK — the primary key constraint enforcing unique (REG_SERVICE_CODE, LANGUAGE) combinations.
• UMX_REG_SERVICES_TL_U1 — the unique index on (REG_SERVICE_CODE, LANGUAGE, ZD_EDITION_NAME), supporting edition-aware lookups.
• FND_LANGUAGES — the reference table against which LANGUAGE and SOURCE_LANG values are validated.
• The UMX registration APIs and the FND Application Object Library translation utilities that populate and maintain these rows during patching and language installation.

Together these objects form the localized service registry surface consulted by User Management during authentication and authorization processing.