cancel
Showing results for 
Search instead for 
Did you mean: 

migo issue error posting time

Former Member
0 Kudos

This error send to migo issue transaction

narendra suthar

ntime Errors MESSAGE_TYPE_X

te and Time 01.11.2010 14:16:02

ort dump has not been completely stored (too big)

hort text

The current application triggered a termination with a short dump.

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

rror analysis

Short text of error message:

Document number 1000 4900000002 2010 was already assigned

Long text of error message:

Diagnosis

Document number 4900000002 in company code 1000 and fiscal year

2010 has already been assigned.

System Response

Termination of processing.

Procedure

Check document number range 49 in company code 1000 and fiscal year

2010 and correct the number range status if necessary.

Technical information about the message:

Message class....... "F5"

Trigger Location of Runtime Error

Program SAPLMBWL

Include LMBWLU21

Row 59

Module type (FUNCTION)

Module Name MB_POST_GOODS_MOVEMENT

NHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.

NHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.

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.

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.

MOVE-CORRESPONDING xmkpf TO emkpf.

CALL FUNCTION 'MB_MOVEMENTS_REFRESH'

EXCEPTIONS

error_message = 4.

IF NOT sy-subrc IS INITIAL.

Source Code Extract

Line SourceCde

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

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

31 * CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in

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

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

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

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

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

37 * information after switching off MBxx in later release.

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

39 * AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))

40 l_mem_id = 'MKPF-XBLNR'. " 641365

41 EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365

42 ENDIF.

43 IF xmkpf-xabln IS INITIAL. "note 434093

44 CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093

45 ENDIF. "note 434093

46

47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.

48

Number.............. 152

Variable 1.......... 1000

Variable 2.......... 4900000002

PLease give me

Accepted Solutions (0)

Answers (1)

Answers (1)

JL23
Active Contributor
0 Kudos

the short dump cleary says what you should do:

Document number 4900000002 in company code 1000 and fiscal year

2010 has already been assigned.

Procedure

Check document number range 49 in company code 1000 and fiscal year

2010 and correct the number range status if necessary.

Translated: SAP will create document 4900000002 , but this number is already in your database (check with SE16 in MKPF)

Former Member
0 Kudos

Dear Sir

How to check please give me a spro path

narendra suthar

Former Member
0 Kudos

Hi

Go to FBN1 to insert new number range for the fiscal year

Thx krishna

Former Member
0 Kudos

Dear sir

49 2008 4900000000 4999999999 4900000060

49 2010 4900000000 4999999999 4900000001

49 9999 4900000000 4999999999 4900000003

Number Range ok in FBN1 N t code

narendra suthar

Former Member
0 Kudos

Hi Narendra,

Were you able to get a solution to this problem ?

I am getting the similar kind of problem in MIGO.

I also checked the number ranges for Goods Receipt and found the same to be correctly maintained for the current fiscal year, along with the current status for these number range.

Kindly let me know how did you deal with this problem of yours.

Regards,

Zafar.