I am working in a project where we are doing a lot of work in the Usability area, and one challenge we got was that there was a need to be able to add a reason code when the customer creates corrective invoices in M3.
How can we solve that without modifying the Java code? The answer is creating a jscript and use the custom extension tables to store the data.
When you create a corrective invoice you change price/quantity on the lines, and then you approve. Our jscript will open a popup window when we do the approval, and in that box you have to choose a reason code.
The available reason codes are taken from CRS103, reason codes. We are using CMS100MI to get the codes. CMS100MI is a new API, available from 13.3, for which you create your own API-transactions.
When you click save, the data is saved in CUGEX1, which is one of the custom extension tables that was introduced in 13.1. Since there are standard API:s available for add/change/delete records in CUGEX1, we don´t have to code any API:s on our own.
To be able to view the reason codes we have created a mashup, but we will also use the data in reports. Below you can see a part of a mashup, where we see the lines from the corrective invoice, combined with the changed values, the reason codes and who did the change from CUGEX1.
This is one example of how you can create really good solutions combining the new Infor tools. More examples will follow, so keep reading the blog!