Skip to Content
0
Former Member
May 13, 2013 at 02:54 PM

Dump in MIGO while Transfer posting with 311 E

795 Views

Hello Experts:

I am getting dump in MIGO tcode saying not authorizeed to Sales Order change:

I am doing Stocktransfer using 311 E. Material is managed with serial numbers. This error is occuring for only 1 sloc, for rest of the slocs within plant document is being posted.

Authority object 'V_VBAK_VKO' with activity 02 is checked during post. My question is why sales order change object is being checked while sales order stock transfer within Plant for particular sloc only?

note: After debugging it is found that CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT' is giving SY-SUBRC = 4 and thus executing following code causing dump:

IF NOT sy-subrc IS INITIAL.

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

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

Here is dump:

Runtime Errors MESSAGE_TYPE_X
Date and Time 13.05.2013 22:41:21

Short text
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:
No authorization for maintaining sales documents in 3021 03 01

Long text of error message:
Diagnosis
According to the settings in your user master record you do not
have the authorization to execute this function.
Procedure
If you need this authorization, contact the person responsible for
assigning authorizations.
Authorization object: V_VBAK_VKO

Technical information about the message:
Message class....... "V1"
Number.............. 515
Variable 1.......... 3021
Variable 2.......... 03
Variable 3.......... 01
Variable 4.......... " "

ger Location of Runtime Error
Program SAPLMBWL
Include LMBWLU21
Row 62
Module type (FUNCTION)
Module Name MB_POST_GOODS_MOVEMENT

ce Code Extract

SourceCde

2 * 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 ELSE. "1245374

43 l_mem_id = 'MKPF-XBLNR'. "1245374

44 FREE MEMORY ID l_mem_id. "1245374

45 ENDIF.

46 IF xmkpf-xabln IS INITIAL. "note 434093

47 CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093

48 ENDIF. "note 434093

49

50 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.

51

52 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.

53 CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'

54 EXCEPTIONS

55 error_message = 4.

56 * As soon as we have started to put things into UPDATE TASK, we must

57 * ensure that errors definitely terminate the transaction.

58 * MESSAGE A is not sufficient because it can be catched from

59 * external callers which COMMIT WORK afterwards, resulting in

60 * incomplete updates. Read note 385830 for the full story.

61 IF NOT sy-subrc IS INITIAL.

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

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

64 * MESSAGE A263.

65 ENDIF.

66 * Optische Archivierung

67 * Spaete Erfassung mit Barcode

68 * Redesign of barcode handling -> note 780365

69 PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr

70 xmkpf-mjahr

71 barcode.

72

73 MOVE-CORRESPONDING xmkpf TO emkpf.

74 CALL FUNCTION 'MB_MOVEMENTS_REFRESH'

75 EXCEPTIONS

76 error_message = 4.

77 MOVE-CORRESPONDING xmkpf TO emkpf.

78 CALL FUNCTION 'MB_MOVEMENTS_REFRESH'

79 EXCEPTIONS

80 error_message = 4.

81 IF NOT sy-subrc IS INITIAL.