---
title: "Post the Staging journals"
slug: "post-the-staging-journals"
tags: ["Task", "PLM"]
updated: 2026-07-21T07:44:44Z
published: 2026-07-21T07:44:44Z
canonical: "docs.staedean.com/post-the-staging-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.

# Post the Staging journals

Use the **Staging journal posting engine** to post multiple open PLM staging journals. You can filter the journals by scenario, configure parallel processing, transfer failed lines to a separate error journal, and run the posting as a batch job.

## Steps

1. Go to **Modules > Engineering change management > Periodic tasks > Post staging journals**.
2. In the **Staging journal posting engine** dialog, expand **Records to include**.
3. Select **Filter** and define the journals to include. You can filter by:
  - **Journal ID**
  - **Journal status**
  - **Batch (Record-ID)**
  - **Scenario**
4. In the **Journal status** field, select **Open**.
5. In the **Scenario** filter, select one or more applicable scenarios, such as:
  - **Import parts**
  - **Import ECO**
  - **Import migration**
  - **Import release**
6. Under **Posting helpers**, review and configure the following options:
  - **Number of threads**: Enter the number of threads to use for parallel processing. Increase this value only when parallel processing is required.
  - **Transfer failed lines**:
    - Set to **Yes** to post valid lines and move failed lines to a separate error journal.
    - Set to **No** to stop the posting when a validation error occurs.
7. Under **Run in the background**, configure the batch options when required:
  - **Batch processing**: Set to **Yes** to run the posting as a batch job.
  - **Task description**: Review or update the batch task description.
  - **Batch group**: Select the batch group that will process the job.
  - **Private**: Set to **Yes** to make the batch job visible only to you.
  - **Critical job**: Set to **Yes** if the batch job must be treated as a critical job.
  - **Monitoring category**: Select a category for monitoring the batch job.
  - **Recurrence**: Configure a recurring schedule for the batch job.
  - **Alerts**: Configure notifications for the batch job.

> [!NOTE]
> Note
> 
> The batch fields are used only when **Batch processing** is set to **Yes**.
8. Select **OK** to start the posting process.
9. Review the Infolog message and journal status after posting.

### Posting results

The posting can have one of the following results:

- **Successful**: All selected journals are posted successfully. The journal status changes to **Posted**.
- **Partially successful**: Valid lines are posted, and failed lines are moved to an error journal. The source journal status changes to **Posted with errors transferred**.
- **Failed validation**: No valid lines are posted. When **Transfer failed lines** is set to **Yes**, the failed lines are moved to an error journal.
- **System error**: An unexpected database, infrastructure, or system error stops the entire posting process. Failed lines are not transferred.