• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Supply Chain Management Lawson S3 Supply Chain

Mobile Supply Chain - Upload Error

 4 Replies
 0 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Bev Edwards
Veteran Member
Posts: 366
Veteran Member
11/7/2013 5:53 PM
We had 4 items ordered. 3 display a Status of Upload Complete, however 1 of the items had an upload error due to a Unit Cost message.

I was told this morning that none of the items were received.

Would one failed item cause the entire order to not go through?
Sheri
Veteran Member
Posts: 163
Veteran Member
11/7/2013 6:28 PM
Hi, yes it would hold the order up in MSC. The problem being the item is new and does not have a cost. Do you use PO25 ? If the item is in PO25 it would go thru but in MSC the order gets held up when a new item without a system cost.

**Total flaw in the system- which Lawson should fix.
Michelle Wetzel
Veteran Member
Posts: 183
Veteran Member
11/7/2013 7:50 PM
Yes - the requisition is in an unreleased state in lawson because of that one line in error. When this error occurs, I've found a couple of possibilities:

1) the vendor on the par cart doesn't match the vendor on the contract.
2) there is no contract (PO25) for the item

Another problem that occasionally occurs is not having a GL Category on the par cart for the item. This also kicks out an error.

Once you fix any of these errors, you can usually resend it through the MSCM webband.
Bev Edwards
Veteran Member
Posts: 366
Veteran Member
11/7/2013 8:35 PM
I found that this particular item did not have a pricing agreement in place, so I removed it from that bulk cart that it was listed on until it can be resolved.

Thanks everyone  for the feedback. Appreciated as always!
The Alchemist
Advanced Member
Posts: 34
Advanced Member
11/11/2013 3:58 PM
Hello a couple of other things to consider and might be helpful.
If the item is an inventory item (aside from having it loaded in PO25)...
Once it has been received/invoiced a cost is now attached and it will not error.
Or because of the process flow at my previous place I would adjust the item in and then back out with the cost. That also brought in a cost keeping it from turning into an unreleased req.