Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Hi All, I transported about 8 new TRs for the indexes in my Production server the night when users are less this activity. Took about 2 hours and there are was dump in st22 for 5-6 users which were working at that time. The dump(run time error) was "POSTING_ILLEGAL_STATEMENT". Runtime Errors POSTING_ILLEGAL_STATEMENT Date and Time 22.03.2011 20:27:22 Short text Statement "COMMIT" is not allowed in this form. What happened? Error in the ABAP Application Program The current ABAP program "SAPLGLIU" 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 There is probably an error in the program "SAPLGLIU". This program is triggered in the update task. There, the following ABAP/4 statements are not allowed: - CALL SCREEN - CALL DIALOG - CALL TRANSACTION - SUBMIT How to correct the error Probably the only way to eliminate the error is to correct the program. - If the error occurs 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: "POSTING_ILLEGAL_STATEMENT" " " "SAPLGLIU" or "LGLIUF1A" "INS_FAGLFLEXA" 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. ystem environment SAP-Release 700 Application server... "ciGRP" Network address...... "10.1.66.164" Operating system..... "HP-UX" Release.............. "B.11.31" Hardware type........ "ia64" Character length.... 16 Bits Pointer length....... 64 Bits Work process number.. 8 Shortdump setting.... "full" Database server... "cbe6pdb" Database type..... "ORACLE" Database name..... "GRP" Database user ID.. "SAPGRP" Char.set.... "C" SAP kernel....... 700 created (date)... "Oct 31 2010 21:16:35" Memory consumption Roll.... 16192 EM...... 25139040 Heap.... 0 Page.... 114688 MM Used. 1955344 MM Free. 2231872 r and Transaction Client.............. 30 User................ "UWZFIEX5" Language key........ "E" Transaction......... "FBCJ " Transactions ID..... "4D8893125DDE4845E10000000A0142A3" Program............. "SAPLGLIU" Screen.............. "SAPMSSY0 1000" Screen line......... 6 Please help... Thanks in advance. Lucky | __.____._ Copyright © 2011 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | Most Popular White Papers In the Spotlight _.____.__ |