Search Results xdp_wf_migrate

Overview

XDP_WF_MIGRATE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as OTHER within the ETRM repository. Its documented purpose is to migrate Oracle Workflow configuration and runtime data associated with the Oracle iStore / Oracle Advanced Outbound (XDP) product family between environments. The package header shown in the source excerpt declares AUTHID CURRENT_USER, confirming that all SQL inside the package executes with the privileges of the invoking user rather than the package owner, which is significant because the migration routines copy Workflow "local" entities — roles, users, user-role assignments, lookup types, and item type definitions — that must land in the schema of the target environment.

The search term wf_local maps directly to this package's migrated objects. The Workflow tables WF_LOCAL_ROLES, WF_LOCAL_USERS, and WF_LOCAL_USER_ROLES hold the directory of roles and users native to a Workflow installation. XDP_WF_MIGRATE includes dedicated routines (MOVELOCALROLES, MOVELOCALUSERS, MOVELOCALUSERROLES) that relocate these local directory entries, together with the sequences and IDs that back them, as declared by the package-level variables g_WF_ADHOC_ROLE_S_SEQ, g_WF_NOTIFICATIONS_S_SEQ, and g_WF_PROCESS_ACTIVITIES_S_SEQ. In effect the package is a targeted environment-cloning utility for Workflow metadata in an XDP/XDPWF deployment, not a general-purpose tool.

Key Procedures and Functions

The twenty documented routines fall into verification, preprocessing, movement, and postprocessing groups.

• VerifySuffix — validates the unique suffix supplied by the caller; the suffix is appended to lookup type and display name values when conflicts with existing rows are detected.
• VerifyItemType — determines whether an item type is eligible for migration; only non-Workflow item types absent from the target instance may be moved.
• VerifyDirectory — performs the equivalent eligibility check for Workflow directory (local user and role) data.
• GetUniqueLookupType / GetUniqueDisplayName — generate conflict-free internal names and display names using the verified suffix.
• InitializeSequences / ResetSequenceNumbers — capture and later reset the Workflow sequence values used to key the migrated rows.
• PreprocessMigration — top-level controller that orchestrates the preprocessing phase and populates the package-level collections.
• PreprocessLookupTypes — scans WF_LOOKUP_TYPES_TL and related lookup tables for conflicts, recording them into the WF_LOOKUP_TYPE_TL_LIST and WF_LOOKUP_TYPE_TL_DISP_LIST PL/SQL tables declared in the specification.
• MoveConfigData — migrates Workflow configuration entities such as lookup types and item type definitions.
• MoveRuntimeData — migrates runtime artifacts, including notifications and activity records.
• MoveLocalRoles, MoveLocalUsers, MoveLocalUserRoles — copy rows from the WF_LOCAL_ROLES, WF_LOCAL_USERS, and WF_LOCAL_USER_ROLES directory tables, the objects most relevant to the "wf_local" search.
• ReenqueueDeferredAct — requeues deferred workflow activities so migrated instances resume processing correctly.
• Postprocess — final reconciliation step executed after the move phase.
• Display / Create_Log_Files — emit diagnostic output and write log files summarizing the migration, including any conflict resolutions.

Tables Accessed

The ETRM metadata does not enumerate specific base tables, and the routines are documented as accessing objects through APPS synonyms. Based on the declared functionality, the package reads and writes the Workflow local directory tables WF_LOCAL_ROLES, WF_LOCAL_USERS, and WF_LOCAL_USER_ROLES; the lookup tables WF_LOOKUP_TYPES and WF_LOOKUP_TYPES_TL together with their display-name rows; item type and activity tables such as WF_ITEM_TYPES, WF_ITEM_ATTRIBUTES, WF_ACTIVITIES, and WF_PROCESS_ACTIVITIES; notification data in WF_NOTIFICATIONS; and the deferred activity queue underlying WF_DEFERRED. Sequence values for ad hoc roles, notifications, and process activities are read and reset directly. The lookup-conflict collections declared in the package specification are populated from these same lookup tables during preprocessing.

Usage Notes

XDP_WF_MIGRATE is an internal migration utility rather than a user-facing API. It is intended to be invoked by an administrator or a wrapper concurrent program during an environment refresh or an XDP implementation rollout, when Workflow configuration and local directory data created in a source instance must be reproduced in a target instance. Because the package is AUTHID CURRENT_USER and manipulates APPS-synonymed Workflow tables, it must be executed by a user with the appropriate Workflow and APPS privileges, and it should be run in a controlled downtime window: the preprocessing routines populate package-level state, the move routines commit in batches governed by g_CommitCount, and ResetSequenceNumbers and ReenqueueDeferredAct are required for the target instance to operate consistently afterward. ETRM records zero dependent packages, so it is not called programmatically by other shipped code; any invocation is from a concurrent program, SQL*Plus script, or custom wrapper. The Display and Create_Log_Files routines should always be included in the invocation sequence so that conflict resolutions produced by GetUniqueLookupType and GetUniqueDisplayName are captured for audit.