2015 Oct 01 4:06 PM
Dear experts,
I'm using the above mentioned bapi (also tried BAPI_SALESORDER_CREATEFROMDAT2), but it ends with the short dump MOVE_TO_LIT_NOTALLOWED_NODATA in program SAPFV45P. As far as I have checked, the data apperars to be OK (I even created a sales order manually from Tx SE37, using the same data, but programatically it failed).
the short dump occurs in program SAPFV45P, include FV45PFAP_VBAP_FUELLEN_VBAPKOM, routine VBAP_FUELLEN_VBAPKOM.
I also searched over the notes database, but haven't found this dump related to that program.
Some components' versions: SAP ECC 6.0, SAP_APPL 617 004, SAP BASIS 740 006.
As a side note: we were having some problems related to disk space, several days ago. I don't know if that might be related.
Have you come across this error while trying to create a sales order? Any hints or tips would be appreciated.
Regards,
Sergio Pereira
Dear experts,
I'm using the above mentioned bapi (also tried BAPI_SALESORDER_CREATEFROMDAT2), but it ends with the short dump MOVE_TO_LIT_NOTALLOWED_NODATA in program SAPFV45P. As far as I have checked, the data apperars to be OK (I even created a sales order manually from Tx SE37, using the same data, but programatically it failed).
the short dump occurs in program SAPFV45P, include FV45PFAP_VBAP_FUELLEN_VBAPKOM, routine VBAP_FUELLEN_VBAPKOM.
I also searched over the notes database, but haven't found this dump related to that program.
Some components' versions: SAP ECC 6.0, SAP_APPL 617 004, SAP BASIS 740 006.
As a side note: we were having some problems related to disk space, several days ago. I don't know if that might be related.
Have you come across this error while trying to create a sales order? Any hints or tips would be appreciated.
Regards,
Sergio Pereira
2015 Oct 01 4:11 PM
It usually happens when an importing parameter is getting changed.
you can check if you are trying to change any import parameter.
2015 Oct 01 5:33 PM
Can you send the code while making the call to the FM: BAPI_SALESORDER_CREATE?
2015 Oct 01 9:54 PM
But in which field / line does this happen exactly? It should be related to a specific field value and this information should be in the short dump.
If you are saying that it works in SE37 but doesn't work in program then what could possibly be different? Could it be a data type in your program? Or a value conversion?
Just think about it.
2015 Oct 02 3:43 AM
Hi, thank you all for your promptly replies.
I found the cause of the problem: there were two customer fields in the structure EXTENSIONIN, such fields were not included in the structure VBAPKOZ. This article helped me identify the issue:
The structure Extensionin was not used during the test in SE37, that's why it didn't failed as it did in the program
Regards
2015 Oct 02 2:27 PM
Glad we could play the cardboard programmer here. If this is answered, kindly close the discussion - see this blog:
http://scn.sap.com/community/support/blog/2013/04/03/how-to-close-a-discussion-and-why