11-05-2007 12:10 PM
Hi all
While doing MIGO for Delivery I am geeting a run time error, I am giving the details of the error below.
Runtime Errors MESSAGE_TYPE_X
Date and Time 05.11.2007 06:05:17
Short dump has not been completely stored (too big)
ShortText
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Could not determine recipients for message type INVCON
Technical information about the message:
Diagnosis
An IDoc of message type INVCON was passed to the ALE layer, but the
three receiver fields in the header record were not filled. In this
case the ALE layer tries to determine the receivers from the
entries in the distribution model. There are no entries available
in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message
type or deactivate distribution for these message types.
Message classe...... "B1"
Number.............. 003
Variable 1.......... "INVCON"
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
gger Location of Runtime Error
Program SAPLMBWL
Include LMBWLU21
Row 53
Module type (FUNCTION)
Module Name MB_POST_GOODS_MOVEMENT
rce Code Extract
e SourceCde
23 ENDIF.
24 xcommit = x. "Performance
25 IF NOT xblnr_sd IS INITIAL.
26 xmkpf-xblnr = xblnr_sd.
27 MODIFY xmkpf INDEX 1.
28 * when a goods movement for an inbound or outbound delivery is posted
29 * directly from VL31N/ VL01N, XBLNR is not yet known when we call
30 * CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
31 * BKPF as well. There is no other way to forward XBLNR to FI as not
32 * every document is posted by MB_CREATE -> a new function module in
33 * MBWL for transferring the information, called by FI, meant to load
34 * the complete function group for all MBxx postings when this isn't
35 * required (Performance). Would be the better way to transport the
36 * information after switching off MBxx in later release.
37 * corresponding IMPORT ... FROM MEMORY ... can be found in
38 * AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
39 l_mem_id = 'MKPF-XBLNR'. " 641365
40 EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365
41 ENDIF.
42 IF xmkpf-xabln IS INITIAL. "note 434093
43 CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093
44 ENDIF. "note 434093
45 CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
46 EXCEPTIONS error_message = 4.
47 * As soon as we have started to put things into UPDATE TASK, we must
48 * ensure that errors definitely terminate the transaction.
49 * MESSAGE A is not sufficient because it can be catched from
50 * external callers which COMMIT WORK afterwards, resulting in
51 * incomplete updates. Read note 385830 for the full story.
52 IF NOT sy-subrc IS INITIAL.
>>> MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
54 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
55 * MESSAGE A263.
56 ENDIF.
The programme was terminated in line 53 where there was a note 385830, I am trying to apply note 556000, is this the right approach.
Please guide me.
Suresh
11-06-2007 3:39 AM
Hi Suresh,
Yes you can apply that note. Also you need to apply note 561872. What is your SAP version?
Regards,
Atish
11-06-2007 3:37 AM
apply the new note and check again...
as it is standard code you can change it through note application or patch application..
search for the MIRO dump note or correction for note 385830
11-06-2007 4:33 AM
Hi Sharyu
Thanks for the reply. I will do that and let u know.
suresh
11-06-2007 3:39 AM
Hi Suresh,
Yes you can apply that note. Also you need to apply note 561872. What is your SAP version?
Regards,
Atish
11-06-2007 4:37 AM
Hi Atish,
thanks for immediate reply, I am in ecc 6.0, yes i have to apply the note along with 556000. what confuses me here is theshort text of the error message " could not determine recipients of error mesage type INVCON". Is there any thing I have to do realted to this.
Suresh
11-06-2007 4:46 AM
Hi Suresh,
I don't think you need to implement this note as you are on ECC6.0. This is for upto SAP 4.7.
Search OSS you may find some other note.
Regards,
Atish
11-06-2007 4:58 AM
H Atish
Thanks for your reply. Can u clarify some of my queries as I am not from technical back ground.
1. But if u see the note 385830 where the programme has been terminated is also not required to implement in ECC 6.0, but if u can see in my case they have implemented that note.
2. If u see the notes in SAP they have mentioned corrections for versions, but why i dont know we have note 385830 in our progarmme though we are in ECC 6.0.
3. The reason I was mainly asking for note 556000 is the programme was terminated in 53 line where there is note 385830 implemented.
Thanks in advance for ur reply
Suresh
11-06-2007 5:05 AM
Hi Suresh,
These could be because your system was upgraded from a previous version which had this requirement for that note.
Even so, if it's implemented, you can revert it back( Technical Team can ) and then apply the new note using SNOTE transaction ( BASIS activity).
I guess then your issue would be resolved.
Regards
Nishant
11-06-2007 5:07 AM
Hi Suresh,
Let me explain you logic behind notes. They are most of the time version dependent.
As this issue was identified by SAP in earlier versions so they may have come up with Note and later rectified the same using support packs or upgrades.
I think this answers your point 1 and 2.
And there may be other reason for the termination at that line. You may be able to find some other Note. If you are unable to find, raise an OSS message with SAP and they will provide the solution as it is dump in standard code.
Regards,
Atish
11-06-2007 5:11 AM
Hi Nishant
Thanks for u r clarification. The note 556000 is solution for the short dump due to 385830 . My question is even though version was upgraded the note will be have same effect, will it cause short dump. AM I RIGHT?. I may not recommend to revert the note back, bcoz i am not sure about consequences. If answer to my earlier question is YES then i will go for above said note .
thanks in advance for your reply.
Suresh
11-06-2007 5:14 AM
Hi Atish
Thanks for your clarification, Ok then I will go for OSS message.
Thanks again
Suresh
11-06-2007 5:21 AM
Hi Suresh,
In my honest opinion, you can just go and revert the original note since all the other notes are for 47C. None of 'em are valid for ECC 6.0 and though I am not sure of the dump, I am sure they can cause errors in the system
Basically you can revert in DEV then move it to Quality and do your testing. If it's not correct you can always revert it back
Regards
Nishant
12-18-2007 10:51 AM
01-31-2011 10:56 AM
Hi Suresh,
Can you please provide the details about the resolution of this problem. Which userexit is the issue and how you rectified it.
I am also getting the same problem.
Thanks in Advace !!
Pradeep