New Features in G5, version 22.5
Here's a summary of the major new features in version 22.5 of MONITOR G5, broken down by our teams that specialize in developing each area of the system. We hope you'll find this useful. For more information on all new development and changes in this version, read the Changelog at monitorerp.com/changelogs. There you also can watch a video rundown of the major new features in this version.
During this sprint we’ve been focusing a lot on issues, so the quantity of completed development is not so high.
Weight calculations from material rows in BOM and routing is now copied to the manufacturing order. It can be seen in Manufacturing order info, and edited in Register manufacturing order.
Via the document setting "Show weight calculation", you can select to print weight calculation data on the manufacturing order documents.
A new way of reporting material has been introduced in the Web client. This method was already available in the Desktop client.
For your active operation you can select to report the appropriate amount on all material rows for a simulated operation quantity. This is useful when you want to report the material before you report the operation.
The team has resolved 65 issues, of which 49 were reported by customers.
During the next sprint, we'll finish the functionality for clocking Site in the mobile recording terminal. After that, we can deliver this to our customers. For now, we are testing it on our own Monitor production system.
During this sprint we’ve been focusing mainly on Customer Order Transfer (COT) with configuration, and some additions to variable receiving inspection. The team members working with COT will work with other tasks moving forward.
In Register customer agreement, we have added the setting "Create basis for" to determine how many years of the agreement basis that will be created when the agreement becomes Active. Previously, it was only possible to create agreement bases for one year ahead. This can be useful if you want to invoice several years ahead.
When setting "Valid to" date in the agreement header, all agreement bases are now created ahead to this date.
When adding a serial number on an agreement, it will now be possible to view this in the event log in the Serial number/Batch procedure.
A smaller, but highly requested feature is to see the customer's part number on the order row. This is now possible in the procedures Register quote and Register customer order. The customer’s part number, which is taken from the customer link, is now found under "More info" in these procedures.
Changing the customer order status on the order header will now update the status on the customer order row. We have also added the Row status as a visible field under the Rows tab in Register customer order.
The field Create delivery note number when delivery planning is now available as an editable presentation field in the Customer list, via the procedure backstage and list type Standard.
It is now possible to select on "Delivery note number" in Order list – Purchase. We have added Delivery note number as an available selection field in the procedure backstage. To be able to see what you selected, we also added Delivery note number as an available presentation field.
An invoice is often expected to contain free text; text that you have entered in Document texts. This is the case when using, e.g., factoring. Text entered in Additional texts on documents at the Additional texts tab, in the Document texts procedure, is now exported in the customer invoice format. The texts are exported in the XML element DocumentText, added in version 5 of the EDI format for customer invoice.
Some shipment agents (e.g., Ahola) require a payment reference to be specified when the receiver pays the freight. We have added a folded button with a Payment reference field, adjacent to the Freight payer field. The folded button and payment reference field is only active if Freight payer is Purchaser pays.
We have also added a new column in the Delivery terms tab in the Terms procedure. Here it is possible to set a default value for the payment reference.
Since we have now added Payment reference and recently added Delivery date as new fields to the shipment, we have made these fields available as presentation fields in the Shipment list backstage.
As when using the information source, Customer, the information sources Pick list and Pick list with package structure now take into account the Communication section in the Customer register, so that when creating a shipment we:
Remote configuration copies
When you make copies of a row with a remote configuration, we now create a copy of the configuration with a new configuration ID in the remote company.
This happens when you:
We now create a text row with the configuration result in the sales company. The text is generated by the remote configurator in the same way as in the production company, but uses the language from the mailing address on the quote/order in the sales company. This makes it possible to get a text row on quotes, and on customer orders in the correct language and before they are transferred.
Some smaller fixes have been made to the UI.
If you have parts with serial numbers, the serial numbers are normally generated in the production company and transferred to the sales company when delivery is reported in the production company.
There is now a new option to transfer the serial numbers to the sales company already when the order is created in the sales company. This is useful if you want to show the serial numbers to the customer on the Acknowledgement. This was a customer request.
The team has resolved 64 issues, of which 44 were reported by customers.
During the summer sprint we will focus on adding a new list type, where it will be possible to compare the sales statistics against budget. Beside this, we'll also make some adjustments in Register customer agreement. We also plan to add a setting where it will be possible to select if the Delivery planning should consider Qty/pkg or not.
Beside this we will focus on:
We have managed to close 40 issues (48 support cases within issues and development items) in the May sprint. Our developers have been working very hard, and we managed to close a lot of development features.
A new field "Finish date" on the case has been developed, which can be useful for either planning when a case should be done, or to see when it was actually closed. When the status is set to “Finished” the finish date is set; but it can be changed.
We have now added support for multiple parts on a case. The parts are now visible in printouts and the case list (through a new list type). This makes it easier to see how many parts are linked to the same case.
You can now see the name (in a separate column) for the column customer/supplier/main part in the planning window.
It is now easier to handle batches and serial numbers with scanning in Stock count in list. New settings have been added so that every stock count can be more optimized for its purpose, scanning parts, batches or serial numbers. The new settings are:
The sales forecast now supports Staggered prices. When running the procedure it is possible to select to show staggered prices.
In total we have closed 57 development items during the sprint, which are a mix of country specific developments as well as standard functionality and UI/UX improvements.
In previous versions, the exchange rate type to be used was set per module. The rate type per customer and supplier is now specified. If necessary, you can also let the order type determine which rate type is to be used.
With the help of different exchange rate types, you can manage parallel exchange rates for the same currency, such as a variable USD exchange rate and a fixed exchange rate. But you can also set unique rate types that are to be used for individual customers/suppliers.
A new list type, Detailed – VAT row, has been added. In this list you can analyze and view more detailed information about the records (vouchers and invoices) that the VAT report is based on. This can be done for any time period, even for periods reported already. This report shows the details grouped/totaled per VAT row. You can select the report on a number of different concepts, such as customer, supplier, date, VAT code, etc.
The list also shows the customers and suppliers' VAT registration numbers, in case they need to be checked. If the system is set to report VAT based on the VAT code in general ledger transactions, it is also possible to update the VAT code on the transactions directly in the list.
When you work with the percentage of completion method and use the price alternative "Continuous with profit mark-up", another field for profit mark-up has been added in basic data-project, where you enter your percentage for the profit mark-up. It is possible to override this on the project.
When you use this price alternative, a new Mark-up tab in basic data-project is also activated, where you can enter exceptions per cost type. If you want the system to automatically update the forecast on the project based on costs incurred and mark-ups, specify the type of revenue to be used for the automatic update on this tab. The profit mark-up will now be used in the profit calculation.
We have developed two areas in the list type, Payment suggestions. Both developments are linked to the payment format ISO 20022, which is more stringent regarding negative/zero amount per supplier.
The first area is that the setting "Exclude suppliers with negative remaining amount" has changed logic, whereby suppliers with zero in remaining amount will also be excluded, and the setting has been renamed to "Exclude suppliers with negative/zero in remaining amount".
And the second area is that we have added a setting for displaying credit invoices awaiting final recording. It is not possible to include credit invoices that are not yet final recorded, but you will receive the information about these invoices in the authorization flow at an early stage. Since the entire credit invoice has to be covered when sending the payment suggestion to the bank, you can better deal with the credit invoices when informed at an early stage.
The purpose of the new list type is to review and update postings for purchase orders. Only orders with remaining amounts are displayed in the list. Both accounts and dimensions can be updated in the list, and you can also use Find and replace. Mass update of accounts can, for instance, be useful in the transition to posting the stock against the stock account on the balance sheet, instead of on the cost account.
Imported Credit invoices are displayed in their own inbox, "Register credit invoices" in the Register supplier invoice procedure, until they are registered. Previously, these invoices weren't displayed in the Invoice overview – EIM procedure, but now, a new EIM status, "Register credit invoice", has been implemented, which can be used as a selection term in the list type "Current status in Workflow".
During this sprint we have closed 72 issues, of which 17 have been patched and 38 are linked to support cases.
Performance improvements have been made in the Invoicing log and in Register supplier invoice when loading supplier invoice from CrossState.
During the next sprint we'll be focusing on the following development:
In this sprint we've once again had a lot of focus on resolving issues. As well as continuing work with MSSQL, reducing database sizes, and overall improvements such as extra fields on operation rows, new ways of searching in pickers and a lot of important backend work.
Around 40 issues have been resolved in this sprint. These include:
In the next sprint, we'll be focusing on improved functionality regarding time zones, making it possible to use Find & replace in extra fields, and making further improvements to the Lookup. A big development worth mentioning is the Client filtering improvement, which will make it clearer for the user to know that it's not only the filtered out, visible, data that may change when saving, but all listed rows that have changes.