Search Results set_conc_error




Overview
Explore in AI Chat

Overview

The APPS.ZPB_WF_ERROR package is a workflow error-handling utility that belongs to the Oracle Enterprise Business Suite Advanced Planning and Demand Planning product family, specifically the module associated with the ZPB schema prefix. In Oracle EBS 12.1.1 and 12.2.2, this package provides the standardized mechanism through which Oracle Workflow activities related to analysis cycles and analysis cycle tasks signal failure back to the Workflow engine. Rather than embedding error-reporting logic directly inside each business activity, the analysis cycle workflow definitions invoke the two procedures in this package as the terminal (error) branch of their process diagrams. The package translates a runtime or concurrent-program failure into the function-activity result expected by Oracle Workflow, thereby allowing the process to transition cleanly to a notification or completion activity instead of stalling in an error state.

Key Procedures and Functions

Two documented procedures are exposed in the package specification:

  • SET_ERROR — serves as the standard Workflow function activity handler for the analysis cycle processes. It accepts the Workflow item type, item key, activity identifier, and function mode inputs, and returns a result value through the resultout OUT parameter. Its purpose is to record or derive the error condition associated with the running workflow item and to communicate the appropriate result code back to the Workflow engine so the process can branch accordingly.
  • SET_CONC_ERROR — performs the analogous role for error conditions originating from concurrent program execution. It carries the same five-parameter signature, including the resultout NOCOPY OUT parameter, but is tailored to the concurrent-request error context, allowing the workflow to surface a concurrent manager failure as a meaningful workflow outcome.

Both procedures share the identical parameter shape, which permits the analysis cycle workflow definitions to substitute one for the other depending on the source of the failure.

Tables Accessed

The package operates against several documented objects, accessed through APPS synonyms:

  • FND_CONCURRENT_REQUESTS — read to determine the status and outcome of a concurrent request when SET_CONC_ERROR is invoked, providing the basis for the error result returned to Workflow.
  • ZPB_ANALYSIS_CYCLES, ZPB_ANALYSIS_CYCLE_INSTANCES, and ZPB_ANALYSIS_CYCLE_TASKS — the core planning entities. The package updates or inspects these records so that the persisted cycle, instance, and task state reflect the workflow-level error condition.
  • DBMS_LOCK — the Oracle-supplied locking package, used to serialize access to the analysis cycle records during error processing and prevent concurrent workflow activities from corrupting shared state.

Usage Notes

ZPB_WF_ERROR is not intended for direct invocation by end users or ordinary custom code. It is referenced as a Workflow function activity within the analysis cycle item type definitions, meaning Oracle Workflow invokes SET_ERROR or SET_CONC_ERROR automatically when a process reaches its error branch. In practice, the procedures are triggered when an analysis cycle task or its associated concurrent program fails, allowing the process to record the failure and notify the appropriate planner. The package is documented as referenced by zero other packages, confirming its role as a leaf-level integration point invoked by the Workflow engine rather than by other PL/SQL units. Developers troubleshooting stuck or failed analysis cycle workflows can inspect the parameters passed at invocation — item type, item key, activity ID, and function mode — to trace the workflow instance in the Workflow monitor and correlate it to the concurrent request that raised the error.