on 01-23-2013 8:50 PM
I have this odd situation and I'm not sure how to resolve it.
We have a component that was added to a nework activity and then deleted. The status is DLT.
The CN33 BOM transfer is a batch job. Something was wrong with the MM BOM and the CN33 batch transfer added then DLT'd the component 3x.
The problem is that MRP still sees demand for this component. I checked table RESB, and there are reservations in there that do not have the deletion indicator set. I am assuming that the deletion indicator should be set on these reservations automatically when the component is deleted from the network.
hopefully the following screenshots tell the story:
CJ20N, notice it was deleted 3x:
MD04 shows 2 requirements (for this network):
Table RESB shows 2 of the 3 reservations are not deleted:
Any suggestions on how to fix this?
There is no standard way to set the deletion indicator for reservations that were generated by the system so we had to create a program that manually set the deletion indicator on these erroneous records. We think it happened because of conflicting validity dates on a BOM. We can't reproduce the error but it has happened 2x in the past year.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please check with MARC table wherin you will get all deleted item RESB table is for reservation only means only for confirm items.
MRP will generate requirement for all BOM items but due to delation flag set it will convert in error.
Regards,
Sanjeev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
9 | |
9 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.