message type_x runtime error.

Former Member · ‎2014 Mar 19

i created bdc program. there is no syntax error. but while creating the data, i got runtime error message type_x.

how can i rectify this error?

PeterJonker · ‎2014 Mar 19

That is the most critical error you can have (ABORT). I would debug your code to see what is wrong or check ST22 after you run the program.

former_member201275 · ‎2014 Mar 19

I had this problem once before. We upgraded to the latest sapgui and that resolved the issue.

Hope that helps.

former_member201275 · ‎2014 Mar 19

Forgot to ask... please also can you post the dump here to give more detail.

Former Member · ‎2014 Mar 19

This is my program.

REPORT ZD_BDC.

*************************************************************************

***declarations of flat file***

types: begin of ty_table,

lifnr type rf02k-lifnr,

ktokk type rf02k-ktokk,

name1 type lfa1-name1,

sortl type lfa1-sortl,

land1 type lfa1-land1,

regio type lfa1-regio,

kunnr type lfa1-kunnr,

END OF ty_table.

data: ta_table type TABLE OF ty_table,

wa_table type ty_table.

**********************************************************************

***declaration of bdc data***

data: ta_bdcdata type TABLE OF bdcdata,

wa_bdcdata type bdcdata.

**********************************************************************

***declaration***

PARAMETERS: p_file type IBIPPARMS-PATH.

data: g_file type string.

**********************************************************************

***getting flatfile through selection screen***

at SELECTION-SCREEN on VALUE-REQUEST FOR p_file.

CALL FUNCTION 'F4_FILENAME'

EXPORTING

PROGRAM_NAME = SYST-CPROG

DYNPRO_NUMBER = SYST-DYNNR

FIELD_NAME = 'P_FILE '

IMPORTING

FILE_NAME = P_FILE

.

**********************************************************************

***UPLOAD FILE**

clear g_file.

g_file = p_file.

CALL FUNCTION 'GUI_UPLOAD'

EXPORTING

FILENAME = g_file

FILETYPE = 'ASC'

HAS_FIELD_SEPARATOR = 'X'

TABLES

DATA_TAB = ta_table

EXCEPTIONS

FILE_OPEN_ERROR = 1

FILE_READ_ERROR = 2

NO_BATCH = 3

GUI_REFUSE_FILETRANSFER = 4

INVALID_TYPE = 5

NO_AUTHORITY = 6

UNKNOWN_ERROR = 7

BAD_DATA_FORMAT = 8

HEADER_NOT_ALLOWED = 9

SEPARATOR_NOT_ALLOWED = 10

HEADER_TOO_LONG = 11

UNKNOWN_DP_ERROR = 12

ACCESS_DENIED = 13

DP_OUT_OF_MEMORY = 14

DISK_FULL = 15

DP_TIMEOUT = 16

OTHERS = 17.

IF SY-SUBRC = 0.

loop at ta_table into wa_table.

perform bdc_dynpro using 'SAPMF02K' '0100'.

perform bdc_field using 'BDC_CURSOR'

'RF02K-KTOKK'.

perform bdc_field using 'BDC_OKCODE'

'/00'.

perform bdc_field using 'RF02K-LIFNR'

wa_table-lifnr.

perform bdc_field using 'RF02K-KTOKK'

wa_table-ktokk.

perform bdc_dynpro using 'SAPMF02K' '0110'.

perform bdc_field using 'BDC_CURSOR'

'LFA1-REGIO'.

perform bdc_field using 'BDC_OKCODE'

'/00'.

perform bdc_field using 'LFA1-NAME1'

wa_table-name1.

perform bdc_field using 'LFA1-SORTL'

wa_table-sortl.

perform bdc_field using 'LFA1-LAND1'

wa_table-land1.

perform bdc_field using 'LFA1-REGIO'

wa_table-regio.

perform bdc_dynpro using 'SAPMF02K' '0120'.

perform bdc_field using 'BDC_CURSOR'

'LFA1-KUNNR'.

perform bdc_field using 'BDC_OKCODE'

'/00'.

perform bdc_field using 'LFA1-KUNNR'

wa_table-kunnr.

perform bdc_dynpro using 'SAPMF02K' '0130'.

perform bdc_field using 'BDC_CURSOR'

'LFBK-BANKS(01)'.

perform bdc_field using 'BDC_OKCODE'

'=ENTR'.

perform bdc_dynpro using 'SAPMF02K' '0380'.

perform bdc_field using 'BDC_CURSOR'

'KNVK-NAMEV(01)'.

perform bdc_field using 'BDC_OKCODE'

'=ENTR'.

**********************************************************************

***calling transaction***

CALL TRANSACTION 'XK01' USING TA_BDCDATA UPDATE 'S' MODE 'A'.

REFRESH TA_BDCDATA.

ENDLOOP.

ENDIF.

*&---------------------------------------------------------------------*

*& Form BDC_FIELD

*&---------------------------------------------------------------------*

* text

*----------------------------------------------------------------------*

* -->P_0270 text

* -->P_0271 text

*----------------------------------------------------------------------*

FORM BDC_FIELD USING FNAM FVAL.

WA_BDCDATA-FNAM = FNAM.

WA_BDCDATA-FVAL = FVAL.

APPEND WA_BDCDATA TO TA_BDCDATA.

CLEAR WA_BDCDATA.

ENDFORM. " BDC_FIELD

*&---------------------------------------------------------------------*

*& Form BDC_DYNPRO

*&---------------------------------------------------------------------*

* text

*----------------------------------------------------------------------*

* -->P_0260 text

* -->P_0261 text

*----------------------------------------------------------------------*

FORM BDC_DYNPRO USING PROGRAM SCREEN.

WA_BDCDATA-PROGRAM = PROGRAM.

WA_BDCDATA-DYNPRO = SCREEN.

WA_BDCDATA-DYNBEGIN = 'X'.

APPEND WA_BDCDATA TO TA_BDCDATA.

CLEAR WA_BDCDATA.

ENDFORM. " BDC_DYNPRO

after i entered all the value , i got that error.. by using st22 , i got the below things.

error in message class: am,

number 010

message_type_x

the program line is

message id 'am' type 'x' number 10.

former_member821147 · ‎2014 Mar 19

Hi,

Can you share the dump details.

Former Member · ‎2014 Mar 19

Category ABAP Programming Error

Runtime Errors MESSAGE_TYPE_X

ABAP Program SAPMF02K

Application Component FI-AP-AP

Date and Time 19.03.2014 16:10:28

----------------------------------------------------------------------------------------------------

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

----------------------------------------------------------------------------------------------------

|What can you do? |

| Note down which actions and inputs caused the error. |

| |

| To process the problem further, contact you SAP system |

| administrator. |

| |

| Using Transaction ST22 for ABAP Dump Analysis, you can look |

| at and manage termination messages, and you can also |

| keep them for a long time. |

----------------------------------------------------------------------------------------------------

|Error analysis |

| Short text of error message: |

| Address doesn't exist |

| |

| Long text of error message: |

| |

| Technical information about the message: |

| Message class....... "AM" |

| Number.............. 010 |

| Variable 1.......... " " |

| Variable 2.......... " " |

| Variable 3.......... " " |

| Variable 4.......... " " |

| Last error logged in SAP kernel |

| |

| Component............ "NI (network interface)" |

| Place................ "SAP-Server IDES_00 on host IDES (wp 4)" |

| Version.............. 40 |

| Error code........... "-2" |

| Error text........... "hostname 'iwdf8334.wdf.sap.corp' unknown" |

| Description.......... "NiHLGetNodeAddr: hostname cached as unknown" |

| System call.......... " " |

| Module............... "nixxhl.cpp" |

| Line................. 193 |

| |

| The error reported by the operating system is: |

| Error number..... " " |

| Error text....... " " |

| |

----------------------------------------------------------------------------------------------------

|How to correct the error |

| Probably the only way to eliminate the error is to correct the program. |

| - |

| |

| If the error occures in a non-modified SAP program, you may be able to |

| find an interim solution in an SAP Note. |

| If you have access to SAP Notes, carry out a search with the following |

| keywords: |

| |

| "MESSAGE_TYPE_X" " " |

| "SAPMF02K" or "MF02KFMD" |

| "DEBITOR_VERBUCHUNG" |

| |

| If you cannot solve the problem yourself and want to send an error |

| notification to SAP, include the following information: |

| |

| 1. The description of the current problem (short dump) |

| |

| To save the description, choose "System->List->Save->Local File |

| (Unconverted)". |

| |

| 2. Corresponding system log |

| |

| Display the system log by calling transaction SM21. |

| Restrict the time interval to 10 minutes before and five minutes |

| after the short dump. Then choose "System->List->Save->Local File |

| (Unconverted)". |

| |

| 3. If the problem occurs in a problem of your own or a modified SAP |

| program: The source code of the program |

| In the editor, choose "Utilities->More |

| Utilities->Upload/Download->Download". |

| |

| 4. Details about the conditions under which the error occurred or which |

| actions and input led to the error. |

| |

----------------------------------------------------------------------------------------------------

|System environment |

| SAP Release..... 731 |

| SAP Basis Level. 0002 |

| |

| Application server... "IDES" |

| Network address...... "192.168.140.50" |

| Operating system..... "Windows NT" |

| Release.............. "6.0" |

| Hardware type........ "3x AMD64 Level" |

| Character length.... 16 Bits |

| Pointer length....... 64 Bits |

| Work process number.. 4 |

| Shortdump setting.... "full" |

| |

| Database server... "IDES" |

| Database type..... "SYBASE" |

| Database name..... "ides" |

| Database user ID.. "SAPSR3" |

| |

| Terminal.......... "TEST" |

| |

| Char.set.... "C" |

| |

| SAP kernel....... 720 |

| created (date)... "Mar 1 2012 02:06:42" |

| create on........ "NT 6.0 6002 S x86 MS VC++ 16.00" |

| Database version. "Sybase ASE 15.7.0.1010 " |

| |

| Patch level. 210 |

| Patch text.. " " |

| |

| Database............. "15.7" |

| SAP database version. 720 |

| Operating system..... "Windows NT 5.1, Windows NT 5.2, Windows NT 6.0, Windows |

| NT 6.1, Windows NT 6.2" |

| |

| Memory consumption |

| Roll.... 0 |

| EM...... 29328544 |

| Heap.... 0 |

| Page.... 90112 |

| MM Used. 10719424 |

| MM Free. 1846832 |

----------------------------------------------------------------------------------------------------

|User and Transaction |

| Client.............. 800 |

| User................ "DHIVYA" |

| Language key........ "E" |

| Transaction......... "XK01 " |

| Transaction ID...... "D552AFE307DEF118BFBB005056BD3EB4" |

| |

| EPP Whole Context ID.... "005056BD3EB41EE3ABEA340655053FBB" |

| EPP Connection ID....... 00000000000000000000000000000000 |

| EPP Caller Counter...... 0 |

| |

| Program............. "SAPMF02K" |

| Screen.............. "SAPMF02K 0380" |

| Screen Line......... 51 |

| Debugger Active..... "(TPDA)" |

----------------------------------------------------------------------------------------------------

|Information on where terminated |

| Termination occurred in the ABAP program "SAPMF02K" - in "DEBITOR_VERBUCHUNG". |

| The main program was "SAPMF02K ". |

| |

| In the source code you have the termination point in line 802 |

| of the (Include) program "MF02KFMD". |

|Error occurred during batch input processing |

----------------------------------------------------------------------------------------------------

|Source Code Extract |

----------------------------------------------------------------------------------------------------

|Line |SourceCde |

----------------------------------------------------------------------------------------------------

| 772| ENDIF. |

| 773| SELECT SINGLE * FROM KNA1 WHERE KUNNR = RETDEB-KUNNR. |

| 774| IF SY-SUBRC = 0. |

| 775| LV_RETDEB_TYP = 'L'. |

| 776| CALL FUNCTION 'CUSTOMER_MAINTAIN_VB_EX_VENDOR' |

| 777| EXPORTING |

| 778| I_KNA1 = RETDEB |

| 779| I_RETDEB_TYPE = LV_RETDEB_TYP |

| 780| I_LFA1_ADRNR = LFA1-ADRNR |

| 781| I_DEBI_EX_KRED = DEBI_EX_KRED |

| 782| I_KNA1_OLD = 'X' |

| 783| I_ADDR_CHG = ADDR_CHG |

| 784| IMPORTING |

| 785| E_KNA1 = RETDEB. |

| 786| ENDIF. |

| 787| ENDIF. |

| 788| |

| 789|* in case Customer>BP synchronization has failed and PPO is activated |

| 790|* the vendor must not be saved n_1231338_V |

| 791| DATA: adrs_sel LIKE addr1_sel. |

| 792| adrs_sel-addrnumber = lfa1-adrnr. |

| 793| CALL FUNCTION 'ADDR_GET' |

| 794| EXPORTING |

| 795| address_selection = adrs_sel |

| 796| EXCEPTIONS |

| 797| parameter_error = 1 |

| 798| address_not_exist = 2 |

| 799| version_not_exist = 3 |

| 800| internal_error = 4. |

| 801| IF sy-subrc = 2. |

|>>>>>| MESSAGE ID 'AM' TYPE 'X' NUMBER '10'. |

| 803| ENDIF. "n_1231338_^ |

| 804| |

| 805| PERFORM ADDR_MEMORY_SAVE. |

| 806| ENDIF. |

| 807| |

| 808|* Änderungen im Debitor------------------------------------------------* |

| 809|* Nur wenn kein Kunde anzulegen ist |

| 810| CHECK RETDEB_TYP = 'A' OR |

| 811| RETDEB_TYP IS INITIAL. |

| 812|* Nur beim Verändern |

| 813| CHECK T020-AKTYP = 'V'. |

| 814|* Nur wenn ein Feld in LFA1 geändert wurde |

| 815| CHECK YLFA1 NE LFA1. |

| 816|* Nur wenn die Kundennummer nicht initial ist |

| 817| CHECK NOT LFA1-KUNNR IS INITIAL. |

| 818|* Nur wenn A-Segment bearbeitet wurde |

| 819| CHECK NOT KRED-XASEG IS INITIAL. |

| 820|* Keine Änderung wenn Debitor gerade angelegt wurde |

| 821| CHECK RETDEB_DONE IS INITIAL. |

----------------------------------------------------------------------------------------------------

|Contents of system fields |

----------------------------------------------------------------------------------------------------

|Name |Val. |

----------------------------------------------------------------------------------------------------

|SY-SUBRC|2 |

|SY-INDEX|0 |

|SY-TABIX|1 |

|SY-DBCNT|0 |

|SY-FDPOS|1 |

|SY-LSIND|0 |

|SY-PAGNO|0 |

|SY-LINNO|1 |

|SY-COLNO|1 |

|SY-PFKEY|380V |

|SY-UCOMM|ENTR |

|SY-TITLE|Create Vendor: Contact persons |

|SY-MSGTY|X |

|SY-MSGID|AM |

|SY-MSGNO|010 |

|SY-MSGV1| |

|SY-MSGV2| |

|SY-MSGV3| |

|SY-MSGV4| |

|SY-MODNO|0 |

|SY-DATUM|20140319 |

|SY-UZEIT|161028 |

|SY-XPROG|SAPLCCCO |

|SY-XFORM|XAB_READ |

----------------------------------------------------------------------------------------------------

|Active Calls/Events |

----------------------------------------------------------------------------------------------------

|No. Ty. Program Include Line |

| Name |

----------------------------------------------------------------------------------------------------

| 7 FORM SAPMF02K MF02KFMD 802 |

| DEBITOR_VERBUCHUNG |

| 6 FORM SAPMF02K MF02KFML 1843 |

| LTS_UPDATE |

| 5 FORM SAPMF02K MF02KFV0 293 |

| VERBUCHUNGSAUFRUF |

| 4 FORM SAPMF02K MF02KFS0 344 |

| SCHLUSS_BEARBEITUNG |

| 3 FORM SAPMF02K MF02KFS0 601 |

| SICHERN_JA_NEIN |

| 2 FORM SAPMF02K MF02KFF0 94 |

| FOLGEDYNPRO_SETZEN_F |

| 1 MODULE (PAI) SAPMF02K MF02KI00 919 |

| FOLGEDYNPRO_SETZEN |

---------------------------------------------------------------------------------

Former Member · ‎2014 Mar 19

Hi,

that looks like invalid address data in your UPLOAD table.

Pleasw check the address data fields for valid content in debugger.

Regards,

Klaus

Former Member · ‎2014 Mar 19

i did not give any address field. i checked all the values in debugger. it accepts all the values. at last of inserting a record, it shows that error.

PeterJonker · ‎2014 Mar 19

lfa_addrnr is determined in the user exit. What happens in the user exit? Has it been implemented ?

Did you check in debug what the value is of lfa_addrnr just before the FM ADDR_GET is called ?

Did you try to call the FM with this addrnr in se37 ?

Former Member · ‎2014 Mar 19

Hi,

this message of type X is part of SAP note 1231338.

Your issue may be caused by a failing Business Partner synchronization. Please read SAP note 1231338.

It will not solve your issue but may give a hint.

Regards,

Klaus

Former Member · ‎2014 Mar 20

sir, i already hear about that sap note. how can i access that one??

Former Member · ‎2014 Mar 20

i found some fault with my recording. i rectified and got the output.

thanks for your great support..

regards,

Dhivya N

Former Member · ‎2014 Mar 20

but i want to know about the sap notes. where can i access it??

awaiting for your reply..

thankyou...

ThangaPrakash · ‎2014 Mar 20

Hello Dhivya,

You can access notes either in SAP or in portal https://websmp206.sap-ag.de/~SAPIDP/002006825000000234912001E

In SAP:

Goto t.code SNOTE ---> click on download SAP note icon (Ctrl+F8) and give your note number and download.

Then goto SAP note browser (Ctrl+F9) ---> give your note number and execute ---> Double click on the entry , it will take you to the note description and in the left node you can see the objects corrected by this note.

In Portal:

Goto the link ---> click on SAP support portal --> provide username and ID --> Help and support --> Search for SAP note and KBA's --> give your note number in the right search parameter.

Regards,

TP

satyabrata_sahoo3 · ‎2014 Mar 20

Update your Software Component SAP_APPL to 606. This error has been corrected in Note 1678415.

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My Account

My Account

message type_x runtime error.