Production Confirmation - Revision history

Dgarratt: Updated by push_wiki.py

2026-04-01T10:00:30Z

Updated by push_wiki.py

@@ 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.
-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.
-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.
-[[file:Production Confirmation2.png|400px]]
+[[Category:Commander4j]]

Dgarratt at 10:26, 23 August 2024

2024-08-23T10:26:53Z

← Older revision		Revision as of 12:26, 23 August 2024
Line 14:		Line 14:
	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.		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.

	[[file:Production Confirmation1.png\|400px]]		[[file:Production Confirmation1.png\|link=\|400px]]


	[[file:Production Confirmation2.png\|400px]]		[[file:Production Confirmation2.png\|400px]]

Dgarratt at 15:30, 22 August 2024

2024-08-22T15:30:14Z

← Older revision		Revision as of 17:30, 22 August 2024
Line 1:		Line 1:
	[[Category:Commander4j ~~Pallet Transactions~~]]		[[Category:Commander4j]]
	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.		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.

Dgarratt at 15:28, 22 August 2024

2024-08-22T15:28:16Z

← Older revision		Revision as of 17:28, 22 August 2024
Line 1:		Line 1:
			[[Category:Commander4j Pallet Transactions]]
	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.		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.

Dgarratt at 13:22, 19 August 2024

2024-08-19T13:22:29Z

← Older revision		Revision as of 15:22, 19 August 2024
Line 13:		Line 13:
	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.		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.

	[[file:Production Confirmation1.png\|~~600px~~]]		[[file:Production Confirmation1.png\|400px]]

	[[file:Production Confirmation2.png\|~~600px~~]]
			[[file:Production Confirmation2.png\|400px]]

Dgarratt: Created page with "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..."

2024-08-19T13:21:01Z

Created page with "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..."

New page

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.

[[file:Production Confirmation1.png|600px]]

[[file:Production Confirmation2.png|600px]]