Search Results set_item_parent

Overview

The APPS.WF_ITEM package body implements the core runtime services of the Oracle Workflow engine that manage the lifecycle of a workflow item. In Oracle EBS 12.1.1 and 12.2.2, a "workflow item" (identified by a numeric item key, an item type, and an item key value) is the fundamental unit of process execution. Every business event routed through Workflow — an order booking, a requisition approval, an iExpense notification — corresponds to one or more workflow items. The WF_ITEM package provides the primitive operations required to create, locate, own, lock, age, and terminate those items, insulating higher-level components such as WF_ENGINE from direct manipulation of the underlying WF_ITEMS table.

Per the documented ETRM metadata, the object is owned by APPS, holds VALID status in both release levels, and is classified as OTHER. It exposes twelve documented procedures and functions and is itself invoked by 32 other packages, which underscores its role as a foundational dependency across the Workflow schema.

Key Procedures and Functions

The twelve documented entry points address distinct lifecycle concerns:

• CLEARCACHE — purges cached item metadata so that subsequent lookups read current data from the base tables.
• CREATE_ITEM — instantiates a new workflow item record, establishing the root of an execution instance.
• SET_ITEM_PARENT — records the parent-child relationship used to model subprocess and nested-process hierarchies.
• SETITEMOWNER — assigns or reassigns the owner (responsible party) of an item.
• SETITEMUSERKEY / GETITEMUSERKEY — set and retrieve the user-facing item key that correlates a runtime item with its business document.
• ITEM_EXIST — validates whether a given item already exists, supporting idempotent creation logic.
• ROOT_PROCESS — identifies the top-level process item associated with a given execution thread.
• ACTIVE_DATE — returns or evaluates the date on which an item became active, used for aging and escalation.
• ACQUIRE_LOCK — obtains a logical lock on an item to serialize concurrent engine modifications.
• ATTRIBUTE_ON_DEMAND — resolves an item attribute lazily, deferring retrieval until it is actually needed.
• SETENDDATE — records the completion or termination timestamp for an item.

Tables Accessed

The ETRM dependency listing records the following APPS synonyms: WF_ITEMS, WF_ITEM_ATTRIBUTES, WF_ITEM_ATTRIBUTE_VALUES, WF_ACTIVITY_ATTRIBUTES, and PLITBLM. WF_ITEMS is the master table that stores each item instance. WF_ITEM_ATTRIBUTES defines the attribute metadata for an item type, while WF_ITEM_ATTRIBUTE_VALUES holds the runtime attribute values consumed by ATTRIBUTE_ON_DEMAND. WF_ACTIVITY_ATTRIBUTES supplies activity-level attribute definitions that influence item state. PLITBLM is the standard PL/SQL table buffer utility used internally. The listed dependencies also include WF_ACTIVITY, WF_CACHE, WF_CORE, WF_ENGINE, and WF_ITEM, reflecting the package's tight integration with engine internals.

Usage Notes

WF_ITEM is an internal Workflow engine package and should not be invoked directly from forms or concurrent programs in typical customization. It is called by WF_ENGINE and the 32 dependent packages documented in ETRM, which orchestrate item creation and completion on behalf of user-facing events. Developers inspecting or extending Workflow should query WF_ITEMS and its companions rather than manipulating them directly, and should treat WF_ITEM procedures as engine API. Because the package is central to concurrency, any custom code that bypasses ACQUIRE_LOCK risks corrupting item state.