Results for “wf_local_roles_stage”

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

Overview

WF_LOCAL_ROLES_STAGE is a staging table in the APPLSYS schema within the Oracle E-Business Suite FND (Application Object Library) product. It functions as the interim repository into which the Workflow Directory Services synchronization process writes role, user, and group records before they are merged into the runtime role definitions consumed by Oracle Workflow. In this capacity, the table isolates inbound role data — sourced from external directories, HZ origin systems, or bulk load operations — from the live directory, allowing validation, reconciliation, and controlled promotion of records before they become available to notification routing and approval logic.

The heuristic Data Vault classification mined from the foreign-key structure marks this table as standalone. In modeling terms, this suggests WF_LOCAL_ROLES_STAGE does not behave as a conventional hub, link, or satellite. Its identity is only partially resolved through the composite unique index, and its three outbound foreign keys act as reference lookups rather than as a hub spine. Practitioners should therefore treat it as a transient, load-oriented structure rather than a durable modeled entity.

Key Information Stored

The table contains 24 documented columns. The most significant are the identity and descriptive attributes: NAME, DISPLAY_NAME, DESCRIPTION, EMAIL_ADDRESS, and FAX, which together define the addressable role or user. NOTIFICATION_PREFERENCE, LANGUAGE, and TERRITORY control how workflow notifications are formatted and delivered. ORIG_SYSTEM and ORIG_SYSTEM_ID identify the authoritative source directory and the record's key within it.

Lifecycle attributes include START_DATE, EXPIRATION_DATE, and STATUS, which govern the validity window of the role. USER_FLAG distinguishes individual users from group or role entries. SECURITY_GROUP_ID, PARTITION_ID, and ORIG_SYSTEM_ID are foreign-key columns referencing FND_SECURITY_GROUPS, JTF_FM_PARTITION_X_REQUEST, and HZ_ORIG_SYSTEMS_B respectively. The columns PARENT_ORIG_SYSTEM and PARENT_ORIG_SYSTEM_ID capture hierarchy relationships, while OWNER_TAG supports ownership grouping.

No single surrogate primary key column is documented; instead, the business-key candidate is the composite unique index WF_LOCAL_ROLES_STAGE_U1 defined over (NAME, ORIG_SYSTEM, ORIG_SYSTEM_ID, PARTITION_ID). Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are present as expected.

Common Use Cases and Queries

Typical uses include troubleshooting failed or stalled Workflow Directory Services synchronization jobs, reconciling staging counts against the live WF_LOCAL_ROLES table, and auditing inbound role loads from external directories.

• Detecting staged roles that failed promotion: SELECT name, orig_system, status FROM wf_local_roles_stage WHERE status <> 'ACTIVE';
• Identifying records by source system: SELECT s.name, o.orig_system_name FROM wf_local_roles_stage s, hz_orig_systems_b o WHERE s.orig_system_id = o.orig_system_id;
• Reviewing partition-scoped staging rows: SELECT name, partition_id FROM wf_local_roles_stage WHERE partition_id IS NOT NULL;
• Comparing staging versus runtime roles by the composite business key (NAME, ORIG_SYSTEM, ORIG_SYSTEM_ID, PARTITION_ID).

Related Objects

• HZ_ORIG_SYSTEMS_B — joined via ORIG_SYSTEM_ID; identifies the source directory.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; scopes role visibility.
• JTF_FM_PARTITION_X_REQUEST — joined via PARTITION_ID; supports partitioned synchronization.
• WF_LOCAL_ROLES — the runtime directory table into which staged rows are promoted.
• WF_LOCAL_USER_ROLES — stores user-to-role assignments derived from staging.
• WF_ROLES and WF_USERS — workflow role and user views consuming the directory.
• WF_DIRECTORY — the API package driving synchronization between staging and runtime tables.