Search Results exec_wi_workflow

Overview

XDP_PROCEDURE_BUILDER is a dynamic PL/SQL code generation package within the Oracle EBS Application Object Library / E-Business Suite provisioning infrastructure (XDP schema). It serves as the runtime engine that constructs, compiles, and manages PL/SQL procedure and package source code used by Oracle's provisioning and workflow automation framework. The package operates with AUTHID CURRENT_USER privileges, meaning generated code executes under the privileges of the invoking user rather than the package owner — a deliberate design choice that allows provisioned procedure bodies to respect the calling session's security context.

The package is intrinsically tied to the provisioning macro language used for automated configuration of Oracle applications. Constants declared in the package specification define the vocabulary of this macro system, including RESPONSE_CONTAINS (g_MacroResponseContains), SEND, SEND_HTTP, LOGIN, GET_RESPONSE, GET_PARAM_VALUE, NOTIFY_ERROR, AUDIT, and GET_LONG_RESPONSE. These macros, together with type identifiers such as DYNAMIC_WI_MAPPING, DYNAMIC_FA_MAPPING, EXEC_WI_WORKFLOW, and the various parameter evaluation procedure types, are assembled by this package into executable PL/SQL units at runtime. The g_MacroResponseContains constant corresponds to the RESPONSE_CONTAINS directive, which tests provisioned device or service responses against expected patterns during automated installation and configuration workflows.

Key Procedures and Functions

The documented procedure set (14 total) centers on programmatic assembly of PL/SQL source text:

• GENERATEPACKAGENAME — Derives a valid package identifier from the provisioning definition context.
• DECODEPROCNAME — Resolves an encoded procedure name back to its logical form, supporting naming conventions used in generated artifacts.
• GENERATEPROCSPEC / GENERATEPROCDEFBODY / GENERATEPROCHEADER / GENERATEPROCFOOTER / GENERATEPROCBODY — Produce the individual components of a standalone PL/SQL procedure: its specification, definition body, header, footer, and main executable body. These are composed in sequence to emit syntactically complete procedure text.
• GENERATEPACKAGESPEC / GENERATEPACKAGEBODY / GENERATEPACKAGEHEADER / GENERATEPACKAGEFOOTER — The analogous package-level generators, assembling package specifications and bodies from stored fragments.
• PRECOMPILEPROCEDURE — Performs validation or pre-compilation checks on generated procedure source before it is persisted or executed.

No parameter lists are documented in the ETRM metadata; only procedure purposes are enumerated. The package is referenced by three other packages in the ETRM object graph, confirming its role as a shared code-generation utility within the provisioning stack.

Tables Accessed

The only documented table accessed via APPS synonyms is XDP_PROC_BODY. This table stores the body text of provisioned procedures, and XDP_PROCEDURE_BUILDER both reads existing fragments and writes newly generated or precompiled procedure bodies to it. The package's global specification variables (g_SvcWIMapSpec, g_FAParamEvalSpec, g_LocateFESpec, g_ConnectSpec, and related *Comments and *DefBody declarations, each varchar2(2000)) serve as in-memory staging buffers for the code fragments that are ultimately persisted to XDP_PROC_BODY.

Usage Notes

XDP_PROCEDURE_BUILDER is not typically invoked by end users directly. It is called programmatically by the provisioning framework during setup of automated installation workflows — for example, when Oracle Applications Manager or the Rapid Install / AutoConfig provisioning engines process a provisioning definition containing macros such as RESPONSE_CONTAINS or SEND_HTTP. Custom integrators extending the provisioning macro language may invoke the generator routines to compile bespoke procedure bodies into XDP_PROC_BODY. Because the package declares AUTHID CURRENT_USER, callers must have appropriate object privileges on referenced tables and any dynamically compiled units. The presence of the 11.5.6-era header comment and the subset of macros flagged "New for 11.5.6++" indicates the package has remained stable across the 12.1.1 and 12.2.2 releases, with the RESPONSE_CONTAINS macro available throughout. Any modification or recompilation should be performed with the APPS schema credentials, and generated source should be reviewed before compilation since the package emits executable code dynamically.