---
title: Outbound message configuration fields
description: The add new outbound message configuration record in Zero Copy Connector for ERP \(Enterprise Resource Planning\) contains information that defines IDoc outbound messages.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/erp-integration-framework/erp-canvas-add-new-outbound-message-configuration-fields.html
release: australia
product: ERP Integration Framework
classification: erp-integration-framework
topic_type: reference
last_updated: "2026-08-06"
reading_time_minutes: 1
keywords: [erp, canvas, erp canvas, integration, data hub, zero, copy, connector, sap, erp data, connect, outbound, message]
breadcrumb: [Field descriptions, Reference, Zero Copy Connector for ERP, Workflow Data Fabric]
---

# Outbound message configuration fields

The add new outbound message configuration record in Zero Copy Connector for ERP \(Enterprise Resource Planning\) contains information that defines IDoc outbound messages.

For process details, see [Create an IDoc outbound message configuration in Zero Copy Connector for ERP](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/erp-integration-framework/create-an-idoc-outbound-message-configuration.md).

<table id="table_xxc_pk4_bhc"><thead><tr><th>

Field

</th><th>

Description

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

Name

</td><td>

Unique name for the new outbound message configuration.

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

Operation

</td><td>

The action, function, or process used to send data.

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

Receiver partner number

</td><td>

Number for which a master record is created in a system application, for example, S4LOCAL.

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

Receiver partner type

</td><td>

Partner role or function. Common types include:-   LS: Logical System
-   KU: Customer \(for outbound messages\)
-   LI: Vendor \(for outbound messages\)

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

System

</td><td>

Name of the ERP system on which the new configuration should be stored.

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

Partner Profile

</td><td>

Identifier for the partner. Automatically added based on the specified system.

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

Message type

</td><td>

The IDoc message type, for example, ORDERS.

</td></tr></tbody>
</table>