Production Confirmation: Difference between revisions

Latest revision as of 12:00, 1 April 2026

Production Confirmation is the process by which a pallet — identified by its SSCC barcode — is formally matched to a Process Order. Confirming a pallet tells Commander4j that the product has been manufactured and recorded against the order, and triggers an outbound message to notify any connected ERP system.

How Pallets are Created

A pallet record is created in one of two ways:

Label printing — when Commander4j prints a pallet label, it creates the SSCC record automatically and sets its status based on the system configuration.
External system — an external ERP or WMS can insert pallet records into Commander4j via the XML interface.

Depending on configuration, a newly created pallet may be set to either Confirmed or Unconfirmed status at the point of creation.

Confirming a Pallet

An unconfirmed pallet can be confirmed through two routes:

Desktop Application

The Pallet Admin screen in the desktop application allows supervisors and administrators to search for pallets and confirm them individually or in bulk. This is useful for corrections and exception handling.

Web Scanner Interface (c4j_web_react)

The primary method on the shop floor is through the web scanner interface, accessed from a handheld barcode scanner or tablet browser. This is the most efficient method for operators confirming pallets as they come off the production line.

The scanner workflow proceeds as follows:

The operator logs in and selects Production Confirmation from the menu.
The Production Confirmation screen displays an SSCC input field and a running count of confirmations made in the current session.
The operator scans the SSCC barcode on the pallet label.
The system validates the SSCC, matches it to its Process Order, and marks it as Confirmed.
The confirmed count increments. Any validation error is shown in a yellow message bar.
The operator continues scanning the next pallet.

Variant screens exist to support additional validation steps at some sites:

Screen	Purpose
productionConfirm.jsp	Standard SSCC scan and confirm
productionConfirmPlusDU.jsp	Validates a Despatch Unit (DU/tray) barcode against the expected material and process order before confirming
productionConfirmPlusSSCC.jsp	Two-step confirmation requiring both a DU scan and an SSCC scan

What Happens on Confirmation

When a pallet is confirmed:

The pallet record in `APP_PALLET` is updated to Confirmed status.
A record is written to `APP_PALLET_HISTORY` capturing the before and after state.
An outbound Production Declaration Confirmation message is generated, which can be consumed by a connected ERP system to update stock or order progress.

Unconfirming a Pallet

Pallets can be set back to Unconfirmed from the desktop application if a correction is needed. This also generates an outbound Production UnConfirm message to notify the ERP system of the reversal.

Confirmed Count

The web scanner session tracks a running confirmed count — the number of pallets confirmed since the operator logged in or last reset the counter. This gives the operator immediate feedback on progress against a production run without needing to query the system separately.

@@ Line 1: / Line 1: @@
-[[Category:Commander4j]]
+Production Confirmation is the process by which a pallet — identified by its SSCC barcode — is formally matched to a [[Process Orders|Process Order]]. Confirming a pallet tells Commander4j that the product has been manufactured and recorded against the order, and triggers an outbound message to notify any connected ERP system.
-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.
+== How Pallets are Created ==
+A pallet record is created in one of two ways:
+* '''Label printing''' — when Commander4j prints a pallet label, it creates the SSCC record automatically and sets its status based on the system configuration.
+* '''External system''' — an external ERP or WMS can insert pallet records into Commander4j via the [[Interface Message Formats|XML interface]].
+Depending on configuration, a newly created pallet may be set to either '''Confirmed''' or '''Unconfirmed''' status at the point of creation.
+== Confirming a Pallet ==
+An unconfirmed pallet can be confirmed through two routes:
+=== Desktop Application ===
+The Pallet Admin screen in the desktop application allows supervisors and administrators to search for pallets and confirm them individually or in bulk. This is useful for corrections and exception handling.
+=== Web Scanner Interface (c4j_web_react) ===
+The primary method on the shop floor is through the [[Web_Applications_Overview|web scanner interface]], accessed from a handheld barcode scanner or tablet browser. This is the most efficient method for operators confirming pallets as they come off the production line.
+The scanner workflow proceeds as follows:
+# The operator logs in and selects '''Production Confirmation''' from the menu.
+# The '''Production Confirmation''' screen displays an SSCC input field and a running count of confirmations made in the current session.
+# The operator scans the SSCC barcode on the pallet label.
+# The system validates the SSCC, matches it to its Process Order, and marks it as Confirmed.
+# The confirmed count increments. Any validation error is shown in a yellow message bar.
+# The operator continues scanning the next pallet.
+'''Variant screens''' exist to support additional validation steps at some sites:
+{| class="wikitable"
+|-
+! Screen !! Purpose
+|-
+| productionConfirm.jsp || Standard SSCC scan and confirm
+|-
+| productionConfirmPlusDU.jsp || Validates a Despatch Unit (DU/tray) barcode against the expected material and process order before confirming
+|-
+| productionConfirmPlusSSCC.jsp || Two-step confirmation requiring both a DU scan and an SSCC scan
+|}
-When a pallet is created in the database it can have a "Confirmed" or "Unconfirmed" status.
+== What Happens on Confirmation ==
-So what is the difference ?
+When a pallet is confirmed:
-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.
+* The pallet record in `APP_PALLET` is updated to '''Confirmed''' status.
+* A record is written to `APP_PALLET_HISTORY` capturing the before and after state.
+* An outbound '''Production Declaration Confirmation''' message is generated, which can be consumed by a connected ERP system to update stock or order progress.
-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.
+== Unconfirming a Pallet ==
-When you print a label from Commander4j or accept a message from an external system you have the option of leaving it as Unconfirmed.
+Pallets can be set back to Unconfirmed from the desktop application if a correction is needed. This also generates an outbound '''Production UnConfirm''' message to notify the ERP system of the reversal.
-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.
+== Confirmed Count ==
-[[file:Production Confirmation1.png|link=|400px]]
+The web scanner session tracks a running '''confirmed count''' — the number of pallets confirmed since the operator logged in or last reset the counter. This gives the operator immediate feedback on progress against a production run without needing to query the system separately.
+See also: [[Pallet Admin]], [[Pallet History]], [[Despatch]], [[Interface Message Formats]], [[Process Orders]], [[Web_Applications_Overview]]
-[[file:Production Confirmation2.png|400px]]
+[[Category:Commander4j]]