When I try to delete an operation in a Job, i get the following error. Note: There is no labor attached to this operation.
Operation cannot be deleted because has link at least one Part Wip record(Last Activity Date: 3/13/2019). Please run Adjust WIP or Move WIP program before deleting.
Exception caught in: Epicor.ServiceModel
Error Detail
Description: Operation cannot be deleted because has link at least one Part Wip record(Last Activity Date: 3/13/2019). Please run Adjust WIP or Move WIP program before deleting.
Program: Erp.Services.BO.JobEntry.dll
Method: JobOperBeforeDelete
Line Number: 33226
Column Number: 17
Table: JobOper
Client Stack Trace
at Epicor.ServiceModel.Channels.ImplBase`1.ShouldRethrowNonRetryableException(Exception ex, DataSet[] dataSets)
at Erp.Proxy.BO.JobEntryImpl.Update(JobEntryDataSet ds)
at Erp.Adapters.JobEntryAdapter.OnDelete()
at Ice.Lib.Framework.EpiBaseAdapter.Delete(DataRow dr)
at Erp.UI.App.JobEntry.Transaction.Delete()
Operation cannot be deleted because has link at least one Part Wip record(Last Activity Date: 3/13/2019). Please run Adjust WIP or Move WIP program before deleting.
Doesn’t have to be Labor, could be some other Link.
So, I have looked at Adjust WIP and saw nothing. On Move WIP it showed a quantity for the previous Operation. My engineer was in here with me and she said that it could be that because the previous operation is 1 then that would force the next operation to be at lest 1, correct? Thus having a WIP???
Yes, WIP automatically get’s pushed to the next op once the operation is complete. If you look at that part number in part tracker you can see the location in WIP.
Operation cannot be deleted because has link at least one Part Wip record
KB0039422
0 Views
*Product this article applies to:* ERP 10
*Published to customer portal:*No
*Issue*
------------------------------------------------------------------------
When trying to delete an operation an error message shows up
*Error*
------------------------------------------------------------------------
Business Layer Exception
Operation cannot be deleted because has link at least one Part Wip
record( Last Activity Date:
1/11/2018 ). Please run Adjust WIP or Move WIP program before deleting.
Exception caught in: Epicor.ServiceModel <http://epicor.servicemodel/>
*Resolution*
------------------------------------------------------------------------
They system (lower versions) allowed the user to remove operations with
quantity in WIP but this was causing orphaned records in this table
In order to resolve this problem,, the Move WIP is required
Go to:
Material Management, Advanced Material Management, General Operations,
Move WIP
Once there, you would need to enter the job number , select the
operation and add the quantity to move.
Make sure the warehouse and bin fields are showing the desired records
and click ok
*Notes*
------------------------------------------------------------------------
The SCR 181127 was created to address this issue and was applied to
10.1.500, working as designed in this version,
Now you have to move the qty in WIP before delete any operation.
Authored by Miriam Puente
Last modified 2018-04-26 10:03:30
Helpful?YesNo
Show comments
Hide comments
External Permalink <#>
Print This Article <javascript:window.print()>
info:
document.getElementById("info_outputmsg_image").setAttribute('alt',
"Informational Message");Close Messages
To add one more to this, I was able to remove the WIP and delete the operation if the operation was anything but the first. Now I have an job that needs the first operation removed but it is giving the WIP error. However, in Adjust WIP it says there is no WIP on that operation.
not saying I don’t believe you, but I’m going to ask for some proof. Can you show some screen shots? The error, and the part tracker of that part number, and the part numbers (materials or assemblies) that go into it.
Parts that go into it will sit on the first operation of the next level up.
If you do a query on the PartWip table, is there anything on that job/assy seq?
select
[PartWip].[Plant] as [PartWip_Plant],
[PartWip].[PartNum] as [PartWip_PartNum],
[PartWip].[JobNum] as [PartWip_JobNum],
[PartWip].[AssemblySeq] as [PartWip_AssemblySeq],
[PartWip].[OprSeq] as [PartWip_OprSeq],
[PartWip].[MtlSeq] as [PartWip_MtlSeq]
from Erp.PartWip as PartWip
So I’m pretty sure that’s what your problem is. But I don’t know how to fix it. I see some of the same things in our system if I look. I have old job, with wip records sitting out there, and both move and adjust wip don’t work.
I think some of goes back to this thread (sort of related, but not quite what you are dealing with)
I think you might have to just close your job and rebuild if you have to get rid of that operation. Or you can just complete it with no labor on it and move on.
update: If you close your job, the WIP will get cleared out. Then you can re-open it. I can’t test the delete though, because my operation has labor.
They system (lower versions) allowed the user to remove operations with
quantity in WIP but this was causing orphaned records in this table
In order to resolve this problem, the Move WIP is required
Go to:
Material Management, Advanced Material Management, General Operations,
Move WIP
Once there, you would need to enter the job number , select the
operation and add the quantity to move.
Make sure the warehouse and bin fields are showing the desired records
and click ok
