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

MSCM Upload Error

 5 Replies
 2 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Bev Edwards
Veteran Member Send Private Message
Posts: 366
Veteran Member
6/9/2015 1:10 PM

I have several MSCM orders that failed due to one item getting a Unit Cost Required error.

I did find on the IC12 that the replenishment info was missing, so I fixed that. I also went to the PO25.6 and made sure the agreement had been released.

I went back to MSCM and selected the RESEND option, but the order goes from Pending to failed again. Not sure what I'm missing or what I'm doing wrong.

 

 

Stephanie
Veteran Member Send Private Message
Posts: 86
Veteran Member
6/9/2015 1:25 PM
Hi Bev, are the items being ordered stock or non-stock? Also, have these items been received yet?
Stephanie Kowal | skowal@rpic.com
Bev Edwards
Veteran Member Send Private Message
Posts: 366
Veteran Member
6/9/2015 1:32 PM

They are NS and they have not been received because the order failed.

I did notice when comparing the LUM IC12 to other LUM IC12s, that the inventory flag was set to Y instead of N. I tried to change it, but received a message: Cannot change. Item loc exists as a replenishment source.

Sheri
Veteran Member Send Private Message
Posts: 163
Veteran Member
6/9/2015 1:50 PM
Hi, I receive that same error on new ns items that have not been ordered/matched/paid, even when they have a PO25 for pricing. I use a Paint screen to put in the last cost, then I am able to release the orders in MSCM.
Seems the items have to have a last cost in order to be released in MSCM, big fail on Lawson's part.
Me
Veteran Member Send Private Message
Posts: 96
Veteran Member
2/2/2017 9:12 PM
Has anyone found a different workaround outside of a paint screen for this MSCM error?
Kat V
Veteran Member Send Private Message
Posts: 1020
Veteran Member
2/6/2017 8:46 PM
I'm told "faking a change" - go to IC81, put in FC C(Change) and click CHANGE without actually changing any data - once the problem is fixed will refresh MSCM, but the count needs to be redone. That specific record needs to be killed.