Results for “requested_start_date”

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

Overview

UMX_REG_REQUESTS is a registration request table owned by the APPLSYS schema and defined within the FND — Application Object Library product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about registration requests raised through the User Management (UMX) infrastructure, which governs user provisioning, self-service registration, and account lifecycle workflows. Each row represents a discrete registration request, typically tied to a workflow-driven approval process that evaluates whether a user, party, or role association should be created or modified.

Based on the foreign key structure mined from the metadata, the table classifies heuristically as a link table under a Data Vault modeling approach. It connects multiple reference entities — users who raise requests, users or parties for whom requests are raised, registration services, and security groups — making it a junction-style record rather than a pure descriptive satellite or a standalone hub.

Key Information Stored

The documented physical schema contains 20 columns. The most significant include:

• REG_REQUEST_ID — surrogate primary key (UMX_REG_REQUESTS_PK) and also defined by the unique index UMX_REG_REQUESTS_U1, making it the business-key candidate in this schema.
• REG_SERVICE_CODE — foreign key to UMX_REG_SERVICES_B, identifying which registration service governs the request.
• REG_SERVICE_TYPE — classifies the nature of the registration service applied.
• STATUS_CODE — current workflow or disposition state of the request.
• REQUESTED_BY_USER_ID — FK to FND_USER, the user who initiated the request.
• REQUESTED_FOR_USER_ID — FK to FND_USER, the user the request targets.
• REQUESTED_FOR_PARTY_ID — FK to HZ_PARTIES, linking the request to a trading community party.
• REQUESTED_USERNAME — proposed or affected login name.
• REQUESTED_START_DATE / REQUESTED_END_DATE — validity window for the requested access.
• WF_ROLE_NAME — workflow role associated with the request.
• AME_APPLICATION_ID / AME_TRANSACTION_TYPE_ID — Approval Management Engine context for routing approvals.
• JUSTIFICATION — free-text rationale captured from the requester.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, enforcing multi-tenant data segregation.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include auditing pending registrations, monitoring approval bottlenecks, and reconciling self-service signups against FND_USER. A representative query enumerating open requests joined to the requesting user:

• SELECT r.reg_request_id, r.status_code, u.user_name requested_by, r.requested_username, r.justification FROM umx_reg_requests r, fnd_user u WHERE r.requested_by_user_id = u.user_id AND r.status_code = 'PENDING';
• Reporting requests by service: join to UMX_REG_SERVICES_B on REG_SERVICE_CODE to summarize volume per registration service.
• AME analysis: filter by AME_APPLICATION_ID and AME_TRANSACTION_TYPE_ID to trace approval routing histories.
• Party reconciliation: join to HZ_PARTIES via REQUESTED_FOR_PARTY_ID to detect supplier or customer portal registrations.

Related Objects

• FND_USER — referenced twice, via REQUESTED_BY_USER_ID and REQUESTED_FOR_USER_ID.
• HZ_PARTIES — via REQUESTED_FOR_PARTY_ID, connecting registration to trading community data.
• UMX_REG_SERVICES_B — via REG_SERVICE_CODE, defining the service semantics.
• FND_SECURITY_GROUPS — via SECURITY_GROUP_ID, governing data access partitioning.
• UMX_REG_REQUESTS_PK / UMX_REG_REQUESTS_U1 — the primary and unique indexes on REG_REQUEST_ID.
• AME_APPLICATION_ID / AME_TRANSACTION_TYPE_ID — implicit references into AME approval configuration tables.