MES Transactions - Usage in BC

This page is about the GUI side, i.e. the MES Transactions page within BC which is the one that keeps the transactions imported from the MES.

This covers…

how to process these entries and what will the posting method do
how to see if there are some transactions on error
how to archive already processed entries

Setup

There is not much setup to do, in order to start using the MES Transactions.

MES Terminal

Every transaction sent in through the API needs to belong to a specific MES Terminal. Therefore a terminal needs to be created for every system/machine sending in data.

Settings on the MES Terminal include:

Default location on transactions
Default stock center on transactions
Default Stage on transactions
Control if production lot is to be imported from the MES (instead of needing to create in Wisefish beforehand)
Control if pallet barcodes are to be imported from the MES (instead of letting BC generate barcodes)

User Profile

As usually in Wisefish, defaults can be set for following fields on User Profile card:

Location
Stock Center
Stage

Page: MES Transactions

The MES Transactions get all entries imported from the MES with API endpoints.

This is the only page that the user needs to work with on a daily basis.

This following overview mainly lists the columns visible to the user through both the main page and the child page that holds the MES Transaction Lines.

Field List: Transaction

Thi

	Field Name	Type	Description
1	ID	BigInteger	The id of the Transaction After posting, this value will become a connection to the posted trade item, because it will be inherited into field “WP Connection PK” in Open Trade Item and Trade Item Ledger Entry.
2	Date Created	Date	The date when the entry was created.
3	Terminal Code	Code 10	Field “Terminal Code” will say from which manufacturing unit this entry comes from. If there is only one terminal, this can be set up as a default.
4	Ext. Reference	Code 10	The sender must put it’s own reference on every transaction to be able to relate it to the entry in the MES system.
5	Type	Option	Options: Receipt - this can be both received landed (own) items and received purchases Consumption - related to a production lot Output - related to a production lot Shipment Transfer Adjustment
6	Stock Center Code	Code 20	The Stock Center this entry belongs to. All item movements in one transaction must belong to the same stock center.
7	Location	Code 10	The Location to use when the item movements will be posted. All item modifications in one transaction must belong to the same location.
8	Document Type	Enum	Options are the document types of both Wisefish and standard BC, such as Sales Order, Sales Agreements, Fishing Trips etc.
9	Document No.	Code 20	This field belongs to the Document Type field. Shipping and receiving transactions must belong to a document, output transactions can belong to a document but don’t need to. This is explained better in the API documenation for every transaction Type.
10	Lot	Code 10	A transaction can belongs to a lot, but if it does, it is only one lot. At the other hand, when posting consumption, the consumed items will usually belong to different lots which are given on the Transaction Lines.
11	Stage	Code 20	When there is a lot, there is always a Stage as well.
12	Activity Date	Date	Activity Date is the real date of the related event, such as production date, receipt date, transfer date etc.
13	The fields here after are the ones populated after the entry has been created in BC (i.e. not populated by the API request):
14	No. of Lines	Integer (Flowfield)	Drill down this counter to open the Transaction Lines that belong to this Transaction. See next sub-chapter for field list.
15	Status	Option	Options: Ready - the entry is waiting to be processed. It has either just been created, or errors have been removed. Error - the entry has errors, which can be seen by drilling down from “No. of Errors” On Hold - for some reason user has put this entry on hold, it will not be processed automatically Processed - entry is processed, but waiting to be archived
16	No. of Errors	Integer (Flowfield)	A counter from the error list.
17	Error Description	Text (Flowfield)	Shows the first error in the error list.
18	Posting Document No.	Code 20	Where possible, shows the Document No. on the posted entries, i.e. as on the Item Ledger Entries. This is used to do Find Entries, which navigates into all posted entries in BC.
19	Posting Date	Date	Posting Date for this transaction. For an unposted transaction, this can be modified manually if needed before for an
20	No. of Item Ledger Entries	Integer
21	Posted Quantity (ILE)	Decimal

Field List: Transaction Line

	Property	Type	Description
1	Transaction ID	BigInteger	PRIMARY KEY The id of this Transaction.
2	Line No.	Integer	PRIMARY KEY The number of this line, within the transaction.
3	Transaction Type	Enum	Same as on the transaction.
4	Item No.	Code 20	The item number of the line.
5	Item Description	Text (Flowfield)	The description of the item, this is calculated from Item card.
6	Quantity	Decimal	If skipped, the today’s date will be used by default.
7	Unit of Measure Code	Code 10	The unit that goes with the Quantity field.
8	Weight	Decimal	If quantity and unit is not give, the Weight can be used instead.
9	Lot	Code 10	The same lot as on the transaction header.
10	Consumed Lot	Code 10	Only for consumption, another lot must be given.
11	Trade Item Stage Trade Item Line No.	Code Integer	For consumption, this is used to create a relation to a single trade item.
12	Trade Item Barcode	Code	If the trade item is barcoded.
13	Pallet Barcode	Code 20	Pallet barcode, used when the trade items shall be put on a pallet. This pallet might exist, or shall be created when transaction is processed.
14	Pallet No.	Code	Pallet number, must be given when a pallet shall be created.
15	Pallet Status	Option	Give this, to update the status of a pallet when the trade item is put on it.
16	Reserve to Document Type Reserve to Document No. Reserve to Line No.	Option Code 20 Integer	To use when the created trade item shall be reserved to a document immediately after creation.

Actions Overview

At the top of the page there is an action bar.

Action	Description
Error Check	For an unprocessed entry. The action deleted the existing errors and then runs the error check again.
Process	To process the selected entries. Multiple entries can be selected with Shift+down/up and then processed. See chapter below MES Transactions - Usage in BC \| Process Transaction
Process all	Processes all transactions in the list that are not processed, i.e. both with Status = Ready and Error.
Open Document	For all transactions that have a Document Type and Document No., open the page for that particular document.
Find entries…	For processed transactions with a Posting Document No., run the standard navigation page to find all entries that were created by the posting method.
Archive	If archiving of processed transaction is set up to be done manually, this action is used to run it.

Factboxes

There are 2 factboxes that can be made visible:

MES Transaction Info
This shows various information from the entry. Mots of this information is also visible as a column, but for convenience, some columns could be hidden, because the info is also in this factbox.
Lot - Current Totals
This factbox shows total figures for the lot in the active transaction

Process Transaction

This is the main action of this page. Process can be initiated by either…

when user manually clicks Process or Process All
with a Job Queue

This processing method works in a few layers

Error Handling is finished first with any data being modified. After this the Status can become Error. → See below.
If there is no error, the posting of the item transactions is done, i.e. new items created, consumed items, transfers, shipments or whatever the transaction contains. After this, the Status becomes Processed.

Posting Job Queue

Job Queue is created for codeunit WiFiAPIs MES Post Transaction

add photo

Error Checks

Before posting, the error check is run. If there is an error, the transaction will stop with Status = Error and no data has been modified in BC. The entry will wait until someone fixes the entry, or the setup in BC which caused the error.

There is a cue in Wisefish that will show the user if there are some transactions that could not be processed.

Users need to…

Drill down the Error cue
Fix the problems. These might possibly be wrong input data or posting setup missing.
Process the entries - or just set the status back to “Ready” to let the automatic batch job process them.

Posting

After the posting of one transaction the following data changes may have been done in BC / Wisefish:

Lot may have been created (if it did not already exist)
Pallets may have been created (if they did not already exist)
Item Ledger Entries has been created for the trade item(s)
Open Trade Item(s) may have been created or deleted
Trade Item Ledger Entries may have been

The MES Transaction has been updated so now it has:

Status = Processed
Posting Document No. => This creates a direct link from the transaction to the standard BC item ledger.

Archiving

A processed transaction can either be archived directly - or at pre-defined intervals, such as daily or weekly.

After the archiving:

MES Transaction has been deleted
MES Transaction Archive has been created. This table has all the same information as the MES Transaction.