Transaction VL02N MESSAGE_TYPE_UNKNOWN

[Former Member]

Hello could you please solve me the short dump with the message "MESSAGE_TYPE_UNKNOWN " in transaction VL02N.

I searched the notes, but wasn't able to find the corresponding one.

The current ABAP program "SAPLZCONV" had to be terminated because it has come across a statement that unfortunately cannot be executed.

User and Transaction

Transaction......... "VL02N "

Program............. "SAPLZCONV"

Screen.............. "SAPMV50A 1000"

Screen line......... 39

Information on where terminated

| Termination occurred in the ABAP program "SAPLZCONV" - in "ZTDC_ASSAY_SEARCH".

| The main program was "SAPMV50A ".

|

In the source code you have the termination point in line 76

| of the (Include) program "LZCONVU03".

Source Code Extract

-

---

|Line |SourceCde

-

---

| 46| and vtweg = vtweg

| 47| and spart = spart.

| 48| lv_kvgr1 = it_knvv-kvgr1.

49

| 50| if vkorg = '9999'.

| 51| lv_kvgr1 = '30'.

| 52| endif.

53

54

| 55| CALL FUNCTION 'QC01_BATCH_VALUES_READ'

| 56| EXPORTING

| 57| I_VAL_MATNR = matnr

| 58| I_VAL_WERKS = WERKS

| 59| I_VAL_CHARGE = charg

| 60| I_LANGUAGE = SY-LANGU

| 61| I_DATE = SY-DATUM

| 62| IMPORTING

| 63| E_CLASS = lv_class

| 64| TABLES

| 65| T_VAL_TAB = it_values

| 66| T_CHAR_TAB = it_char

| 67| T_ATT_TAB = it_att

| 68| EXCEPTIONS

| 69| NO_CLASS = 1

| 70| INTERNAL_ERROR = 2

| 71| NO_VALUES = 3

| 72| NO_CHARS = 4

| 73| OTHERS = 5.

74

| 75| IF SY-SUBRC <> 0.

>>>>>	MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
77	WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

| 78| ENDIF.

79

| 80| if lv_class is initial.

81	CALL FUNCTION 'QC01_BATCH_CLASS'

| 82| EXPORTING

| 83| I_BATCH = charg

| 84| I_MATERIAL = matnr

| 85| I_LANGUAGE = SY-LANGU

| 86| IMPORTING

| 87| E_CLASS = lv_class

| 88| EXCEPTIONS

| 89| NO_CLASS = 1

| 90| INTERNAL_ERROR = 2

| 91| NO_MATERIAL = 3

| 92| NO_BATCH = 4

| 93| NO_PLANT = 5

| 94| OTHERS = 6.

[Former Member]

Hi,

VL02N is an SD transaction code , there are usually some user exits written to customize some calculation on the fly.

Please check with the Functional consultant as to when they are getting the short dump. What is the action they are performing which is resulting in the dump.

Only st22 will not show anything, it just says that there is a problem in module pool. Check the sm21 logs, check the sm13 for any update errors and check the application logs , if neccessary (tcode slg1).

the best way to solve a Short dump in ST22 is to understand the activity being done by Functionla consultant , lot of times there could be a problem in configuration/customizing.

Thanks

Prasanna