Jackfruit - GreenCommerce

The Jackfruit release is the final release of 2025 and therefore a mandatory version. This release includes, among other things, developments for dynamic price markups, with a new screen added under ‘Prices’ (behind a module). In addition, it is now possible to define a shipment and unloading sequence for a transportable line. The Jackfruit release also contains developments for the WMS App, Production App, and QC App. Read all the release notes below:

The Producer relationship has been added to the batch as a property. A producer relationship can be entered manually via [Edit] in the batch specification. When splitting batches, a different producer can be selected. When choosing a producer, a preference filter has been added so that only configured producers of a supplier can be selected.

In auction trade with suppliers with different underlying producers, the producer relationship of batches can be suggested. In this case, the shipment location of a purchase order line and the purchase location (= unloading location) of a purchase order line are used. An entered shipment location takes precedence over the purchase location.
The producer can be shipped at order line level via:

  • Excel import
  • Order import
  • Inbound instruction

When you now modify a scheduled order in the Production App or want to schedule a new order, you will see under the standard what the default standard of that item is (if it has been entered in the master data).

When saving a transport order where the unloading time is earlier than the shipment time, a notification appears. If the user selects ‘No,’ an error message with the same text will then appear, to prevent all entered information from being lost.

In the ‘Quick Sales Screen’ (ALT + 6), an option has been added that allows users to manage whether a default quantity should be suggested. The options are [Sellable], [Allocatable], [Directly Sellable], and [Current Sellable].

With this adjustment, users can browse through the list of items and use [ALT + T] to directly add an order line for the suggested quantity. By pressing [ENTER], you remain in the quantity input field, allowing you to adjust the number if necessary. Multiple lines can be selected.

The following input options are available:

  • Single incl. prices
    The existing flow remains unchanged: the quantity can be adjusted per item, and both price information and active suggestions are displayed.
  • Single excl. prices
    Entering quantities remains possible, but no price information is retrieved or displayed. This makes the screen faster to use and assigns a price of 0.00 when saving an order line.
  • Multi incl. prices
    Entering quantities is blocked, and the quantity is derived from the setting (see above). After the order lines are created (with price 0.00), the active price suggestion is then applied.
  • Multi excl. prices
    Entering quantities is blocked, and the quantity is derived from the setting (see above), with a price of 0.00.

When importing outbound instructions and merging them into a single sales order line, only unique remarks are now used. This prevents duplicate remarks in the sales order line. If there are different remarks in the outbound instructions, they will still be recorded, separated by commas.

When multi-editing an item, the following fields have been added:

  • Sorting characteristic
  • Production speed

An adjustment has been made to enable more efficient communication with the database. An assumption has been introduced regarding the number of days that normally occur between shipment and unloading (controlled by a parameter).

By default, it is assumed that there can be 3 days between shipment and unloading relative to the delivery date. If a larger value is needed, this can be configured in ccTransportableLinesSendingMarginToDeliveryDate. This change has also significantly improved performance.

Er is een nieuwe knop ‘Knowledge base’ toegevoegd rechtsonder in het scherm naast de update melding. The Knowledge base verwijst naar een aparte pagina buiten GreenCommerce.

A new screen has been added under ‘Prices’ → ‘Dynamic Price Markups’. Multiple lines can be edited or deleted simultaneously by adjusting the “through” date. An element can be entered to determine the general ledger account during invoicing; if left empty, the system falls back to the element in the parameter. In the dynamic price markup, customers, item groups, and locations can be linked. For item groups and locations, the list can also be treated as “not allowed” or blacklisted. The dynamic price markup then applies to all item groups or locations except those selected.

For a new sales order, the applicable dynamic price markups for the customer on the delivery date are carried over to the sales order (under the ‘Financial’ tab). It is possible to restore all dynamic price markups applicable to that sales order after deletion. A log is available.

When creating a sales order line, the system checks which dynamic price markups of the sales order apply to the item and location of the order line. These dynamic price markups are then calculated and added to the colli price. This is displayed as a single amount in the price calculation. If one of the dynamic price markups is excluded, the amount will differ from the colli price breakdown. Note: the basis for the percentages also changes, so the price may differ from what is expected.

This functionality is behind a module. Please contact us if you wish to use it.

The financial control screen has been expanded with a "Pallet Packaging" tab. This tab shows the pallet packagings that have not yet been financially approved. With the "Approve" button, the pallet packaging and any underlying elements can be financially approved. Not checked = not invoiced. By default, new and copied pallet packagings are marked as not financially approved.

The functions for approving and resetting the status are also available in the pallet packaging overview screen and the pallet packaging management screen. In addition, a filter has been added in the pallet packaging overview screen for financial control status. These developments are behind a parameter "WorksWithFinancialControlMasterData."

The screen where the CBS declaration can be made has been expanded with a setting to export sales orders based on the invoice date.
Note: In this case, sales orders that have not been invoiced will not be exported.

When the user actually exports the data via "Export," the setting of the "Invoice date" checkbox is stored in the user-specific system parameter:

  • CBSDeclarationSalesExportOnInvoiceDate

On the "Extra" tab of a relation, a new field "Fiscal entity" has been added in the "Financial" section. When searching for the desired fiscal entity for a relation, the VAT number and the VAT number country are also displayed. Currently, this field is for registration purposes only.

A new system parameter "CustomerAdvicePriceDefaultRoundingOffFactor" has been created, which allows setting the rounding off of the customer advice price. By default, this is empty and no rounding off is applied in places where it was not previously used.
If it is set, it will be applied to:

  • Taking over the suggested price in the sales order line based on the customer-specific daily price
  • Recalculating sales order lines based on the daily price
  • Default price suggestion when selling a new item (if the customer-specific daily price is set as an active suggestion)
  • Taking over the advised customer daily price in SalesOrderLine (ALT + 5)

A new button, "Change program line prices," has been added to the Sales Order (with tasks MayApplySalesPricesInProgram and AdjustSalesOrders) and Purchase Order screens. The sales order must not be handling, must not be final, and the selection of lines must not include a correction.

For the purchase order screen, the user must have the task MayApplyPurchasePricesInProgram, the system parameter WorksWithsCommercialData must be enabled, and the purchase order must be of type standard, correction, or commission.

When selecting order lines, the correct program lines are searched. The correct program line can be found based on program type (purchase or sales), date (delivery date or price reference date for sales order), company of the order, relation of the order (customer or supplier), and the article of the order line. It also checks whether the colli price matches.

From the QC App, the number of photos added to an inspection report is now sent along. This is stored in GreenCommerce and is visible everywhere inspection registrations are displayed. For this, the column "NumberOfPhotos" can be enabled.

In the purchase order screen, a "buyers" filter has been added. The value of this filter is stored in a user-specific system parameter. In the sales order screen, filters for "sellers" and "account managers" have been added. The values of these filters are stored in user-specific system parameters.

This concerns a development in the Excel import module. For purchase orders imported with type "Credit," all underlying lines are now also marked as "Credit."

Since manually imported credit lines are not linked to element deliveries, the following options have been made available:

  • Manually adjust the price and remark
  • Delete lines
  • In a credit order, any financial differences can be corrected by adding new element lines. These must be elements with the process filter "costs and discounts."

The relation setting to not send corrective invoices by default has now been made generally available in GreenCommerce. This setting can be found on the Customer tab in the relation screen. It is only available if the relation setting "Consolidated invoicing" is turned off.

The screen for manually linking crops to batches is no longer available in GreenCommerce.

Disable of "Sales Forecasts" screen [Sales] and "Supply vs. Sales Overview" screen [Sales]

Disable of "Crop Registration" [Master Data] and disable of UO declaration [Relation Management]. System parameters that have been removed:

  • SafetySheetsFertilizersAttachmentFolder
  • SafetySheetsPesticidesAttachmentFolder

With the introduction of the Data Warehouse module, "Sales Digger" under "Overviews" has been disabled. This also led to the removal of the system parameter "SalesResultDiggerModule."

The "Tracing" screen within the "Overviews" menu has been disabled.

The screen in GreenCommerce that provided information on the status of the ServiceBusConnector (link between GreenCommerce and ServiceBus) has been disabled.

The following system parameters have been removed:

  • WorktsWithCommercialService
  • CommercialRelation

 

A separate "Edit" button has been created to allow the exchange rate to be edited, facilitating tabbing through the fields. This provides a consistent way to enter data. It has been applied in the following screens:

  • SalesOrder
  • PurchaseOrder
  • CostItem
  • PurchaseInvoice
  • PurchaseAdvance
  • SalesAdvanceMutation
  • Program

Various FreshBabel messages have been extended so that gross and net weight are recorded at the pallet level (visible on the pallet card, tab "Weights"). On the pallet line, the average content per colli and average fruit weight have been added.

  • [401] ProductionConfirmationDto
  • [500] InboundInstructionDto
  • [501] InboundConfirmationDto
  • [503] OutboundConfirmationDto

When working with pallet weighings, the pallet weight is also linked to the pallet as the active weight. This makes it possible to add gross and net weight as columns in various screens. Note: the messages include a gross and net weight. The difference between these is the element weight (master data). If a pallet is then split, a different element weight can be used and the net weight may no longer be correct. Therefore, it has been decided to use the net weight for the inbound instruction and calculate the gross weight based on the master data.

The output registration within GreenCommerce has been adjusted so that the extra fields "AverageContentPerColli" and "AverageFruitWeight" on the pallet line can optionally be used.

Per location, it can be set whether pallet lines are selected with these properties. The settings "Content per colli in mutations" and "Fruit weight in mutations" can be used for this. The goal is to select the pallet actually used by the packer.

The fields are filled either by importing inbox messages or through manual entry. This can be done via the "Edit Pallet Data" button or within a pallet line in the "Weights" section.

If an item has no product information, the net weight is displayed in the "Content" field.

An extra field has been added to the finalization form where the average fruit weight can be entered. The field is only enabled for items marked as unsorted bulk stock.

After entering, the value is recorded on the finalized pallet line and also sent to the sales company (if finalized on an order). For pallets booked into stock and later registered via transport with the sales company, the average fruit weight is also transferred when the pallet is created at the sales company.

A new field "Sorting Process" has been added to "Item." The field can be left empty, or filled with "sorted" or "unsorted bulk."

A new supplier-customer setting has been created: "PalletWeightRequiredForUnsortedBulk." This setting is managed by jem-id.

Contact us if you want to use this setting.

In GreenXchange, it is now impossible for a grower to complete a transport if the supplier-customer setting PalletWeightRequiredForUnsortedBulk is enabled. The same applies if the pallet contains an item marked as "unsorted bulk" and the pallet does not have an actively entered weight.

A new menu item "Bulk Bin Items" has been created under "Master Data" → "Item Master Data." Here, all items of type "bulk" can be found. A bulk item can be opened to view various details. Note: Bulk bin items can no longer be found or added in the Items screen.

In the form where pallet weights can be recorded, the average fruit weight can now also be entered. It is not mandatory to fill in a value; if left blank, nothing will be saved. This is managed by jem-id.

Contact us if you want to use this feature.

To process the average fruit weights entered by growers in GreenCommerce, messages (215) are sent from GreenXchange to GreenCommerce. This creates a registration of the average fruit weight for the specified pallet lines. This must be set up by jem-id.

Contact us if you want to use this feature.

In GreenXchange, the determination of load carriers that may be "delivered" has been extended with an additional validation. The check for bulk bins has been enhanced so that items marked as "unsorted bulk" may also not be delivered.
Note: For orders placed with a grower (planned rerouting) of bulk articles, this does not currently apply.

For a transport line, it is now possible to record a shipment and unloading sequence. Additionally, a separate form has been added to manage the shipment and unloading sequence for an entire transport order at once.

In "Transport Orders," the sequence can be edited via right-click in the detail panel. Within a transport order, the sequence can also be edited using the "Edit Shipment and Unloading Sequence" button. These changes are saved immediately.

There is also an option to manually enter the shipment and unloading sequence via "Edit Shipment and Unloading Data" in the transport lines.

De functionaliteit om op sorteerrapporten ook pallets als verbruik te kunnen boeken is uitgefaseerd. De betreffende schermen waarmee dit kon worden uitgevoerd zijn ook uit de sorteerrapport-schermen weggehaald.

A new pallet label has been created, which can be configured per grower. Both the average fruit weight and the pallet weight have been added as separate lines.

Contact us if you want to use this feature.

To prevent incorrect mixes, it is checked at the time of consumption whether a situation arises where items are mixed by sorting process. After a pallet with unsorted bulk stock is consumed, an additional attribute (IsWithBulkItemConsumption) is recorded on the order for easier later recognition. When consumption is reversed, the attribute is recalculated.

In the WMS App and Production App, the average content per colli and average fruit weight have been made visible. In the WMS App, this is shown on the pallet card and when picking or splitting a pallet, and in the Production App, when adding pallet consumption.

For the order, purchase order line, and sales order line, a column "CreatedTimestamp" has been added. The value is recorded when new timestamps are added.

A stock filter has been added to the work order overview in GreenCommerce. It is now possible to filter work orders based on:

  • Production
  • Output
  • Stock

Under "Inventory Management," the menu items "Work Orders" and "Work Instructions" have been made available. This was implemented because work orders can also originate through inventory.

The new menu items can be made accessible to users via roles and components, allowing easy access to these functionalities from the "Inventory" menu.

The work order type with its number is clearly displayed using a chip with corresponding colors.

In the WMS App, a button has been added to switch between the different sorting options:

  • Work order type
  • Deadline

The grouping in the work order overview in the WMS App has been adjusted. The group header above each work order type has been removed, creating more space in the overview. With an indicator and the addition of filter/sort options, the overview of the different work order types remains clear and user-friendly.

Enhancement in the Excel import functionality. For Excel import of orders, additional fields have been added to allow mapping of "custom codes" as columns.

This applies to the following fields:

  • Order: Relation
  • Order: Carrier
  • Order: Handling Relation
  • Order: Incoterm
  • Order: Transport Means
  • Order Line: Item
  • Order Line: Element
  • Order Line: Product
  • Order Line: Crop
  • Order Line: Pallet Packaging
  • Order Line: Shipment Location
  • Order Line: Unloading Location
  • Order Line: Country
  • Order Line: Final Destination

A new task has been added, which is automatically assigned to the role "Transport Employee."

To enable task-driven operations in the warehouse, inventory transfer orders can be scheduled and processed via work orders. The following parameters must be set:

  • PalletRegistration
  • WorkInstructionLicenseCode

From "Inventory Transfer Orders," work instructions can now be generated. These work instructions can then be scheduled in a work order and assigned to warehouse employees, who can process them further via the WMS App. The progress shown in the inventory transfer order overview is based on the progress (NumberInProcess + NumberProcessed) in the work order for the transfer order.

A checkbox "Notify Carrier" has been added to the "Add Transport Instruction" screen. If the checkbox is selected, the carrier will be notified immediately when a transport instruction is added.

The checkbox is available if the user has the task NotifyCarrier. If the user has the UI system parameter SaveAndNotifyDirectly enabled, the checkbox is selected by default.

An enhancement has been made in the Tasks API to process the event `transportplanning-request.ready_for_import`. This concerns the automatic acceptance of a confirmation, specifically transport planning confirmations.

Automatic acceptance does not occur if it is a manual verification action or if the carrier does not have the communication settings for the TransportConfirmation message set to automatic processing. In all other cases, the confirmation is automatically accepted. This setting is managed by jem-id.

The Transport Planning Confirmation has been extended with "License Plate" and "Driver." When creating a transport order (via a transport planning confirmation), these fields are included.

A new task "Generate Transport Orders Based on Instructions" has been created. This allows restricting which users have the rights to generate a transport order via an instruction.

Column chooser added to transport order and transport instruction planning screen, with user-specific column selection saved.

The shipment and unloading dates when scheduling transport are suggested in a specific way. An adjustment has been made to better align with the times already present in the transport lines. By default, the shipment date is determined by the "latest shipment date" and the unloading date by the "earliest unloading date," which remains unchanged.

In the "Add Transport Order" popup, options have been added to adjust shipment and unloading times as well as shipment and unloading references. Right-clicking displays these options for one or multiple selected lines.

In "Transport Instructions," an additional tab has been added showing the planned transport lines.

The visit address has now also been added in "Relation Management – Relation." The label "Visit Address" has been renamed to "Logistics Address."

Enhancements have been made to the filter options in the crop overview screen:

  • The period filter has been replaced with a choice to filter by historical, active, or future crops, with active crops selected by default.
  • Filtering by product group is now possible.

In the sales order line, there are two calculators. In both calculators, the first block breaks down the item daily price based on the standard element prices, and the second block rebuilds the daily price based on the specific relation prices of the elements.

In the first block, the description always shows the standard price. In the second block, the relation price is now displayed if it differs from the standard price; otherwise, the standard price is shown. This makes the descriptions more readable.

The batch suggestion functionality has now also been added to the inventory planning screen, similar to assignment in a sales order line. Based on the sales requirement set on the sales order (line), it is determined whether a batch is suitable. Suitable batches are shown in green, unsuitable batches in red, and unknown batches (suitable/unsuitable) remain white.

A new supplier setting has been created to automatically schedule imported purchase orders in a transport instruction. This applies to FreshBabel or Excel import templates. The carrier from the order is used for the transport instruction, defaulting to the supplier’s standard carrier if none is specified. The master data settings are used for the transport rate. For transport instructions created this way, the carrier is notified immediately.

Er zijn geen release notes met dit label gevonden.

Stay up-to-date

Please subscribe to our newsletter and be the first one to be up-to-date about GreenCommerce.

Subscribe now