ABAP Dump

[Former Member]

Hello,

I am encounting ABAP dump in MIGO transaction since last 10 days.When i checked up the OSS note refered in the error is 385830.

Just before 10 days BADI(Business Add-In) was implemented for batch management and we are suspecting it might be due to this.

What might the possible reasons?

Kindly provide some inputs wrt to OSS note.

Helpfull answers will be rewarded.

Regards

Nisha

[Former Member]

/thread/629062 [original link is broken]

[Former Member]

Hi Nisha,

Can you tell more about dump as what error you are getting.

Regards,

Atish

[Former Member]

Hi,

I have put full description of the Error is as follows

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).

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.......... " "

Trigger Location of Runtime Error

Program SAPLMBWL

Include LMBWLU21

Row 53

Module type (FUNCTION)

Module Name MB_POST_GOODS_MOVEMENT

ENDIF.

xcommit = x. "Performance

IF NOT xblnr_sd IS INITIAL.

xmkpf-xblnr = xblnr_sd.

MODIFY xmkpf INDEX 1.

when a goods movement for an inbound or outbound delivery is posted

directly from VL31N/ VL01N, XBLNR is not yet known when we call

CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in

BKPF as well. There is no other way to forward XBLNR to FI as not

every document is posted by MB_CREATE -> a new function module in

MBWL for transferring the information, called by FI, meant to load

the complete function group for all MBxx postings when this isn't

required (Performance). Would be the better way to transport the

information after switching off MBxx in later release.

corresponding IMPORT ... FROM MEMORY ... can be found in

AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))

l_mem_id = 'MKPF-XBLNR'. " 641365

EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365

ENDIF.

IF xmkpf-xabln IS INITIAL. "note 434093

CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093

ENDIF. "note 434093

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.

<b>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.</b> MESSAGE A263.

ENDIF.

Optische Archivierung

Spaete Erfassung mit Barcode

Redesign of barcode handling -> note 780365

PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr

xmkpf-mjahr

barcode.

MOVE-CORRESPONDING xmkpf TO emkpf.

CALL FUNCTION 'MB_MOVEMENTS_REFRESH'

EXCEPTIONS error_message = 4.

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 A261.

ENDIF.

PERFORM buchen_initialisieren(sapmm07m).

Regards

Nisha

[Former Member]

Hi Nisha,

What is your SAP version?

Are you using message type INVCON and can you also check the settings in BD64 for the same.

Regards,

Atish

[Former Member]

Hi,

Thanks for your immediate reply.

We are in ECC 5.00 version

we are using message type INVCON.Kindly advise me what to check in BD64.

Thanks

Nisha

[Former Member]

hi Nisha,

Go to BD64 -> and go to the distribution model which is using this message type

and then go to Enviornement -> generate partner profiles.

Regards,

Atish

[Former Member]

hi Atish,

Please advise next step like what we need to see after generating partner profile.

Thanks

nisha

[Former Member]

Hi Nisha,

Test now. Are you still getting dump?

Regards,

Atish

[Former Member]

Hi,

Still the problem persists even after generating partner profile.

thanks

nisha

[Former Member]

Hi Atish,

Kindly let me know what should i do if we are not using the message type INVCON.

If possible I would request all consultants to give feedback on this issue.

Helpful answers will be rewarded

Urgent.

Thanks

Nisha A

[Former Member]

Hi,

Please provide some solution.

Thanks

nisha

[Former Member]

hi Nisha,

Are you able to see your partner profile in WE20.

Can you let me know what are the settings there.

Regards,

Atish