05-09-2008 4:12 AM
05-09-2008 4:20 AM
*code inspector:
*The Code Inspector (transaction code SCI) is a tool for checking Repository objects regarding performance, security, syntax, and adherence to name conventions. You can also determine statistical information or search for certain ABAP words (tokens). In the Code Inspector, you can define inspections that, with the help of check variants, examine certain sets of objects. As the result of an inspection, you receive information messages, warning messages, or error messages on different properties of the examined objects.
You can check the following link for details.
http://help.sap.com/saphelp_erp2004/helpdata/en/56/fd3b87d203064aa925256ff88d931b
Code Inspector is SAP tool for the analysis of static ABAP code, data dictionary objects and other repository objects. The tool (transaction SCI) has a set of predefined performance checks that can help you to improve your code so as to optimize the performance of your program.
--The Code Inspector is a tool for checking Repository objects regarding performance, security, syntax, and adherence to name conventions
You can call the Code Inspector using transaction code SCI or through the menu path SAP Menu à Tools à ABAP Workbench à Test à Code Inspector. Also, you can call the Code Inspector from the following transactions:
ABAP Dictionary (SE11) for DDIC tables
Class Builder (SE24) for classes and interfaces
Function Builder (SE37) for function groups
ABAP Editor (SE38) for programs or reports
ABAP Workbench (SE80)
http://help.sap.com/saphelp_nw04/helpdata/en/56/fd3b87d203064aa925256ff88d931b/frameset.htm
List of Code Inspector checks with the categories:
Performance
Security
Syntax Check
General Checks
to have completely knowledge on code inspector
go to se38.open any program.then
go to menu program->check->codeinspector
then you will see a screen.in that screen you will see a blue button named as 'i' in standard tool bar.press that button and click on checkdocumentation.you will find complete details about code inspector.
Reward points..
05-09-2008 4:20 AM
*code inspector:
*The Code Inspector (transaction code SCI) is a tool for checking Repository objects regarding performance, security, syntax, and adherence to name conventions. You can also determine statistical information or search for certain ABAP words (tokens). In the Code Inspector, you can define inspections that, with the help of check variants, examine certain sets of objects. As the result of an inspection, you receive information messages, warning messages, or error messages on different properties of the examined objects.
You can check the following link for details.
http://help.sap.com/saphelp_erp2004/helpdata/en/56/fd3b87d203064aa925256ff88d931b
Code Inspector is SAP tool for the analysis of static ABAP code, data dictionary objects and other repository objects. The tool (transaction SCI) has a set of predefined performance checks that can help you to improve your code so as to optimize the performance of your program.
--The Code Inspector is a tool for checking Repository objects regarding performance, security, syntax, and adherence to name conventions
You can call the Code Inspector using transaction code SCI or through the menu path SAP Menu à Tools à ABAP Workbench à Test à Code Inspector. Also, you can call the Code Inspector from the following transactions:
ABAP Dictionary (SE11) for DDIC tables
Class Builder (SE24) for classes and interfaces
Function Builder (SE37) for function groups
ABAP Editor (SE38) for programs or reports
ABAP Workbench (SE80)
http://help.sap.com/saphelp_nw04/helpdata/en/56/fd3b87d203064aa925256ff88d931b/frameset.htm
List of Code Inspector checks with the categories:
Performance
Security
Syntax Check
General Checks
to have completely knowledge on code inspector
go to se38.open any program.then
go to menu program->check->codeinspector
then you will see a screen.in that screen you will see a blue button named as 'i' in standard tool bar.press that button and click on checkdocumentation.you will find complete details about code inspector.
Reward points..
05-09-2008 8:22 AM
hi, Poli,
Thank you very much. Now I understand the difference between the 2 tools.
Best regards
Blake Le
05-09-2008 4:22 AM
Extended Syntax Check -
Many checks are excluded from the standard syntax check for performance reasons. The extended program check performs a complete check that includes the interfaces of external procedures called from your program.
Errors in the extended program check cause exceptions, which in turn cause runtime errors when you run the program. You must correct them. The exception to this is coding that cannot be reached. However, you should delete this to minimize the size of your program and make the source code easier to understand.
Warnings in the extended program check should also be corrected. If your program contains statements that are definitely correct but still produce warnings in the extended program check, you can exclude them from the check using pseudocomments ( "#EC ).
You should always run the extended program check on a new program. You have not finished developing a new program until you can run the extended program check on it without any errors or warnings. Messages are permissible, since they are generally not critical.
The extended program check is also only a static check. It cannot eliminate all of the circumstances that could lead to exception situations or runtime errors. For example, any statements in which you specify arguments dynamically as the contents of fields, or in which you call procedures dynamically, cannot be checked statically.
Code Inspector -
The Code Inspector is a tool for checking Repository objects regarding performance, security, syntax, and adherence to name conventions.
Please have a look at below link for details of code inspector.
http://help.sap.com/saphelp_nw04/helpdata/en/56/fd3b87d203064aa925256ff88d931b/frameset.htm
I hope it helps.
Please mark useful answers
05-09-2008 5:04 AM
Hi
Code Inspector & Extended Program Check
Code Inspector : (static performance check with the standard)
The SAP Product has a defined set of Performance Standards.
To Monitor compliance with these standards(of the code written), we would use a combination of the following tests:
Static Performance Checks with the Code Inspector for all objects. (checks like Syntax, security, performance, search options which comes with the variant).
Dynamic Includes Runtime, trace tool.
Extended Program Check :
This Check Uses the same set of checks that is available with the workbench transaction SLIN for single objects.
It Process the Syntax check which are too time consuming and too complicated. It first performs normal syntax check..
Compared to normal syntax check if any error found, no further checks are performed. But in normal syntax check it goes up to a limit.
Extra work done by Extended Syntax check compared to normal:
It performs check referenced to external units(Very Important), Multi language text literal, Package check, etc.,
some links :
http://abapprogramming.blogspot.com/2007/11/code-inspector-in-abap.html
http://help.sap.com/saphelp_nw70/helpdata/en/d1/801afd454211d189710000e8322d00/content.htm
Reward Points...