Results for “assigning_role_start_date”

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

Overview

WF_UR_ASSIGNMENTS_STAGE is a staging table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite. It functions as an intermediate landing area for user-role assignment data processed by the Oracle Workflow User/Role (WF_UR) infrastructure. In EBS releases 12.1.1 and 12.2.2, this table supports the synchronization and propagation of role assignments into the runtime Workflow directory structures, allowing bulk or external assignment records to be validated, resolved, and merged before they become authoritative.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning it does not participate in a classic hub-link-satellite chain through enforced foreign keys within its own staging scope. Modelers may treat it as a staging or link-stage artifact whose business key is defined by the composite of ASSIGNING_ROLE, USER_NAME, RELATIONSHIP_ID, and PARTITION_ID, as documented by the unique index WF_UR_ASSIGNMENTS_STAGE_U1.

Key Information Stored

The table contains 28 documented columns. The most consequential are those that describe the assignment triplet and its temporal validity:

• USER_NAME – the recipient principal of the assignment.
• ROLE_NAME – the role being granted.
• ASSIGNING_ROLE – the role from which the grant originates; part of the unique business key.
• RELATIONSHIP_ID – identifier linking the assignment to a defined relationship context.
• PARTITION_ID – partition scope; participates in the unique index and carries the only documented foreign key.
• START_DATE / END_DATE – overall effective window of the staged assignment record.
• USER_START_DATE / USER_END_DATE, ROLE_START_DATE / ROLE_END_DATE, ASSIGNING_ROLE_START_DATE / ASSIGNING_ROLE_END_DATE – granular validity windows for each element of the assignment triad, enabling precise temporal reconciliation.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – resolved effective dating applied when the record is promoted.
• USER_ORIG_SYSTEM / USER_ORIG_SYSTEM_ID, ROLE_ORIG_SYSTEM / ROLE_ORIG_SYSTEM_ID, PARENT_ORIG_SYSTEM / PARENT_ORIG_SYSTEM_ID – origin-system identifiers supporting multi-source integration.
• OWNER_TAG – ownership classification of the staged record.
• ASSIGNMENT_REASON – textual rationale for the grant.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on auditing, troubleshooting, and reporting on role provisioning before or after synchronization into runtime tables. A common pattern selects staged rows for a given user and role:

SELECT user_name, role_name, assigning_role, start_date, end_date
FROM applsys.wf_ur_assignments_stage
WHERE user_name = :p_user
ORDER BY start_date DESC;

Analysts frequently join staged records to partition metadata via PARTITION_ID → JTF_FM_PARTITION_X_REQUEST to trace partition-scoped assignment loads. Reconciliation reports compare staged effective dates against the live directory to detect orphaned or expired grants. Audit queries filter on ASSIGNMENT_REASON or OWNER_TAG to identify assignments originating from specific provisioning events, while origin-system columns support multi-node or third-party HR integration checks.

Related Objects

• JTF_FM_PARTITION_X_REQUEST – referenced through WF_UR_ASSIGNMENTS_STAGE.PARTITION_ID; the sole documented foreign key target.
• WF_USER_ROLES – runtime directory of user-role grants to which staged rows are promoted.
• WF_ROLES – master role definitions joined on ROLE_NAME.
• WF_USERS – principal definitions joined on USER_NAME.
• WF_USER_ROLE_ASSIGNMENTS – related assignment relationship data supporting hierarchical grants.
• FND_USER – application user master referenced when resolving USER_NAME.

Together these objects form the Workflow User/Role directory ecosystem in which WF_UR_ASSIGNMENTS_STAGE serves as the controlled entry point for assignment synchronization.