Starting SQL-Trace Automatically - Transaction Code: ST05

Good Morning Experts!
I have got a problem with my "SAP - Business Warehouse (BW) System".
We have very much Traffic on this System every night (between 03:00 and 04:00 a.m.).
Because nobody is at work so early in the morning, I wanted to ask you, if there is a possibility to start the SQL-Trace (which you can call by transaction code: ST05) automatically.....?
Is there a possibility to write a short ABAP Code to start the SQL-Trace automatically?
Thank's and best regards.

Hello Rob.
Thank you for replying.
I tried to create a job with the "Job Wizard" with SM36.
Now i realized, that i have to wirte my own ABAP-Report (Programme), which uses the ST05 SQL-Trace function.
I am not an ABAP-Professional, so would you be so kind and give me the code-lines of this programme?
I can not imagine if you have to write only 5-10 lines or if the code is much longer...
Thank you and best regards.

Similar Messages

No insert Statements for EKKO EKPO in ST05 sql trace for transaction me21n

No insert Statements for EKKO EKPO in ST05 sql trace for transaction me21n.
IN ST05 I set a filter for ME21N and executed transaction to create a Purchase Order and then checked
ST05 but there is NO insert for EKKO or EKPO??
How Do I find in which columns of EKKO and EKPO data is inserted in ST05?
Edited by: DeepakNandikanti on Apr 28, 2010 8:27 AM

Hi,
I tried in my system and I can see INSERT statement on EKKO and EKPO tables. What exactly you are looking for? Some one else might have switched on the trace at the same time. Can you try again and see.
ST05=>Switch on trace
ME21N=>Create PO.
ST05=>Switch off and display trace.
In trace list search for EKKO and EKPO.
Column names are not shown in the trace list. It is the SQL trace and column list is generated dynamically like :A0, :A1....
@ Suhas,
That might be because the tables are updated via BAPIs ... Do you think SAP uses direct update statements on the DB tables ??
I didn't get above statement. Is there any other way of updation that happens when using BAPI? I believe that, even in case of BAPI there will be update task FMs called during database update. Please correct if i got it wrong.
Thanks,
Vinod.

Cannot trace the transaction code within a role

Hello All,
We, in our project trying to trace out various transaction codes assigned to each of roles.
I have an issue tracing an transaction code FB60. When i searched in suim for transaction codes within the role, I could see FB60 listing in the results.
But when i go to role through pfcg and see in the menu tab i cannot find the transaction code there.
what went wrong here? Now i want to remove the transaction code from the role so that next time when i use suim it wont be listed in the results.
Kindly advice.
Regards,
Brahmeshwar Poloju

HERE IS THE OUTPUT.
OBJECT     AUTH         VARIANT FIELD      LOW                                      HIGH
S_TCODE    T-DC84003900         TCD        SCPE*
S_TCODE    T-DC84003900         TCD        SDD1*                                    SE03
S_TCODE    T-DC84003900         TCD        SE07                                     SE16N
S_TCODE    T-DC84003900         TCD        SE17                                     SECQ*
S_TCODE    T-DC84003900         TCD        SEEF*                                    SI24_12
S_TCODE    T-DC84003900         TCD        SI2414                                   SIBU
S_TCODE    T-DC84003900         TCD        SIC_*                                    SLAT
S_TCODE    T-DC84003900         TCD        SLG0                                     SLIB_*
S_TCODE    T-DC84003900         TCD        SLIN                                     SLXT
S_TCODE    T-DC84003900         TCD        SM30
S_TCODE    T-DC84003900         TCD        SM31                                     SM37
S_TCODE    T-DC84003900         TCD        SM50
S_TCODE    T-DC84003900         TCD        SM51
S_TCODE    T-DC84003900         TCD        SMAR*                                    SMEZ
S_TCODE    T-DC84003900         TCD        SMTH*                                    SNLS
S_TCODE    T-DC84003900         TCD        SNRO                                     SO99
S_TCODE    T-DC84003900         TCD        SOACARRY*                                SOTR*
S_TCODE    T-DC84003900         TCD        SP02
S_TCODE    T-DC84003900         TCD        SCUS*                                    SDCA*
S_TCODE    T-DC84003900         TCD        /*                                       DA_*
S_TCODE    T-DC84003900         TCD        DC*                                      PFCF*
S_TCODE    T-DC84003900         TCD        PFD*                                     RYZ*
S_TCODE    T-DC84003900         TCD        RZZ*                                     SAIM*
S_TCODE    T-DC84003900         TCD        SAIO*                                    SAK*
S_TCODE    T-DC84003900         TCD        SAM*                                     SAPTE*
S_TCODE    T-DC84003900         TCD        SARJZ*                                   SARTN*
S_TCODE    T-DC84003900         TCD        SASAPCATT                                SBEA
S_TCODE    T-DC84003900         TCD        SBI*                                     SC2_*
S_TCODE    T-DC84003900         TCD        SCA*                                     SCBZ*
S_TCODE    T-DC84003900         TCD        SCDO                                     SCI*
S_TCODE    T-DC84003900         TCD        SCTS*                                    SCU3
S_TCODE    T-DC84003900         TCD        SWF_TR*                                  SYNT
S_TCODE    T-DC84003900         TCD        SZG*                                     TRBS
S_TCODE    T-DC84003900         TCD        TRCM*                                    UR_M*
S_TCODE    T-DC84003900         TCD        USRM*                                    _Z*
S_TCODE    T-DC84003900         TCD        SWF_CN*                                  SWF_RE
S_TCODE    T-DC84003900         TCD        SPEC*                                    SPERS*
S_TCODE    T-DC84003900         TCD        SPP*                                     SPROJE
S_TCODE    T-DC84003900         TCD        SQ00                                     SRT*
S_TCODE    T-DC84003900         TCD        SSC                                      SSDZ*
S_TCODE    T-DC84003900         TCD        SST0                                     ST05*
S_TCODE    T-DC84003900         TCD        ST14                                     ST62
S_TCODE    T-DC84003900         TCD        STCU                                     STKZ*
S_TCODE    T-DC84003900         TCD        SV*                                      SWF_BA
S_TCODE    T-DC84003900         TCD        SURAD                                    SURVEY
S_TCODE    T-DC84003900         TCD        SU50                                     SU52
S_TCODE    T-DC84003900         TCD        SU3
S_TCODE    T-DC84003900         TCD        SU2
S_TCODE    T-DC84003900         TCD        SU0
S_TCODE    T-DC84003900         TCD        STS*                                     STYLE*
Regards

Error when launching transaction code CRMBS02

Hello all...whenever we attempt to launch the t-code CRMBS02 or BS02, we get a popup that says:
Error in object editing: This syntax cannot be used for an object name
Selecting the documentation drop down provides:
Message no. TK103
Diagnosis
The syntax of the transferred objects is incorrect. R3TR BSVS made this check.
This could be caused by the following:
The object type R3TR BSVS is unknown
The syntax of the object name is incorrect
The object is a component of a system object
System Response
The function terminates.
Procedure
Correct the syntax.
Any suggestions? When this occurs, it does not enable editing and allows for display only. I have SAP_ALL assigned to the user, so I don't see any authorization errors when I trace the transaction code.
Suggestions?
Thanks in advance!
Joe

Hello Joe,
Tasks template of type T and Workflow Task of type WF, are no more used after release 45b. The were substituted by the TS Templates and by Workflow Template.
Please notes: 114811 -
From release 4.5 onwards only WS/TS tasks can be created via the standard workflow editor transaction however WF tasks created in previous releases may still be maintained. If it is important to be able to create WF flows in release 4.5 then you may still do so with transaction PFWF. This transaction has been removed from the menu to encourage the use of WS flows wherever possible.
A copy utility to copy WF flows and it's components to WS flows will be made available to speed up the transfer to client independent flows.
"Check also note: *152871 Release Upgrade considerations for workflow 3. WS / WF workflows (all releases)
"From Release 3. 1 onwards, it is possible to create customer workflows
of type 'WS'.
Solution: If you have 'WF' workflows, they will continue to run after an upgrade. You can modify them too. However, some of the new features of future releases only apply to 'WS' workflows. See note 114811 for a complete discussion of this subject.
You should pass from T and WF templates to the New WS and TS templates.
1) In relation to workflows of type 'WF' (Workflow Task) and task 'T' they have not been developed since release 40B, instead the Workflow Template (WS) was introduced and Tasks 'TS'. This error has seldomly
been observed in the case of trying to work with WFlow tasks of type WF instead of type WS.
Existing WF will run also in higher releases, however if you change a WF task in a higher release it may produce dumps or numerous errors. This is valid too for Tasks.
Please refers to note 114811.
If you want to change them please copy them first to templates type WS or TS rather than WF or T. Use PFTC in order to copy them and then you can make the changes and you will have much more functionality than type
WF or T.
Additional Inforamtions:
Note 1068627 - Composite note about workflow upgrade
thanks
Willie

How to use the transaction STO5 (SQL Trace)

Hi,
I want to check the performance of program using the ST05 transaction. Please send me the step by step procedure to trace my program.
Thanks & Regards,
Santhosh Kumar.R

Hi,
following explanation clearly you abt ST05
Hi,
SQL trace(ST05) provides the developer with the ability to analyse database select statements. Simply execute ST05 to turn on SQL trace, then execute the statement/program you want to analyse. Now turn off SQL trace using ST05
and click on list trace to view the details.
You can also perform traces on other items such as authorisation objects.
The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on the SPFLI table in our test program is mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Performance Tuning is useful mainly reducing load on database. It is very important aspect while writing the programs/FM etc.....
SQL Trace
Use
The SQL Trace function is an on-demand log of selected SQL statements that are issued against the database through the Open SQL Engine. The SQL Trace can be switched on or off dynamically. The log format is database independent. Besides the SQL statement text, each log record contains information about the point in time when the statement was executed, its duration, its input parameters and results (where applicable) as well as context information.
Features
The SQL Trace is especially useful for:
Development:
SQL Trace can help JDO, enterprise beans, servlet and JSP developers to learn which kind of database accesses their code produces.
 Performance analysis
Typically, performance issues are caused by inefficient database accesses. In this case SQL Trace can be used to show the issued SQL statements and their duration, thus helping to identify inefficient SQL statements.
Functions
The following functions are available on the initial screen:
Select trace:
Select the trace mode SQL Trace, Enqueue Trace, RFC Trace, or Table Buffer Trace. You can select mutliple trace modes simultaneously.
Select trace function:
Start the trace recording.
Stop the trace recording.
Branch to trace list, detailed list, or time-sorted list.
Branch to Explain SQL to analyze an SQL statement without an explicit trace file.
Trace files are managed by the system. Thus they can be saved, like any other object;
saved trace files can be displayed and deleted.
Trace Status
A trace can only be activated once on any application server. The Trace Status display informs you whether another user in the system has already activated a particular trace.
Starting the Trace
Prerequisites
You can only switch on the Performance Trace for a single instance. You should already have decided the scope and targets of your performance analysis.
Procedure
To analyze a trace file, do the following:
... 1. Choose the menu path Test  Performance Trace in the ABAP Workbench.
The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.
2. Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).
3. If you want to switch on the trace under your user name, choose Trace on.
If you want to pass on values for one or several filter criteria, choose Trace with Filter.
Typical filter criteria are: the name of the user, transaction name, process name, and program name.
4. Now run the program to be analyzed.
You will normally analyze the performance trace file immediately. In this case, it is a good idea to use a separate session to start, stop, and analyze the Performance Trace
If you are shown trace kernel errors on the initial screen (for example, not enough storage space available), you must first remove the errors or have them removed by your system administrator.
The selected trace types can be changed as required during a performance trace interval (time between switching on and off the trace). The user (user group) must remain unchanged.
Result
The results of the trace recording are written to a trace file. If trace records are overwritten during the trace interval, the system displays a message to inform you when you analyze the trace file.
The results of the trace recording are stored to ten trace files. Overwriting trace records, however, cannot be entirely excluded in this case either.
The Performance Trace records all database access calls, table buffer calls, remote calls, or calls for user lock activity. These measurements can affect the performance of the application server where the trace is running. To preserve system performance, you should therefore turn off the trace as soon as you finish recording your application.
Stopping the Trace
Prerequisites
You have started the trace and finished running the program that you want to analyze.
For performance reasons, you should switch off the traces as soon as you have finished recording.
Procedure
To deactivate the trace:
... 1. Choose Test Performance Trace in the ABAP Workbench.
The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.
2. Select the trace functions that you want to switch off.
3. Choose Deactivate Trace.
If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-
Result
The results of the trace are stored in one or more trace files. You can then analyze the performance data stored in the trace file. See also, Analyzing Performance Data.
Look at the below link
http://www.sapbrainsonline.com/TOOLS/SQLTRACE/SQL_TRACE.html
Reward with points if helpful.
Regards,
Vijay

SQL Trace(ST05) and Run Time Analysys(SE30)

Hi ABAP Experts,
Can any one explain what is the use of
1) ST05 and
2) SE30
ponits will be given for clear cut explanation
Thanks and Regards
Vijaya

Hi,
The SQL Trace part of the Performance Trace tool allows you to see how the OPEN SQL statements that you use in ABAP programs are converted to standard SQL statements (see Embedded SQL) and the parameters with which the embedded SQL statements are passed to the database system.
Overview
From the time you turn on the trace function to the time you turn it off again, all database activity occurring either for a specific user or for an entire system is recorded. The SAP System takes OPEN SQL statements and converts them in to embedded SQL statements that it passes to the database and makes the results available. The embedded SQL statement and its parameters are recorded in the SQL Trace file. The results of the SQL statement, like return code, number of entries retrieved, inserted, or deleted by the database are recorded in the SQL Trace file as well. The log file also contains the runtime of the statement and the place in the application program, respectively transaction, from which it was called which enables additional analyses (supported by the SQL Trace function).
From the recorded SQL trace you can deduce:
·        which SQL statements your application carries out
·        which values the system uses for specific database accesses and changes
·        how the system translates ABAP OPEN SQL commands (such as SELECT) into standard SQL commands
·        where your application positions COMMIT statements
·        where your application makes repeated database accesses
·        what database accesses or changes occur in the update section of your application
Create a Trace (SQL Server Profiler)
To create a trace
On the File menu, click New Trace, and connect to an instance of SQL Server.
The Trace Properties dialog box appears.
Note:
The Trace Properties dialog box fails to appear, and the trace begins instead, if Start tracing immediately after making connection is selected. To turn off this setting, on the Tools menu, click Options, and clear the Start tracing immediately after making connection check box.
In the Trace name box, type a name for the trace.
In the Use the template list, select a trace template on which to base the trace, or select Blank if you do not want to use a template.
To save the trace results, do one of the following:
Click Save to file to capture the trace to a file. Specify a value for Set maximum file size. The default value is 5 megabytes (MB).
Optionally, select Enable file rollover to automatically create new files when the maximum file size is reached. You can also optionally select Server processes trace data, which causes the service that is running the trace to process trace data instead of the client application. When the server processes trace data, no events are skipped even under stress conditions, but server performance may be affected.
Click Save to table to capture the trace to a database table.
Optionally, click Set maximum rows, and specify a value.
Caution:
When you do not save the trace results to a file or table, you can view the trace while SQL Server Profiler is open. However, you lose the trace results after you stop the trace and close SQL Server Profiler. To avoid losing the trace results in this way, click Save on the File menu to save the results before you close SQL Server Profiler.
Optionally, select the Enable trace stop time check box, and specify a stop date and time.
To add or remove events, data columns or filters, click the Events Selection tab. For more information, see: How to: Specify Events and Data Columns for a Trace File (SQL Server Profiler)
Click Run to start the trace.
Runtime analysis:
se30 is the tcode for run time analysis, is a tool it
display report based on lps for abap pragram execution
time , data base load, system load. these are all will
display in micro seconds.this tool will use for Transaction
code, function modules , abap progrmes
In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.
For our case, let this be ZABAP_PERF_TUNING
After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the BACK button.
On the original SE30 screen, now click on ANALYZE button.
The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.
SQL trace:
/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy
SE30
/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy
regards,
vasavi.
kindly reward if helpful.

Diff b/w Run time Analyizer(se30),Sql Trace (st05) and Performance Analyzie

Can any one tell me the Diff b/w Run time Analyizer(se30),Sql Trace (st05) and Performance Analyzie(al21) ?

Hi
these all are doing t he same thing that is checking the program for better performance
Tools for Performance Analysis
Run time analysis transaction SE30
SQL Trace transaction ST05
Extended Program Check (SLIN)
Code Inspector ( SCI)
Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Extended Program Check
This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.
Code Inspector (SCI)
You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).
The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.
reward if usefull

ST05: different ways to analyze SQL trace, different authority checks

Hi there,
Here is the issue I faced.
I need to analyze SQL statement for example. I can do it two ways:
1) run ST05> Enter SQL statement> Explain
or via trace itself:
2) run ST05> Display trace> Explain
The thing is that when doing it the second way it requires additional authorizations that are not required when going the first route.
Additional authorizations which way 2) requires are:
S_TCODE SM69, SM49
S_DBCON with ACTVT=36
I was able to remove check for S_TCODE using transaction SE97, so that S_TCODE is not checked for SM69 and SM49 now for ST05 transaction. As for the S_DBCON - as SAP says:
"36 Extended Maintenance
Permission to execute all kinds of SQL statements on the database. This authorization is
extremely powerful and should not be granted on a routine basis.
Extended Maintenance, which should be restricted from use. This authorization allows a user
to execute any SQL statements on the database it is granted for. Improper use of this
feature can do significant damage."
So this object with ACTVT=36 cannot be given to a basic developer or basis, only to superuser, right?
My question is,
Is there way to go the second way (as it is more convinient to analyze SQL statement when viewing trace) and not to give the authorization above?
P.S.
ECC6.0, MSSQL, SAP_BASIS 700, SP 18
Thanks,
Igor
Edited by: Igor Kustov on Sep 21, 2010 8:10 AM

Julius, thanks.
Well, yes, when in Trace List there is a button "Editor for Changing SQL Statement" which brings you to the Enter SQL statement screen (first option in my original post) with the statement you clicked on and ability to change it. You click "Explain" and analysis appears with no additional checks there.
It is strange why S_DBCON with ACTVT=36 is required to just push "Explain" button within Trace list. From my experience the ability to execute any SQL code (natively to RDMS) from either ST05 or ST04 was revoked with basis SP12 when DBACOCKPIT was introduced.
OK, it looks like there is a workaround to analyze a statement from trace with two clicks and not just one. May be I should open a message with SAP then.
But still, since you cannot execute SQLs anymore what this S_DBCON with Extended maintenance acitivity is intended for?
Thanks,
Igor

Code inspector, SQL trace

Hi all,
Can anyone help me to analyse the output of sql trace and code inspector that we do for a program.
Thanks & regards,
Saroja.

SQL trace(ST05) provides the developer with the ability to analyse database select statements. Simply execute ST05 to turn on SQL trace, then execute the statement/program you want to analyse. Now turn off SQL trace using ST05
and click on list trace to view the details.
If you notice performance issue, you can perform an SQL trace :
1 - ST05
2 - Activate trace
3 - Run your prog.
4 - Deactivate trace & display it !
You'll see accessed tables, with runtime, etc...
You can also perform traces on other items such as authorisation objects.
Authorisation trace analysis 1. Open two sessions
2. Execute transaction ST01 in one of the sessions
3. Select the authorisation checkbox, note the other traces
you can perform (SQL, RFC, Table Buffer etc)
4. Click the 'Trace On' button
5. Within your other session execte the transaction/report
you want to trace or get the user in question to do it
6. Return to the session where you turned the trace on and
click on 'Trace Off' otherwise it will continue to record
all athorisation checks
7. Click on the 'Analysis' button
8. Enter appropriate data into selection screen such as
Username, type of trace records (i.e. Authorization check)
9. Click on the Execute button.
10. Report displaying trace results will now be displayed
http://www.sapdevelopment.co.uk/perform/perform_sqltrace.htm
Code inspector is a static check on your code. This check highlights statements that MAY cause long run times or inconsistant results.
This is new as of 6.10, it can be installed on 4.6C or 4.6D systems.
Code inspector includes the checks from the earlier 'Extended program check', (also transaction SLIN). The transation code for 'Code inspector' is SCII.
Regards,
Amey
Message was edited by:
Amey Potale

Ho to automate data extraction from KSB1 and GR55 transaction code

Hi All,
Can you please let me know if their is a way to automate data extraction from transaction code KSB1 and GR55. I have to extract data from 5 different servers .i.e different server for each region and again i have different controlling area codes in each region. Following are the details which i use to extract the data. It takes too long for me to extract data from all this regions and controlling area codes using my parameters. It's very time consuming so i want to automate this process. I am end user so i don't have any admin rights. Please let me know any workable solution asap.
Production areas : PNA for Americas, PSI for Asia Pacific and Japan, PGY for Germany, PIT for Italy and PEU for Europe
Controlling area codes in PNA : CAR for Argentina, CBR for Brazil, CMX for Mexico and CUS for USA. Same way there so may other controlling area codes for all other production areas
Period From 1 to 12
Fiscal Year : 2009
Cost Centre Group : G_6284
Cost Element Group : 1742000000
Please let me know in case you need more details.

Hi,
Here follows a translation from German:
SAP GUI (client) for Windows enable
Start SAP Logon and log on to the SAP server.
Click the button on the toolbar to adjust for Local Layout.
Click Options and then click the tab for the scripting.
Select the Enable checkbox for scripting.
Disable the checkbox for Notify when a script is assigned to an active GUI and the checkbox for Notify when a script opens a connection.
Save the settings and restart the SAP GUI again.
SAP-server enable
With the following procedure, you can enable scripting by the SAP client temporarily. The specified value in this way is lost when you restart the server.
Start SAP Logon and log on to the SAP server.
Start a transaction RZ11.
Enter sapgui / user_scripting in the window to manage the profile parameters.
Click on ads.
Click in the window to display the profile parameter attributes to change value.
Enter TRUE in the field for a new value.
Save the settings and log out from the SAP GUI.
Quit the SAP Logon.
Note:
If the server administrator edited the application server profile of the SAP system to sapgui / user_scripting = TRUE to include the scripting is enabled when you restart the server by default.
SAP provides an option to change the network connection mode at any server. The following two connection modes are available: high-speed connection (LAN) and connecting with a slow speed. Although Functional Tester works in both modes, the high-speed connection with a recorded script is played only in this mode. This also applies to other modes. They must reflect your SAP script in the same network connection mode, with which the script was recorded. It is recommended that the mode of "high-speed connection, as it offers a greater number of valid recognition properties.
Regards,
ScriptMan
Edited by: ScriptMan on Apr 13, 2010 12:32 PM

What is Transaction Code to start report RSNAST00 as a backgroud process ?

I would like to know the Transaction Code or the Access Path to start report RSNAST00 as a backgroud process at a certain time ((Tools > Administration ?).
Thanks.

Hi Oscar,
1.You can go to SE38 give the report RSNAST00 and give the input criteria.
2. Now save this as a variant in the path Goto-Variant-Save as Variant
3. In the new screen give a variant name and save it with a description
4.Now go to SM36 and give a job name, and job class (Status should be scheduled and target server should be nil
5.Then click the Step button at the top
6. In the new screen, click the button ABAP program, and in that screen meant for ABAP program, in the place of name, give the program which you want to execute(In this case RSNAST00) and select the variant of your program which needs to be executed.
7. If you want the ouputs to be triggered in some specific language, you can mention the language also.Otherwise it will be executed in your logon language.
8.If you want the background job to be executed with some other user id, that user id can be mentioned in the user id field at the top.
9. After entering these data, click the check button and then save this.
10. Now the screen will go off, and the earlier will come. Now click save in this screen once again.
11.Now click the startcondition button at the top, click the Date/time button in the new screen and give the date and time at which the job should execute.
12. Save the new screen.
13. Again save the old screen now.
Once this is done, the job will be automatically scheduled for the time you have mentioned, Now you can check this job in SM37 at that time.
Pls reward points if it helps.

Sql trace (st05)

hi friends
.pls tell in detail how to evaluate the performance of one select querry by using sql trace.( pls tell all traces )

Kumar,
SQL Trace
SQL trace(ST05) provides the developer with the ability to analyse database select statements. Simply execute ST05
to turn on SQL trace, then execute the statement/program you want to analyse. Now turn off SQL trace using ST05
and click on list trace to view the details.
You can also perform traces on other items such as authorisation objects.
Authorisation trace analysis 1. Open two sessions
2. Execute transaction ST01 in one of the sessions
3. Select the authorisation checkbox, note the other traces
you can perform (SQL, RFC, Table Buffer etc)
4. Click the 'Trace On' button
5. Within your other session execte the transaction/report
you want to trace or get the user in question to do it
6. Return to the session where you turned the trace on and
click on 'Trace Off' otherwise it will continue to record
all athorisation checks
7. Click on the 'Analysis' button
8. Enter appropriate data into selection screen such as
Username, type of trace records (i.e. Authorization check)
9. Click on the Execute button.
10. Report displaying trace results will now be displayed
http://www.sapdevelopment.co.uk/perform/perform_sqltrace.htm
Some useful transaction related to this are ..
ST01 SAP system trace
ST02 Buffer statistics.
ST03 Workload analysis.
ST04 Database performance analysis.
ST05 SQL trace .
ST06 Operating system monitor ...
From the recorded SQL trace you can deduce:
· Which SQL statements your application carries out
· Which values the system uses for specific database accesses and changes
· How the system translates ABAP OPEN SQL commands (such as
SELECT) into standard SQL commands
· Where your application positions COMMIT statements
· Where your application makes repeated database accesses
· What database accesses or changes occur in the update section of your
application
Look at the below links, you will get the idea
http://help.sap.com/saphelp_erp2005/helpdata/en/d1/801f89454211d189710000e8322d00/content.htm
http://www.sapbrain.com/TOOLS/SQLTRACE/SQL_TRACE.html
Don't forget to reward if useful...

In Transaction code va41 how to set default sales contract start date

Hi ,
In Transaction code " VA41 " how to set default sales contract start date and end date.
Can any one tell me the correct user exit for the same.
Thanks
Basu

hi,
u have to use user exits or badis.
use sutable exits mentioned below.
SDTRM001 Reschedule schedule lines without a new ATP check
SDVFX006 User exit: Tax line (transfer to accounting)
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
Edited by: katigiri linganna on Apr 28, 2009 12:19 PM

Requesting a list of transaction codes with starts from sd and fi..........

hi,
sap gurus,
requesting a list of transaction codes which ends from SD point of view and
starts with FICO module.
i.e. which deals with posting of revenues from the customer to A/R.
plz requesting to find a solution for my question.
regards,
balaji.t
09990019711.

hi
T.codes SD
http://www.sap-img.com/sap-sd/sap-sd-transaction-codes-list.htm
http://www.sap-img.com/sap-sd/task-specific-sd-transaction-codes.htm
http://www.sap-img.com/sap-sd/task-specific-sd-transaction-codes-2.htm
http://www.sap-img.com/sap-sd/sap-sd-tcodes-for-india.htm
http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
Reports
http://www.sap-img.com/sap-sd/standard-sap-sd-reports.htm
Tables :
http://www.sap-img.com/sap-sd/important-tables-for-sap-sd.htm
nagesh

Automatically start SQL Agent service after SQL Server service fails and starts.

Hi!
I have SQL Server 2008 R2 with two main services - SQL Server and SQL Agent.
I'll try to describe my situation. It happens very occasionally, but sometimes SQL Server service terminates unexpectedly. It's my log:
09/13/2013 10:46:21,Service Control Manager,Error,The SQL Server (MSSQLSERVER) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
09/13/2013 10:46:21,,Error,[359] The local host server is not running,,,,
09/13/2013 10:46:22,MSSQLSERVER,Error,The MSSQLSERVER service terminated unexpectedly.,Server,1073760843,,
09/13/2013 10:46:22,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #1)...,,,,
09/13/2013 10:46:27,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #2)...,,,,
09/13/2013 10:46:32,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #3)...,,,,
09/13/2013 10:46:32,,Error,[140] AutoRestart: The MSSQLSERVER service could not be restarted after 3 attempts,,,,
09/13/2013 10:46:32,,Warning,[360] SQLServerAgent initiating shutdown following MSSQLSERVER shutdown,,,,
As you can see, SQL Server service terminates unexpectedly. Then SQL Agent service tries to start SQL Server service. After unsuccessfully attempts to start SQL Server service, SQL Agent service stops itself. I have the option setting in SQL Server
service to start itself after unexpectedly stop within 2 minutes and it is works well. But I have to start my SQL Agent service after this manually. Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly and in this case I just want
to make the settings to start both of my services SQL Server and SQL Agent automatically after this. How can I set up this? How can I make my SQL Agent service starts after SQL Server service?

Hello,
SQL server agent service depends on SQL server service so unless SQL server service comes online agent will not come online so agent is depended on SQL server not the other wise.
Now is your server 2008 R2 patched to latest service pack (SP2).If not please upgrade it to latest SP.Some fixes are there in Sp which will subside this issue.Can you paste output of
select @@version
>>Then SQL Agent service tries to start SQL Server service.No this is not the case
>>Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly
Did you checked sql server errorlog and windows event log completely.Please do so and paste if you find some more info
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Starting SQL-Trace Automatically - Transaction Code: ST05

Similar Messages

Maybe you are looking for