# Inbound Transmission Overview

When you generate _Inbox Items_, Vault also generates related _Inbound Transmissions_ to capture the details of each inbound case, which you can review in the _Transmissions_ section of _Inbox Items_ and _Cases_. _Inbound Transmissions_ detail the source of _Inbox Items_ created by email, import, and literature articles from SafetyDocs. For imported E2B files, Vault generates ICH-compliant acknowledgments and adds them to _Inbound Transmissions_. In addition, Vault references the _Origin_ field on _Inbound Transmissions_ during <a href="/en/gr/01246/#back-reporting-components">back reporting</a>. During _Case_ promotion, in Vaults using the <a href="/en/gr/01141/#enhanced">enhanced _Potential Matches_ page</a>, if duplicate detection returns any potential matches Vault generates a [results log][1] and attaches it to _Inbound Transmissions_.

## Case Access Group Security

If your Admin has configured <a href="/en/gr/01182/">Case Access Group security</a>, Vault populates the _Case Access Group_ and _Case Access Group Assignment Reason_ on the _Inbound Transmission_. This identifies which _Case Access Group_ the _Inbox Item_ or _Case_ belongs to and the reason Vault assigned that group. Case Access Group security for <a href="/en/gr/01182/#user-access">_Inbound Transmissions_</a> is based on the localization of the associated _Case_ or _Inbox Item_.

## Document Import

For _Inbox Items_ generated from source documents in your _Library_, you can view links to the _Inbox Item_ and the _Inbound Transmission_ on the document's <a href="/en/gr/9753/">_Doc Info_ pane</a>.

## E2B Import

When Vault <a href="/en/gr/01286/">generates _Inbox Items_ from E2B</a> source documents, Vault generates an _Inbound Transmission_ <a href="/en/gr/01134/">mapped to the source data</a>. On the record, Vault generates and attaches an <a href="/en/gr/01286/#acknowledgment-generation">ICSR acknowledgment</a>.

### View ICSR Acknowledgments {#view-acks}

For E2B-imported _Inbox Items_, Vault generates an ICH-compliant E2B ICSR acknowledgment in the same E2B format the file was received in. To view the acknowledgement:

1. On the _Inbox Item_ received from an E2B transmission, expand **Inbound Transmissions**.
2. On the _Inbound Transmission_, expand **Transmission Messages**.
3. Open the _Transmission Message_. The acknowledgment file and Message Delivery Notifications (MDN) response is an attachment on the _Transmission Message_.
4. To view the acknowledgment or MDN, select **Body**.

## Email Intake

When Vault <a href="/en/gr/715459/">generates _Inbox Items_ from email</a>, Vault populates the _Sender (Person)_ and _Sender (User)_ fields on the _Inbound Transmission_ of the _Inbox Item_. If a _Vault Person_ has the same email address as the sender and belongs to an _Access Group_, Vault populates the _Sender (Person)_ field on the _Inbound Transmission_. If multiple _Vault Persons_ meet this criteria, Vault uses the record with the most recent created date. If no _Vault Person_ meets this criteria, Vault looks for a _User_ with the same email address as the sender. If such a _User_ exists, Vault sets the _Sender (User)_ field on the _Inbound Transmission_. If multiple _Users_ meet this criteria, Vault uses the record with the most recent created date.

## Follow-Up Case Promotion {#fu-promotion}

After follow-up _Case_ <a href="/en/gr/01136/">promotion</a>, Vault creates an _Inbound Transmission_ if none exists on the related _Inbox Item_. You can also see the <a href="/en/gr/01152/">audit trail</a> on a _Case_ to view the changes.

Upon creating a follow-up _Case_, Vault attaches a change log to the _Attachments_ section of the _Inbound Transmission_. The change log displays the fields that were changed during the merge and the action taken. For domestic follow-up _Cases_, the change log displays both the global and localized fields that were changed.

## Potential Matches Results Log {#results-log}

During _Case_ promotion, if duplicate detection returns any potential matches on the <a href="/en/gr/01141/#enhanced">enhanced _Potential Matches_ page</a>, Vault generates a CSV log of the matched records and saves it in the _Attachment_ section of the _Inbound Transmission_ on the _Inbox Item_ and _Case_. If multiple _Inbound Transmissions_ exist, Vault attaches the CSV to the one with the earliest _Created Date_. If duplicate detection is re-run, Vault saves a new CSV for each set of results.

Vault lists the results in the same order as they appeared on the page. The CSV includes the following columns:

* **Rank**: Includes <a href="/en/gr/01141/#id">_ID Matches_</a>, <a href="/en/gr/01141/#subject">_Subject Matches_</a>, and <a href="/en/gr/01141/#possible">_Possible Matches_</a>
* **Record ID**: The _Inbox Item_ or _Case_ ID 
* **Record Name**: The _Inbox Item_ or _Case_ name
* **Match Type**: Includes _WWUID_, _ID_, _Subject_, and _Possible_

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: On <em>Cases</em> with no <em>Inbound Transmission</em>, Vault does not generate a CSV log. This known limitation will be addressed in a future release.</p>
    </div>
  </div>
</div>



## Inbound Transmission Sections

_Inbound Transmissions_ include _Details_, _Transmission Messages_, _Systems_, and _Signatures_ section fields, as well as _Workflow Timeline_ and _Attachments_ sections. 

### Details Section Fields

The following fields may be available:

<table>
    <thead>
        <tr>
            <th>Field</th>
            <th>Description</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td><em>Case</em></td>
            <td>Vault populates a reference link to the <em>Case</em>.</td>
        </tr>
        <tr>
            <td><em>Inbox Item</em></td>
            <td>Vault populates a reference link to the <em>Inbox Item</em>.</td>
        </tr>
        <tr>
            <td><em>Transmission Date</em></td>
            <td>Vault populates the <em>Inbound Transmission</em> creation date or source data from the imported <a href="/en/gr/01134/#e2br3">E2B(R3)</a> or <a href="/en/gr/01134/#e2br2">E2B(R2)</a> file.</td>
        </tr>
        <tr>
            <td><em>Transmission Profile</em></td>
            <td>Select the <em>Transmission Profile</em> configured for submitting ICSRs to the destination agency.</td>
        </tr>
        <tr>
            <td><em>Origin</em></td>
            <td>Select your organization.</td>
        </tr>
        <tr>
            <td><em>Destination</em></td>
            <td>Select the destination agency to which the report will be sent.</td>
        </tr>
    </tbody>
</table>

### Transmission Messages Section Fields

The following fields may be available:

<table>
    <thead>
        <tr>
            <th>Field</th>
            <th>Description</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td><em>Name</em></td>
            <td>Upon receiving the file, Vault populates a name.</td>
        </tr>
        <tr>
            <td><em>Message Type</em></td>
            <td>Vault populates the message type as either <em>Base Transmission Message</em> or <em>E2B ACK</em>.</td>
        </tr>
        <tr>
            <td><em>Response</em></td>
            <td>Vault populates the sender's response.</td>
        </tr>
    </tbody>
</table>

## Additional Sections

Depending on your Admin's configuration, additional tracking may appear in the _Signatures_ and _Attachment_ sections.

[1]: #results-log