Search Results order_parameter

Overview

XDP_TYPES is a PL/SQL specification package owned by APPS in Oracle E-Business Suite, delivered as part of the Service Fulfillment Manager (SFM) and telecommunications provisioning modules. Unlike conventional PL/SQL packages that expose executable procedures and functions, XDP_TYPES is a pure datatype definition package: it declares no procedures or functions of its own. Its sole business purpose is to establish a shared, canonical set of PL/SQL record and collection structures that describe service orders, order headers, order parameters, and order line items. These structures are consumed by the broader XDP (Service Fulfillment Manager) API family so that order data can be passed between packages, forms, and integration layers in a consistent, strongly typed manner.

Key Procedures and Functions

The package declares no documented procedures or functions. Its API surface consists exclusively of type definitions. The principal public datatypes are:

• ORDER_HEADER — a record describing an SFM order header, including order_number, order_version, provisioning_date, priority, due_date, customer_required_date, order_type, order_action, order_source, related_order_id, org_id, customer details, service_provider_id, order_status, order_state, actual_provisioning_date, completion_date, previous/next_order_id, sdp_order_id, jeopardy_enabled_flag, order reference name/value, and sp_order_number.
• ORDER_HEADER_LIST — a BINARY_INTEGER-indexed table of ORDER_HEADER records, used to pass collections of order headers.
• ORDER_PARAMETER — a record holding PARAMETER_NAME and PARAMETER_VALUE (up to 4000 characters).
• ORDER_PARAMETER_LIST — a BINARY_INTEGER-indexed table of ORDER_PARAMETER records. This is the element referenced by the caller search term service_order_param_list, which corresponds to the order parameter list construct used to pass name/value pairs into service order processing APIs.
• LINE_ITEM — a record describing an order line, with LINE_NUMBER, LINE_ITEM_NAME, VERSION, IS_WORKITEM_FLAG, ACTION, and PROVISIONING_DATE.

Tables Accessed

The ETRM metadata documents no referenced tables for XDP_TYPES. This is consistent with its role: because the package contains only type declarations, it performs no SQL of its own and neither reads nor writes any application tables. All table access occurs in the packages that consume these types. Any table interaction attributed to order processing is performed by those consumer packages, which pass ORDER_HEADER, ORDER_PARAMETER_LIST, and LINE_ITEM structures to and from the database.

Usage Notes

XDP_TYPES is a foundational dependency rather than an invoked program. It is referenced by 33 other packages in the APPS schema, indicating it is a core building block of the XDP service-order API set. Custom developers should reference XDP_TYPES in the same way Oracle's own packages do: declare local variables of type XDP_TYPES.ORDER_HEADER, XDP_TYPES.ORDER_HEADER_LIST, XDP_TYPES.ORDER_PARAMETER_LIST, or XDP_TYPES.LINE_ITEM, populate them, and pass them to the relevant service-order APIs (for example, order submission and provisioning routines). The package is compiled with AUTHID CURRENT_USER and is unlikely to require ATG grants for direct invocation since it exposes no callable code. Because the header record includes defaults such as provisioning_date DEFAULT SYSDATE, priority DEFAULT 100, and jeopardy_enabled_flag DEFAULT 'N', callers inherit sensible defaults when fields are left unset. When searching for service_order_param_list, note that this functionality is realized through the ORDER_PARAMETER_LIST type, which functions as the service order parameter list for passing name/value pairs into the provisioning APIs. The specific parameter list signature used by any given API should be confirmed against the documentation for the consuming package, since XDP_TYPES itself defines only the type and not the procedure parameters.