Search Results exec_dynamic_create_msg

Overview

XNP_UTILS is the shared utility package body within the Oracle E-Business Suite Telecommunications Service Fulfillment (ETRM / XNP) application. It provides reusable PL/SQL services invoked across the service provisioning and fulfillment stack rather than implementing a single business transaction. Its primary responsibilities include translating inbound flat XML messages into structured order and line parameter collections, resolving fulfillment element (FE) metadata such as names and geographic information, formatting canonical date representations, writing diagnostic output, and dispatching acknowledgements and dynamically constructed messages to downstream SOA endpoints.

The package is classified as API classification OTHER, indicating it is an internal implementation utility rather than a formally published integration API. It carries no formal inbound API guarantee, and signature stability is not assured across patches or upgrades.

Within the 12.1.1 and 12.2.2 releases the package body retains the same general construction. Its header signature in the excerpted source (XNPUTILB.pls) reflects an older revision, so implementations deployed on later release levels should be validated against the shipped file version on the target instance.

Key Procedures and Functions

The package exposes 32 documented procedures and functions. Notable members include:

• MSG_TO_ORDER — Parses a flat XML work item message into structured LINE_PARAM_LIST and ORDER_LINE_LIST collections, populating line number, line item name, action, provisioning flag, and starting/ending number values. Raises an internal mandatory-data exception when required parameters are absent.
• EXEC_DYNAMIC_CREATE_MSG — The routine referenced in the user's search term. It executes a dynamically generated message creation request, allowing message content and dispatch parameters to be assembled at runtime rather than at compile time.
• SEND_ACK_MSG — Dispatches acknowledgement messages back through the fulfillment integration layer.
• GET_FE_NAME_FOR_SP, GET_FE_NAME, GET_ADAPTER_NAME — Resolve human-readable names for fulfillment elements, service providers, and adapters based on identifiers held in configuration tables.
• GET_DONOR_FE, GET_ORIG_DONOR_FE, GET_NRC_FE, GET_RECIPIENT_FE, GET_SENDER_FE — Return the fulfillment element associated with each role in a number-portability or transfer transaction: donor network, original donor network, number range carrier, recipient, and sender.
• GET_DONOR_NAME, GET_ORIG_DONOR_NAME, GET_NRC_NAME, GET_RECIPIENT_NAME, GET_SENDER_NAME — Companion lookups returning the descriptive names of the same roles.
• GET_GEO_INFO — Retrieves geographic area details used in routing and number-range validation.
• LOG_MSG — Persists diagnostic or transaction-level messages, typically writing to the XNP debug infrastructure.
• CANONICAL_TO_DATE, DATE_TO_CANONICAL — Convert between canonical string date representations and native DATE values used in message payloads.

Tables Accessed

The package reads and writes configuration, work item, geographic, and diagnostic tables through APPS synonyms:

• XDP_WORKITEMS, XDP_WI_PARAMETERS — Define work items and their required parameters; queried by MSG_TO_ORDER to determine mandatory data.
• XDP_FES, XDP_FE_GENERIC_CONFIG, XDP_FULFILL_WORKLIST — Fulfillment element definitions, generic configuration values, and active worklist entries supporting the FE name and role lookups.
• XNP_SP_ADAPTERS, XDP_ADAPTER_REG, XDP_ADAPTER_TYPES_B — Adapter registration and type metadata used by GET_ADAPTER_NAME and dynamic message dispatch.
• XNP_GEO_AREAS_B — Geographic area definitions backing GET_GEO_INFO.
• XNP_NUMBER_RANGES — Number range definitions referenced during message processing.
• XNP_CALLBACK_EVENTS, XNP_SV_SOA — Callback registration and service-oriented endpoint configuration supporting acknowledgement and outbound messaging.
• XNP_DEBUG, XNP_DEBUG_S — Debug and logging tables written by LOG_MSG.
• DBMS_AQ — Oracle Advanced Queuing is referenced for enqueue or dequeue operations associated with asynchronous message flow.

Usage Notes

XNP_UTILS is not typically invoked directly by end users. It is consumed by other PL/SQL packages in the ETRM schema — the metadata records nine dependent packages — and executes in the context of concurrent programs, fulfillment workflows, and message-driven integration processes. Because EXEC_DYNAMIC_CREATE_MSG performs dynamic SQL execution, callers should ensure only trusted, internally generated message definitions are passed to it; input validation and privilege control rest with the invoking program unit. The package depends on the APPS schema and on NLS settings, as evidenced by its use of FND_GLOBAL and USERENV for line-terminator normalization. Customizations should avoid modifying the shipped package body and instead extend behavior through wrapper packages or the supported ETRM configuration interfaces.