Results for “ame_application_id”

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

Overview

UMX_REG_SERVICES_B is the base metadata table for the Oracle User Management (UMX) registration framework within the FND – Application Object Library product. It resides in the APPLSYS schema and stores the definition of each registration service made available through Oracle User Management, such as self-service user registration, approver-driven registration, and related request-handling flows. Each row describes a discrete registration process: its type, the function that launches it, the notification event that drives workflow communication, and the AME (Approvals Management Engine) configuration that governs its approval routing.

The table serves as the definitional anchor for the registration lifecycle. Transactional registration activity is captured downstream in UMX_REG_REQUESTS, which references this table through REG_SERVICE_CODE, while translatable descriptive attributes are externalized to UMX_REG_SERVICES_TL. The presence of administrative columns such as START_DATE, END_DATE, SECURITY_GROUP_ID, and ZD_EDITION_NAME indicates that service metadata is versioned and date-effectivity controlled rather than static.

Under the heuristic Data Vault classification derived from its foreign key structure, UMX_REG_SERVICES_B is satellite-leaning. It carries descriptive and configuration attributes attached to the registration service concept, references several independent reference entities (application, function, workflow event, security group), and is itself referenced by dependents. This suggests modeling it as a satellite oriented around the REG_SERVICE_CODE business key, rather than as a standalone hub or an associative link.

Key Information Stored

The table contains nineteen documented columns. The most significant are:

• REG_SERVICE_CODE – The primary key column and business identifier of the registration service, used throughout the UMX schema as the join key to requests and translations.
• ZD_EDITION_NAME – The editioning discriminator used in 12.2 online patching; jointly with REG_SERVICE_CODE it forms the unique index UMX_REG_SERVICES_B_U1.
• REG_SERVICE_TYPE – Categorizes the registration process, distinguishing registration styles and workflows.
• APPLICATION_ID – Foreign key to FND_APPLICATION, identifying the owning application context.
• REG_FUNCTION_ID – Foreign key to FND_FORM_FUNCTIONS, the executable function invoked to perform the registration.
• WF_NOTIFICATION_EVENT_GUID – Foreign key to WF_EVENTS, the workflow business event raised for registration notifications.
• WF_BUS_LOGIC_EVENT_GUID – A second workflow event reference governing business logic invocation.
• WF_ROLE_NAME – The workflow role associated with the service for routing and assignment.
• EMAIL_VERIFICATION_FLAG – Indicates whether email address verification is required during registration.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS controlling data access scope.
• AME_APPLICATION_ID and AME_TRANSACTION_TYPE_ID – Identify the AME application and transaction type used to evaluate approval rules for the service.
• START_DATE, END_DATE – Effective dating for the service definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns maintained by the framework.

The surrogate primary key is UMX_REG_SERVICES_B_PK on REG_SERVICE_CODE; the business-key candidate is the unique index UMX_REG_SERVICES_B_U1 spanning REG_SERVICE_CODE and ZD_EDITION_NAME, reflecting edition-aware uniqueness.

Common Use Cases and Queries

Typical usage centers on identifying which registration services are active, which approval configuration applies, and how requests tie back to a service definition. A common pattern joins the base table to its translation table and to the application definition:

• Listing active services with their owning application and launching function.
• Reporting AME approval configuration per registration service.
• Joining UMX_REG_REQUESTS to this table to attribute registration activity to a service code.
• Auditing which services require email verification or specific workflow events.

A representative query pattern selects REG_SERVICE_CODE, REG_SERVICE_TYPE, EMAIL_VERIFICATION_FLAG, and the audit columns from UMX_REG_SERVICES_B joined to FND_APPLICATION on APPLICATION_ID, and to UMX_REG_SERVICES_TL on REG_SERVICE_CODE for the localized name, filtering by START_DATE and END_DATE for currently effective rows. Administrators commonly constrain results by SECURITY_GROUP_ID to align with data access.

Related Objects

• UMX_REG_REQUESTS – References this table via REG_SERVICE_CODE; holds individual registration requests submitted against each service.
• UMX_REG_SERVICES_TL – References this table via REG_SERVICE_CODE; stores translatable name and description attributes.
• FND_APPLICATION – Referenced through APPLICATION_ID; identifies the owning application.
• FND_FORM_FUNCTIONS – Referenced through REG_FUNCTION_ID; the executable registration function.
• WF_EVENTS – Referenced through WF_NOTIFICATION_EVENT_GUID and WF_BUS_LOGIC_EVENT_GUID; drives workflow notification and business logic.
• FND_SECURITY_GROUPS – Referenced through SECURITY_GROUP_ID; governs access scope.

These relationships position UMX_REG_SERVICES_B as the central definition table that the registration request, translation, workflow, and security subsystems all depend upon.