Search Results create_stage_indexes

Overview

APPS.WF_LOCAL_SYNCH is the Workflow Local Synchronization package in Oracle E-Business Suite, shipped under the Oracle Workflow (OWF) product family. Its declared purpose, as documented in the package header, is to provide application programming interfaces that enable synchronization between the user and role information stored in application tables by the various Oracle E-Business Suite modules and the corresponding information held in the Workflow local tables. The package is defined with AUTHID CURRENT_USER and carries an "internal" scope designation, a display name of "Workflow Local Synchronization," an active lifecycle, and a compatibility status of "S". Its primary business entity category is WF_USER. Functionally, the package keeps the Workflow directory cache — principally WF_LOCAL_ROLES and its related association tables — consistent with the authoritative definitions of users and roles maintained elsewhere in the E-Business Suite, and it additionally maintains the entity manager cache used by the Workflow directory services.

Key Procedures and Functions

The package exposes twelve documented procedures and functions, the majority of which are concerned with propagating and validating user and role data and with managing the local directory cache.

• PROPAGATE_USER — Synchronizes the information for a single user from an application table into the Workflow local roles table, identifying the user by originating system and originating system ID, and updating the entity manager where appropriate. It accepts an attribute list plus start and expiration dates.
• PROPAGATE_ROLE — Performs the equivalent synchronization for a role rather than a user.
• PROPAGATE_USER_ROLE — Synchronizes the role assignment of a user.
• PROPAGATEUSERROLE — A closely related entry point for propagating user-role information, listed separately in the documented API inventory.
• BULKSYNCHRONIZATION — Drives a bulk synchronization of the Workflow local tables from the application source data.
• BULKSYNCHRONIZATION_CONC — The concurrent-program entry point that invokes the bulk synchronization process.
• CHECKCACHE — Verifies the state of the Workflow local directory cache.
• DELETECACHE — Removes cached directory information.
• VALIDATEUSERROLES — Validates user-role relationships held in the local tables.
• VALIDATEUSERROLES_CONC — The concurrent-program entry point for the user-role validation process.
• CREATE_STAGE_INDEXES — Creates the staging indexes required to support bulk synchronization.
• BULK_RESET_NTFPREF — Resets the notification preference state as part of bulk processing.

Tables Accessed

The package reads and writes the core Workflow directory tables: WF_LOCAL_ROLES, WF_LOCAL_USER_ROLES, WF_ROLE_HIERARCHIES, WF_USER_ROLE_ASSIGNMENTS, and WF_DIRECTORY_PARTITIONS, with WF_PARAMETER_LIST_T supplying the attribute list type used by the propagation APIs. Source user data is obtained from FND_USER, while FND_LANGUAGES and FND_LOOKUP_VALUES provide language and lookup context. Administrative and diagnostic operations on the staging indexes rely on the DBA_INDEXES, DBA_IND_COLUMNS, DBA_IND_EXPRESSIONS, and DBA_IND_PARTITIONS data dictionary views, supported by DBMS_SQL and PLITBLM. These accesses reflect the package's dual role: reading authoritative user and role definitions, and writing the denormalized local directory structures that Workflow uses at runtime.

Usage Notes

WF_LOCAL_SYNCH is an internal package and is not intended for direct invocation by end users through standard forms. It is most commonly exercised indirectly: when users and roles are created or amended in the application modules or in Oracle User Management, the propagation APIs are called to reflect those changes into the Workflow directory. The bulk synchronization, validation, and cache procedures are exposed through concurrent programs (as indicated by the _CONC entry points), which administrators schedule to reconcile the local tables after significant user or role changes. Because the package is referenced by thirty-three other packages in the E-Business Suite, customizations should avoid modifying it and should instead call the documented APIs where integration with Workflow directory data is required. The iHelp references FND/@lsyapi and FND/@lsyapi#a_lspu direct readers to the associated online help for the synchronization interface and the propagate user API respectively.