With EDI studio, you can include purchase and sales charges in EDI messages.

This topic gives an example of how to include charges in export of purchase orders and import of purchase order confirmations.

To import charges for sales orders, you can apply a similar setup as to import purchase order confirmations.

Export from D365FO to XML

You can include charges in the export of a purchase order to an XML file.

To include charges in the export of a purchase order, this set up is required:

• Source document: Add charges (markup) records and fields to the source document for both the purchase order as the purchase line level.
• Target document: Add charges (markup) records and fields to the target document for both the purchase order as the purchase line level.
• Message: Add the mapping of the purchase order charges and purchase line charges to the message.

Example - Export from D365FO to XML:

• Source document - Purchase order charges:
  
• Source document - Purchase line charges:
  
• Target document - Purchase order charges:
  
• Target document - Purchase line charges:
  
• Message:
  

Import from XML to staging

You can include charges in the import of a purchase order confirmation from an XML file to the EDI purchase order confirmation staging journal.
The charges, as imported to an EDI purchase order confirmation staging journal, are stored in a separate table: BisEdiPurchaseMarkupTrans.

To include charges in the import of a purchase order confirmation to the EDI purchase order confirmation staging journal, this set up is required:

• Source document: Use the target document of the 'Export from D365FO to XML' example as source document.
• Target document: Add charges (markup) records and fields to the target document for both the purchase order as the purchase line level. As record table, use the BisEdiPurchaseMarkupTrans table.
• Message: Add the mapping of the purchase order confirmation charges and purchase order confirmation line charges to the message.

Example - Import from XML to staging:

• Target document - Purchase order confirmation charges:
  
• Target document - Purchase order confirmation line charges:
  
• Message - Purchase order confirmation charges mapping (note the reference fields, used to properly link to the header):
  
• Message - Purchase order confirmation line charges mapping (note the reference fields, used to properly link to the line):
  

Import from staging to D365FO

You can include charges in the import of a purchase order confirmation from an EDI purchase order confirmation staging journal to a purchase order in D365FO.
The charges in the EDI purchase order confirmation staging journal are stored in a separate table: BisEdiPurchaseMarkupTrans.

To include charges in the import of an EDI purchase order confirmation staging journal to a purchase order, this set up is required:

• Source document: Use the target document of the 'Import from XML to staging' example as source document.
• Target document: Use the source document of the 'Export from D365FO to XML' example as target document.
• Message: Add the mapping of the purchase order confirmation charges and purchase order confirmation line charges to the message.

Example - Import from staging to D365FO:

• Message - Purchase order confirmation charges mapping (note the key field selection and the constant values):
  
• Message - Purchase order confirmation line charges mapping (note the key field selection and the constant values):