Category ABAP Programming Error Runtime Errors MESSAGE_TYPE_X ABAP Program ...

125 Pages·2014·0.12 MB·English

(cid:0)Category ABAP Programming Error
Runtime Errors MESSAGE_TYPE_X
ABAP Program SAPLOLEA
Application Component BC-FES-OAC
Date and Time 01.03.2014 22:50:38
--------------------------------------------------------------------------------
--------------------
--------------------------------------------------------------------------------
--------------------
|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:
|
| Control Framework : Error processing control
|
|
|
| Long text of error message:
|
| Diagnosis
|
| An error occurred when the system tried to process the commands
|
| from the Automation Queue on the presentation server.
|
| There are several possible reasons for this:
|
| - The installation of the SAP GUI on the presentation server is
|
| faulty or obsolete.
|
| - There is an error in the application program
|
| - There is an error in the SAPGUI or an integrated control
|
| Procedure
|
| 1. Make sure that you have imported the appropriate Support
|
| Package, the current kernel, and GUI patch for the release of your
|
| system
|
| 2. Check whether the error occurs locally on one or a few PCs, or
|
| generally on all PCs. Note whether the error only occurs for some
|
| users, for example because of a specific Customizing setting.
|
| If it only occurs locally, this suggests an installation problem
|
| with the PC. Check the installation; if necessary, reinstall the
|
| software. In the dump, search for the SY-MSGLI field, since it may
|
| point to the cause of the error.
|
| 3. Activate the Automation Trace (in accordance with SAP Note
|
| 158985).
|
| 4.Start the transaction and continue until the screen immediately
|
| before the dump.
|
| 5. From the System -> Utilities menu, choose Autom. Queue,
|
| Synchronous Processing.
|
| The status bar of the GUI displays the text:
|
| "Automation synchron flush mode on"
|
| 6. If you now proceed with the application, the short dump will
|
| display the ABAP call that caused the error; the Automation Trace
|
| will contain the error on the presentation server.
|
| 7. If necessary, load the short dump and trace files on to
|
| sapservX, so that SAP can analyze them.
|
|
|
| Technical information about the message:
|
| Message class....... "CNDP"
|
| Number.............. 006
|
| Variable 1.......... " "
|
| Variable 2.......... " "
|
| Variable 3.......... " "
|
| Variable 4.......... " "
|
--------------------------------------------------------------------------------
--------------------
--------------------------------------------------------------------------------
--------------------
|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" " "
|
| "SAPLOLEA" or "LOLEAU02"
|
| "AC_SYSTEM_FLUSH"
|
|
|
| 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..... 702
|
| SAP Basis Level. 0014
|
|
|
| Application server... "TALOS"
|
| Network address...... "46.4.92.231"
|
| Operating system..... "Linux"
|
| Release.............. "2.6.32-71.29.1.el6.x"
|
| Hardware type........ "x86_64"
|
| Character length.... 16 Bits
|
| Pointer length....... 64 Bits
|
| Work process number.. 13
|
| Shortdump setting.... "full"
|
|
|
| Database server... "TALOS"
|
| Database type..... "ORACLE"
|
| Database name..... "E62"
|
| Database user ID.. "SAPSR3"
|
|
|
| Terminal.......... "Finkijl-Note"
|
|
|
| Char.set.... "C"
|
|
|
| SAP kernel....... 720
|
| created (date)... "Dec 22 2013 19:26:41"
|
| create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
|
| Database version. "OCI_112, 11.2.0.2.0, V1, default"
|
|
|
| Patch level. 521
|
| Patch text.. " "
|
|
|
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.
*.*" |
| SAP database version. 720
|
| Operating system..... "Linux 2.6, Linux 3"
|
|
|
| Memory consumption
|
| Roll.... 0
|
| EM...... 8352576
|
| Heap.... 0
|
| Page.... 1048576
|
| MM Used. 4956448
|
| MM Free. 260464
|
--------------------------------------------------------------------------------
--------------------
--------------------------------------------------------------------------------
--------------------
|User and Transaction
|
| Client.............. 500
|
| User................ "EXT900001811"
|
| Language key........ "P"
|
| Transaction......... "/CONSOLUT/IDRPU51000"
|
| Transaction ID...... "53121F8A48597837E10000002E045CE7"
|
|
|
| EPP Whole Context ID.... "6C626DD559F51ED3A8B157C787C706F3"
|
| EPP Connection ID....... 00000000000000000000000000000000
|
| EPP Caller Counter...... 0
|
|
|
| Program............. "SAPLOLEA"
|
| Screen.............. "SAPMSDYP 0011"
|
| Screen Line......... 0
|
| Debugger Active..... "none"
|
--------------------------------------------------------------------------------
--------------------
--------------------------------------------------------------------------------
--------------------
|Information on where terminated
|
| Termination occurred in the ABAP program "SAPLOLEA" - in "AC_SYSTEM_FLUSH".
|
| The main program was "RPU51000 ".
|
|
|
| In the source code you have the termination point in line 29
|
| of the (Include) program "LOLEAU02".
|
--------------------------------------------------------------------------------
--------------------
--------------------------------------------------------------------------------
--------------------
|Source Code Extract
|
--------------------------------------------------------------------------------
--------------------
|Line |SourceCde
|
--------------------------------------------------------------------------------
--------------------
| 1|FUNCTION AC_SYSTEM_FLUSH .
|
| 2|*"----------------------------------------------------------------------
|
| 3|*"*"Lokale Schnittstelle:
|
| 4|*" IMPORTING
|
| 5|*" VALUE(CALLED_BY_SYSTEM) TYPE C OPTIONAL
|
| 6|*" EXCEPTIONS
|
| 7|*" CNTL_SYSTEM_ERROR
|
| 8|*" CNTL_ERROR
|
| 9|*"----------------------------------------------------------------------
|
| 10| data: sysubrc like sy-subrc.
|
| 11|
|
| 12| CALL FUNCTION 'AC_FLUSH_CALL'
|
| 13| EXPORTING
|
| 14| SYSTEM_FLUSH = 'X'
|
| 15| CALLED_BY_SYSTEM = CALLED_BY_SYSTEM
|
| 16| IMPORTING
|
| 17| MESSAGE_NR = sysubrc
|
| 18| MESSAGE_TEXT = SY-MSGLI.
|
| 19|
|
| 20| sy-subrc = sysubrc.
|
| 21|
|
| 22| CASE SY-SUBRC.
|
| 23| WHEN 0.
|
| 24| WHEN 1.
|
| 25|* system_error
|
| 26| MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.
|
| 27| WHEN 2.
|
| 28|* method_call_error
|
|>>>>>| MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
|
| 30| WHEN 3.
|
| 31|* property_set_error
|
| 32| MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
|
| 33| WHEN 4.
|
| 34|* property_get_error
|
| 35| MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
|
| 36| WHEN 8.
|
| 37|* maximal number of modi reached
|
| 38| MESSAGE ID 'CNDP' TYPE 'X' NUMBER 011 RAISING CNTL_SYSTEM_ERROR.
|
| 39| WHEN OTHERS.
|
| 40| RAISE CNTL_ERROR.
|
| 41| ENDCASE.
|
| 42|
|
| 43|ENDFUNCTION.
|
--------------------------------------------------------------------------------
--------------------
--------------------------------------------------------------------------------
--------------------
|Contents of system fields
|
--------------------------------------------------------------------------------
--------------------
|Name |Val.
|
--------------------------------------------------------------------------------
--------------------
|SY-SUBRC|2
|
|SY-INDEX|0
|
|SY-TABIX|0
|
|SY-DBCNT|0
|
|SY-FDPOS|40
|
|SY-LSIND|0
|
|SY-PAGNO|0
|
|SY-LINNO|1
|
|SY-COLNO|1
|
|SY-PFKEY|INIT
|
|SY-UCOMM|INIT
|
|SY-TITLE|Aumento simples sal.norm.p/rubricas salariais avaliadas indiretamente
|
|SY-MSGTY|X
|
|SY-MSGID|CNDP
|
|SY-MSGNO|006
|
|SY-MSGV1|
|
|SY-MSGV2|
|
|SY-MSGV3|
|
|SY-MSGV4|
|
|SY-MODNO|0
|
|SY-DATUM|20140301
|
|SY-UZEIT|225035
|
|SY-XPROG|SAPMSSY1
|
|SY-XFORM|XAB_READ
|
--------------------------------------------------------------------------------
--------------------
--------------------------------------------------------------------------------
--------------------
|Active Calls/Events
|
--------------------------------------------------------------------------------
--------------------
|No. Ty. Program Include
Line |
| Name
|
--------------------------------------------------------------------------------
--------------------
| 19 FUNCTION SAPLOLEA LOLEAU02
29 |
| AC_SYSTEM_FLUSH
|
| 18 FORM SAPFGUICNTL SAPFGUICNTL
256 |
| HANDLE_FLUSH_PBO
|
| 17 FORM SAPMSSYD SAPMSSYD
210 |
| %_CTL_OUTPUT_FLUSH
|
| 16 MODULE (PBO) SAPMSSYD SAPMSSYD
199 |
| %_CTL_OUTPUT_FLUSH
|
| 15 RFC SAPLOLEA LOLEAU10
227 |
| AC_FLUSH_CALL_INTERNAL
|
| 14 FUNCTION SAPLOLEA LOLEAU10
227 |
| AC_FLUSH_CALL_INTERNAL
|
| 13 FUNCTION SAPLOLEA LOLEAU18
46 |
| AC_FLUSH_CALL
|
| 12 METHOD CL_GUI_CFW====================CP CL_GUI_CFW==============
======CM002 6 |
| CL_GUI_CFW=>FLUSH
|
| 11 METHOD CL_EPSS_WORKFLOW_SERVICE======CP CL_EPSS_WORKFLOW_SERVICE
======CM002 50 |
| CL_EPSS_WORKFLOW_SERVICE=>SET_BUTTON_STATE
|
| 10 METHOD CL_EPSS_HTML_VIEWER===========CP CL_EPSS_HTML_VIEWER=====
======CM009 38 |
| CL_EPSS_HTML_VIEWER=>UPDATE_TOOLBAR
|
| 9 METHOD CL_EPSS_HTML_VIEWER===========CP CL_EPSS_HTML_VIEWER=====
======CM005 80 |
| CL_EPSS_HTML_VIEWER=>SHOW_HTML_DOCUMENT
|
| 8 METHOD CL_EPSS_SAPEVENT==============CP CL_EPSS_SAPEVENT========
======CM00B 16 |
| CL_EPSS_SAPEVENT=>LINES_DISPLAY
|
| 7 METHOD CL_EPSS_HELP_SERVICE==========CP CL_EPSS_HELP_SERVICE====
======CM001 55 |
| CL_EPSS_HELP_SERVICE=>SHOW_GIVEN_DOCUMENT
|
| 6 FUNCTION SAPLSHL2 LSHL2U18
98 |
| HELP_DOCULINES_SHOW
|
| 5 FORM SAPLSHL2 LSHL2F01
293 |
| DOKU_ANZEIGEN
|