Search Results add_line_param

Overview

XDP_ENGINE is the runtime engine package for Oracle E-Business Suite's fulfillment and order-processing framework, delivered under the APPS schema as an AUTHID CURRENT_USER package. It provides the programmatic core that activates, evaluates, and retrieves fulfillment parameters at runtime, spanning order header, order line, fulfillment action, and work item contexts. The package maintains the session-level pv_FeAttributeList (typed as XDP_TYPES.ORDER_PARAMETER_LIST) and defines the standard evaluation-mode constants that govern when a fulfillment element's configuration is resolved: ON_ORDER_RECEIPT, ON_PROCESS_ORDER, and ON_WORKITEM_START. Its API classification is OTHER, reflecting its role as an internal infrastructure layer rather than a public business API, though it is referenced by 21 other database packages across the fulfillment stack.

Key Procedures and Functions

The 47 documented subprograms fall into distinct parameter-scope families. The work item family includes GET_WORKITEM_PARAM_VALUE, GET_WORKITEM_PARAM_REF_VALUE, GET_WORKITEM_PARAM_LIST, SET_WORKITEM_PARAM_VALUE, GET_WORKITEM_PROV_DATE, and SET_WORKITEM_PROV_DATE. The documented behavior of GET_WORKITEM_PARAM_VALUE is notable: the fulfillment engine's $WI.<parameter_name> macro invokes this function to perform runtime value substitution, taking a work item instance ID and a parameter name and returning the value as VARCHAR2.

A parallel family covers fulfillment action (FA) parameters: GET_FA_PARAM_VALUE, GET_FA_PARAM_REF_VALUE, GET_FA_PARAM, GET_FA_PARAM_LIST, and SET_FA_PARAM_VALUE. Order- and line-level access is provided by GET_ORDER_PARAM_VALUE, GET_ORDER_PARAM_LIST, SET_ORDER_PARAM_VALUE, GET_LINE_PARAM_VALUE, GET_LINE_PARAM_REF_VALUE, ADD_LINE_PARAM, and SET_LINE_PARAM_VALUE. The package also exposes configuration-introspection functions such as GET_FE_CONFIGINFO and GET_FE_ATTRIBUTEVAL, which resolve fulfillment element configuration metadata and attribute values at runtime. The PARAMETER_REC record type — carrying PARAMETER_NAME, IS_VALUE_EVALUATED_FLAG, PARAMETER_VALUE, and PARAMETER_REFERENCE_VALUE — is the common data structure behind the list-returning APIs. The reference-value variants distinguish static configuration values from those resolved dynamically at evaluation time.

Tables Accessed

The package operates against a broad set of XDP foundation tables accessed through APPS synonyms. Work item and fulfillment action processing draws on XDP_FULFILL_ACTIONS, XDP_FULFILL_WORKLIST, XDP_FA_DETAILS, XDP_FA_PARAMETERS, and XDP_FA_RUNTIME_LIST. Order context is supplied by XDP_ORDER_HEADERS, XDP_ORDER_LINE_ITEMS, and XDP_ORDER_LINEITEM_DETS. Fulfillment element configuration is read from XDP_FES, XDP_FE_TYPES, XDP_FE_ATTRIBUTE_DEF, XDP_FE_ATTRIBUTE_VAL, XDP_FE_GENERIC_CONFIG, and XDP_FE_SW_GEN_LOOKUP. Audit information is captured in XDP_FE_CMD_AUD_TRAILS, supporting traceability of command execution against fulfillment elements.

Usage Notes

XDP_ENGINE is invoked indirectly rather than from end-user forms. The fulfillment engine calls it during order processing and work item execution to evaluate parameters and resolve macro substitutions, and the 21 dependent packages indicate it sits beneath higher-level fulfillment and order-management APIs. Custom code should treat it as a read-mostly runtime service: the GET-family and configuration functions are safe for retrieval within fulfillment extension logic, while SET/ADD operations modify runtime parameter state and should be used only where the calling process owns that state. Because the package relies on APPS synonyms and is compiled AUTHID CURRENT_USER, callers must have appropriate execute privileges on XDP_ENGINE and select privileges on the underlying XDP tables.