Search Results umx_reg_services_vl




Overview
Explore in AI Chat

Overview

UMX_REG_SERVICES_VL is a documented, VALID view owned by the APPS schema within the FND — Application Object Library product family of Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a "VL" view — that is, a translatable view that joins the base (non-translated) registration services table with its language-specific translations table, filtering the translation rows to the session's current language. The view's stated purpose in the ETRM metadata is to serve as the VL view for registration processes handled by the User Management (UMX) infrastructure.

Registration processes in EBS — account self-service registration, approver notification, e-mail verification, and workflow-based provisioning — are defined as registration service records. This view exposes those service definitions, their associated Workflow event GUIDs, AME (Approvals Management Engine) mappings, and the human-readable display name, description, and usage text for the current language. It serves as the principal reporting and integration interface over registration service configuration without requiring callers to join the base and translation tables manually or to hard-code a language.

Underlying Base Objects

The ETRM 12.2.2 metadata lists two referenced base objects, exposed in APPS through synonyms:

  • UMX_REG_SERVICES_B — the base table holding language-independent attributes such as service code, service type, workflow notification and business-logic event GUIDs, e-mail verification flag, application identifier, role name, function identifier, and AME application and transaction type identifiers.
  • UMX_REG_SERVICES_TL — the translation table holding DISPLAY_NAME, DESCRIPTION, and USAGE for each supported language.

The view text joins the two on REG_SERVICE_CODE and restricts T.LANGUAGE to USERENV('LANG'), so each row returned reflects the translation corresponding to the caller's session language. The column list is derived from B, with the three translated columns appended from T, plus the pseudo-column B.ROWID aliased as ROW_ID. Both base objects are referenced through APPS synonyms rather than fully qualified table names.

Key Columns

Common Use Cases and Queries

Typical uses include auditing registration service configuration, verifying AME and Workflow bindings ahead of an upgrade, and building custom inquiry or integration extracts that require translated labels.

List all registration services with their translated names:

  • SELECT reg_service_code, reg_service_type, display_name, description, usage FROM apps.umx_reg_services_vl ORDER BY reg_service_code;

Identify services where e-mail verification is enabled:

  • SELECT reg_service_code, display_name, wf_role_name FROM apps.umx_reg_services_vl WHERE email_verification_flag = 'Y';

Review AME and Workflow integration points for a given service:

  • SELECT reg_service_code, wf_notification_event_guid, wf_bus_logic_event_guid, ame_application_id, ame_transaction_type_id FROM apps.umx_reg_services_vl WHERE reg_service_code = :p_code;

Because the view resolves translations dynamically through USERENV('LANG'), the same query returns language-appropriate text for each user session, making it suitable for both English and localized reporting environments in 12.1.1 and 12.2.2.