This application is used by two customers in the wholesales business. Common to them both is they are receiving lots of customer orders via the batch-order entry programs in M3. The two customers wanted to make it easier to handle batch-orders and for one of them, they also needed the ability to make additional changes to the batch-order before they are transferred to actual orders in M3. The application runs in both Smart Office and the H5 client because one of the customers is doing a rollout of H5. So, it was necessary to run the app in two different M3 environments. The application is using the customize table, CUGEX1, where we are saving additional data related to e-com orders. This is related to information not available in M3 standard. With one of the customers, we are also using CUGEX1 to simulate orders upfront of the batch-order. We do check on specific orders if there are available items in stock. Here, we run OIS340MI to simulate a standard M3 availability check and the result is saved in CUGEX1. By doing this, we can show directly in the app if there are available items in stock or not. The main purpose of this feature is to later automate the batch-order entry. But the customer wants a step-by-step action plan to establish the best process in the long-run.
To achieve this, MeC and a customized table are part of the solution. We have also established rules on how to “read” a batch-order in MeC, so in some cases, based on some rules, we stop the batch-order in status 05 to be manually handled within the web app. If the batch-order is in status 05 in M3, no integration whatsoever is done to an actual customer order. This means you can then change the order type, warehouse code, line type, delivery method, and joint delivery code before releasing the order directly in the web application.
There are lots of bookmark functions in the app, and you are working very close to the standard M3 OIS275.