---
title: "Set up document - Other journals"
slug: "set-up-document-other-journals"
description: "Streamline your data imports with Connectivity Studio's journal document types, including WMS journal, Report as finished, and Project journal."
updated: 2026-07-15T08:34:20Z
published: 2026-07-15T08:34:20Z
canonical: "docs.staedean.com/set-up-document-other-journals"
---

> ## 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.

# Set up document - Other journals

Connectivity Studio provides you with several other journal-related document types:

- **WMS journal** Use a **WMS journal** document to import data into a WMS journal. You can, for example, import or post a packing slip for a purchase order or an item arrival.
- **Report as finished journal** Use a **Report as finished journal** document to import data into the Report as finished journal to report production orders as finished.
- **Production picking list** Use a **Production picking list** document to create a production order picking list and post it.
- **Project journal** Use a **Project journal** document to import project data into the project journals. You can, for example, import hours or expenses.

### Steps

1. Click **Connectivity studio - Integration Design**.
2. Click the **Documents** tab.
3. Click **New**.
4. Define a meaningful name for the document. **Example:** If the document is used for a sales integration, you can use names like 'Sales - Order' or 'Sales - Invoice'. In the **Document** field, type a value.

> [!NOTE]
> **Best practice**
> 
> In the document name, do not use the:
> 
> - Application name: Use the **Application** field to define the applicable application.
> - Document type: Use the **Document type** field to define the applicable document type.
5. In the **Project** field, enter or select a value.
6. Define the applicable application for the document. For a journal document, for example, select a ‘D365 F&SCM’ application.

In the **Application** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> You can only select an application that is defined for the applicable project. You can define project applications on the **Projects** page.
7. Select one of the journal-related document types:

In the **Document types** field, select an option.
  - **WMS journal**
  - **Report as finished journal**
  - **Production picking list**
  - **Project journal**
8. Sub-task: Set properties.
  1. Expand the **Properties** section.
  2. Enter the journal name that defines the desired journal type. Based on the document type and journal name, the journal header is created.

In the **Name** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> You can only select journal names that are related to the selected document type.
  3. You can automatically post the journal when the import is finished.

Select **Yes** in the **Post journals** field.

> [!NOTE]
> **Note**
> 
> - When testing the document and message, you are advised to set this field to **No**. So, you can review the imported data before the journal is posted.
> - For the **Report as finished journal**, these tables are used to post: **ProdJournalTable** and **ProdJournalRoute**.
9. Sub-task: Set custom handler.
  1. Expand the **Custom** section.
  2. For each journal document type, a standard handler class is available. You can use a customized handler class. To do so, extend a standard handler class.

In the **Handler** field, enter or select the desired handler class.
10. Sub-task: Set advanced features.
  1. Expand the **Advanced** section.
  2. Select the desired query type:

    - **Standard**: To select the data, only one D365 F&SCM query is created for the document.
    - **Custom**: To select the data, a separate query is created for each document record.

The **Custom query** feature offers an alternative approach to data retrieval. Unlike the standard query, with the **Custom query**, you can:

    - Join data across different companies.
    - Control queries more precisely with the **Group by** function.
    - Limit the selection to the first record only for complex queries.
    - Use fields from ancestor records in record relations.

In the **Query type** field, select an option.

> [!NOTE]
> **Note**
> 
> Try to use the standard query unless the standard query does not give the desired results. So, only use the custom query if required to get a specific query result.
11. Close the page.

## Related

- [Customize document handler class](/customize-document-handler-class.md)
- [Create separate files](/create-separate-files.md)
- [Custom query for internal documents](/custom-query-for-internal-documents.md)