---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Outbound Request

# Outbound Request {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 30. Juni 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

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 {#outbound-request-configuration-table__section_o15_xrv_1fc}

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 {#outbound-request-configuration-table__section_i2h_ktv_1fc}

{#outbound-request-configuration-table__table_f3d_3tv_1fc__entry__3}

| 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 {#outbound-request-configuration-table__ul_s5w_knr_wgc} |
| 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 |
[Tabelle : 1. Field and descriptionsList of fields on the Outbound request table, their descriptions, and the type of fields.]

{#outbound-request-configuration-table__table_f3d_3tv_1fc}

## Security roles {#outbound-request-configuration-table__section_tzz_bwv_1fc}

{#outbound-request-configuration-table__table_mhz_2wv_1fc__entry__2}

| 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 |
[Tabelle : 2. Roles and access]

{#outbound-request-configuration-table__table_mhz_2wv_1fc}