RE:[sap-log-mm] Runtime Dump 'MOVE_TO_LIT_NOTALLOWED_NODATA' in MIGO

Reply from susanhuang on Jan 4 at 3:55 AM
Dear Dave

I got it. I compare material master forecast data with the other material. I found "Period Indicator" value "K" is different from the other material. So I changed old value "K" to new value "M". and then I posted good issue successfully.

Thank you very much.


---------------Original Message---------------
From: Dave Thornburgh
Sent: Wednesday, January 04, 2012 1:51 AM


Trust me when I say that Ha Tran (HT) does indeed read before posting. I find it very likely that HT did an OSS search and found the note listed - and therefore chose to believe the OP's note search might have been less than optimal. It's actually the same thought I had.

Susan -

You mentioned that you had enhanced the code prior to your upgrade. You might want to take a hard look at the process in the debugger to see why this one material is causing you fits. Before diving into a marathon session there, though, you might want to go through the master data with a microscope to see if there's anything unique about it - and don't ignore the forecast data, just in case.


Reply to this email to post your response.
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
Copyright © 2012 and message author. 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Mark as helpful
View this online
Ask a new question
In the Spotlight for iPhone & Android: Ask Questions & Get Answers Anywhere. Download the Free App


0 Response to "RE:[sap-log-mm] Runtime Dump 'MOVE_TO_LIT_NOTALLOWED_NODATA' in MIGO"

Post a Comment