Skip to main content

Barcode Register

Every code Businessflo generates for a record, and every existing code linked to one, is written here once. When that code is scanned later, this register is asked first, and its answer is final.

Where
Barcode Register (OSBP)
Who uses it
The implementation consultant and the supervisor
When
To see what a code belongs to, to count reprints, to void a code
Needs first
A code generated, linked or printed on some screen

What it is for​

Nobody types lines into this screen in normal work. The system fills it in three ways:

  • Generate barcode on a document registers the code that was built against that document.
  • A scan with a LINK action registers a code that is already on the goods, such as a supplier's or a carton's barcode, against the record that is open.
  • The first print of a label from a Print link or a print icon, such as a batch label, registers that label so its prints are counted.

That registration is what makes a generated code safe to scan. The engine does not have to work out from the characters what the code is. It finds the code in the register and reads off the record.

It also answers three everyday questions. What does this label belong to? How many labels have been printed? Is it still valid?

Printed labels are counted, not looked up

A label printed from a Print link is registered with Entity Type LABEL, only so its prints are counted. A scan of it is not answered from here. It is read by the nomenclature rule for its prefix, and the record is found through Barcode Identity.

A linked code names the item

A code linked on the item screen is registered with Entity Type ITEM and the item number as Entity Key. A scan of it is answered as that item, exactly as if the item's own code had been scanned.

Every field, in plain words​

FieldWhat it meansWhat to put in itNotes
BarcodeThe exact characters in the codeFilled by the systemRequired. Must be unique. This is what a scan is compared with
Human ReadableThe text printed under the barsFilled by the systemFor a GS1 code it shows each identifier in brackets
Issued From ScreenThe screen the code was generated onFilled by the system
DocumentThe document number it was generated forFilled by the system
Entity TypeThe kind of thing the code stands forFilled by the systemA code generated for a document is DOCUMENT. A linked code takes the kind of the screen it was linked on, such as ITEM. A printed cell label is LABEL
Entity KeyThe key of the record it stands forFilled by the system
UnitThe pack the code stands forA carton or pallet unit, or emptySet it on a linked carton or pallet code. A scan of the code then adds a line in this unit instead of single items
NomenclatureThe rule book it was built withFilled by the system
SymbologyThe printed formFilled by the system
Legal EntityThe company that issued itFilled by the systemA scan finds the code when this is the scanning user's company, or empty
Print CountHow many labels of this code have been sent to printFilled by the systemGoes up by the Labels to print each time Print is pressed in the label dialog. Opening or generating counts nothing
Last PrintedWhen it was last producedFilled by the system
VoidThe code is withdrawnTick to withdraw itA void code is no longer found by a scan. The line stays, as the history
Void ReasonWhy it was withdrawnA short reason

How to configure it​

There is nothing to configure. To use the screen:

  1. Open it and look the code up by the Barcode, or by the Document.
  2. Read Issued From Screen, Document and Entity Key to see what the label belongs to.
  3. To withdraw a label that must no longer work, tick Void, give a Void Reason, and save.

Scenarios​

A label was damaged and must be printed again​

Open the document and press Generate barcode again. The system finds the code already issued for that record and gives the same code back. The dialog is headed Existing barcode. Print it, and Print Count goes up by the labels sent. The new label matches every label already out there.

Goods arrive with the supplier's barcode on them​

Link the supplier's code to the item once, by scanning it on the item screen with a LINK action. See Barcode Assignment. The code then appears here against the item. If it is a carton's code, put the carton's unit in Unit and save.

A label was stuck on the wrong goods​

Open the code here, tick Void and write the reason. From then on a scan no longer finds it in the register.

The same code is needed for a different record​

The system refuses, saying the code is already live against the first record and must be voided before it is issued again. Void it here first.

What it is connected to​

  • Barcode Assignment produces the lines here: its Template builds the code that is registered, its LINK action records an existing code, and its PRINTCELL links count printed labels.
  • Legal Entity must have Barcode Enabled for a code to be generated at all.
  • Barcode Identity is asked only when this register has no answer.

If something looks wrong​

  • "that code is already live against" another record - the same characters are registered to a different record. Void the old line first.
  • "A voided label still does something when scanned" - the register no longer answers for it, so the engine went on to the Barcode Identity resolvers and one of them matched the characters. Check which resolver.
  • "A printed batch label is not listed here" - it has not been printed from its Print link yet. It is added on its first print.
  • "Print Count did not go up" - the label was printed again from the browser without pressing Print in the label dialog. Only the dialog's Print counts.
  • "Print Count went up but nothing was printed" - the count is taken when the print window opens, even if it is then cancelled.
  • "A carton code adds single items" - Unit is empty on its line here, or the order's lines have no unit beside their quantity.
  • "The code is here but a scan does not find it" - it is void, or it was issued by a different legal entity from the one the user is logged in to.