Search Results xnp_wf_standard




Overview
Explore in AI Chat

Overview

The APPS.XNP_WF_STANDARD package is a PL/SQL package that resides in the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Communications / service fulfillment domain associated with the XNP application family, which governs number porting, service provisioning, and workflow-driven event handling. The package is documented with a status of VALID and is classified under the API classification category OTHER, indicating it is primarily an internal orchestration and utility layer rather than a public open interface.

Its central business role is to bridge workflow events with downstream service activation, SOA (Service-Oriented Architecture) integration, and notification logic. The name WF_STANDARD reflects its function as the standard workflow support package, exposing routines that prepare notifications, publish events, invoke workflow activities, and synchronize parameters with external worklist and fulfillment systems. It also encapsulates SMS provisioning and porting operations tied to the number portability lifecycle.

Key Procedures and Functions

The package exposes 58 documented procedures and functions. The principal categories are summarized below. Parameter lists are intentionally not reproduced; only purpose is described.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

  • XDP_FA_DETAILS — stores fulfillment activity detail records consumed and updated during workflow activity execution.
  • XDP_WORKLIST_DETAILS — holds worklist item attributes exchanged using the download/upload parameter routines.
  • XNP_SERVED_NUM_RANGES — defines served number ranges referenced when creating or deleting ported numbers.
  • XNP_SV_SMS — holds SMS service records for provisioned and deprovisioned numbers.
  • XNP_SV_SMS_FE_MAPS — maps SMS services to front-end network elements used during provisioning.

Usage Notes

XNP_WF_STANDARD is referenced by just one other package, APPS.XNP_EVENT, which indicates it operates as a supporting library invoked from the event-handling layer rather than being called directly by forms. In practice it is triggered as part of Oracle Workflow process execution (fulfillment activity function calls) and during SOA-based integration flows for number portability and service activation. Custom extensions should call SET_SDP_CONTEXT before invoking any dependent routine and must treat the package as an internal API, since it is not published as an open interface. Direct DML against the underlying XNP/XDP tables should be avoided in favour of these documented entry points.