Outbound Request

  • Release version: Australia
  • Updated June 16, 2026
  • 1 minute to read

    • Initiate outbound requests to manage service orders by interacting with external Service Order Management (SOM) to facilitate end-to-end order fulfillment. This process requires specific roles and is enabled via bi-directional REST API integration with Order Management for Sales and Service API Core.

    Overview of the Outbound Request table

    The Sales and Service Core API (com.sn_tmt_core) plugin is required to use the Outbound Request table (sn_tmt_core_outbound_request).

    As a provider, you can initiate an outbound request to manage service orders by interacting with external systems such as Service Order Management (SOM). This process supports the end-to-end order fulfillment life cycle, enabling seamless coordination between internal and external platforms.

    Fields on the Outbound Request Table

    Table 1. Field and descriptionsList of fields on the Outbound request table, their descriptions, and the type of fields.
    Field Description Type
    Request ID Outbound request ID that is generated by the Order Management for Telecommunications, Media, and Technology application. String
    State State of the outbound request. String (choices):
    • Not applicable: Created, but not in use yet
    • Fulfilled: The service order fulfillment is completed
    • Pending error: The service order has encountered an error and is waiting for a resolution
    • Failed: The record is discarded and not in use
    Table name Name of the table that is referenced in the source record. Table
    Number Unique number generated for each record.

    strict_read_only field

    		 String: auto generated
    Source record Reference field values from different tables. Document ID

    Security roles

    Table 2. Roles and access
    Role Access
    sn_tmt_core.outbound_request_write Create, read, update, delete, report_view, and report_on
    sn_tmt_core.outbound_request_read report_view, report_on, and read