Functionality blocking/validation in Webapp
Scenario:
Workshop staff are utilising the GRPO, WO Receipt, WO issue functionality in the BEAS WebApp. There are controls that are required from the business process to provide a block with popup alert box on these transactions if they exceed the planned amount.
For example,
a) A business rule is to block the GRPO transaction if there is an over receipt, or at least prompt.
b) A business rule is to block over-receipt of a work order.
Issue:
There is block capability to prevent partial backflush/issue, however over-receipting does not appear to be locked down.
Solution:
It would be a good resolution to allow some additional configuration settings/flags to turn on off the ability to over-receipt in these functionalities for the WebApp.
-
This is still an issue, especially for the WO receiving in multiple steps via WebApps. As soon as there is more then one WO receipt via WebApps, the planned quantity can be over receipt.
This also has an impact on the backflushed components as not always enough material is available and this leads to more errors.
It would be great to get an update on the above post.
Please sign in to leave a comment.
Comments
1 comment