Production Confirmation

From Commander4j
Revision as of 17:28, 22 August 2024 by Dgarratt (talk | contribs)

A pallet (SSCC) can be created within the Commander4j database by 2 main methods. The Commander4j software can create the record when it prints a label, or it can be inserted via a message from an external system, such as an automatic labeller.

When a pallet is created in the database it can have a "Confirmed" or "Unconfirmed" status.

So what is the difference ?

If you confirm a pallet when you print the label or set the confirmed flag in the inbound message from the external system Commander4j will generate an output message which can be used to update an external ERP system. Basically tell the ERP that a pallet of product x has been against Process Order y.

You might decide however that you want to verify that a pallet exists (physically) before sending a message to an ERP system. This step might be wise if there is any possibility of labels failing to print properly.

When you print a label from Commander4j or accept a message from an external system you have the option of leaving it as Unconfirmed.

Your will then need to confirm the pallet which can be done using a Wireless Mobile Barcode scanner, or by using the desktop application as shown below.