Merge-same-WO-in-Manufacturing-Project

ERPAG 5.1

Merge same WO in Manufacturing Project

manufacturing project
_________________________________________________________________________________

1. Introduction

In companies that use multilevel BOM, in the manufacturing project, the data is usually displayed in relation aka 'tree view'. In practice, it happens that the identical work orders show up, because their position in multilevel BOM is different. Depending on the production process, sometimes it's more optimal to merge the identical work orders. We are leaving summarizing, or merging, to be the operator's choice because the mutual relations can be really complicated. In this short instruction, we will work with an example above.
_________________________________________________________________________________

2. Detection of the identical work orders

ERPAG detects the same work orders in the projects by itself. If it's possible to merge the work orders, on the right side of the output items we will have a "call to action button" with a sum symbol (Greek letter Sigma).

merging work orders

In our example from the picture, the following work orders are identical:
WO-000003 = WO-000007
WO-000001 = WO-000005
WO-000002 = WO-000006

This mark/button won't show up on the first identical work order, but on the second, third one etc. (this is because of the performances of the system).
_________________________________________________________________________________

3. Merging the work orders

By activating the call to action button we have a choice whether we will add the activated work order to the identical one, or vice versa - load the identical work order in the activated one.

loading-merging work orders

If we have three or more identical work orders, the question will always be regarding the first generated work order.
_________________________________________________________________________________

4. The result of merging

Since the data is mutually connected, when the work orders are merged, the relations are transferred as well. The work order that is added or loaded will permanently be deleted from the database. Only the work orders with the status-planned, entered or approved are possible to merge.

merging work orders

In our example, we merged WO-000003 and WO-000007. Work order WO-000003 is deleted and his relations are transferred to WO-000004. If we want to merge the child work orders as well, it's necessary to use the merging option on them as well.

The result of our example:

same work orders merged

5. Conclusion

This is an advanced option, it takes a bit more attention and devotion from the operator's side, if he is sure he wants to merge the same work orders. Later it will be a bit difficult to follow up with the mutual relations, because they are not the same as they were in the original BOM.
_________________________________________________________________________________

2019. ERPAG Inc.

0 comments:

Post a Comment