---
title: Outbound Request
description: 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.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/order-management/outbound-request-configuration-table.html
release: australia
topic_type: concept
last_updated: "2026-10-09"
reading_time_minutes: 1
breadcrumb: [Sales and Service API Core, Lead-to-cash foundation apps, Configure, Sales Customer Relationship Management]
---

# Outbound Request

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 id="table_f3d_3tv_1fc"><thead><tr><th>

Field

</th><th>

Description

</th><th>

Type

</th></tr></thead><tbody><tr><td>

Request ID

</td><td>

Outbound request ID that is generated by the Order Management for Telecommunications, Media, and Technology application.

</td><td>

String

</td></tr><tr><td>

State

</td><td>

State of the outbound request.

</td><td>

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

</td></tr><tr><td>

Table name

</td><td>

Name of the table that is referenced in the source record.

</td><td>

Table

</td></tr><tr><td>

Number

</td><td>

Unique number generated for each record.strict\_read\_only field

</td><td>

String: auto generated

</td></tr><tr><td>

Source record

</td><td>

Reference field values from different tables.

</td><td>

Document ID

</td></tr></tbody>
</table>## Security roles

|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|

**Related topics**  


[Using lead-to-cash foundation applications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/using-lead-cash-foundation.md)

[Lead-to-cash foundation reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/reference-lead-cash-foundation.md)