Legal Entity barcode switch
Three fields on the company decide whether it may generate barcodes, which rule book its generated codes follow when a screen names none, and what every generated code starts with.
What it is for
Legal Entity is the company record. This page covers only its Barcode group. The rest of the screen is not barcode setup.
The group answers one question per field. May this company generate barcodes at all? When a screen does not name a rule book, which one do this company's generated codes follow? Should every code this company generates start with the same characters?
Every field, in plain words
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Barcode Enabled | The company may generate barcodes for its records | Tick it | With it off, Generate barcode on any screen answers "barcode is not enabled for this company - switch it on in Legal Entity". It is checked when a code is generated for a record. It is not checked when a code is scanned, and not by the Print links on grid cells |
| Default Nomenclature | The rule book used to build a code when the screen's assignment line names none | A nomenclature from Barcode Nomenclature, or leave empty | Used only when a code is generated. Order: the assignment line's Nomenclature, then this field, then DEFAULT |
| Barcode Prefix | Characters put in front of every code this company generates from a template | A short fixed text, or leave empty | Added in front of the whole built code. It is not added to labels printed from a grid cell, which have their own prefix on the action line |
When a code is scanned, the rule book is the one on the screen's assignment line, and if that is empty, DEFAULT. The company's Default Nomenclature is not consulted for reading. If the company must read with its own rule book, put that nomenclature on each process line in Barcode Assignment.
How to configure it
- Open Legal Entity and bring up the company.
- In the Barcode group, tick Barcode Enabled.
- Leave Default Nomenclature empty to build codes with
DEFAULT, or choose the company's own. - Fill Barcode Prefix only if every generated code must carry a company marker. Remember that a nomenclature rule must then exist that reads a code with that prefix.
- Save.
Scenarios
Two companies share one database and must not read each other's labels
Give each company its own Barcode Prefix. Then give each company a nomenclature whose rules expect that prefix, and name it on the process lines of that company's Barcode Assignment.
The company only scans supplier labels and never prints its own
Barcode Enabled can stay off. Scanning does not check it. The company still needs its Barcode Assignment document with Scan Enabled lines.
What it is connected to
- Barcode Nomenclature supplies the value of Default Nomenclature.
- Barcode Assignment is the next thing checked after this switch when a code is generated: the screen needs a process line with Generate Enabled.
- Barcode Register receives a line for every code generated for a record.
If something looks wrong
- "barcode is not enabled for this company - switch it on in Legal Entity" - Barcode Enabled is off for the company the user is logged in to.
- "A scan still works although Barcode Enabled is off" - correct. The switch gates generation only.
- "Generated codes are not recognised when scanned back" - the Barcode Prefix was added but no nomenclature rule expects it, or the scanning screen's process line names a different nomenclature.