Mass update app
Safe and fast Mass Updates
Traditional mass update tools treat everything as a flat file structure and lack grouping and visualisation of connections between different data types. They also don't do a good job of validating the data before sending it in to M3 for processing.
In our app we expose each data object that you can mass update as a template consisting of a set of fields connected to the data object in question, for example an item or a purchase order line. All these fields have built in validation so that you can’t enter values that aren’t accepted by M3. From this template you as an administrator define task-specific update views for specific scenarios like "planning info update", "catalog info update", "purchasing info update" and so forth. This way the user can only work with the fields needed for the task which ensures that the mass update is handled in a very safe and intuitive way.
As a user you can log the details for why you did the update for auditing purposes. This will then generate a PDF with this text, the user that did the change and when it was done (date and time). This will generate an archive so that you have a complete audit trail of the changes done.
Decision-based mass updates
Current mass update tools lack a concept of decision based update. The impact of this is that you can't work from an analysis-based perspective when working with updates.
A scenario that illustrates this could be the following. You know you have issues with producing the required amount of a specific product for this week, and you know that you can only produce 500 of the 1000 required pieces. In this scenario you would like to search for where you are planning to use this product and see the consequences of an eventual update before you do it so that you can make informed decisions on what customers will be affected. You can perform a search product and see the results grouped per customer that is affected. When expanding the customer you can see the affected customer orders and order lines. You can then make a decision if you would like to do an update or not based on customer priority and so forth. If you in your template have defined that users can work with quantity and delivery date these will be the fields open for updating.