> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/getting-started/base-configuration.md).

# Base Configuration

**DATANORM Setup** is the central configuration of the app. You reach it from the application search or from the role centre under **Setup**.

## General

<table><thead><tr><th width="290">Field</th><th width="150">Default</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Default Vendor No.</strong></td><td>–</td><td>Vendor proposed when importing.</td></tr><tr><td><strong>Default DATANORM Version</strong></td><td>Version 5</td><td>Version used for <strong>export</strong>. Import detects the version itself.</td></tr><tr><td><strong>Ask for Vendor on Manual Import</strong></td><td>on</td><td>Prompts for the vendor on every manual import instead of always using the default vendor. Recommended if you read in files from several suppliers.</td></tr></tbody></table>

## Import Settings

<table><thead><tr><th width="290">Field</th><th width="240">Default</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Duplicate Handling</strong></td><td>Mark for Manual Review</td><td>What happens when an article is already known: skip, update, create new, or mark for review.</td></tr><tr><td><strong>Duplicate Match Field</strong></td><td>DATANORM Article No.</td><td>Field used for matching: article number, EAN/GTIN or vendor item number.</td></tr><tr><td><strong>Match Duplicates per Vendor</strong></td><td>on</td><td>Takes the vendor into account when matching, so different suppliers may reuse the same article number or EAN without overwriting each other.</td></tr><tr><td><strong>Check Pending Staging for Duplicates</strong></td><td>off</td><td>Also checks not yet synchronised data from other sessions. Deliberately off, because re-reading the same file would otherwise flag every article as a duplicate.</td></tr><tr><td><strong>Auto-Sync to Items</strong></td><td>off</td><td>Transfers approved staging data to the item master without a further click.</td></tr><tr><td><strong>Archive Imported Files</strong></td><td>on</td><td>Keeps the original file content on the import session – valuable for troubleshooting.</td></tr></tbody></table>

## Record Filters

This is where you switch individual record types on and off. All toggles are **on** by default.

<table><thead><tr><th width="290">Field</th><th>Record type</th></tr></thead><tbody><tr><td><strong>Process Articles</strong></td><td>A and B record</td></tr><tr><td><strong>Process Texts</strong></td><td>T record</td></tr><tr><td><strong>Process Prices</strong></td><td>P record</td></tr><tr><td><strong>Process Product Groups</strong></td><td>S record</td></tr><tr><td><strong>Process Discount Groups</strong></td><td>R record</td></tr><tr><td><strong>Process Dimensions</strong></td><td>D record</td></tr><tr><td><strong>Process Graphics</strong></td><td>G record</td></tr><tr><td><strong>Process Surcharges</strong></td><td>Z record</td></tr><tr><td><strong>Process Services</strong></td><td>C record</td></tr><tr><td><strong>Process Part Lists</strong></td><td>J record</td></tr></tbody></table>

See also [Record Type Reference](/datanorm-item-import/datanorm_en_us/overview/record-types.md).

## Automation

<table><thead><tr><th width="290">Field</th><th width="150">Default</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Batch Size</strong></td><td>10,000</td><td>Number of lines processed per block.</td></tr><tr><td><strong>Use Background Processing</strong></td><td>on</td><td>Processes large files in a background session so the client is not blocked.</td></tr><tr><td><strong>Background Threshold</strong></td><td>1,000</td><td>Line count above which the import runs in the background.</td></tr><tr><td><strong>Auto Approve Staging</strong></td><td>off</td><td>Marks imported records as approved immediately, skipping manual review.</td></tr><tr><td><strong>Skip Duplicate Check</strong></td><td>off</td><td>Speeds up very large imports at the cost of duplicate detection.</td></tr></tbody></table>

{% hint style="warning" %}
Turning on **Auto Approve Staging** and **Skip Duplicate Check** together means a file goes into your item master unchecked. Only do that for files whose quality you know.
{% endhint %}

## Price Lists

<table><thead><tr><th width="290">Field</th><th width="220">Default</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Write Purchase Price Lists</strong></td><td>on</td><td>Writes imported prices as purchase price lines into a DATANORM price list per vendor.</td></tr><tr><td><strong>Purchase Price Source</strong></td><td>Net Price then List Price</td><td>Which DATANORM price becomes the purchase price: net price (indicator 2), list price (1), or preferably the net price with the list price as fallback.</td></tr><tr><td><strong>Apply Discount Groups to Purchase Price</strong></td><td>off</td><td>Applies the discounts of the DATANORM discount group to the list price. Discounts are chained multiplicatively, as DATANORM specifies.</td></tr><tr><td><strong>Write Scale Prices (Z Records)</strong></td><td>on</td><td>Transfers scale prices as additional price lines with a minimum quantity.</td></tr><tr><td><strong>Write Sales Price Lists</strong></td><td>off</td><td>Also writes the list price into a sales price list for all customers.</td></tr><tr><td><strong>Price List Status</strong></td><td>Active</td><td>Whether new price lists are active immediately or created as drafts.</td></tr><tr><td><strong>Price List Code Prefix</strong></td><td><code>DN</code></td><td>Prefix of the generated price list codes, for example <code>DN-PUR-10000</code>.</td></tr></tbody></table>

Covered in full under [Purchase Price Lists](/datanorm-item-import/datanorm_en_us/prices/purchase-price-lists.md).

## Part Lists (Sets)

<table><thead><tr><th width="290">Field</th><th width="150">Default</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Create Assembly BOM from Part Lists</strong></td><td>on</td><td>Builds assembly BOMs on the set item from J records.</td></tr><tr><td><strong>Include Optional Set Lines</strong></td><td>off</td><td>Also picks up lines with calling flag 2 and 4. By default only automatically inserted lines are used.</td></tr><tr><td><strong>Set Item Replenishment System</strong></td><td>Assembly</td><td>Whether the set item is switched to <em>Assembly</em> automatically or left untouched.</td></tr></tbody></table>

In full under [Building Assembly BOMs](/datanorm-item-import/datanorm_en_us/part-lists-sets/building-assembly-boms.md).

## Item Defaults

These values apply to every item synchronisation creates.

<table><thead><tr><th width="290">Field</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Default Item Category Code</strong></td><td>Item category for new items.</td></tr><tr><td><strong>Default Gen. Prod. Posting Group</strong></td><td>General product posting group.</td></tr><tr><td><strong>Default VAT Prod. Posting Group</strong></td><td>VAT product posting group.</td></tr><tr><td><strong>Default Inventory Posting Group</strong></td><td>Inventory posting group.</td></tr></tbody></table>

{% hint style="warning" %}
If one of these posting groups is missing, synchronisation fails for the affected item with an error message in staging. See [Common Problems](/datanorm-item-import/datanorm_en_us/operations-and-troubleshooting/common-problems.md).
{% endhint %}

## Numbering

<table><thead><tr><th width="290">Field</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Item No. Series</strong></td><td>Number series for newly created items. If left empty, the DATANORM article number is used as the item number.</td></tr><tr><td><strong>Import Session No. Series</strong></td><td>Number series for import sessions.</td></tr></tbody></table>

## Actions

<table><thead><tr><th width="290">Action</th><th>Effect</th></tr></thead><tbody><tr><td><strong>Initialize Units</strong></td><td>Creates the default mappings for DATANORM units. Run once after installation.</td></tr><tr><td><strong>Run Feature Tests</strong></td><td>Runs the smoke tests for licence, setup, SFTP, import, sync and export.</td></tr><tr><td><strong>Run Record Type Test Cases</strong></td><td>Verifies the DATANORM 4 and 5 record types against the specification.</td></tr><tr><td><strong>Show Test Results</strong></td><td>Results of the last run, including detail messages.</td></tr></tbody></table>

See [Built-in Tests](/datanorm-item-import/datanorm_en_us/operations-and-troubleshooting/built-in-tests.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/getting-started/base-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.