MIGO Dump

Former Member — Mon, 05 Nov 2007 12:24:14 GMT

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)

ShrtText

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

Re: MIGO Dump

Former Member — Tue, 18 Dec 2007 10:50:15 GMT

problem with user exit

Re: MIGO Dump

Former Member — Tue, 18 Dec 2007 12:48:20 GMT

hi ,

the dump is correct . becuase of inconsistency system going to dump.

Put a break point at below FM and debug the FM and find out why sy-subrc eq 4 and where it is happenning. The reason for dump is not because of ABAP it is because of the Wrong functional process(some where in Config).

CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'

EXCEPTIONS

error_message = 4.

IF NOT sy-subrc IS INITIAL.( other than 0 goes to dump)

MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830

sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

MESSAGE A263.

ENDIF.

topic MIGO Dump in Application Development and Automation Discussions

MIGO Dump

Re: MIGO Dump

Re: MIGO Dump