Search Results set_ord

Overview

XNP_WF_STANDARD is a PL/SQL package body owned by APPS within the Oracle E-Business Suite, classified under the OTHER API category. It supports workflow-driven and Service Oriented Architecture (SOA) integration for Oracle's telecommunications and number-portability provisioning modules. The package header comment defines its principal role: it copies item attributes defined in a workflow to the equivalent workitem parameters recorded in XDP_WORKLIST_DETAILS. Beyond this workflow-synchronisation capability, the package contains a broad set of telecommunications provisioning routines covering SMS number portability, NES provisioning, cutoff-date management, and event publication. The documented procedures and functions number 58, of which the metadata names 21 explicitly. First shipped code carries a header revision of 120.0 dated 2005, indicating the package has been maintained across EBS releases, and it is referenced by one other package, confirming that XNP_WF_STANDARD functions as a shared service within the XNP and SOA integration stack.

Key Procedures and Functions

The workflow utilities form the heritage core of the package. SET_SDP_CONTEXT is invoked at itemtype initiation and populates the package globals g_ORDER_ID and g_WORKITEM_INSTANCE_ID using wf_engine.GetItemAttrNumber. It responds to the SET_CTX, SET_ORD, and SET_WI command modes, allowing partial or full context population. DOWNLOADWIPARAMS and DOWNLOADFAPARAMS move workflow item attributes into worklist detail parameters, while UPLOADFAPARAMS performs the reverse propagation back into workflow attributes. PREPARE_NOTIFICATION, PUBLISH_EVENT, SUBSCRIBE_FOR_EVENT, and SUBSCRIBE_FOR_ACKS manage Business Event System messaging and acknowledgement handling.

The telecommunications routines address mobile number portability and network element provisioning. SMS_CREATE_PORTED_NUMBER and SMS_DELETE_PORTED_NUMBER maintain ported-number records; SMS_PROVISION_NES and SMS_DEPROVISION_NES are the routines most relevant to the search term sms_provision_nes, handling activation and deactivation of numbers in network element systems. The SOA-facing procedures include SOA_CREATE_PORTING_ORDER, SOA_UPDATE_CUTOFF_DATE, SOA_UPDATE_SV_STATUS, SOA_UPDATE_CHARGING_INFO, SOA_CHECK_ORDER_STATUS, SOA_CHECK_NOTIFY_DIR_SVS, and CHECK_SOA_STATUS_EXISTS, which together orchestrate provisioning state between EBS and external SOA middleware. Execution helpers EXECUTE_FA and EXECUTE_FA_N_SYNC_WI_PAR drive fulfillment activities while synchronising workitem parameters.

Tables Accessed

The package reads and writes several tables through APPS synonyms. XDP_FA_DETAILS stores fulfillment activity definitions and parameters consumed by the FA execution routines. XDP_WORKLIST_DETAILS holds the workitem parameters that DOWNLOADWIPARAMS and related procedures synchronise with workflow attributes. XNP_SERVED_NUM_RANGES defines telephone number ranges, and XNP_SV_SMS maintains SMS service records; both support the porting and provisioning operations. XNP_SV_SMS_FE_MAPS maps SMS services to front-end network elements, underpinning the NES provisioning and deprovisioning logic.

Usage Notes

XNP_WF_STANDARD is invoked primarily from Oracle Workflow process definitions rather than directly by end users. The SET_SDP_CONTEXT function is registered as a workflow function activity, receiving RUN, SET_CTX, SET_ORD, and SET_WI commands during itemtype execution. The SOA and SMS procedures are normally called by concurrent programs, Business Event subscriptions, or inbound web-service handlers that process porting orders and provisioning requests. The presence of PUBLISH_EVENT and the subscription routines indicates integration with the Business Event System, allowing external systems to react to provisioning milestones. Because the package exposes public procedures in a shared APPS schema, custom code should call only the documented entry points and should not manipulate the package globals directly. Customers upgrading between 12.1.1 and 12.2.2 should note that the SMS and SOA procedures reflecting number portability were added after the original workflow utility set, and any seed data or workflow definitions referencing them must be verified during patching.