Delete delivery short dump. Message me803

I am trying to delete a delivery created in 2012, for which pgi is not done.
Short dump occured. Someone help how to rectify this.

Hi
Did you search in Google before posting this query? This has already been discussed many times.
Check these links and see what Jurgen has suggested.
When ME 803 is triggered?
ME 803 - quantity not completely distributed | SCN
Thank$

Similar Messages

How to delete the short dump list in st22

Hi all,
i want to clear the runtime error list in ST22.
How to clear the list of short dump in ST22.
is there any T.code kindly suggest
thanks in advance
Sundar.c

Dear Sundar,
By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing
Goto u2192 Reorganize in ST22. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump u2192 Keep/Release in ST22.
The short dumps are stored in table SNAP. If there are too many entries in table SNAP, problems can occur during the reorganization (see SAP Note 11838). There are different options for deleting short dumps from table SNAP:
1. Call transaction ST22. Choose Goto u2192 Reorganize. You can now specify that all short dumps older than n days old (default 7) are to be deleted. If a very large number of records are deleted at once during the reorganization,
ORACLE error ora1562, failed to extend rollback segment ..., can occur. In this case, see SAP Note 6328.
2. Dropping and recreating table SNAP with the database utility (transaction SE14): you can use this transaction to drop and recreate the table SNAP. This means that all short dumps are deleted.
3. The reorganization program RSSNAPDL deletes old short dumps in pieces (to avoid database problems) from table SNAP. It deletes short dumps that are not flagged for retention and are older than seven days old. Schedule this program at a time of low workload, as large changes in the database are to be expected. The program RSNAPJOB performs a standard scheduling: it starts the program RSSNAPDL every day at 1:00 a.m.
4. TableSNAP is also automatically reorganized. At every short dump that occurs in dialog (the dump is displayed immediately after it is created), a maximum of 20 short dumps that are older than 7 days old are deleted from SNAP. This reorganization should be sufficient in normal production operation.
Hope this information resolves your error and also more useful in the feature.
Thanks
Kishore

BAPI_GOODSMVT_CREATE short dump while posting a GR for inbound delivery

Dear Experts,
I am using BAPI_GOODSMVT_CREATE to post a goods receipt for a PO using Inbound Delivery
here is how I am populating bapi input parameters:
lw_goodsmvt_code-gm_code = '01'.
lw_goodsmvt_item-deliv_numb = lw_inb_delivery_items-delivery.
lw_goodsmvt_item-quantity = lw_inb_delivery_items-deliv_qty.
lw_goodsmvt_item-entry_qnt = lw_goodsmvt_item-quantity
lw_goodsmvt_item-no_more_gr = ''.
lw_goodsmvt_item-move_type = '101'.
lw_goodsmvt_item-mvt_ind = 'B'.
lw_goodsmvt_item-STGE_LOC = '0001'.
    lw_goodsmvt_item-po_number and   lw_goodsmvt_item-po_item are populated as well.
When I execute the BAPI I get the short dump
Message Class: 'VL'
Number = 143
in the module MB_POST_GOODS_MVT and a reference to 385830 note.
Would you please help me how to solve this problem?

from the dump the error orrcurs here:
CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
        EXCEPTIONS
          error_message = 4.
As soon as we have started to put things into UPDATE TASK, we must
ensure that errors definitely terminate the transaction.
MESSAGE A is not sufficient because it can be catched from
external callers which COMMIT WORK afterwards, resulting in
incomplete updates. Read note 385830 for the full story.
   IF NOT sy-subrc IS INITIAL.
>      MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
                 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    MESSAGE A263.
   ENDIF.
The short text of the error is: Cannot be processed with this transaction.
Can you tell me if my BAPI Call is correct to post GR in Inbound Delivery?

Short Dump in rfc call in background

Hi All,
I am getting an RFC error short dump in a background program the short dump message says "RFC_ERROR_SYSTEM_FAILURE: no system found in another group for import queue", the same RFC works fine in foreground and in another background program. I looked into the target system, there is no dump generated.
I tested it in one system it works fine but in another it generates a short dump. I am trying to understand why this is happening any inputs are welcome.
Thanks in advance,
Barjinder

It has been resolved the called FM was raising an exception and it was not captured in the calling FM.
Thanks to all.

SAP Short Dumps and PCI Compliance

We've run into an issue with our PCI Compliance audit around being able to see unencrypted credit cards in short dump messages in SAP. Has anyone run into this issue?
Only work around I've got at this point is to restrict all access to short dumps and require many documented signoffs before turning on and off access to a short dump. This is pretty cumbersome, and still leaves a hole in my overall security.
We've managed to purge restricted CC data from our XI logging, and done everything right with encryption, but this short dump issue just doesn't seem to have a solution.
Can anyone help? We're on 6.0.
Thanks!

Hi David,
This is an interesting situation you have described. ABAP short-dumps or run-time errors as they are also known as, are unhandled exceptions during program execution. The conditions that cause such exceptions is unknown or cannot be handled at run-time. To help analyze what went wrong with the said program during execution, it is necessary for the dump to contain all possible information including data values passed between programs when the error occurs. Encryption of restricted data values is a program step in itself. If the dump were to occur after this step then of course it would contain encrypted CC info. Unfortunately in your case it exposes restricted CC info because the dump occurs BEFORE this step.
I don't believe there is a way to prevent this from happening -- for the same reason that the program logic does not know at run-time how to "handle" the exception. If occurrences of such dumps is fairly common in your system, you may want to investigate the likely causes -- for example, missing or incorrect customization. Analyzing the short dumps will probably give you a clue. Your customization team may be able to identify a pre-condition that causes this unhandled exception. If this exception can then be handled (via a program change) that returns a meaningful error instead of a short dump you would be able to close the security hole. This however entails modification to SAP standard code. I don't usually recommend such changes, but given the sensitive nature of your data it may be worth consideration.
I personally advocate restricted access to ST22. The steps you have undertaken to enforce this may be cumbersome despite efforts to keep it simple. I suppose that's the price we pay in administering the system. If you have not already done so, you may also want to ensure that short-dumps that contain restricted CC info are not saved (using the "Keep" feature in ST22) for easy retrieval at a later point in time or they are saved, it be available only to 'restricted eyes'. Short-dumps are normally saved in the system for 7 or 14 days (not sure of exact # of days). The bigger challenge in my opinion is: How do you prevent the restricted info from being viewed by the user who during the course of program/transaction execution encounters the said short dump? No amount of security controls around ST22 will mitigate this risk. The only option that remains is program change (as mentioned above). But to get there you first need to know what causes the exception.
Regards.
Ashutosh

Short dump in update rules

I removed from my comm structure some objects that I didn't need there.
Some of them are not connected in the datasource to any field, they just get filled in the update rules by routines. Others just weren´t used anymore and already out of the cube. Since that when I extract the info to the cube, the requisition freezes in the end of update rules waiting for final response.
I re-activated the comm structure, the datasources, the cube, but the update rules gives me a short dump:
Message type x
Msg classe RSAU
N.º 001
Var 1 " "
Var 4 " "
The termination occurred in the ABAP program "%_T0ITS2" in "INSTANTIATE".
the main program was "SAPMRSAU"
The termination occured in line 0 of the source code of the (Include)
program " "
of the source code of program " " (when calling the editor 00).
Did this happen to someone?! Or knows what could bwe the problem?!
Thank you
Joã

Thank you for forcing me to go there once again.
I was looking at my routines, and forgot to check the formulas.
Had a calculated key figure with one of that objects. By correcting this I also correct other error. 2 in 1 :-D
Thankx

Dump "Message X" when converting plan.order in APO (Operation classified)

Hello,
We are using master recipes. One operation is classified with work center class type 019 assigned. Operation is classified with two values so I get two alternative modes in APO PDS.
I can drag and drop between alternative modes in the Planning Board, and then save so I can see the mode change also in the order processing view for example.
However when I am triggering the conversion of planned to process in APO then order is never converted. An error queue appears in the qRFC inbound monitor in ERP stating that a short dump has occurred
Short dump "MESSAGE TYPE X" Information on where terminated
Termination occurred in the ABAP program "SAPMSSY0" - in "%_ORDER_FORM_LEVEL". The main program was "SAPMSSY1 ".
Thanks in advance
Carlos

Hello Carlos,
Have you updated alternative resources with the values in the user fields of the operation. ?
Also assign the work center class for the operation (same class which you have assigned for the work centers)
Best Regards,
Roopesh
Edited by: Roopesh Menon on Feb 17, 2011 9:55 AM

Short dump while loading Hierarchy flat file

Hi gurus,
i am trying to load data from flat file to hierarchy, when i am trying to schedule the InfoPackage its giving message a dump :-
"ASSIGN_LENGTH_0" C
"SAPLRRSV" or "LRRSVU10"
"RRSV_INT_CHA_VAL_SPLIT"
These are the steps i followed.
1 created a ZINREGION
2. enabled hierarchy of ZINREGION and included ZINCOUNTRY as external characteristics.
3.and then created infosource and assigned DataSource and created hierarchy and created InfoPackage.
4. selected the hierarchy in InfoPackage, which was created by clicking the hierarchy structure in DataSource and transfer structure.
5.when i scheduled the load in InfoPackage i got above short dump message.
I FOLLOWED THIS BLOG
/people/prakash.bagali/blog/2006/02/07/hierarchy-upload-from-flat-files
thanks
Sathya Pathapati

Hi Philippe,
The processing step, as I could see in the status tab of the monitor, is ".Service API" I am not sure if this is what you are asking for. If not, please let me know what you want me to check for. Below is the description I have in the Status Tab.
InfoIdocs missing; file system
Diagnosis
InfoIDocs are missing. With the file system as source system, the IDocs are created in BW. As this did not happen there was probably a short dump in BW.
System response
No end-confirmation arrived in the Warehouse from
Procedure
Check the short dumps in BW.
Check the data in the InfoCube.
Error Correction:
If the data was correctly updated in the InfoCube, then it is possible that no InfoIDocs were generated.
Set the data request status manually to "OK" (green traffic light).
This error has occured in a standard SAP Program.
Hi Ravi,
I am not loading the data to the cube but only to the ODS. I have plans to load the data later from ODS to Cube.
I am not using the process chains to load the data and anyway, as I am not loading to the cube, I auume the index will not come into picture. Please correct me if I am wrong.
And, what do you mean by "Split the file". Can you please elaborate?
Thanks,
RPK.

Own text in short dump

Hi ABAP-community,
i want to put an own text to short-dump message.
E.g. in a defined situation a message type 'X' will be processed in my application. In the created short dump i want to show additional info like relevant order numbers. WRITE command before processing the X-Message does not work!
Does anyone have a better idea, hint?
Looking forward to your reply! Thanks in advance!
Helpful answers will be rewarded!
Gunther

Looks like my idea worked.
- In SE24 created a new excpetion class ZCX_MAXWELL_A_EXCEPTION
     - Inherits from CX_NO_CHECK (so that it can be thrown without having to be caught)
     - Included a new paramter called MyString (Can contain any additional information I want in the dump)
     - Included a textID called FOOBAR (Can include various text IDs for different issues
The constructor of the excpetion object has it's code automatically updated to include the new attribute:
>method CONSTRUCTOR.
>CALL METHOD SUPER->CONSTRUCTOR
>EXPORTING
>TEXTID = TEXTID
>PREVIOUS = PREVIOUS.
>me->MYSTRING = MYSTRING .
>endmethod.
- Wrote a test program with the lines:
raise exception type ZCX_MAXWELL_A_EXCEPTION
exporting
TextID = ZCX_MAXWELL_A_EXCEPTION=>FOOBAR
MyString = 'BLAH'.
When exeucting the text program it creates a short dump that displays:
                                                                                >Error analysis
>    An exception occurred which is explained in detail below.
>    The exception, which is assigned to class 'ZCX_MAXWELL_A_EXCEPTION', was not
>     caught and
>    therefore caused a runtime error.
>    The reason for the exception is:
>    Something went wrong! FOOBAR!!!
At the top of the short dump screen there is a button that says "Exception Object". Pushing this button takes me to the specific fields that I've set in the exception:
> Level    1     Class    ZCX_MAXWELL_A_EXCEPTION
> Program Z_MAXWELL_B                      Include Z_MAXWELL_B                         Row   15
> Short Te Something went wrong! FOOBAR!!!
>KERNEL_ERRID
>MYSTRING                       BLAH
The aboove shows for the exception in the short dump bother the TextID that has been set as well as any other attributes that I've set (in this case MYSTRING = "BLAH")
~Ian

Custom error message in user exit is giving Short dump

Hi All,
We have a scenario where in if any user try to create/Change/Delete particular types of contract in SAP system we have to issue error message
saying ZIN/ZIR contract creation/Change/Deletion is blocked in SAP. This has to be done from the web application. So we are putting below code
in user exit MV45AFZZ in the form USEREXIT_SAVE_DOCUMENT_PREPARE.
CONSTANTS: lc_vbcpic01 TYPE sy-uname VALUE u2018VBCPIC01u2019, u201CWeb application user ID
         lc_zin           TYPE vbak-auart VALUE u2018ZINu2019,
                     lc_zir            TYPE vbak-auart VALUE u2018ZIRu2019,
                     lc_text(32)    TYPE c VALUE u2018Check long text for more detailsu2019.
DATA: l_uname TYPE sy-uname.
CLEAR: l_uname.
MOVE sy-uname TO l_uname.
*If user ID is not the Web application ID then block the creation/Change/Deletion
IF   l_uname NE lc_vbcpic01
AND ( vbak-auart EQ lc_zin
OR    vbak-auart EQ lc_zir ).
MESSAGE e830(zv) WITH lc_text.
ENDIF.
This code is working fine while creating/Changing the contract i.e. Giving us error message so that user wonu2019t be able to create/change the contract.
But when we delete the contract from VA42, Control is coming to this message statement and is giving Short dump. Below is the error analysis of the dump.
Error Analysis:
During "Exit Command" processing, the program tried to send a " " message.
This is not allowed at this point in processing.
The program had to be terminated.
Screen name.............. "SAPMV45A"
Screen number............ 4001
If any one has come across such scenario/any work around for this problem please let me know your inputs. Your inputs are highly appreciated.
I am working on 4.6C version of SAP.
Note: When i issue information/Warning message contract is getting deleted after displaying the message.
Thanks,
Vinod.

I exactly replicated the same in DELETE_DOCUMENT also
I am getting the Dump. I tried with exit also , but it continued and deleted. To avoid deletion we have to use Leave program or LEAVE TO CURRENT TRANSACTION.
Delete Function is Defined as EXIT command. so it is not possible to give error message. To convice you i just copied demo program and raised the error message.
it is also giving the dump.
copy the demo program DEMO_DYNPRO_AT_EXIT_COMMAND and make this change , information to error .
MODULE cancel INPUT.
MESSAGE e888(sabapdocu) WITH text-001 ok_code input1 input2.
IF ok_code = 'CANCEL'.
    CLEAR ok_code.
    LEAVE PROGRAM.
ENDIF.
ENDMODULE.
and see...

Short Dump while Complete deletion of data Contents from a Cube.

Hello Experts,
I am facing a runtime Short dump whenever i attempt to delete data from a Cube. Shown Below:-
Runtime Errors         MESSAGE_TYPE_X
Error analysis
    Short text of error message:
Data request to the OLTP
    Long text of error message:
    Technical information about t
    Message class....... "RSM"
    Number.............. 000
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "SAPLRSM1" or "LRSM1U43"
    "RSSM_UPDATE_RSBKREQUEST"
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSM1" - in
     "RSSM_UPDATE_RSBKREQUEST".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 117
    of the (Include) program "LRSM1U43".
Line SourceCde
   87   call function 'RSSTATMAN_GET_TYPE_FOR_DTA'
   88     exporting
   89       i_dta = l_dta
   90     importing
   91       e_type = l_dta_type
   92     exceptions
   93       error = 1
   94       others = 2.
   95   if sy-subrc <> 0.
   96     message id sy-msgid type sy-msgty number sy-msgno
   97             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   98   endif.
   99   call function 'RSSTATMAN_DELETE_STATUS'
100     exporting
101       i_dta      = l_dta
102       i_dta_type = l_dta_type
103       i_process = 'ALL'.
104
105   sort l_t_iccont by rnsidlast ascending.
106   loop at l_t_iccont.
107     data: l_s_reqdone like rsreqdone.
108     select single * from rsreqdone into l_s_reqdone where
109            rnr = l_t_iccont-rnr.
110     if sy-subrc <> 0.
111       read table l_h_dtpreq with key
112            requid = l_t_iccont-rnsidlast.
113       if sy-subrc = 0 and
114          ( l_h_dtpreq-ustate = '0' or l_h_dtpreq-tstate = '0' ).
115         clear l_s_reqdone-archived.
116       else.
>>>>>         message x000.
   118       endif.
119     endif.
120     if l_s_reqdone-archived <> rs_c_false.
121       call function 'RSREQARCH_RELOAD_REQUEST'
122         exporting
123           i_rnr         = l_t_iccont-rnr.
124     endif.
125     select single * from rsbkrequest into l_s_req where
126            requid = l_t_iccont-rnsidlast.
127     if sy-subrc <> 0.
128       continue.
129     endif.
130
131     read table l_h_rsbkdtp with table key
132          dtp = l_s_req-dtp.
133     if sy-subrc <> 0.
134       l_h_rsbkdtp-dtp = l_s_req-dtp.
135       insert table l_h_rsbkdtp.
136     endif.
This issue only exists in Production system not QTY or development thr Cube deletion is working fine.
So far I have tried Deleting Index's and then deleting the Cube Contents & Run Elementary Checks from RSRV but not find any lead yet.Also unable to find appropriate notes for this issue aswell I am using SAP_Bw comp 700 with SP26.
Any suggestion would be of great help .
Thanks & Regards
Aman

Hi Ap_SAP & Arvind,
Any recent upgrades or system refresh done?
In recent update just from SP24 to SP26 was updated and a DB stats Referesh was carried on.But this proublem existed before these activities.
Except deleting can you able to perform all other operations like loading data..etc?
Other than deletion I am able to do load data into cube extract from R3 and also i can delete data from PSA.Only deletion giving dump.
You are trying to delete transactional or master data.
I am tring for transaction data.
WHen I try to delete request by request it also lead to the same short dump.
@ arvind : I checked Sm12 there i see not table which has been locked.
Thanks
Aman

Short Dump in system while deleting the SC item

Hi Experts,
We are receiving the short dump while trying to delete the shopping cart item.
The dump Says... "Buffer table not up to date"
When we debugged the same , found that becuase of the error message "No address found for partner function type 0008u201D.(bbp_pd-051) the BBP_PD_ABORT is called and thus the termination
Please let me know the reason for the same.
We are using SRM Version 5.00
Regards,
Ranjitha

Hello,
Kindly check the SAP Notes 1574131 & 1484165.
Best regards,
Rahul

Short Dump Error in deleting the Init request

Hi Gurus,
i am loading master data from sap r3 by init update.
now due to some requirement i have to delete the init request , but when i try to delete the request
it goes to short dump and gives the error message as
Runtime Errors         MESSAGE_TYPE_X
Date and Time          01/05/2009 01:54:15
Short text
     The current application triggered a termination with a short du
What happened?
     The current application program detected a situation which real
     should not occur. Therefore, a termination with a short dump wa
     triggered on purpose by the key word MESSAGE (type X).
Error analysis
     Short text of error message:
     Error when opening an RFC connection
     Long text of error message:
     Technical information about the message:
     Message class....... "RSAR"
     Number.............. 051
     Variable 1.......... "Error when opening an RFC connection"
     Variable 2.......... " "
     Variable 3.......... " "
     Variable 4.......... " "
     Last error logged in SAP kernel
     Component............ "SAP-Gateway"
     Place................ "SAP-Gateway on host sapdev / sapgw00"
     Version.............. 2
     Error code........... 631
     Error text........... "max no of gateways exceeded (100)"
     Description.......... " "
     System call.......... " "
     Module............... "gwxxrd.c"
     Line................. 8438
     The error reported by the operating system is:
     Error number..... " "
     Error text....... " "
Trigger Location of Runtime Error
    Program                                 SAPLRSSM
    Include                                 LRSSMF03
    Row                                     1,627
    Module type                             (FORM)
    Module Name                             DEL_SOURCE_SYSTEM_INIT
1624           communication_failure = 1 message l_msg_text
1625           system_failure        = 2 message l_msg_text.
1626       if sy-subrc <> 0.
>>>>>         message x051(rsar) with l_msg_text(50) l_msg_text+50(50) '' ''.
1628       endif.
Please help me on this as untill it will not be deleted, I will be unable to load the data.
suitable answer will get Full points.
Thanks.

Hi Saurabh,
PLEase go through these notes:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383837393039%7d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383934313030%7d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393738303738%7d

Message_type_x short dump while deleting request from infocube

Hi,
While deleting one of the erroneous requests from some infocubes,
system is resulting in short dump "MESSAGE_TYPE_X".
This is happening only with respect to some infocubes.
Description of short dump:
Short text of error message:
System error in program RSMDATASTATE and form RSM_DATASTATE_CHECK-5- (see long text)
Can any one of you please help with this?
Regards,
Nilima Rodrigues

Hi NILIMA,
I got same problem with my InfoPackage last month with same error msg.
that error come due to data inconstancy in data base table.
in my case i am unable to open my InfoPackage and after double clicking it was giving dump with same error.
If u know abap then just change the sy-subrc value from 4 to 0 before dump line code it will resolve your problem.
for this on dump screen click on debugger button then it opens your code and shows line on which u getting dump with table name check your entry in table ok
if u unable u find table then do one thing just put break point before dump line and open fresh rsa1 and go to same cube and double click it will stop on your debugger point just press f5 button it shos sy-subrc 4 convert it to 0 and press edit button and press f8 .
Regards
Ankit

Delivery Can not Delete Delivery due to ABAP Dump

I have a strange situation on a delviery that is in our production client. We rec;d an APAB dump whenposting goods issue in delivery (successfully posted but still ABAP'd out) this was due to the sales unit field calculated to high of a qty due to a material master setting in the price unit qty, This has been fixed in the material master but we can not get to the delivery to delete it. I have succefully reversed goods issue and successfully cancelled TO confirmation. I can not get to the delivery to delete it. I can not reject line items on the sales order due to it having subsequent documents. Does anyone know how this can be accomplished? Please advise/comment experiences. It would be GREATLY appreciated. See Below ABAP dump if it helps....
Kim
Runtime Errors         DYNPRO_FIELD_CONVERSION
Date and Time          05/16/2011 11:05:21
                   Screen name.............. "SAPMV50A"
                   Screen number............ 1102
                   Screen field............. "LIPSD-PIKMG"
                   Error text............... "FX015: Sign lost."
     Other data:
     If you cannot solve the problem yourself and want to send an error
     notification to SAP, include the following information:
     1. The description of the current problem (short dump)
        To save the description, choose "System->List->Save->Local File
     (Unconverted)".
     2. Corresponding system log
        Display the system log by calling transaction SM21.
        Restrict the time interval to 10 minutes before and five minutes
     after the short dump. Then choose "System->List->Save->Local File
     (Unconverted)".
     3. If the problem occurs in a problem of your own or a modified SAP
     program: The source code of the program
        In the editor, choose "Utilities->More
     Utilities->Upload/Download->Download".
     4. Details about the conditions under which the error occurred or which
     actions and input led to the error.

Symptom
A Warehouse Management-relevant (WM-relevant) delivery item is picked, and then the WM transfer order is canceled again using LT0G.
If the storage location for the delivery is changed to a non-WM-relevant storage location and a pick quantity is entered in the delivery, this pick quantity is assigned to the document flow record for the cancellation of the WM transfer order. This is incorrect.
The incorrect document flow record is stored in the database when you save the delivery.
This results in the ABAP runtime error "DYNPRO_FIELD_CONVERSION" when the delivery is processed again with VL02 or VL02N.
Other terms
PIKMG, WM-TA, Warehouse Management (WM) transfer order (TO), VBFA, RFMNG, SAPMV50A, MV50AO0F, FELDAUSWAHL, MV50AO0F, LIPSD-PIKMG
Reason and Prerequisites
This problem is caused by a program error.
Solution
Implement the specified correction to prevent this inconsistency in the table VBFA from occurring again.
Correction report Z_CORRECT_VBFA_FROM_LTAP:
Implement the correction report specified below with transaction SE38 using the attributes:
Title            Correction report for note 435274
Type            1 Executable program
Status                T    Test program
Application              V     Sales
Input parameters for execution of the report:
P_VBELN: Document number of the delivery that has document flows
         for the WM transfer order that are to be corrected.
        While the report is running, make sure that
        no changes are made to the relevant
        document.
P_TEST = 'X': Analysis:   Analysis of the missing document flow records;
                        no changes in the document.
P_TEST = ' ': Correction: Document flow records between delivery and
                        WM transfer order are corrected.
refer SAP Note 435274 - Negative pick quantity in the delivery

Delete delivery short dump. Message me803

Similar Messages

Maybe you are looking for