---
schema_version: "1"
id: a3fb9477ca73f077b595b9eeba9e3965135b63cb5f52b3af0fd94e0a789d27ef
title: Send to Partners Message Type Settings
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/message-type-send-to-partners.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/message-type-send-to-partners
source_site: docs.mulesoft.com
content_type: documentation
content_hash: df4fe17c145e54aaa00bb50e1381f0e6007830c6a4b561dfa9636ff32fc0d91f
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# Send to Partners Message Type Settings

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The Send to Partners message type defines the way in which Anypoint Partner Manager transforms the
outbound transactions sent from your organization to your partner. You can define the CSV, EDIFACT,
JSON, X12, or XML format for a Send to Partners message type.

## CSV

Use the following settings to define CSV as the format for the Send to Partners message type:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th><th>Required</th></tr></thead><tbody><tr><td><p>Usage</p></td><td><p>Message usage. Allowed value is <code>Send to Partners</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Format</p></td><td><p>Format of the message. Allowed value is <code>CSV</code>.</p></td><td></td><td><p>Yes</p></td></tr></tbody></table>

## EDIFACT

Use the following settings to define EDIFACT as the format for the Send to Partners message type:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th><th>Required</th></tr></thead><tbody><tr><td><p>Usage</p></td><td><p>Message usage. Allowed value is <code>Send to partners</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Format</p></td><td><p>Format of the message. Allowed value is <code>EDIFACT</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Version</p></td><td><p>EDIFACT version, such as <code>d03b</code> or <code>d12a</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Message type</p></td><td><p>EDIFACT message type, such as <code>ORDERS</code>, <code>DESADV</code>, or <code>INVOIC</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Schema</p></td><td><div><div><p>EDI schema for the message type. Options include:</p></div><div><ul><li><p><strong>Use standard EDIFACT-&lt;version&gt;-&lt;message-type&gt;</strong><br>Applies the standard EDIFACT schema for the version and message type configured.</p></li><li><p><strong>Customize</strong><br>Enables you to import a customized <a href="https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference">EDI schema language</a> file if you must make adjustments to the standard EDIFACT schema.</p><div><p>When using a customized EDI schema, you can assign a custom name to the message type definition, for example, <code>EDIFACT-d97a-ORDERS-&lt;PartnerName&gt;</code>.</p></div></li></ul></div></div></td><td><p>Use standard EDIFACT- &lt;version&gt;</p></td><td><p>Yes</p></td></tr><tr><td><p>Name</p></td><td><p>Message type name that Partner Manager automatically generates from the schema filename. You can modify this name.</p></td><td></td><td><p>Yes</p></td></tr></tbody></table>

## JSON or XML

Use the settings in the table to define JSON or XML as the format for the Receive from Partners
message type.

If you process cXML messages with <DOCTYPE> tags, you must set the `minMuleVersion` to 4.5.0 or
higher and upgrade your runtime environment. For more information, see Partner Manager deployment
settings for [CloudHub](https://docs.mulesoft.com/partner-manager/latest/cloudhub-deployment-settings),
[CloudHub 2.0](https://docs.mulesoft.com/partner-manager/latest/cloudhub2-deployment-settings), and [Runtime Fabric](https://docs.mulesoft.com/partner-manager/latest/rtf-deployment-settings).

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th><th>Required</th></tr></thead><tbody><tr><td><p>Usage</p></td><td><p>Message usage. Allowed value is <code>Send to partners</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Format</p></td><td><p>Format of the message. Allowed value is <code>JSON</code> or <code>XML</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Schema</p></td><td><p>Imported JSON or XSD schema file for the message type.</p></td><td></td><td><p>No</p></td></tr><tr><td><p>Name</p></td><td><p>Name of the new message type</p></td><td></td><td><p>Yes</p></td></tr></tbody></table>

## X12

Use the following settings to define X12 as the format for the Send to Partners message type:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th><th>Required</th></tr></thead><tbody><tr><td><p>Usage</p></td><td><p>Message usage. Allowed value is <code>Send to partners</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Format</p></td><td><p>Format of the message. Allowed value is <code>X12</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Version</p></td><td><p>X12 version, such as <code>3010</code> or <code>5040</code>.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Message type</p></td><td><p>X12 transaction set number, such as <code>850</code> for a purchase order or <code>214</code> for the shipment status.</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Schema</p></td><td><div><div><p>EDI schema for the message type. Options include:</p></div><div><ul><li><p><strong>Use standard X12-&lt;version&gt;-&lt;message-type&gt;</strong><br>Applies the standard X12 schema for the version and message type configured.</p></li><li><p><strong>Customize</strong><br>Enables you to import a customized <a href="https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-schema-language-reference">EDI schema language</a> file if you must make adjustments to the standard X12 schema.</p><div><p>When using the customized EDI schema, you can assign a custom name to the message type definition, for example, <code>X12-7050-204-PartnerName</code>.</p></div></li></ul></div></div></td><td><p>Use standard X12-&lt;version&gt;</p></td><td><p>Yes</p></td></tr><tr><td><p>Name</p></td><td><p>Message type name that Partner Manager automatically generates from the schema filename. You can modify this name.</p></td><td></td><td><p>Yes</p></td></tr></tbody></table>

For an example that shows how to customize an X12 schema, see
[Customize EDI X12 Schema for B2B Integrations](https://www.mulesoft.com/exchange/works.integration/b2b-x12-custom-schema-example)
in Anypoint Exchange.

## See Also

- [Message Types](https://docs.mulesoft.com/partner-manager/latest/document-types)

- [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type)

- [Deleting Message Types](https://docs.mulesoft.com/partner-manager/latest/delete-message-types)