Pallet History

From Commander4j
Revision as of 20:10, 19 August 2024 by Dgarratt (talk | contribs) (Created page with "600px In addition to performing the role of recording the history of a SSCC, the database also uses the Transaction Ref in the first column to drive the interfaces. If you look at the transactions above for example you will see one of the rows is described as a PROD DEC CONFIRM and in the "Ref" column you will see a transaction number - 13 in this example. If we assume that the interfaces have been configured and running then when the pallet...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

In addition to performing the role of recording the history of a SSCC, the database also uses the Transaction Ref in the first column to drive the interfaces.

If you look at the transactions above for example you will see one of the rows is described as a PROD DEC CONFIRM and in the "Ref" column you will see a transaction number - 13 in this example. If we assume that the interfaces have been configured and running then when the pallet was confirmed the system would have passed this transaction number to the interface module. All the information required in the output message can be derived by the interfaces looking at this entry in Pallet History.

See Interface Admin