Import Process

The core workflow of every import: from the file through staging to items, prices and BOMs.

Every import runs through the same four phases, whether you upload the file manually or have it collected via SFTP.

The four phases

1

Read

The app reads the file line by line, detects the DATANORM version from the header record and assigns each line to its record type. An import session is created that holds the whole operation together.

2

Stage

The recognised data lands in intermediate tables: articles in Article Staging, prices in Price Staging, sets in Part Lists, plus texts, product groups and discount groups. At this point the item master is untouched.

3

Review and approve

The app flags possible duplicates and errors. You decide which records are applied. See Reviewing and Approving Staging.

4

Synchronise

Approved records become items, purchase price list lines and assembly BOMs.

Staging is the reason a faulty supplier export cannot damage your item master: you see the data before it takes effect.

Import session status

Status	Meaning
Pending	The session exists, processing has not started.
Processing	The file is being read.
Completed	All lines were processed without error.
Completed with Errors	The file was processed, but individual lines could not be read.
Error	Processing was aborted, for example because the file is unreadable.
Cancelled	The session was cancelled manually.

Staging record status

Status	Meaning
New	Imported, not yet assessed.
Review	Waiting for your decision, usually because of a possible duplicate.
Approved	Cleared to be applied.
Rejected	Will not be applied.
Synced	Transferred to the item master.
Error	Applying it failed; the cause is on the record.
Skipped	Deliberately not processed, for example a set line with no matching item.

Large files

Above the line count in Background Threshold – shipped as 1,000 – the app processes the file in a background session. You can carry on working and follow progress on the import session. Batch Size determines how many lines are processed per block.

Order of multiple files

A delivery often consists of several files. This order has proven itself:

1

Groups first

.WRG (product groups) and .RAB (discount groups), so that articles and prices find the groups already in place.

2

Then the articles

DATANORM.001 and, where applicable, the follow-up files .002, .003 in ascending order.

3

Price changes last

DATPREIS.001. This file assumes the articles already exist.

Reading a price change file before the articles produces price records with no matching article. They stay in staging without effect.

Next

Topic	Page
Upload a file manually, pick the vendor	Manual Import and Vendor Assignment
Collect files automatically	Automated SFTP Import
Assess and approve staging	Reviewing and Approving Staging
Understand duplicates	Duplicates and Validation
A complete walkthrough with sample files	Example Import