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

Posted by Sap Land Friday, 30 December 2011 01:18

Reply from susanhuang on Dec 30 at 4:26 AM

Dear HT

Thank you for your reply.

If this part goods receive from purchasing order. It's OK. but if I use MIGO , MB1A or addon-program post goods issue and reverse from production order, It's always get system mail "Update was terminated ". The other parts would not get error message. I had upgrade to ECC6.0 for three years. I had made enhancement before upgrade. There is one goods issue from production order on OCT. 25,2011 in MB51.

BR,
Susan

---------------Original Message---------------
From: Susan Huang
Sent: Wednesday, December 28, 2011 7:02 AM
Subject: Runtime Dump 'MOVE_TO_LIT_NOTALLOWED_NODATA' in MIGO

Dear Expert

When I post a goods Issue, system show Material document. But, I use MB03 display material document, system shows "Material document not found.". I found a Runtime Error "MOVE_TO_LIT_NOTALLOWED_NODATA" in ST22. It comes in the following statement:-

Error analysis
A new value is to be assigned to the field "<F>", although this field is
entirely or partly protected against changes.

The following are protected against changes:
- Character literals or numeric literals
- Constants (CONSTANTS)
- Parameters of the category IMPORTING REFERENCE for functions and
methods
- Untyped field symbols not yet assigned a field using ASSIGN
- TABLES parameters if the actual parameter is protected against changes
- USING reference parameters and CHANGING parameters for FORMs, if the
actual parameter is protected against changes and
- Accesses using field symbols if the field assigned using ASSIGN is
protected (or partially protected, e.g. key components of an internal
table with the type SORTED or HASHED TABLE) against changes
- Accesses using references, if the field bound to the reference is
protected (or partially protected) against changes
- External write accesses to READ-ONLY attributes,
- Content of a shared object area instance accessed using a shared lock
(ATTACH_FOR_READ).
.............

If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:

"MOVE_TO_LIT_NOTALLOWED_NODATA" " "
"SAPLMBMS" or "LMBMSF00"
"VERBRAUCH_FORTSCHREIBEN_30"
.........

My System environment is SAP-Release 700
I have check SAP OSS notes, but could not get any one.

Please kindly give me a hand.

Thanks,
Susan

Reply to this email to post your response.

__.____._

Manage Settings | Unsubscribe | Create FAQ | Send Feedback