Integrating Order Management with southbound external systems

  • Release version: Zurich
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Integrating Order Management with southbound external systems

    ServiceNow’s Order Management application, available with a Telecommunications Service Management subscription, enables Communications Service Providers (CSPs) to integrate with external southbound systems that handle the fulfillment lifecycle of service orders. This integration supports network activation, configuration, and resource management by submitting outbound service order requests and managing responses and exceptions.

    Show full answer Show less

    Key Features

    • Outbound requests can be triggered for one or more domain service orders using the TMF 641 Open POST order API.
    • Updates about inflight changes to existing domain service orders are shared with external systems to maintain synchronization.
    • Inbound responses to outbound requests are managed, including error and exception handling.
    • Integration supports hierarchical and non-hierarchical domain orders, ensuring appropriate routing of child or individual domain orders to external systems.
    • Use of UI actions such as “Create fulfillment request” and “Create Outbound Fulfillment Request” allows administrators and service order managers to initiate outbound communication with external systems.
    • Service Order Open API activation is required to capture customer service orders, forming the basis for outbound integration.
    • Integration endpoints are configurable via Workflow Studio flow integrations, allowing flexible connection to external fulfillment systems.

    How the Integration Works

    • Administrators activate the TMF641 Service Order Open API to enable capturing of customer orders.
    • Order fulfillment managers initiate fulfillment requests through UI actions on the domain order table.
    • A policy decision table evaluates domain order attributes to generate the appropriate payload for the external system.
    • The payload is sent to the configured external endpoint, with hierarchical orders sending all child orders accordingly.
    • Service order managers can create outbound fulfillment requests directly from the service order form when no prior successful request exists or an error state is present.
    • Outbound responses from external systems are recorded in the Outbound Request table, enabling tracking and management of order fulfillment status.

    Practical Benefits for ServiceNow Customers

    This integration enables CSPs to automate and streamline the communication between ServiceNow’s Order Management and external systems responsible for technical order fulfillment. It reduces manual intervention, improves order processing accuracy, and provides visibility into order status and exceptions, thereby enhancing operational efficiency and customer satisfaction.

    If you have a Telecommunications Service Management subscription, you can submit outbound service order requests to various external systems by integrating the Order Management application with the external southbound systems.

    After the decomposition of an order, the Order Management application requires support from external systems. These systems manage the fulfillment life cycle of the order. They include network activation, network configuration, and resource management.

    Using this integration, a Communications Service Provider (CSP) can do the following tasks:
    • Trigger outbound requests for one or more domain service orders by using the TeleManagement Forum (TMF) 641 Open POST order API.
    • Share updates with the external systems about the inflight changes to the existing domain service orders that have outbound requests.
    • Manage the inbound response of the outbound requests for the domain service orders.
    • Manage the errors and exceptions for the outbound requests and inbound responses.

    How the integration works

    The integration process for Order Management with the external technical order management systems is as follows:
    1. As the administrator, you activate the Service Order Open API to capture the service order from the customer orders. To learn more, see TMF641 Service Order Open API- POST.
    2. The integration now begins:
      1. The order fulfillment manager selects the Create fulfillment request UI action in the domain order table.
      2. The Service Order Outbound Policy decision table checks the domain order attributes, and the order management system generates the payload for the domain service order.
      3. The generated payload is sent to the endpoint of the external fulfillment system. For more information on configuring external system endpoints by creating an integration request, see Workflow Studio flow integrations.
      Note:
      • If the domain order is configured as hierarchical, all child service domain orders are sent to the external system configured in the application spoke selector.
      • If the domain order is configured as non-hierarchical, only individual domain orders are sent to the external system configured in the application spoke selector.

      To learn more about spokes, see Building spokes using Spoke Generator.

    3. The service order manager selects the Create Outbound Fulfillment Request UI action on the service order form and the system shares the service order details with the external systems.
      Note:
      The UI action appears if any of the following conditions is met by the system:
      • No successful outbound request exists for the service domain order yet.
      • An outbound request exists but the current external fulfillment state of the service domain order is an error.
    4. If the fulfillment request is successful, a response is received from the external system and is captured in the Outbound Request table (sn_tmt_core_outbound_request). To learn more, see Create outbound requests for service orders.