Supported DATANORM Versions
Which DATANORM versions are read, how detection works and how to recognise the files.
Overview
DATANORM 4.0
yes
yes
Article data is split across an A and a B record that belong together.
DATANORM 5.0
yes
yes
All article details sit in the A record. Recommended version.
Automatic detection
The version is determined from the header record (V record) as the file is read, so you never have to specify it.
The app recognises the version from the shape of the first line that starts with V:
DATANORM 4
The V record contains no semicolon. It is a fixed 128-character line.
DATANORM 5
The V record is semicolon-separated and starts with V;050;.
The header record (V record)
The first data line of a valid file must be a V record. If it is missing, the app treats the file as DATANORM 5 and warns that the result may be wrong for a V4 file.
DATANORM 4 — fixed 128 characters, no semicolon
The V4 header is not a semicolon-separated line. Fields sit at fixed positions. That is how export writes the line, and how import reads the date and currency.
1
1
V
2
1
Space
3–8
6
Creation date DDMMYY
9–48
40
Info 1, usually supplier or file name
49–88
40
Info 2
89–123
35
Info 3 / reserved
124–125
2
Version number 04
126–128
3
Currency, for example EUR
Exact header from the sample delivery (128 characters, ending in 04EUR):
A file with A records appends the article lines after this header. In DATANORM 4 the A and B record belong together; the article lines themselves are semicolon-separated:
This is the first line of the sample delivery (Wannentechnik catalogue).
DATANORM 5 — semicolon-separated
For comparison, the V5 header from the same demo delivery:
Fields: record type, version number 050, data mark, date YYYYMMDD, currency, description.
The key difference
In DATANORM 4 an article is described across two lines: the A record carries description, price and unit, the B record carries additional details such as EAN, match code, catalogue page or copper weight. Both belong to the same article number.
The app merges the A and B record into one staging record. A file with 4,637 articles therefore produces 4,637 staging rows, not 9,274.
In DATANORM 5 those details are already in the A record; there is no B record.
The full comparison is under Differences Between DATANORM 4 and 5.
Files and naming conventions
A DATANORM delivery usually consists of several files with meaningful extensions:
DATANORM.001, DATANORM.002 …
Article data. Numbered sequentially for large catalogues.
DATPREIS.001
Price change only, for articles already delivered.
*.RAB
Discount groups.
*.WRG
Product groups.
Character set
DATANORM files are traditionally DOS-encoded (code page 437/850). The app reads them accordingly so that umlauts in article descriptions arrive intact. Do not open and save a file as UTF-8 in a text editor before importing it – that loses the umlauts.
Last updated
