---
title: "Custom Briefing Job: ERP Export"
slug: "custom-briefing-job-erp-export"
updated: 2025-09-16T13:47:48Z
published: 2025-09-16T13:47:48Z
canonical: "documentation.encodify.com/custom-briefing-job-erp-export"
---

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

# Custom Briefing Job: ERP Export

## Overview

---

The **ERP Export Job** exports **briefing and product data** into two formats:

1. **XML files** – one campaign per file, with unique names based on the chain abbreviation, campaign code, and current date (e.g., `pt10811p1IT03032008.xml`).
2. **Fixed-format “navik” file** – contains one or more campaigns and is **overwritten each run**.

The job supports:

- Scheduled runs.
- Multiple campaigns per execution.
- Email notifications upon completion.

**Required Field Mapping in Briefing System Module Configuration:**

To execute the job correctly, the following fields must be mapped in their respective modules:

| Module | Required Fields |
| --- | --- |
| **Briefing** | Briefing Code Field, Field with Chains, Field with Export to Financial System (Date Field), Field with briefing period purchase start, Field with briefing period purchase end, Briefing Name Field |
| **Chains** | Field with Abbreviation, Partner # Field |
| **Prices** | Field with Original Price, Field with Price, Rental Field |
| **Products on Briefing** | Field with Headline, Field with Product |
| **Supplier** | Field with Number and Name |
| **Products** | Field with Product Name, Field with Product Number, Supplier Field (link to Supplier Module Field with Number and Name) |

**Export Criteria:**

- Only campaigns where the **Export to Financial System** date is today or in the past are included.

## How it works

---

The **ERP Export Job**works as below:

1. The job runs **once or more per day** according to configured start times.
2. Generates **navik file** (overwritten each run) and **XML files** (one per campaign).
3. Files are saved to the configured **drop folder**.
4. Sends email notifications to configured recipients.

**Important Notes:**

- Ensure all mapped fields exist and are correctly configured to avoid missing or incorrect data.
- XML filenames are generated based on the **chain abbreviation + campaign code + current date**.
- Navik files include all applicable campaigns and are overwritten on each execution.

## Parameters

---

The table below provides an overview of parameters supported for the **ERP Export Job**

| Parameter | Description | Notes |
| --- | --- | --- |
| `joblist=ERPExportJob` | Name of the scheduler job. | — |
| `job.ERPExportJob.type` | Class that performs the job: `enCode.app.common.briefing.jobs.ERPExportJob`. | — |
| `job.ERPExportJob.startimes` | Comma-separated list of start times (HH:MM). | Daily execution, spaces not allowed. |
| `job.ERPExportJob.param.dropdir` | Folder where exported XML and navik files are saved. | Ensure path exists. |
| `job.ERPExportJob.param.SenderEmail` | Email address from which notifications are sent. | — |
| `job.ERPExportJob.param.RecipientEmail` | Email address to receive notifications. | — |
| `job.ERPExportJob.param.EmailSubject` | Subject line for notification email. | — |
| `job.ERPExportJob.param.EmailBody` | Body content for notification email. | — |
| `job.ERPExportJob.param.SiteID` | Site ID for which the job will be performed. | — |

## Example Configuration

---

The below is an example of the **Briefing Import Job**

```plaintext
joblist=ERPExportJob
job.ERPExportJob.type=enCode.app.common.briefing.jobs.ERPExportJob
job.ERPExportJob.startimes=05:00,12:00
job.ERPExportJob.param.dropdir=/data/Files/customer/inbox
job.ERPExportJob.param.SenderEmail=blane@encode.dk
job.ERPExportJob.param.RecipientEmail=abn@encode.dk
job.ERPExportJob.param.EmailSubject=Transfer file from Briefing system to Navision
job.ERPExportJob.param.EmailBody=Transfer file from Briefing system to Navision
job.ERPExportJob.param.SiteID=4
```

**Explanation:**

- Runs daily at 05:00 and 12:00.
- Generates both XML and navik files for external ERP or financial systems.
- XML files are created per campaign, navik file is overwritten each run.
- Sends notification emails to recipients upon completion.