Example Import

A complete walkthrough with sample files – from product groups to the price change.

This walkthrough shows the whole flow on a manageable data set. It works well for onboarding new users and for sign-off after configuration.

Run the walkthrough in a sandbox environment. It creates items, price list lines and BOMs.

Starting point

The walkthrough uses a small sample delivery of around 25 articles:

File	Contents
DATANORM.WRG	Product groups
DATANORM.RAB	Discount groups
DATANORM.001	Articles with prices and long texts
DATPREIS.001	Price change of roughly +10% on the same articles

Preparation

1

Check the setup

Default vendor, item defaults and number series are set, see Base Configuration.

2

Units initialised

DATANORM Setup → Initialize Units has been run.

3

Duplicate handling on review

Set Duplicate Handling to Mark for Manual Review so you see the mechanism during the walkthrough.

Step 1: Import the groups

Import DATANORM.WRG first, then DATANORM.RAB. Both files are small and processed in seconds.

Then check DATANORM Product Groups and DATANORM Discount Groups. The descriptions should appear as plain text.

If the discount groups all show 0%, that is not an error. Many suppliers do not include their terms in the file, see Discount Groups.

Step 2: Import the articles

1

Import

Import DATANORM File, pick DATANORM.001 and confirm the vendor in the dialog.

2

Look at the session

The import session shows the version, the vendor and the number of records processed.

3

Check article staging

Open article staging. Spot-check description, unit, list and net price and the product group. Umlauts must be rendered correctly.

4

Approve and synchronise

Approve the records and synchronise. Then open one of the new items and check the base unit of measure, posting groups and the extended text.

Step 3: Write the purchase price list

Run Write Purchase Price List on the import session. The app reports how many price lines were written.

Open the result with Show Purchase Price List. You see a price list for the vendor with one line per article. Details under Purchase Price Lists.

Step 4: Build the part lists

If the delivery contains sets, run Build Part Lists and then open Show Part Lists. An assembly BOM with the set's lines appears on the set item. See Building Assembly BOMs.

Step 5: Import the price change

1

Note the price beforehand

Note the purchase price of one article from the price list.

2

Import DATPREIS

Read in DATPREIS.001, choosing the same vendor.

3

Check price staging

Price staging shows the new prices with their price indicator and validity date.

4

Write the price list again

Run Write Purchase Price List and look at the article you noted. Its price is now roughly 10% higher.

Sign-off checklist

✓	Check
	Product groups and discount groups have plain text descriptions.
	The article count in staging matches expectations (not double, for V4).
	Umlauts in article descriptions are correct.
	Every new item has a base unit of measure.
	Posting groups are populated.
	The long text appears as an extended text on the item.
	The purchase price list has one line per article and is assigned to the right vendor.
	Sets appear as an assembly BOM on the set item.
	After the price change the new purchase price is correct.

To test behaviour with large catalogues, use a full delivery of several thousand articles. That exercises background processing, see Import Process.