Search Results deprovision_fe




Overview

XNP_FA_CB is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the number-range provisioning lifecycle for communications service providers. It functions as the callback handler for the FA (Fulfillment Automation) subsystem, reconciling requests issued by the provisioning engine against the asynchronous responses returned by downstream network elements. In practice, the package translates an incoming FA_DONE message into the appropriate state transition on the feature-element (FE) mapping records held in the service management tables.

The package is declared with AUTHID CURRENT_USER, so all unqualified object references resolve against the invoking schema's privileges rather than the package owner's. Its source revision ($Header: XNPFACBS.pls 120.2, dated 2006/02/13) identifies it as a comparatively stable component that has not required structural change across the 12.1.1 and 12.2.2 releases. The six documented parameters common to its main procedures — starting number, ending number, FE ID, feature type, provisioning status, order ID, line item ID, work item instance ID, and FA instance ID — confirm that each call operates on a discrete number range within the context of a specific sales order line and workflow instance.

Key Procedures and Functions

  • PROCESS_FA_DONE — The primary entry point for callback processing. It accepts a message identifier and process reference, determines the FE_ID and feature type to which the provisioning system has responded, derives the correct provisioning operation, retrieves the relevant number range, and dispatches to the appropriate subordinate routine. It returns a standard error code and error message pair to the caller.
  • PROVISION_FE — This is the routine referenced by the search term "provision_fe". It updates the FE mapping records in XNP_SV_SMS_FE_MAPS to the provisioning status returned in the FA callback event, thereby recording the successful activation or provisioning of a feature element across the specified number range. It receives the full set of range, order, work item, and FA instance identifiers plus the outbound error pair.
  • DEPROVISION_FE — Performs the inverse operation. It deletes the FE map records associated with the supplied number range and feature type, and when all FE maps for the range have been removed, the corresponding SMS entries are also deleted so that no orphaned service management records remain.
  • MODIFY_FE — Updates the FE map status to reflect a provisioning status returned by the FA callback, specifically resolving to either SUCCESS or ERROR. This procedure is used when the callback represents a change to an existing provisioned state rather than a first-time activation.

Tables Accessed

Two tables are documented through APPS synonyms. XDP_FA_RUNTIME_LIST is the runtime work list from which pending fulfillment automation items are read and against which message identifiers and process references are validated. XDP_FULFILL_WORKLIST holds the fulfillment work items that drive the provisioning flow and are updated as callbacks are consumed. The FE mapping table XNP_SV_SMS_FE_MAPS, although named in the package comments rather than in the table list, is the principal target of the PROVISION_FE, MODIFY_FE, and DEPROVISION_FE status and delete operations.

Usage Notes

XNP_FA_CB is not intended for direct invocation by end users. It is typically called from the fulfillment automation callback infrastructure, invoked when an FA_DONE message is received from the provisioning layer, or from concurrent programs and workflow background processes that poll the runtime list for completed callbacks. Custom code integrating with the provisioning engine should call PROCESS_FA_DONE as the single entry point and rely on it to select the correct operation, rather than calling PROVISION_FE, DEPROVISION_FE, or MODIFY_FE directly. Because the package references no other packages and is referenced by none, it forms a self-contained callback utility whose behavior is governed entirely by the status values supplied in the inbound message.