Checks

Former Member — Fri, 05 Oct 2007 08:04:24 GMT

Hi,

What are EPC, SLIN overview, UCC check this?

How to do ?

Pls help its urgent

Regards,

Re: Checks

Former Member — Fri, 05 Oct 2007 08:11:56 GMT

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.

Run time analysis transaction SE30

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 – ST05

Starting the Trace:
To analyze a trace file, do the following:
...
Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. 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.
Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).
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.
Now run the program to be analyzed.
Stopping the Trace:
To deactivate the trace:
...
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.
Select the trace functions that you want to switch off.
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-

Analyzing a Sample trace data:
PREPARE: Prepares the OPEN statement for use and determines the access method.
OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.
FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.

Extended Program Check

Clicking on Display All changes shows the details of errors, warnings.

Code Inspector - SCI

Reward if usefull

Re: Checks

Former Member — Fri, 05 Oct 2007 08:13:50 GMT

EPC means Extended program check

SLIN is the Tcode to do it

after completing the program code

from menu

PROGRAM-> CHECK-> EXTENDED PROGRAM CHECK

check the character format and all check boxes and select strict below

execute

it displays all the errors.warnings etc

so that you can correct them

UCC means Unicode Check which is applicable to ECC versions of SAP

When you upgrade from lower versions of SAP to ECC versions this will become problematic as the code is checked against all Unicode errors.

ABAP Unicode Scan Tool UCCHECK

You can use transaction UCCHECK to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.

Regards

Anji

Re: Checks

Former Member — Fri, 05 Oct 2007 08:17:12 GMT

good

SET EXTENDED CHECK

Affects the extended program check.

Syntax

SET EXTENDED CHECK ON|OFF.

Switches the extended program check (SLIN) on or off, suppressing the corresponding messages.

EPC (EP Core) and EP (Enterprise Portal)

Usage types EP Core (EPC) and Enterprise Portal (EP) bring SAP NetWeaver and applications running in it to the user in a uniform and consistent manner. They also provide the tools to manage this knowledge, to analyze and interrelate it, and to share and collaborate on the basis of it.

Usage Type EP Core

Usage type EPC provides the basic portal capabilities of SAP NetWeaver, and provides more flexibility when implementing a portal where the full enterprise portal capabilities are not needed.

http://help.sap.com/saphelp_nw04s/helpdata/en/72/4d7b424bfc173be10000000a155106/content.htm

reward point if helpful.

thanks

mrutyun^

Re: Checks

Former Member — Wed, 14 Jan 2009 22:24:30 GMT

thanks

topic Re: Checks in Application Development and Automation Discussions

Checks

Re: Checks

Re: Checks

Re: Checks

Re: Checks