This page lists the messages Innova can send into the Inbound from Innova table (WiFi Inbound from Innova), and what Wisefish MES Connect does with each one. The mapping is in codeunit WiFiAPIs MES Get Innova Data (23014840). How the MES Transactions are posted is described in the MES Transaction documentation.
Applies to all messages
-
Nothing is done unless Innb.Innova to MES is Active is set in setup. An Innb.Innova MES Terminal must also be set up.
-
The entry is created on the setup's MES terminal. Ext. Reference = the inbound
LineNo. Stock Center is mapped fromProducerID. Location is mapped fromWarehouseID, or is the terminal's production location if blank. -
ItemIDis mapped to a BC item no. through Data Mapping, if Data Mapping is active. -
If Ignore Packet Id is set,
PacketIDis not copied (otherwise it becomes the Trade Item Barcode). -
When handled, the entry is moved to Flushed Inb. from Innova and linked to the MES Transaction ID. Messages with other IDs stay in the inbound table untouched.
Message types
The example bodies use the field names on the Inbound from Innova page. The values are taken from test entries in the demo company. 108 and 122 have no test data yet, so their examples are made up.
|
Message Type |
ID (soapId) |
How it works |
Example body |
|---|---|---|---|
|
Production (output) |
107 |
Creates an Output MES Transaction with one line.
|
JSON
|
|
Production of palletized and reserved item |
107 |
Same as Production above, but the packet is placed on a pallet and reserved to a Sales Agreement line.
|
JSON
|
|
Production credit (reversal of output) |
123 |
Creates an Output MES Transaction marked Credit. The quantity and weight on the line are given a negative sign. The body is the same as the original 107 entry it reverses.
|
JSON
|
|
Palletizing |
111 |
The items have already been produced; this message only puts them on a pallet (and reserves them if an agreement is given). Creates a Shipment MES Transaction with one line.
|
JSON
|
|
Sales line (item on a Delivery Agreement line) |
120 |
Creates a Shipment MES Transaction with one line, reserved to the Sales Agreement line
|
JSON
|
|
Receipt |
108 |
Creates a Receipt MES Transaction with one line, for a standard BC Purchase Order (Receipt Agreements are not supported).
|
JSON
|
|
Consumption |
122 |
Creates a Consumption MES Transaction with one line.
|
JSON
|
|
Production started (In process at MES) |
300 |
No MES Transaction is created; only a status is updated.
|
JSON
|
|
Production finished (MES finished) |
301 |
|
JSON
|