Hi
Request you all to go through the dump,
| |What happened? | | | |
| | | Error in the ABAP Application Program | | |
| | | | | |
| | | The current ABAP program "SAPLSPO1" had to be terminated because it has | | |
| | | come across a statement that unfortunately cannot be executed. | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
| |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 | | | |
| | | During background processing, the system attempted to send a screen to a | | |
| | | user. | | |
| | | | | |
| | | Current screen: "SAPLSPO1 " 0500. | | |
| | | | | |
| | | Additional system information: | | |
| | | "currently running as cpic server" | | |
| | | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
| |How to correct the error | | | |
| | | If the error occurred in your own ABAP program or in an SAP | | |
| | | program you modified, try to remove the error. | | |
| | | | | |
| | | | | |
| | | 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: | | |
| | | | | |
| | | "DYNPRO_SEND_IN_BACKGROUND" " " | | |
| | | "SAPLSPO1" or "LSPO1U06" | | |
| | | "POPUP_TO_CONFIRM" | | |
| | | | | |
| | | 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. 0005 | | |
| | | | | |
| | | Application server... "lecc-prd-10" | | |
| | | Network address...... "172.18.218.141" | | |
| | | Operating system..... "Linux" | | |
| | | Release.............. "2.6.32-220.2.1.el6.x" | | |
| | | Hardware type........ "x86_64" | | |
| | | Character length.... 16 Bits | | |
| | | Pointer length....... 64 Bits | | |
| | | Work process number.. 8 | | |
| | | Shortdump setting.... "full" | | |
| | | | | |
| | | Database server... "lsdb-prd-2" | | |
| | | Database type..... "ORACLE" | | |
| | | Database name..... "EP1" | | |
| | | Database user ID.. "SAPSR3" | | |
| | | | | |
| | | Terminal.......... " " | | |
| | | | | |
| | | Char.set.... "C" | | |
| | | | | |
| | | SAP kernel....... 720 | | |
| | | created (date)... "Jan 15 2013 18:18:58" | | |
| | | create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr121116" | | |
| | | Database version. "OCI_112, 11.2.0.3.0, V1, default" | | |
| | | | | |
| | | Patch level. 401 | | |
| | | 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...... 12569424 | | |
| | | Heap.... 0 | | |
| | | Page.... 16384 | | |
| | | MM Used. 10030984 | | |
| | | MM Free. 2535400 | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
| |User and Transaction | | | |
| | | Client.............. 100 | | |
| | | User................ "EWMONECC" | | |
| | | Language key........ "E" | | |
| | | Transaction......... " " | | |
| | | Transaction ID...... "530F7949A5601689E1000000AC12DA41" | | |
| | | | | |
| | | EPP Whole Context ID.... "005056B976AF1ED3A8902D8CE1BD4303" | | |
| | | EPP Connection ID....... "53109D4E863D7FBCE1000000AC12DA42" | | |
| | | EPP Caller Counter...... 1 | | |
| | | | | |
| | | Program............. "SAPLSPO1" | | |
| | | Screen.............. "SAPMSSY1 3004" | | |
| | | Screen Line......... 2 | | |
| | | Debugger Active..... "none" | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
| |Server-Side Connection Information | | | |
| | | Information on caller of Remote Function Call (RFC): | | |
| | | System.............. "EP1" | | |
| | | Installation Number. 0020694200 | | |
| | | Database Release.... 731 | | |
| | | Kernel Release...... 720 | | |
| | | Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) | | |
| | | Call Type........... "synchronous and transactional type Q (emode 0, imode 0)" | | |
| | | Inbound TID.........."AC12DA8A728B531098C05738" | | |
| | | Inbound Queue Name..."DLWSWP1CLNT1008000001383" | | |
| | | Outbound TID........." " | | |
| | | Outbound Queue Name.." " | | |
| | | | | |
| | | Client.............. 100 | | |
| | | User................ "EWMONECC" | | |
| | | Transaction......... " " | | |
| | | Call Program........."SAPLIRFC" | | |
| | | Function Module..... "TRFC_QIN_DEST_SHIP" | | |
| | | Call Destination.... "lecc-prd-10_EP1_00" | | |
| | | Source Server....... "lecc-prd-10_EP1_00" | | |
| | | Source IP Address... "172.18.218.141" | | |
| | | | | |
| | | Additional information on RFC logon: | | |
| | | Trusted Relationship " " | | |
| | | Logon Return Code... 0 | | |
| | | Trusted Return Code. 0 | | |
| | | | | |
| | | Note: | | |
| | | - For Releases < 4.0, information on the RFC caller not available. | | |
| | | - The installation number is available from caller Release > 700 | | |
| | | | | |
| | | Additional information on RFC logon: | | |
| | | Trusted Relationship " " | | |
| | | Logon Return Code... 0 | | |
| | | Trusted Return Code. 0 | | |
| | | | | |
| | | Note: For releases < 4.0, information on the RFC caller are often | | |
| | | only partially available. | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
| |Information on where terminated | | | |
| | | Termination occurred in the ABAP program "SAPLSPO1" - in "POPUP_TO_CONFIRM". | | |
| | | The main program was "SAPMSSY1 ". | | |
| | | | | |
| | | In the source code you have the termination point in line 248 | | |
| | | of the (Include) program "LSPO1U06". | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
| |Source Code Extract | | |
----------------------------------------------------------------------------------------------------
| |Line |SourceCde | | |
----------------------------------------------------------------------------------------------------
| | 218| | PERFORM append_icon_to_button | | | |
| | 219| | USING | icon_button_4 | | |
| | 220| | l_quickinfo_button_4 | "*048i | | |
| | 221| | CHANGING button_4. | | | |
| | 222| ENDIF. | "974439 << | | | |
| | 223| | | | ||
| | 224| | | | ||
| | 225|* Aufbereitung des Fragetextes und Berechnung der Dynprogröße | | | ||
| | 226| PERFORM format_text TABLES text_tab1 | | | ||
| | 227| | USING fragetext. | | | |
| | 228| | | | ||
| | 229| PERFORM calculate_screen_size | | | ||
| | 230| | USING | | | |
| | 231| | textlength | | | |
| | 232| | start_spalte | | | |
| | 233| | start_zeile | | | |
| | 234| | CHANGING | | | |
| | 235| | tab_len1 | | | |
| | 236| | tab_len2 | | | |
| | 237| | end_spalte | | | |
| | 238| | end_zeile | | | |
| | 239| | dynpro_nummer. | | | |
| | 240| | | | ||
| | 241| | | | ||
| | 242|* Aufruf der Dialog-Dynpros | | | ||
| | 243| | | | ||
| | 244| CALL SCREEN dynpro_nummer STARTING AT start_spalte start_zeile | | | ||
| | 245| | ENDING AT end_spalte end_zeile. | | | |
| | 246| | | | ||
| | 247| | | | ||
| |>>>>>| answer = antwort. | | | ||
| | 249|ENDFUNCTION. | | |
---------------------------------------------------------------