Understanding DATANORM Sets

How DATANORM describes sets and how the app represents them in staging.

What a set is

Many suppliers sell bundles: a shower tray with a waste fitting and a support frame, a heating set with a pump, valves and fittings. In DATANORM the J record describes such sets.

A set consists of a set item, delivered like any other article in an A record, and its lines from J records.

Values in a J record

Value	Meaning
Set number	Article number of the set item the line belongs to.
Line number	Order within the set.
Component article no.	The article that goes into the set.
Component set no.	Filled when the line is itself a set – a nested set.
Quantity	Quantity of the component in the set. 0 means the user decides the amount.
Calling flag	Controls whether the line is included automatically or is an optional line.
Line text	Additional text for the line.

The calling flag

Value	Meaning	Behaviour of the app
1, 3	Line is inserted automatically	always taken
2, 4	Optional line, selected by the user	only with Include Optional Set Lines enabled

See Nested and Optional Lines.

Sets in staging

The DATANORM Part Lists page shows all imported set lines with set number, line, component, quantity and status.

Status	Meaning
New	Imported, not yet turned into a BOM.
Synced	Created as a BOM component.
Skipped	Not applied – for example because the item is missing or the line is an optional line that was not included.
Error	Applying it failed; the cause is on the record.

Import order

A BOM component needs an existing item. So synchronise article staging first and build the part lists afterwards. Otherwise lines are logged as Skipped.

1

Synchronise the articles

Set item and components must exist as items.

2

Build the part lists

Run Build Part Lists on the import session.

3

Check the result

Open Show Part Lists and review the status of the lines.

How this becomes an assembly BOM is described under Building Assembly BOMs.