---
title: "BisEdiHistory table - Setting field values and mapping IDs"
slug: "bisedihistory-table-setting-field-values-and-mapping-ids"
description: "Integrate the BisEdiHistory table in EDI Studio for effective monitoring and mapping of EDI and D365 F&SCM IDs in your messages and documents."
tags: ["Concept topic"]
updated: 2026-03-20T12:32:50Z
published: 2026-03-20T17:44:14Z
canonical: "docs.staedean.com/bisedihistory-table-setting-field-values-and-mapping-ids"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# BisEdiHistory table - Setting field values and mapping IDs

The **BisEdiHistory** table is the linking pin between EDI Studio and Connectivity Studio. Therefore, you must add this table to your EDI-related messages and documents in Connectivity Studio.

The **BisEdiHistory** table is used to:

- Monitor the EDI history.
- Map external IDs to D365 F&SCM IDs.

You can use the **BisEdiHistory** table for inbound messages and outbound messages.

### **Setting field values on record insert**

When a record is inserted in the **BisEdiHistory** table, several fields are filled based on direction, order type, buyer or seller, and recipient (for inbound messages).

| Field | Description |
| --- | --- |
| AcknowledgementStatus | The acknowledgement status. |
| Buyer | The EAN code for the buyer. |
| CompanyId | The company identification. |
| CustAccount | The related customer. |
| Direction | The message direction. |
| EdiCustomer | The EDI customer. |
| EdiVendor | The EDI vendor. |
| History | The internal history identification. this identification connects all related history records. You can get the history with a custom **BisGetHistoryId** method in you mapping. |
| HistoryId | Can be anything, but it must be unique. |
| InventLocationId | The identification of the location. |
| IsTest | The test indicator as filled from the related EDI document flow. |
| MessageCreatedDateTime | The message creation date and time. |
| MessageType | The message type. For example: Order or Acknowledgement. |
| OriginId | The origin where the data comes from. For example: CRM, website, or EDI. |
| PurchaseJournal | The related purchase journal, if applicable. |
| PurchId | The related purchase order. |
| Recipient | The EAN code for the recipient. |
| SalesId | The related sales order. |
| SalesJournal | The related sales journal, if applicable. |
| Seller | The EAN code of the seller. |
| Sender | The EAN code of the sender. |
| VendAccount | The related vendor. |

### **Mapping IDs on record insert**

On insert of a record in the **BisEdiHistory** table, several fields are filled based on a pre-defined mapping.

For an:

- Inbound message, several EDI field values are imported and converted to the related D365 F&SCM field values.
- Outbound message, several D365 F&SCM field values are taken and converted to the related EDI field values.

#### Seller messages:

For the inbound seller messages, the field value conversion is:

- **Recipient** -> **Legal entity**
- **Seller** -> **Legal entity**
- **Sender** -> **EDI partner / Customer**
- **Buyer** -> **Customer**

For the outbound seller messages, the field value conversion is:

- **Legal entity** -> **Sender**
- **Legal entity** -> **Seller**
- **EDI partner** / **Customer** -> **Sender**
- **Customer** -> **Buyer**

#### Buyer messages:

For the outbound buyer massages, the field value conversion is:

- **Legal entity** -> **Sender**
- **Legal entity** -> **Buyer**
- **EDI partner** / **Vendor** -> **Sender**
- **Vendor** -> **Seller**

For the inbound buyer messages, the field value conversion is:

- **Recipient** -> **Legal entity**
- **Buyer** -> **Legal entity**
- **Sender** -> **EDI partner** / **Vendor**
- **Seller** -> **Vendor**

#### 3PL messages:

For the inbound 3PL messages, the field value conversion is:

- **Recipient** -> **Legal entity**
- **Warehouse** -> **Sender**

For the outbound 3PL messages, the field value conversion is:

- **Legal entity** -> **Sender**
- **Warehouse** -> **Recipient**

## Related

- [BisEdiHistory table - Insert process and customizations](/bisedihistory-table-insert-process-and-customizations.md)
- [Monitor EDI history](/monitor-edi-history.md)