Performance in ABAP statement

hi experts
in one of my program the performance is getting affected in the abap statement not in the database access
the program logic goes in this way from the main program 3 performs were called for in the last performa onlythe entire processing starts
in that last perform it s callin for a report through submit and return statement , the called report s again refering to one include program.
in se30 the highest % it showssthe last perform that s said and the program that s called through submit statement the include program is not affecting the performance please tell mehow to change the report insucha wayi can improve the performance
please reply
will assign marks for sure
thanks in advance

From your as I understand your original message, your report is calling another report and it is taking a very long time in that step.
Obviously, the second program is taking time and that is the one to be analyzed. So, you put a break-point on the SUBMIT statement and see what are the parameters that being sent to the second program. Then, run the second program all by itself using the parameters you have noted down and analyze what the problem is.
If my response is totally off of your question, please clarify the question.

Similar Messages

Performance of ABAP query program

Hi All,
A custom program AQNWZ_TALAT=====TCS_AP_ITEMS== is taking lot of time running. And when checked the cost of the select statement is very high.
I guessed it must be some custom abap query. Correct me if I am wrong.
Also please let me know how to do the performance tuning on this code? Should I be editing the program directly or should I edit at the abap query level.
Regards,
Pooja
Moderator message: Please Read before Posting in the Performance and Tuning Forum
Edited by: Thomas Zloch on Dec 3, 2010 11:01 AM

>A few tips you can use for finetuning a Report
The actually a good collection of the most important pain points. But the recommendations are unfortunately quite poor, and even wrong. I have updated them a little bit.
And for German speaking people I have added a reference to a textbook, where arll my recommendations are explained in detail.
Siegfried
1) Use mostly primary key to access data.
... nonsense, the task determines the WHERE clause, it is not your choice
2) Before READ u sort the itab
No
3) use mostly the indexes fields in ur where clause.
... as 1, it is the other way, the task determines the WHERE-clause, make surwe that there is an index which
supports it
4) Restrict the the fields retrieved by your select sentences to the minimal set. (Avoid select *)
nonsense, most SELECT use and must use *, use field list in wide tables
5) try to use specify where clause so the abap sql optimizer chooses the right index.
o.k., but who understands that in depth?
6) Avoid sentences like select lifnr name1 into corresponding fields of lfa1 from lfa1 where....
feel free to use if required
(You should declare a working area and select into the working area, is twice faster)
... such general statements are always incorrect
7) use hashed tables instead of standard tables. They are faster
no, use sorted tables, hashed are very special and can only be used if there is a unique key
8) avoid the use of collect as much as you can.
total nonsense, use collect with hashed tables, works perfect, if you use it with standard tables, do not mix it with other statements
1 Always check the driver internal tables is not empty , while using FOR ALL ENTRIES
100% correct
2 Avoid for all entries in JOINS
... not generally true
3 Try to avoid joins and use FOR ALL ENTRIES.
... hmmm, there are pages of discussions, this statement was wrong, is wrong and will be wrong!!!
4 Try to restrict the joins to 1 level only ie only for 2 tables
nonsense, joins are complicated, you must know hw indexes are used, if everything is fine, then 10 or 20 tables can be joined
5 Avoid using Select *.
see 4)
6 Avoid having multiple Selects from the same table in the same object.
... try to avoid to SELECT the same data, different criteria can be necessary
7 Try to minimize the number of variables to save memory.
... obvious,
8 The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)
... no is must not the optimizer will not be influenced be the order , but do it, it increases readability
9 Avoid creation of index as far as possible
... no, o.k. if you are not experienced than avoid ... otherwise the creation of the required indexes is absolutely mandatory for new tables, for SAP standard tables most indexes are already there. But still if very new accesses are added, then new indexes can become necessary.
10 Avoid operators like , > , < & like % in where clause conditions
... no, you must add them, but be aware that the search is only poorly supported by them, but the result set is reduced.
11 Avoid select/select single statements in loops.
... if they are going to the database! If the tables are buffered, then these statements are perfect!
12 Try to use 'binary search' in READ internal table. Ensure table is sorted before using BINARY SEARCH.
.... Actually try to avoid standard tables, use sorted tables instead. If you must use a standard table, than the recommendation is true.
13 Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)
.... no, use them if required. Again, if table is buffered, then they MUST be avoided.
14 Avoid using ORDER BY in selects
... if it is not ORDER BY PRIMARY KEY. Again, if the table is buffered, then other orders MUST be avoided.
15 Avoid Nested Selects
... use join. Again, if the tables are buffered, then Nested SELECTs are fine!
16 Avoid Nested Loops of Internal Tables
.... impossible, there is no other option. Use sorted tables and verything is fine!
17 Try to use FIELD SYMBOLS.
... what means try? Use ASSIGNING fieldsymbol in LOOPs, but use it in READs only for very wide tables (>1kB). Use it always for tables with tables in the workarea!
18 Try to avoid into Corresponding Fields of
... see 6) is wrong!
19 Avoid using Select Distinct, Use DELETE ADJACENT.
.... no, use it if required and if it can reduce the result set by a factor of 2 or more. Again, if table is buffered, then it MUST be avoided.
Wenn Sie mit der Performance Ihres ABAP Programms nicht zufrieden sind, werfen Sie doch einen Blick in mein neues Buch:
Siegfried Boes: Performance-Optimierung von ABAP®-Programmen Nov. 2009 464 Seiten 59u20AC
Leseproben und weitere Informationen: http://www.dpunkt.de/buecher/3096.html
Edited by: Thomas Zloch on Dec 3, 2010 10:53 AM

The performance of ABAP programs

Hey Experts , how can one analyze the performance of ABAP programs apart from using the generic tools such as Trace etc.

Hi Chakradhar,
Overview & Introduction
The runtime analysis tool allows you to examine the performance of any ABAP programs, such as reports, subroutines, function modules or classes, that you create in the ABAP workbench. It saves its results in performance data files, which you can display as lists. You can use these results to identify runtime-intensive statements, to combine table accesses, and show the hierarchy of program calls.
Normally you use the runtime analysis tool to measure the runtime of complex program segments or complete transactions (if you want to measure the runtime of smaller program segments or individual ABAP statements you can use the ABAP statement GET RUN TIME FIELD ).
However, we use only simple
The Programs to be Analyzed
Let's assume I am a very newbie in ABAP and I have written a tiny little program which is doing the following:
reading data from a database table
storing that data in an internal table
display that data on a list (at the start of the program you have to specify certain key values; only matching data should be displayed later on).
So here it comes (and it seems to work as designed ...)
REPORT y_wlog_atra_1.
PARAMETERS: p_carrid TYPE sbook-carrid DEFAULT 'LH',
            p_connid TYPE sbook-connid DEFAULT '0400'.
DATA: wa_sbook TYPE sbook,
      itab_sbook TYPE STANDARD TABLE OF sbook.
*SELECT * FROM sbook INTO wa_sbook.*
CHECK: wa_sbook-carrid = 'LH' AND
         wa_sbook-connid = '0400'.
APPEND wa_sbook TO itab_sbook.
ENDSELECT.
LOOP AT itab_sbook INTO wa_sbook.
WRITE: /,
         wa_sbook-carrid,
         wa_sbook-connid,
         wa_sbook-fldate,
         wa_sbook-bookid,
         wa_sbook-customid,
         wa_sbook-custtype.
ENDLOOP.
A nice colleague has thrown a glance at my source code. He has given the hint to use a WHERE clause with the SELECT statement instead of the CHECK statement for reasons of better performance.
So I have written another program:
REPORT y_wlog_atra_2.
*SELECT * FROM sbook INTO wa_sbook*
WHERE carrid = 'LH' AND
        connid = '0400'.
APPEND wa_sbook TO itab_sbook.
ENDSELECT.
I am curious about the performance now. Let's compare the 2 variants with the ABAP Runtime Analysis tool.
ABAP Runtime Analysis: Tool & Procedure
To start it, choose Test --> Runtime Analysis in the SAP Menu, or use transaction SE30 .
The runtime analysis procedure consists of two parts:
Recording performance data (upper part of the screen)
Analyzing the performance data (lower part of the screen; this part only appears if there are performance data files in place)
The procedure for the first part (Recording performance data):
We go to the initial screen of the runtime analysis (transaction code SE30 ) and specify the name of the first program (Y_WLOG_ATRA_1) in the relevant input field. After that we press the button Execute .
The selection screen of the program Y_WLOG_ATRA_1 (including the 2 input fields) is displayed. At the bottom of the screen we are informed that the measurement has been started. We continue by clicking the Execute button.
Later on we will see that a file (containing performance data) has been created in parallel.
Now we repeat that procedure for our second program (Y_WLOG_ATRA_2).
The second step is the analysis of the generated performance data.
To do that we have to go to the initial screen of the Runtime Analysis tool again. On the bottom part of the screen you can specify those performance data files you want to analyze.
You can see some information related to the last measurement run (in our case that was program (Y_WLOG_ATRA_2). By pressing the button Other File we are able to select those performance data files we like to analyze.
I want to see all the files I have created (user BCUSER).
I get the relevant list with 2 lines (related to the performance data files of the programs Y_WLOG_ATRA_1 and Y_WLOG_ATRA_2).
Based on that list you can display the distinct performance data per line. You have to click in the column Object Type of the relevant line.
As a start the tool displays the evaluation overview (showing the cumulated execution times for the ABAP, database and system-level).
Here comes the evaluation overview for program Y_WLOG_ATRA_1
We can do the same for the other program Y_WLOG_ATRA_2
By comparing the perfomance data of the 2 programs we clearly see that I have done well with listening to the advice of my colleague. The performance of the second program is dramatically better.
In the next step you can forward to a more detailed display of the performance data (Hitlists). That listing shows the different granular execution steps ( according to your filter adjustments ). Here you can easily identify the most time-consuming progam units.
And it will also be a good idea to glance at the Tips & Tricks corner. You will find many valuable suggestions about good performance definitely.
Please use the below link to see the Screen shots of the screens
[http://searchsap.techtarget.com/tip/0,289483,sid21_gci1265920,00.html|Performance Analysing]

ABAP statement for JDBC connection to SQL server

Hi Gurus,
i need to connect a WebDynpro abap to a SQL server.
My OS is Unix so i cannot use a ODBC connection.
Can anyone help me to know if it's possible to write an abap statement to connect the SQL server by JDBC connection?
thanks a lot
Regards
Claudio.

Hi,
      ELSEIF SCREEN-GROUP2 = 'PRO'.
      clear: list.
      if screen-name = 'ZAVBAK-ZZPROMO_ID'.
        exec sql.
   commit
          set connection :'CBREPOSITORYPRD'
        endexec.
        exec sql.
          CONNECT TO :'CBREPOSITORYPRD'
        endexec.
        exec sql.
          COMMIT
        endexec
      EXEC SQL.
          OPEN C1 FOR
          SELECT CutterRewardsUserListid,
                 SAPAccountNumber,
                 PromoID,
                 FirstName,
                 LastName
                 FROM CutterRewardsUserList
                 WHERE SAPAccountNumber = :XVBPA-KUNNR ORDER BY PromoID
        ENDEXEC.
        DO.
          EXEC SQL.
            FETCH NEXT C1 INTO :WA5
          ENDEXEC.
          IF SY-SUBRC = 0.
            PERFORM UPDATE_LIST.
          ELSE.
            EXIT.
          ENDIF.
        ENDDO.
        EXEC SQL.
          CLOSE C1
        ENDEXEC.

ABAP statement RSYN

Hi all,
does anyone know what the abap statement RSYN is for?
I haven't found anything about it in help docs.
:bus

Hi,
I am getting dump call_function_format_not_sup which showing sapmssy1 program error. i am attaching the dump. plz check and kindly help me.
ABAP/4 runtime error   CALL_FUNCTION_FORMAT_NOT_SUP
       Occurred on     07.07.2009 at 15:15:18
RFC data format not supported.
What happened?
An error occurred when executing a Remote Function Call.
The current ABAP/4 program "SAPMSSY1" had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your
SAP system administrator.
Error analysis
A data error occurred when executing a Remote Function Call.
The data format used is not supported by the recipient.
How to correct the error
A 'Remote Function Call' passed data in the incorrect format or
length. If both the calling program and the called program are
ABAP/4 function modules, there is an error in the
SAP system.
If one of these programs is a CPI-C program which interprets the
RFC log itself, the error has probably occurred because the program
does not conform to the standards defined by SAP.
System environment
SAP Release.............. "31H"
Application server....... "PCPPROD1"
Network address.......... "10.106.128.71"
Operating system......... "SunOS"
Release.................. "5.6"
Hardware type............ "sun4u"
Database server.......... "PHYPLW02"
Database type............ "ORACLE"
Database name............ "ALP"
Database owner........... "SAPR3"
Character set............ "en"
SAP kernel............... "31I"
Created on............... "Jul 24 2001 05:20:53"
Created in............... "SunOS 5.5.1 Generic_103640-19 sun4u"
Database version......... "ora OCI_73400"
Patch level.............. "616"
Patch text............... " "
Supported environment....
Database................. "ORACLE 7.2..., ORACLE 7.3..., ORACLE
8.0...*"
SAP database version..... "31I"
Operating system......... "SunOS 5.5.1, SunOS 5.6, SunOS 5.7, SunOS 5.8"
User, transaction...
Client.............. 000
User................ "SAPSYS"
Language key........ "E"
Transaction......... " "
Program............. "SAPMSSY1"
Screen.............. "SAPMSSY13004"
Screen line......... 2
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPMSSY1" in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1".
The termination occurred in line 67
of the source code of program "SAPMSSY1" (when calling the editor 670).
Source code extract
000370   ENDMODULE.
000380
000390   MODULE %_RFCDIA_CALL OUTPUT.
000400       "Do not display screen !
000410       CALL 'DY_INVISIBLE_SCREEN'.
000420       PERFORM REMOTE_FUNCTION_DIACALL.
000430   ENDMODULE.
000440
000450   MODULE %_CPIC_START.
000460     IF SY-XPROG(4) = '%RFC'.
000470       PERFORM REMOTE_FUNCTION_CALL USING RFCTYPE_EXTERNAL_CPIC.
000480     ELSE.
000490       CALL 'APPC_HD' ID 'HEADER' FIELD HEADER ID 'CONVID' FIELD CONVID.
000500       PERFORM CPIC_CALL USING CONVID.
000510     ENDIF.
000520   ENDMODULE.
000530
000540
000550   FORM CPIC_CALL USING CONVID.
000560     COMMUNICATION SEND ID CONVID BUFFER HEADER.
000570     IF SY-SUBRC EQ 0.
000580       PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000590     ELSE.
000600       MESSAGE A800.
000610     ENDIF.
000620   ENDFORM.
000630
000640
000650   FORM REMOTE_FUNCTION_CALL USING VALUE(TYPE).
000660     DO.
      CALL 'RfcImport' ID 'Type' FIELD TYPE.
000680       PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000690       RSYN >SCONT SYSC 00011111 0.
000700     ENDDO.
000710   ENDFORM.
000720
000730   FORM REMOTE_FUNCTION_DIASTART.
000740     DO.
000750       CALL 'RfcImport' ID 'Type' FIELD RFCTYPE_RFCDIA.
000760       PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000770       "Parking position for next request
000780       RSYN >SCONT SYSC 00011111 10.
000790       "ALternativ : Free mode
000800       "COMMIT WORK.
000810       "SYSTEM-CALL FREE MODE 0.
000820     ENDDO.
000830   ENDFORM.
000840
000850   FORM REMOTE_FUNCTION_DIACALL.
000860       SY-XCODE = '%_@no@'.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 1
SY-TABIX 0                             SY-DBCNT 0
SY-FDPOS 0                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
SY-MSGV1
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV2
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV3
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV4
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
TYPE                           3
                               0000
                               0003
SY-XPROG
                               22222222
                               00000000
SY-XFORM
                               222222222222222222222222222222
                               000000000000000000000000000000
Active calls / events
No.... Program INCLUDE Line Type.... Name.....................
     1 SAPMSSY1 SAPMSSY1    67 FORM     REMOTE_FUNCTION_CALL
     2 SAPMSSY1 SAPMSSY1    30 MODULE   %_RFC_START
Internal notes
The termination occurred in the function "ab_rfctinfo" of the SAP
Basis System, specifically in line 1178 of the module " ".
The internal operation just processed is "CALY".
List of ABAP/4 programs affected
Program
Load size
Roll size
Gen. date
/ time   Changed         by
SAPMSSY1
20480
83050
21.05.1997
16:27
21.05.1997
SAP
List of internal tables
No dump information available
Directory of application tables (contents)
Program name........... Contents.1........2........3....+....
SAPMSSY1 TCPIC
Directory of data areas (administration information)
No   Program name........... Length Gen.date   Gen.time Ofst Type Next
0    SAPMSSY1 /%_LISTTABLES    3128                       -3 DATA
1    SAPMSSY1 stack area      65536                       -2 DATA
2    SAPMSSY1 text pool        4064                       -1 DATA
3    SAPMSSY1 global data      1136                        0 DATA
4    SAPMSSY1 local data          0                        1 STCK
5    SAPMSSY1 constant data     647                        2 LITL
6    SAPMSSY1 not assigned        0                        3 INVL
7    SAPMSSY1 SYST             2232                        4 TABL
8    SAPMSSY1 SY               2232                        5 TABL
9    SAPMSSY1 RSJOBINFO          84                        6 TABL
10   SAPMSSY1 /%_SCREEN          56                        7 DATA
11   SAPMSSY1 /%_SYS%%          480                        8 DATA
12   SAPMSSY1 TCPIC              70                        9 TABL
Directory of data areas (contents)
No   Program name........... Contents.1........2........3....+....
0    SAPMSSY1 /%_LISTTABLES |00000x0C000000000x0C0
1    SAPMSSY1 stack area     |000x030000ÿÿÿÿ00000000
2    SAPMSSY1 text pool      |ÿÿ000006E000000x01R00000
3    SAPMSSY1 global data    |        0                    x04
4    SAPMSSY1 local data
ABAP/4 control blocks CONT
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl Source Line Source code........
146 CLEA 00     83                         SAPMSSY1   60 MESSAGE A800.
147 CLEA 00     84                         SAPMSSY1   60
148 CLEA 00     85                         SAPMSSY1   60
149 CLEA 00     86                         SAPMSSY1   60
150 MESS 00     327                        SAPMSSY1   60
151 ENDF 00                                SAPMSSY1   62 ENDFORM.
156 PERP 02                                SAPMSSY1   65 FORM REMOTE_FUNCTI
157 WHIL 00 2                             SAPMSSY1   66 DO.
161 WHIL 00 3                             SAPMSSY1   66
165 BRAN 05 Branch to 178                 SAPMSSY1   66
166 CALY 00 3 87     72    73     73     SAPMSSY1   67 CALL 'RfcImport' I
>>>>> CALY 02     88    P0                   SAPMSSY1   67
174 xper 02     22     23                  SAPMSSY1   68 PERFORM (SY-XFORM)
176 SYSC 1F                                SAPMSSY1   69 RSYN >SCONT SYSC 0
177 BRAX 00 Branch to 161                 SAPMSSY1   70 ENDDO.
178 WHIL 00 4                             SAPMSSY1   70
182 ENDF 00                                SAPMSSY1   71 ENDFORM.
187 WHIL 00 2                             SAPMSSY1   74 DO.
End of runtime analysis

About perform in abap

how perform on commit & rollback works explain with real time example ?

hi,
PERFORM n ON COMMIT
Addition
1. ... LEVEL level
Effect
Executes the specified subroutine when a COMMIT WORK occurs. This allows you to execute a subroutine only if the logical transaction has ended successfully. The subroutine is not executed until the key word COMMIT WORK is called. FORMs specified several times are executed only once on COMMIT WORK (see COMMIT WORK ).
If you call ROLLBACK WORK , you delete all the specified routines.
Note
With PERFORM ... ON COMMIT , you cannot transfer any data with USING/CHANGING . To do this, you must either store the data in global variables or store it temporarily with EXPORT ... TO MEMORY .
Addition 1
... LEVEL level
Effect
The addition LEVEL , followed by a field, defines the order in which the subroutines are executed after COMMIT WORK . They are called in ascending order of level. If there is no addition LEVEL , the subroutine always has the level zero. If the level is the same, the order of calls determines the order of execution. Level assignment occurs during development, e.g. by defining constants in an include program. The level must be of type I.
Implicit Database Rollbacks in the R/3 System
The following cases lead to an implicit database rollback:
· Runtime error in an application program
This occurs whenever an application program has to terminate because of an unforeseen situation (for example, trying to divide by zero).
· Termination message
Termination messages are generated using the ABAP statement MESSAGE with the message type A or X. In certain cases (updates), they are also generated with message types I, W, and E. These messages end the current application program.
Also follow this link.
http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/content.htm
Hope this helps, Do reward.
Edited by: Runal Singh on Apr 24, 2008 11:53 AM

Improve data load performance using ABAP code

Hi all,
I want to improve my load performance using ABAP code, how to do this?. If i writing ABAP code in SE38 how i can call
in BW side? if give sample code to improve load performance it will be usefull. please guide me.

There are several points that can improve performance of your ABAP code:
1. Avoid using SELECT...ENDSELECT... construct and use SELECT ... INTO TABLE.
2. Use WHERE clause in your SELECT statement to restrict the volume of data retrieved.
3. Use FOR ALL ENTRIES in your SELECT statement to retrieve the matching records at one shot.
4.Avoid using nested SELECT and SELECT statements within LOOPs.
5. Avoid using INTO CORRESPONDING FIELDS OF. Instead use INTO TABLE.
6. Avoid using SELECT * and select only the required fields from the table.
7. Avoid Executing a SELECT multiple times in the program.
8. Avoid nested loops when working with large internal tables.
9.Whenever using READ TABLE use BINARY SEARCH addition to speed up the search.
10. Use FIELD-SYMBOLS instead of a work area when there are more than 200 entries in an internal table where some fields are being manipulated.
11. Use MOVE with individual variable/field moves instead of MOVE-CORRESPONDING.
12. Use CASE instead of IF/ENDIF whenever possible.
13. Runtime transaction code se30 can be used to measure the application performance.
14. Transaction code st05 can be used to analyse the SQL trace and measure the performance of the select statements of the program.
15. Start routines can be used when transformation is needed in the data package level. Field/individual routines can be used for a simple formula or calculation. End routines are used when you wish to populate data not present in the source but present in the target.
16. Always use a WHERE clause for DELETE statement. To delete records for multiple values, use SELECT-OPTIONS.
17. Always use 'IS INITIAL' instead of equal to '' because null for a character is '' but '0' for an integer.
Hope it helps.

Same ABAP statements for SY-SUBRC 0 or 4

Hi,
I have a READ TABLE statement and if the SY-SUBRC is equal to 0 or 4, the same ABAP statements should be giving to both. What would be the most efficient way of writing this? Should I just not check for for the SY-SUBRC?
Thanks,
RT

You can simply check for 0 and 4, or if there is no chance of sy-subrc being anything other 0 or 4, simply don't check it..
clear itab.
read table itab with key....
check sy-subrc = 0
or sy-subrc = 4.
Regards,
Rich Heilman

Error "Error in ABAP statement when processing an internal table. table."

Hello,
I am facing the error when tried for GR from SRM portal for my shopping cart and for others created shopping cart. The error is
"Error in ABAP statement when processing an internal table. table."
I have the central receipient role. Couold any body assist me?
Thanks,
Pijush

Hi Harish,
Execute the query in RSRT and check whether you have any short dump is in ST22. This would give a clear idea at what might have gone wrong.
Another thing is to check whether the code for the variable is fine in the user exit.
Hope this helps.
Bye
Dinesh

Obsolete ABAP statements in OOPs context

Obsolete ABAP statements in OOPs context

hi,
Check t-code UCCheck.
Put the program name in the t-code and you will get the obsolete statements.
Also check table radir.
<b>Reward points if useful.</b>

In which cases can the ABAP statement CALL TRANSFORMATION be used?

Hi friends,
here is my questions with options below.
In which cases can the ABAP statement CALL TRANSFORMATION be used? (T/F)
-To transform as iXML document object into and ABAP data structure using
XSLT.
- To transform an XML document contained in a string into another XML
document
using and XSLT program.
- To get canonic XML display of an ABAP data structure.
- To transform an XML document contained in an xstring into another XLM
document using an ST program (Simple Transformation).
- To transform and ABAP data structure into an SML document using ST.
Kindly give me the expalnation to each statement with either True or False.

CALL TRANSFORMATION is a new language element in ABAP that we can use to <b>call up the transformation</b>.
The type of transformation:
XML to XML
XML to ABAP
ABAP to XML or
ABAP to ABAP is already determined by the two additions SOURCE and RESULT in CALL TRANSFORMATION.
Check this link for more details.
http://help.sap.com/saphelp_nw04/helpdata/en/a8/824c3c66177414e10000000a114084/content.htm
Regards,
Maha

LIKE and Type in abap statements

Hello All ,
I have a question regarding the 'Like' and' Type'
I have created a badi XXX , The method has a changing parameter 'A' which is referenced to a structure .
The typing method I have mentioned in the method ( in the parameter list ) is TYPE .( I feel it should have been Like ). Can this cause an issue while writing abap statements in the method ?
Thanks in advance .
Best Regards,
swetha

Hi Swetha,
Check out the below link for your question.
what is the difference between type and like
Re: what is the difference between type and like
Re: what is the difference between type and like
Thanks,
Chidanand

How to improve performance of insert statement

Hi all,
How to improve performance of insert statement
I am inserting 1lac records into table it takes around 20 min..
Plz help.
Thanx In Advance.

I tried :
SQL> create table test as select * from dba_objects;
Table created.
SQL> delete from test;
3635 rows deleted.
SQL> commit;
Commit complete.
SQL> select count(*) from dba_extents where segment_name='TEST';
COUNT(*)
4
SQL> insert /*+ APPEND */ into test select * from dba_objects;
3635 rows created.
SQL> commit;
Commit complete.
SQL> select count(*) from dba_extents where segment_name='TEST';
COUNT(*)
6
Cheers, Bhupinder

Obsolete ABAP statements/FM/BAPI in sap 4.7

dear experts
pls gv me the details of obsolete ABAP statements/FM/BAPI in sap 4.7 and their replacement in ECC 6.0,the statements should be related to MODULE POOL ,reports

Hello
ERP 6.0 implies Unicode as well. Therefore have a look at [ABAP and Unicode|http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/content.htm]
You will find useful documentation in the ABAP keyword documenation (ERP 6.0) as well:
Obsolete Statements
The statements described in this subnode are obsolete and are only still available for reasons of compatibility with releases prior to 4.6 or 6.10. You may still come across these statements in old programs but you should not use them in new programs.
Most of the obsolete statements listed here are syntactically forbidden in ABAP Objects or in Unicode programs. As a result, they can now only be used outside of classes or non-Unicode programs. There are replacement constructions for all obsolete statements which improve the efficiency and readability of programs.
Apart from the obsolete statements listed in this node, there are also obsolete variants and additions for non-obsolete statements. These cannot be used in ABAP Objects and Unicode programs either. They are detailed in the description of the corresponding statements.
Regards
Uwe

Urgent: About Obsolete ABAP statements in Netweaver 4.0?

Can any body please help us about the obsolete ABAP statements in Netweaver 4.0 corresponding to SAP 4.6?

Hi,
Pls read first the rules of engagement.
Anyway, open an editor and choose Utilities->Help on->New features in ABAP.
Or check notes like
367676 and 689951
Eddy

Performance in ABAP statement

Similar Messages

Maybe you are looking for