Discover the developments of GreenCommerce - Raspberry - GreenCommerce

Raspberry

We kick off the second quarter of 2021 with a new GreenCommerce release; the Raspberry version. The Raspberry is not a mandatory release. This release includes developments for the packaging module. For example, a new screen has been developed that shows the expected stock per element for the coming days and weeks. The GreenCommerce Quality Service has also been expanded with the option to offer inspections to + receive inspection information from a new inspection application. Read all developments below:

Filter

 

A link has been set up between GreenCommerce and AFAS, and focuses in particular on the exchange of financial process data such as purchase and sales invoices. From the invoice export screen + the purchase invoice export screen in GreenCommerce it is possible to change the export status for one or more invoices.

Are you interested in this link? Then contact us.

In order to be able to give financial follow-up to a packaging (fust) delivery, it has been expanded with an option to credit it. An outgoing package delivery will result in a purchase and an incoming package delivery will result in a sale. These order lines come in an order of a new type, namely “Credit”. Orders of the type “Credit” have no logistical consequences, so the purchase order line does not have to be reported in and the sales order line does not have to be shipped, the container delivery is the logistics part of the order.

It is possible to use a basis for a cost item of the entire weight of an order, including separate elements and separate pallet packaging. The cost item is then distributed in the same way as in the current situation among the parties that are present in the order. This concerns the gross weight.

The status of the customs export declaration is updated to "accepted" or "refused" based on the feedback received from Scope (for processing customs export declarations). When the declaration has been released, the MRN number will also be known and will be updated in GreenCommerce. In addition, the EX-A or EU-A document will be placed with a customs export declaration.

In order to establish at a sub-location that a separate logistics service provider is used for the logistics process of storage, the system must be aware of this party. This can be recorded in the field “Logistics partner”.

 

It is possible to inform the logistics service provider separately from the production department about a production order that is going to be run. It is possible to announce goods that are needed (for order picking / outbound) and goods that will be produced (for inbound). The reference is the job ID as known in GreenCommerce.

It is possible to inform the logistics service provider via FreshBabel Messenger about the pallets that will be received from stock for production.

In order to be able to control movements of pallets in GreenCommerce, it is now possible to create “StockRelocationOrders”. "StockRelocationOrders" can be created at different levels.
- On pallet level from the screen “Pallets in stock”.
- At assignment level from the assignment screen.
- At the purchase order line level from the screen of the purchase order line.
- At batch level from the screen of the batch and / or batches in stock.
- On item level from the stock screen.
In the screen of the "StockRelocationOrders" (menu item: Stock management>, <Stock relocation orders>) the open relocation orders of the active company are displayed by default. By means of the filter settings, the already completed relocation orders can also be viewed. Relocation orders can also be deleted and handled manually here, whereby the number is made equal to the number that has been relocated at that moment.

The CSV export that is generated from the invoicing module has been expanded with an extra column in which the currency code is written. In addition, the invoice amounts for the invoice, invoice lines and VAT lines have been adjusted in such a way that they are exported in foreign currency value.

A difference was found when creating the invoices, when working with sub-invoice lines and packaging tax. Normally, any rounding differences on the product of an item are captured, but because the packaging tax does not contain a product, these differences were therefore not captured. When exporting the invoice, this could cause a difference between the total invoice amount and the addition of the sub-invoice lines.

To counter these differences, the packaging tax is no longer exported as a sub-invoice line from now on.

The trade invoice is substantively based on the language of the business partner that is recorded in the proforma. For documents where "lines" (item / element names) are written to the database, it is now possible to set a different language per relationship. The "rules" will then be translated into the language that is set instead of the language of the relationship for whom the document is intended. For the proforma, invoice and commercial invoice, it is possible to set a different language in the document settings for a business partner. When an invoice is subsequently created, the invoice lines are created in this language.

In the header of the EDI message: INVOIC is the segment VATPER in which the VAT (BTW) percentage of the invoice is indicated. A new trading partner setting has been created for this message, making it possible to influence the VATPER in the header of the message. This makes it possible to specify 21% in the header while the lines contain percentages of 0, 9 and 21.

Customs has indicated that for Great Britain use can be made of the same arrangement as that used for the EFTA countries (Iceland, Liechtenstein, Norway and Switzerland). It has been made possible to send an EU-A declaration to Scope instead of an EX-A.

The result report is provided with cultivation information and a type of result (from the shipment). This is used for external links.

The IDs of both customs and KCB sales order declarations are stored. This ensures that multiple KCB and customs declarations can be submitted for one sales order.

Due to the bundling of order lines in the KCB declaration instead of orders, more information is now stored with the KCB declaration. These were previously removed from the order. It concerns the following fields:
- Importer
- Destination Country
- Destination region
- Export date
- Transport loading date and time
- Transport reference
- Description

When creating a KCB declaration, this information is extracted as much as possible from the linked orders of the order lines. If the information of all orders is the same, this will be suggested. If this is not the case, it will have to be entered manually. A consequence of this extra data is that a new screen has been developed in which the KCB declaration can be viewed. In this screen all data can be viewed and adjusted as long as the declaration has not been sent. Associated sales order lines can be viewed and associated documents managed.

In order to properly keep track of the data that is sent to e-CertNL, a number of fields have been added to the KCB declaration in issue 35459. These are now used in communication towards e-CertNL. The consignee of the shipment in the communication is now the importer of the declaration instead of the customer of an order.

As soon as KCB declaration no longer takes place at order level, a new place must be found to store the associated document numbers and PDF documents for archiving. When the KCB declaration has been sent to e-CertNL and it is accepted, the KCB document and the Phyto document can be requested. These are now recorded in the KCB declaration on the "Documents" tab. Previously, this happened with the order.

In order to be able to process the suggestion for the export administration for an importer (not mandatory), it has been made possible to register an importer with a sales order.

The existing screen [Export administration] has been transformed into a screen that works from a planning perspective. The screen provides an overview of all orders and transport orders that are sent to a country outside the EU and offers the possibility to create compositions based on the underlying order lines for both KCB and customs declaration. If you want to create a KCB or customs declaration, the ticked order lines in the bottom or top block are used to bundle into one declaration. This can therefore concern order lines from multiple sales orders or 1 transport order. It is also possible for the user to make a sub-selection so that only part of the order lines are bundled (by ticking). By choosing [Save], the declaration is only saved, by choosing [OK] the declaration is also sent directly to e-CertNL or prepared for shipment (customs declaration).

For the items to be reserved it has been made possible to copy them, making it possible to add the same multiple times. After copying, the user can adjust the ratio.

An extension has been made in the FreshBabel Messenger - GreenCommerce connector with which, in addition to the customs export declaration confirmation, the associated documents can also be shared with the import agent.

As a solution it was decided to add two separate messages with which data about the import confirmation (806) and documents about the import confirmation (807) can be fed back by an import agent. Both message definitions have been added to FreshBabel Messenger and GreenCommerce. In GreenCommerce, the reference of a processed import confirmation is written to the corresponding declaration.

The master data of CBS groups has been expanded with the option of recording more specific input commodity codes (also known as TARIC). The starting point is that the CBS code is the same as the commodity code (also known as the CN code) that is used for exports from the EU. The import commodity codes can be managed directly and when creating new groups, you can choose to link items to an import commodity code (TARIC). The selection of items is based on the items that have the same CBS group.

To make building the commercial invoice easier, two extra columns have been added to the proforma line table: Commodity code and Commodity codeInput. Both columns are filled for commercial invoice type proformas.

It has been made possible to save the grade and the storage advice of the inspection report and the inspection report lines in the GreenCommerce Quality Database.

It is useful when lines of packaging deliveries / shipments are immediately visible in a shipment schedule, without having to open the shipment schedule. In the screen of the “Planned shipments”, the “Packaging deliveries” have been made transparent.

A column “Reference” has been added to the screen to view the changes in a packaging balance. This column shows the reference of the object that can be found by making the combination between the Type and ID column.

Because a customs export declaration no longer covers one or more sales orders, an adjustment has been made in the services that request "rules" based on customs declaration.

For the processing of customs declarations using different currencies, the correct value can be determined by means of a rate calculation towards the customs of the country of import and export. In GreenCommerce, the management of currencies has been expanded through a new tab in which customs rates can be managed. For help, a calculation is shown so that you know what to enter here. In this example, the export rate is therefore known to be calculated from EUR → GBP.

A link has been made with Auction Hoogstraten to exchange digital messages via FreshBabel Messenger.

For the following buttons it is necessary that the system parameter “Quality functionalities” is on:
- Sending inspection requests
- Requesting inspection reports
- The overview screen of all inspections

In the screens of the Purchase Order, Purchase Order Line, Batch and Sales Order, a button has been added to create an inspection.

The GreenCommerce Quality Service has been expanded with the possibility to:
- Offer inspections to a new inspection application
- Receive inspection information from a new inspection application

The reference from the inspection application can be received from a submitted inspection. This reference can be recorded in GreenCommerce during the inspection.

The GreenCommerce API has been expanded to include calls and processing of inspection data, the API can now handle the additional data between the GreenCommerce database and the GreenCommerce Quality Service.

A new screen has been created in which all created inspections are displayed. The screen can be found under [Inspections] → [Quality inspections]. This screen shows the created quality inspections that fit within the settings of the filter. If an inspection is selected, the rules of the inspection are shown at the bottom of the screen. It is also possible to resend an inspection from this screen to a quality application or to view a created inspection report.

Packaging batches go from stock when they run at 0. This ensures that the stock screen is no longer so 'heavy'.

A new screen has been developed that shows the expected stock per element for the coming days and weeks. This screen can be found under Stock management => Packaging stock per day.

In this new screen, the elements for which the stock must be registered are shown. The forecast inventory is shown for the days of the current week and for the 7 weeks after the current week. It is possible to filter the screen by element, element group and locations. It is also possible to choose to hide zero lines. If the expected stock falls below the minimal supply of the element, the quantity will be displayed in red.

Two changes have been made to the packaging stock, the column “Rolling” has been expanded with “Rolling future”, this depends on the setting “Exclude future reservations” in the filter settings. As a result, the “Rolling” column deals with future numbers like the other columns. The column “Rolling” is now also added to the column “Expected stock”.

A milestone has been reached on the element stock to inform the user(s) if stock is below a certain level.

No more negative elements can be purchased. This provides the fact that the packaging mutation Event gives a message.

The framework has been updated to .NET Core 3.1

The last used filter setting per user is remembered at the checkmark of “Exclude future reservations” in the packaging stock screen.

 

From the ccElements screen it is possible to open the packaging registration settings for 1 or more elements. In these packaging registration settings it is now possible to divide the base stock among the stock holding locations. These base stocks per location are also made visible in the ccElement screen under the tab “Packaging registration”. In addition, the balance relations from the tab “Packaging registration” have been moved to a new tab “Packaging balance” and the tick to switch the container registration on / off has been moved to the general screen above.

In the tab “Stock-keeping locations” of the Packaging stock screen, an indication (!) Is now also given per location when the element falls below the set base stock for that location. In addition, a new column “Base Stock” has been added, which shows the set minimal stock for that location.

In addition to checking whether packaging has come under the total base stock, it is also checked whether packaging has come under the base stock of a location. In the Workflow Management, a distinction can then be made by means of the “IsOnLocation” field whether the element has ended up under the total base stock or under the base stock of a location.

A date filter has been added to the screen to view the changes in the packaging balance. By default, this is set to the last month, but of course if the user wants to look further back that is also possible.

In addition, each pallet of a shipment was previously shown as a mutation. These mutations are now shown as one mutation of a shipment.

In the overview of the elements a new task item has been added “Add packaging balance relations”. With this button multiple relations can be added to multiple elements, with the attribute “IsRegistration”, at the same time. In this way no relations can be deleted, for this the user must be in the element.

No release notes were found with this label.

Stay up-to-date

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

Subscribe now