Honeydew release

When processing an outbound instruction (sales order), the preferences from the master were not yet taken into account when processing a new line, this is now done.

Previously, the number of pallets was also filled in for the number of pallet places, the number of pallet places is now calculated separately and stored separately from the number of pallets in the designated field.

The locations to be informed can only receive a receipt confirmation by email if there are also active lines for this in the system. This is to prevent empty emails from being sent.

In FreshBabel Messenger, sending the InboundInstruction is described from:
- sending an inbound instruction to the locations in the purchase order lines
To:
- sending an inbound instruction to the selected locations in GreenCommerce.

As a result, this ensures that the old location can be informed again, since it is no longer available in the purchase order lines.

For the buttons ‘Save and inform producer’ and ‘Save inform a client’, it is checked whether the producer or client may be informed if the correct communication settings are present. If that is not the case, the normal ‘Save’ button becomes available and the other one is not.

The client or producer will not be automatically informed of an assignment that has been completed. However, they can still be informed manually if the assignment is removed from completed. The columns MustInformProducer and MustInformClient are also no longer adjusted when an assignment has been completed.

Older inbox messages are automatically cancelled when a newer message can be imported. The option ‘Cancel old messages’ has been added to the communication settings of the message types, provided that the option ‘Process in order’ is enabled.

If you want to use this option, please contact support.

The ‘End customer remark’ field of an ‘Order’ is now sent with the ‘Production Instruction’ message.

A check mark has been added to the Purchase sales order line(s) screen, ‘Inform receipt location’. If this check mark is checked, the receipt location will be automatically informed when the purchase order is created. The check mark is behind a parameter ‘SaveAndInformDirectly’. If the receipt location does not contain the correct communication settings, the option is disabled. The location’s relationship must be able to send a receipt instruction. If the user does not have the task ‘Inform receipt location(s) about purchase’, the check mark is not visible and the receipt location cannot be informed immediately.

Adjustments have been added to the FreshBabel connector for a check on assignment to the correct order line. When specifying pallet lines on a purchase order, the first specification is on purchase order lines that have the same reference as the Supplier Line Reference. This applies to importing the Delivery Specification. It is therefore still possible to specify on other lines, but only if the correct purchase order line has been fully specified.

The column ‘ServiceRegistrationDate’ in the fact table for service registrations is filled with the StartDate, if filled. For records where the StartDate has not yet been filled, the fallback is to TimeCreated.

By using this date, the data matches the actual start date of the activities on which service registrations are booked.

The fact table for PurchaseInvoiceLine has been expanded with the following extra columns:

• FinancialFixedInstallationID
• CurrencyID
• Rate

The fact table for SubInvoiceLine has been expanded with the following extra columns:

• FinancialFixedEstablishmentID

The fact table for InvoiceVAT has been expanded with the following extra columns:

• FinancialFixedEstablishmentID

There are a number of fact tables that do not start with the word ‘Fact’. In order to give the facts a consistent name, the name of these tables has been changed so that they start with ‘Fact’. This concerns the following tables:

• DateCalendar
• InvoiceVAT
• BatchSalesShare
• AllocationShare

An extension has been made in FreshBabel whereby the LoadingLocation has been added, so that it can be filled with the shipment location of the purchase order line. Also, when importing the inbound instruction in GreenCommerce, an extension has been made with the search for a linked shipment location. If the message is not filled with a shipment location at line level, then the shipment location at header level is only looked at.

For outbox messages, a column ‘SystemReference’ has been added. This column contains a reference to the object this message is based on.

The filtering has been extended for the message status. Previously, you only had the options to see all open messages and including processed. For this, you could check or uncheck the box ‘Including processed’. This has now been replaced by a dropdown menu. With which you can now also search for specific message statuses.

For message types 200 (delivery message) and 300 (invoice) it is now possible to set up additional recipients. If these recipients are also set up correctly in FreshBabel, these recipients will receive exactly the same message as the relation to which the message is sent.

For further setup of this, please contact support.

If multiple locations use the same GLN, none of these locations will be used to link to this GLN. The SenderCode will be used instead. This already happened if there was no location with this GLN.

A new setting has been added to the supplier master data that allows the use of grower location tiers in the planning of purchase transport. When planning a transport order, from the purchase. When planning the transport order from the purchase (based on the lines to be transported), a separate determination can be made for the transport tier that must be used. In this case, the transport tier of the shipment location relationship is suggested for purchase order lines. If there is no shipment location, the supplier tier is still suggested.

If the same tier line is found for all selected transport lines, it is filled in when planning a transport order.

When reading invoices via Blue10, it has been made so that any deviating financial fixed establishments of the purchase order compared to the purchase invoice are updated in the purchase invoice. With a new purchase invoice, the supplier's set preference is automatically applied in terms of financial fixed establishment. If orders are matched that were purchased at a different fixed establishment, error messages will occur when adding purchase invoice lines. Now, as soon as one or more orders are matched, a comparison is made between the standard suggestion from the supplier master and that of the order. The establishment from the order is considered leading and is updated in the purchase invoice so that the match can then be processed correctly.