This can be happen if mobile user don’t have access to this location. And also if these parts has been unreserved and used in another work. Could you please check both of those scenarios?
This can be happen if mobile user don’t have access to this location. And also if these parts has been unreserved and used in another work. Could you please check both of those scenarios?
I did check this. The two location on the transport task is the default warehouse for my mobile user. So they have access. Also, the part is currently reserved on the transport task for the said work task, so it has not been consumed by someone else.
This can be happen if mobile user don’t have access to this location. And also if these parts has been unreserved and used in another work. Could you please check both of those scenarios?
I did check this. The two location on the transport task is the default warehouse for my mobile user. So they have access. Also, the part is currently reserved on the transport task for the said work task, so it has not been consumed by someone else.
Then it seems bit strange. Can you try following steps in order to figure it out the cause?
- Try “Receive” and check whether you are getting the error
- Try with another part and check
This can be happen if mobile user don’t have access to this location. And also if these parts has been unreserved and used in another work. Could you please check both of those scenarios?
I did check this. The two location on the transport task is the default warehouse for my mobile user. So they have access. Also, the part is currently reserved on the transport task for the said work task, so it has not been consumed by someone else.
Then it seems bit strange. Can you try following steps in order to figure it out the cause?
- Try “Receive” and check whether you are getting the error
- Try with another part and check
Hi @Dakshinie , when I press receive I don't get the error
@Dakshinie, So I believe I have narrowed down the issue. Currently IFS MyStock does not show items with an availability < 1. Almost like a default permission set filter. When I manually receive the part, obviously it’s in mystock (Can see this in IEE) now (my default WHSE) but I don’t see it in mystock in mwo, even though I have an on hand and the reservation is for my work order. Is there a way to see MyStock items in mWo with an availability of zero? Is there a setting I am missing?
@ctaylor56 If availability is > 0 then it should be shown in my stock. But if availability is < 0 then it will not be shown in mobile. Because my stock show part which mobile user have.
@ctaylor56 If availability is > 0 then it should be shown in my stock. But if availability is < 0 then it will not be shown in mobile. Because my stock show part which mobile user have.
I think there is a definite bug in IFS then for issuing reserved material from mWo when the only in stock item you have is reserved to one of your work tasks. @Dakshinie can you try and recreate?
@ctaylor56 I have tried in our core environment, and this works fine with the only in stock item have is reserved to one of work tasks. This may be an environment specific issue. Please raise a case with environment details, if you are expecting to investigate this further.
@ctaylor56 I have tried in our core environment, and this works fine with the only in stock item have is reserved to one of work tasks. This may be an environment specific issue. Please raise a case with environment details, if you are expecting to investigate this further.
Thanks @Dakshinie , I am currently prototyping in a Race environment but when we receive our actual Apps10 build I will raise a case then.
Can you do one more test in your core environment. can you place an item not in your my stock as required material (demand) in mwo. Then from IEE do a manual reservation with a move reservation to the mobile whse (which should create a transport task line). Then do a receive and issue from mWo .
I did find that if you initialize, and re-try the receive and issue the error no longer occurs. Tells me something is missing in the sync rules. Case opened with IFS.