Search Results xnp_standard




Overview

XNP_STANDARD is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Communications / Telecommunications service fulfillment stack (the XNP family of packages). It is a foundational utility package within the number portability and service-order orchestration layer, acting as a shared library that other XNP packages call upon for messaging, event publication, work-item parameter handling, and SOA integration.

The package is documented with an API classification of OTHER, meaning it is a supporting internal library rather than a published, developer-facing API. It is validated in both 12.1.1 and 12.2.2 and is referenced by nine other database objects, which confirms its role as a central dependency rather than an entry point invoked directly by forms or concurrent programs. It is not itself referenced by any database object, indicating it sits at or near the top of its dependency chain.

Key Procedures and Functions

The ETRM metadata documents 31 procedures and functions in this package body. The following are named explicitly:

No parameter signatures are published in the ETRM record; callers should treat the argument lists as internal and always invoke through the documented wrapper APIs of the higher-level XNP packages.

Tables Accessed

Only one table is documented as referenced through APPS synonyms: XNP_SV_SOA. This table stores service-order and SOA integration state, and the SOA_* procedures listed above use it to persist and verify charging information, cutoff dates, porting orders, service-order status, and notification state. All other data access is delegated to the dependent packages.

Usage Notes

XNP_STANDARD is invoked indirectly. It depends on XDP_ADAPTER_CORE_DB, XDP_ENGINE, XNP_CORE, XNP_ERRORS, XNP_EVENT, XNP_MESSAGE, XNP_TIMER_STANDARD, XNP_UTILS, XNP_SV_SOA, FND_MESSAGE, and STANDARD. Customizations should never modify the APPS copy of this package body. Instead, extend behavior by wrapping the higher-level XNP packages, or by calling XNP_STANDARD procedures from custom code only after confirming the signature at runtime, since ETRM does not publish the parameter lists.