---
schema_version: "1"
id: 978f9053b49c91ea41a7485bd3f06d6d5695cc2f0ba95decaf78048f09eef0b4
title: Receive from 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-receive-from-partners.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/message-type-receive-from-partners
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 4758372b26cbfaa340b15358fb14e781b573a9ee9e05698749af75620d0abe99
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# Receive from Partners Message Type Settings

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

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

## CSV

Use the following settings to define CSV as the format for the Receive from 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>Receive from 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><tr><td><p>Separator character</p></td><td><p>Character that separates values in the file.</p></td><td><p>,</p></td><td><p>Yes</p></td></tr><tr><td><p>Quote character</p></td><td><p>Character used as a quote character in the file.</p></td><td><p>""</p></td><td><p>Yes</p></td></tr><tr><td><p>Escape character</p></td><td><p>Character used as an escape character in the file.</p></td><td><p>\</p></td><td><p>Yes</p></td></tr><tr><td><p>Header line</p></td><td><p>When selected, Partner Manager skips the header row when it processes a CSV file.</p></td><td><p>Selected</p></td><td></td></tr><tr><td><p>Ignore empty line</p></td><td><p>When selected, Partner Manager ignores empty lines when it processes a CSV file.</p></td><td><p>Selected</p></td><td></td></tr><tr><td><p>Reference identifiers and attributes mapping</p></td><td><div><div><p>Uploaded DataWeave map that extracts the reference identifiers and custom attributes from the payload received from the partner:</p></div><div><ul><li><p>The extracted reference identifier values are used for dynamic routing into the appropriate message flow.</p></li><li><p>The extracted custom attributes provide visibility into the lifecycle of your B2B workflow. For more information, see <a href="https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes">Using Custom Messaging Attributes with Message Types</a>.</p></li></ul></div></div></td><td></td><td><p>No</p></td></tr></tbody></table>

## EDIFACT

Use the following settings to define EDIFACT as the format for the Receive from 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>Receive from 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>d10b</code> or <code>d96a</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>Reference identifiers and attributes mapping</p></td><td><div><div><p>Uploaded DataWeave map that extracts the reference identifiers and custom attributes from the payload received from the partner:</p></div><div><ul><li><p>The extracted reference identifier values are used for dynamic routing into the appropriate message flow.</p></li><li><p>The extracted custom attributes enable you to have visibility into the lifecycle of your B2B workflow. For more information, see <a href="https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes">Using Custom Messaging Attributes with Message Types</a>.</p></li></ul></div></div></td><td></td><td><p>No</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;</strong><br>Applies the standard EDIFACT schema for the configured format and version.</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 the 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></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 in Access Management. 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>Receive from 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>Message type identifier</p></td><td><div><div><p>Message type identifier value used in the dynamic message routing of inbound B2B transactions:</p></div><div><ul><li><p>If a schema is associated with the message type, Partner Manager automatically generates the message type identifier from the schema filename.<br><br>You can modify this value.</p></li><li><p>If a schema is not assciated with the message type, you must enter the message type identifier manually.</p></li></ul></div><div><p>Your partner must pass the message type identifier as follows when sending inbound messages:</p></div><div><ul><li><p>If you receive the payload via an HTTP-based endpoint, your partner must pass the message type identifier as the relative path in the HTTP request.</p></li><li><p>If you receive the payload via AS2 or a file-based endpoint protocol such as SFTP or FTP, your partner must prefix the message type identifier to the filename (<code>&lt;message-type-id&gt;_&lt;filename&gt;</code>).</p></li></ul></div></div></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Reference identifiers and attributes mapping</p></td><td><div><div><p>Uploaded DataWeave map that extracts the reference identifiers, business key, and custom messaging attributes from the payload received from the partner:</p></div><div><ul><li><p>The extracted reference identifier values are used for dynamic routing into the appropriate message flow.</p></li><li><p>The extracted custom attributes enable you to have visibility into the lifecycle of your B2B workflow. For more information, see <a href="https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes">Using Custom Messaging Attributes with Message Types</a>.</p></li></ul></div></div></td><td></td><td><p>Yes</p></td></tr></tbody></table>

## X12

Use the following settings to define X12 as the format for the Receive from 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>Receive from 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>5020</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> (purchase order) or <code>214</code>( for (shipment status).</p></td><td></td><td><p>Yes</p></td></tr><tr><td><p>Reference identifiers and attributes mapping</p></td><td><div><div><p>Uploaded DataWeave map that extracts the reference identifiers, business key, and attribute from the payload received from the partner:</p></div><div><ul><li><p>The extracted reference identifier values are used for dynamic routing into the appropriate message flow.</p></li><li><p>The extracted custom attributes enable you to have visibility into the lifecycle of your B2B workflow. For more information, see <a href="https://docs.mulesoft.com/partner-manager/latest/use-custom-attributes">Using Custom Messaging Attributes with Message Types</a>.</p></li></ul></div></div></td><td></td><td><p>No</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;</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></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)