Integrating Order Management with southbound external systems

  • Release version: Australia
  • 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

    This integration allows ServiceNow Order Management to submit outbound service order requests to external southbound systems, enabling automated fulfillment across a Communications Service Provider's (CSP) ecosystem. After an order is decomposed, external systems such as network activation, configuration, and resource management handle the fulfillment lifecycle. This ensures seamless coordination between Order Management and technical order fulfillment systems.

    Show full answer Show less

    Key Features

    • Trigger outbound requests for domain service orders using the TMF 641 Open POST order API.
    • Share updates about inflight changes to existing domain service orders with external systems.
    • Manage inbound responses from external systems for outbound requests.
    • Handle errors and exceptions related to outbound requests and inbound responses.
    • Support both hierarchical and non-hierarchical domain orders for outbound communication.

    How the Integration Works

    Administrators activate the Service Order Open API to capture customer service orders. Then, the order fulfillment manager initiates the process by selecting the Create fulfillment request UI action on the domain order table. A policy decision table evaluates domain order attributes and generates a payload that is sent to the configured external system endpoint.

    For hierarchical domain orders, all child service domain orders are sent to the external system configured via the application spoke selector; for non-hierarchical orders, only individual domain orders are sent.

    The service order manager can also select the Create Outbound Fulfillment Request UI action on the service order form to share the service order details with external systems. This UI action appears if no successful outbound request exists or if the current external fulfillment state is an error.

    Successful responses from external systems are captured in the Outbound Request table (sntmtcoreoutboundrequest), allowing tracking and management of fulfillment status.

    Practical Benefits for ServiceNow Customers

    • Automate coordination between Order Management and external fulfillment systems, reducing manual steps.
    • Improve accuracy and timeliness of order fulfillment updates across your service provider ecosystem.
    • Gain visibility into outbound requests and inbound responses including error handling.
    • Leverage TMF 641 Open API standards for interoperability with technical order management systems.
    • Configure flexible workflows for both hierarchical and individual domain orders according to your business needs.

    Submit outbound service order requests to external systems by integrating Order Management with southbound systems. This integration enables automated order fulfillment across your service provider ecosystem.

    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.