Search Results set_mandatory_wi_param_value

Overview

XNP_STANDARD is a PL/SQL package owned by the APPS schema in Oracle EBS Release 12.1.1 and 12.2.2, classified under ETRM as an "OTHER" API. It belongs to the Oracle Communications / Number Portability (XNP) product family, which supports Local Number Portability (LNP) and Service Order Administration (SOA) ordering flows. The package's primary business function is to act as the standard integration layer between workflow-driven order processes (originating from the Service Fulfillment Manager, SFM) and the underlying XNP core and SOA tables. It extracts order information from SFM work item parameters, validates order, service, and role status, publishes events, and orchestrates updates to Service Oriented Architecture (SOA) tables such as XNP_SV_SOA.

The package is declared with AUTHID CURRENT_USER, so it executes with the privileges of the calling user rather than the definer. The header carries the identifier $Header: XNPSTACS.pls 120.1 2005/06/24 04:46:11 appldev ship $, indicating an early-generation XNP object that has remained stable in the EBS stack. A global variable, FE_NAME, is maintained for the publish routine to pass the correct function/entity name to the push() method.

Key Procedures and Functions

• SMS_CREATE_PORTED_NUMBER — Creates an entry in the SMS table for each telephone number (TN) within a porting range. Extracts order information from SFM work item parameters and is invoked for Create Ported Number requests from the Numbering Resource Centre (NRC).
• SMS_DELETE_PORTED_NUMBER — Reads STARTING_NUMBER and ENDING_NUMBER from the SFM work item parameter table and delegates deletion to XNP_CORE.SMS_DELETE_PORTED_NUMBER.
• SOA_UPDATE_CHARGING_INFO — Updates the SV in the SOA table for each TN in a range with invoice information. Triggered when a recipient-requested port succeeds, using mandatory parameters such as STARTING_NUMBER, ENDING_NUMBER, and SP_NAME.
• SOA_UPDATE_CUTOFF_DATE — The procedure associated with the user's search term. It updates the SOA table with cutoff date information, forming part of the port/reconciliation timing logic.
• SOA_CREATE_PORTING_ORDER — Creates the SOA porting order record that underpins the port transaction.
• SOA_CHECK_NOTIFY_DIR_SVS — Validates whether notification is required for directory-published service values.
• DETERMINE_SP_ROLE — Resolves the role of the service provider in the port transaction.
• SOA_UPDATE_SV_STATUS — Updates the status of SOA service values as porting progresses.
• SOA_CHECK_ORDER_STATUS — Evaluates the current status of the order against expected states.
• CHECK_SOA_STATUS_EXISTS — Determines whether an SOA status row already exists before performing inserts or updates.
• SET_ORDER_RESULT — Records the result of an order-processing step.
• PUBLISH_EVENT — Publishes workflow or business events, using FE_NAME for the push call.
• SEND_MESSAGE — Dispatches notification messages associated with port events.
• SMS_DELETE_FE_MAP — Removes function/entity mapping entries from the SMS mapping structures.
• CHECK_PHASE_FOR_ROLE — Validates whether a given workflow phase is appropriate for a particular role.
• GET_WORKITEM_PARAM_VALUE / GET_MANDATORY_WI_PARAM_VALUE — Retrieve optional and mandatory work item parameter values respectively, raising an error when a mandatory value is absent.
• SET_WORKITEM_PARAM_VALUE / SET_MANDATORY_WI_PARAM_VALUE — Write or overwrite work item parameter values used by downstream processing.
• SUBSCRIBE_FOR_EVENT — Registers interest in a business event so that the package is notified when it fires.

Tables Accessed

The documented table reference is XNP_SV_SOA (accessed through an APPS synonym). This table holds SOA service-value and porting-order data. XNP_STANDARD reads from it to validate SOA status and order state, and writes to it when updating charging information, service value status, cutoff dates, and porting order records. The SMS porting functions also imply access to SMS ported-number storage, and the work item parameter routines operate against SFM work item parameter data.

Usage Notes

XNP_STANDARD is an internally invoked package, not a form-level user API. Its procedures are called from XNP workflow processes and from the generated code that drives SFM order processing, evidenced by comments stating "used by publish in the generated code" and "Called by: XNP_STANDARD.SMS_CREATE_PORTED_NUMBER." Because it is referenced by nine other packages, it functions as a shared service layer within the XNP suite. Customizations should avoid direct invocation without replicating the surrounding workflow context, and any direct calls to procedures such as SOA_UPDATE_CUTOFF_DATE should supply the appropriate work item instance and order identifiers.