> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/output-management.md).

# Output Management

Within the Output Management module, all settings related to report generation, email distribution, printing, and archiving to the Document Warehouse are configured.

## Print destinations <a href="#print-destinations" id="print-destinations"></a>

| Print destination        | Behavior and requirements                                                                                                                                                                    |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **9A Archive**           | Archives documents in Document Warehouse; available only for non-proforma documents. Configure the primary table name in report setup to enable tag linking.                                 |
| **9A Screen**            | Displays documents on the user's portable device. The extension determines the application, such as Microsoft Excel for `.xls` files or a PDF viewer for `.pdf` files.                       |
| **9A Printer**           | Supports PDF documents only when the Document Routing Agent runs in interactive mode. With Dox42 as the provider, EMF images can also be generated.                                          |
| **9A Email**             | Sends emails immediately, or as batch jobs when tracking is enabled.                                                                                                                         |
| **9A Email Interactive** | Allows review and editing before sending. With BCC Integration, set the email provider to `EML_Raptor` in **Email parameters** (`System administration > Setup > Email > Email parameters`). |

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-a818f69724284ca8461f043d3601fbf79fc94e00%2Fimage%20(721).png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you're using 9A Email Interactive, but the mail is still nog generated as an EML message, be sure to check the user preferences: User options > Account > Email provider ID.
{% endhint %}

## Report setup <a href="#report-setup" id="report-setup"></a>

The report setup can be found through the following path:\
**9A Raptor DWH > Setup > Output Management > Report Setup**

Currently, the module supports various providers:

* SmartFlows
* SSRS
* Electronic Reporting
* Dox42
* Xperido

{% tabs %}
{% tab title="SmartFlows" %}
**SmartFlows**

* All print destinations are supported with **SmartFlows** reports.
* Before using **SmartFlows** as a provider, ensure that the **9A Kickstart templates** are imported into SmartFlows.
  {% endtab %}

{% tab title="SSRS" %}
**SSRS**

* All print destinations are supported with **SSRS** reports.
* **Troubleshooting Tip**: Verify whether the document is generated correctly via standard **D365FO**.
  {% endtab %}

{% tab title="Electronic Reporting" %}
**Electronic Reporting**

* All print destinations are supported with **Electronic Reporting** reports. However, only the **9A Printer** is supported when Word/Excel documents are converted to PDF.
* Before using **Electronic Reporting** as a provider, ensure that the necessary electronic reporting templates are imported into **D365FO**.
* **Troubleshooting Tip**: Verify whether the document is generated correctly via standard **D365FO**.
* **Key Difference**: With **Electronic Reporting**, you don’t need to set up format mapping in the general print management setup, or in the customer/vendor print management setup. Instead, leave it as standard and set up the required format mapping in the report setup. Additionally, you don’t need to define electronic reporting destinations (as in standard D365FO).
  {% endtab %}

{% tab title="dox42" %}
**dox42**

* All print destinations are supported with **dox42** reports.
* To use dox42 templates, link the SharePoint URL of the dox42 template in the **Flows** section.
  {% endtab %}

{% tab title="XperiDo" %}
**XperiDo**

* This is for existing **XperiDo** customers.
* Connection information can be found in the **Ex Arte V5 Foundation**.
* All print destinations are supported with **XperiDo** reports.
  {% endtab %}
  {% endtabs %}

Some setup options are only available for certain providers. For example, template development is only available when **SmartFlows** or **Dox42** is selected as the provider. Format mapping is only available when **Electronic Reporting** is selected.

***

#### **Settings** <a href="#report-setup-settings" id="report-setup-settings"></a>

The mandatory settings are explained below, detailing how to use them for your reports.

| Setting                | Configuration                                                                                                            |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Report Setup ID**    | A unique identifier for each report setup.                                                                               |
| **Provider**           | SSRS, SmartFlows, Electronic Reporting, Dox42, or Xperido.                                                               |
| **Report Name**        | Match the report name in Print Management. Remove the suffix `.report` (default in D365FO) or any custom suffix.         |
| **Format Mapping**     | Available only for **Electronic Reporting**.                                                                             |
| **Company**            | Enter a company for company-specific setup. If empty, the system searches for a default report setup without a company.  |
| **Primary Table Name** | Required for archiving in Document Warehouse. Supports regular tables, such as journal tables, but not temporary tables. |

***

#### **General Settings** <a href="#report-setup-general-settings" id="report-setup-general-settings"></a>

| Setting                                 | Behavior and availability                                                                                                                                  |
| --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Download XSD**                        | Available for SmartFlows, Dox42, or XperiDo.                                                                                                               |
| **Download XML**                        | Available for SmartFlows, Dox42, or XperiDo.                                                                                                               |
| **Document Template**                   | Works with Raptor Document Warehouse; triggered when **Ex Arte Archive** is the print destination.                                                         |
| **Email ID**                            | Email template for customers and vendors. If no company is selected, ensure the Email ID exists in every company used. Templates can include placeholders. |
| **Activate Tracking**                   | "Yes" tracks emails and sends them via the standard D365FO email batch job. "No" sends immediately.                                                        |
| **Convert to PDF**                      | Converts Excel or Word documents to PDF. Raptor Document Warehouse integration must be activated.                                                          |
| **Output Generation** (Dox42 options)   | 'Default' or 'Word'; Dox42 only. Converts documents to Word and makes "Convert to PDF" available, allowing PDFs with adjustable tables.                    |
| **Trigger Business Event**              | Triggers a business event with print-generation information. XML and attachments are not included.                                                         |
| **Print as EMF**                        | Enabled by default for **Dox42**. Allows the DRA client to run in Windows Service mode.                                                                    |
| **Output Generation** (document format) | PDF or Word for **Dox42**, with PDF as default. For other providers, PDF is always the default.                                                            |

***

#### **Flows** <a href="#report-setup-flows" id="report-setup-flows"></a>

This setup is available when the **SmartFlows**, **Dox42**, or **XperiDo** integration is activated in the **Output Management** tab of the **9A Raptor DWH** parameters.

* **Flow**: Choose a flow from the dropdown when **SmartFlows** or **XperiDo** is selected as the report provider. For **Dox42**, manually input the SharePoint URL where the template is stored.
* **Language**: Optional. Leave blank if the flow is for all languages. The language can be retrieved from the sales or purchase order.

***

#### **Filenames** <a href="#report-setup-filenames" id="report-setup-filenames"></a>

You can set custom filenames to archive documents in Document Warehouse or for email attachments. Filenames can be specified for different languages, and placeholders can be used.

* **Default Filename**: If no specific filename is set for a report setup, a generic filename will be used for every generated document.
* **Electronic Reporting**: When using **Electronic Reporting** as a provider, the filename defined in Electronic Reporting will be used if none is specified in the report setup.

#### **Attachments** <a href="#report-setup-attachments" id="report-setup-attachments"></a>

This is available only when **9A Email** or **9A Email Interactive** is selected as the print destination. Extra attachments can be added to emails based on tag setup. Document Warehouse must be set up before using this feature.

* **Tags**: Enter one or more tags as conditions.
* **Linked to Record**: Include the record as a tag condition (e.g., sales invoice journal, sales confirmation journal).
* **Linked to Company**: Include the company as a tag condition.
* **Linked to Language**: Include the language from the linked record as a tag condition.

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-f2d6dbb3fd7902c96aff3bcce5f2f4a1ec0dcb41%2Fimage%20(153).png?alt=media" alt=""><figcaption></figcaption></figure>

***

#### **Tag Methods** <a href="#report-setup-tag-methods" id="report-setup-tag-methods"></a>

When **9A Archive** is used, tag methods let you add tags to archived documents in Document Warehouse without customizations.

Tag methods start from the primary table configured in the Report setup, and retrieve additional data via a linked record or a query. This data is then translated into tags using the [Entity Configuration](https://docs.dynalogic.com/birds-document-warehouse-product-overview/setup-and-configuration/entity-configuration.md)and applied on the archived document.

<div align="left"><figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-61968cccefbe929fbee9078708e3e8212d6f932c%2Fimage%20(154).png?alt=media" alt=""><figcaption></figcaption></figure></div>

* **Record**: Returns one record as an object.
* **Query**: Returns a query as an object.

Below is a list of existing primary tables with their corresponding table methods:

**Customer Confirmations**

* **Table**: CustConfirmJour
* **Methods**:
  * **queryCustConfirmSalesLink**
* **Purpose**: To return multiple sales order numbers.
* **Return Type**: Query – Records from the **CustConfirmSalesLink** table.
* **Entity Configuration**: The entity behind the **SalesTable** should be configured in Document Warehouse.
* **D365FO Relations**: Use relations in D365FO to link **CustConfirmSalesLink** and **SalesTable** in the [Document Management](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/document-management.md#relation-setup)

***

**Customer Packing Slips**

* **Table**: CustPackingSlipJour
* **Methods**:
  * **queryCustPackingSlipSalesLink**
* **Purpose**: To return multiple sales order numbers.
* **Return Type**: Query – Records from the **CustPackingSlipSalesLink** table.
* **Entity Configuration**: The entity behind the **SalesTable** should be configured in Document Warehouse.
* **D365FO Relations**: Use relations in D365FO to link **CustPackingSlipSalesLink** and **SalesTable** in the [Document Management](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/document-management.md#relation-setup)

***

**Customer Invoices**

* **Table**: CustConfirmJour
* **Methods**:
  * **queryCustInvoiceSalesLink**
* **Purpose**: To return multiple sales order numbers.
* **Return Type**: Query – Records from the **CustInvoiceSalesLink** table.
* **Entity Configuration**: The entity behind the **SalesTable** should be configured in Document Warehouse.
* **D365FO Relations**: Use relations in D365FO to link **CustInvoiceSalesLink** and **SalesTable** in the [Document Management](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/document-management.md#relation-setup)
* **Table**: CustTrans
* **Purpose**: To return the customer transaction voucher.
* **Return Type**: Record – Record from the **CustTrans** table.
* **Entity Configuration**: The **CustTrans** entity should be configured in Document Warehouse.

***

**Project Invoices**

* **Table**: ProjInvoiceJour
* **Methods**:
  * **exaQueryProjInvoiceLinesUnion**
* **Purpose**: To return multiple project numbers.
* **Return Type**: Query – Records from the **ProjInvoiceLinesUnion** view.
* **Entity Configuration**: The entity behind the **ProjTable** should be configured in Document Warehouse.
* **D365FO Relations**: Use relations in D365FO to link **ProjInvoiceLinesUnion** and **ProjTable** in the [Document Management](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/document-management.md#relation-setup)

***

**Customer Quotation Journals**

* **Table**: CustQuotationJour
* **Methods**:
  * **queryCustQuotationSalesLink**
* **Purpose**: To return multiple sales quotation numbers.
* **Return Type**: Query – Records from the **CustQuotationSalesLink** table.
* **Entity Configuration**: The entity behind the **SalesQuotationTable** should be configured in Document Warehouse.
* **D365FO Relations**: Use relations in D365FO to link **CustQuotationSalesLink** and **SalesQuotationTable** in the [Document Management](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/document-management.md#relation-setup)

#### **Placeholders** <a href="#report-setup-placeholders" id="report-setup-placeholders"></a>

In the Placeholders section we can define placeholders and map them to a specific field or method from a particular table.

Placeholders can be used in filenames or email templates. Remember to enclose each placeholder with percent symbols (`%`) as both a prefix and suffix.

For example, the **%customername%** placeholder can be mapped to the **DeliveryName** field from the **CustConfirmJour** table (Sales Confirmations) or the **InvoicingName** field from the **CustInvoiceJour** table (Sales Invoices).

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-7418f23c2fda924fa66d3768f9b6031b3f67f605%2Fimage%20(195).png?alt=media" alt=""><figcaption></figcaption></figure>

Another example is mapping the %**DeliveryAddress%** placeholder to the **deliveryAddress** method from the **CustConfirmJour** table.

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-394927a90890298aa9b0f101faa0af6bd765dd86%2Fimage%20(194).png?alt=media" alt=""><figcaption></figcaption></figure>

## Archive Queued Reports <a href="#archive-queued-reports" id="archive-queued-reports"></a>

If the [#Archiving Processing Mode](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/parameters.md#output-management-archiving-processing-mode) in the parameters is not set to synchronous, then the asynchronous processing can be scheduled via **9A Raptor DWH > Periodic tasks > Output management > Archive queued reports**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/output-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
