Code inspector variant

hi i want to capture all the hard coded values in the program by running code inspector how can i set that option while creating the variant for that,please suggest,when i had looked at the options i did not find please help in this regard.
Babita

problem solved..

Similar Messages

How to create code inspector variant?

Hi all,
how to create code inspector variant?
Regards,
Jeetu

Go to SE38 - Type in your program name
Then in menu Go to Program - > check -> Extended program check ->
You can select the rules to check
Press the edit button and save with some name
regards
Vivek
reward points if this helps

How to create and transport my own globel check variant for Code Inspector

Hi,
I want to create my own global check variant with Code Inspector, so that I can transport the Variant in other systems, but I can not save my variant whitout registering a SSCR-Key.
Can anybody help me?
Best regards
Marcus

I have solved it myself and will post the solution here soon.

How to change Variant in Code inspector from Global to local.

Hi,
I have created my own variant,object set and inspection through T-code SCI and this has been created only for my id.
Now when i go to SE38 and run Code Inspector i want the CI to use my variant instead of the Global DEFAULT variant.
Kindly tell me how can i change from DEFAULt to my Local Variant.
Many Thanks.

Hi,
abap_learner_das wrote:
> Now when i go to SE38 and run Code Inspector i want the CI to use my variant instead of the Global DEFAULT variant.
in that case you have to create a variant called "DEFAULT" as your local one. That variant will be used in SE38.
In SE38 you can only use the DEFAULT variant. either the global one (if your user does not have a local one named DEFAULT) or the local one of your user.
HTH,
Hermann

Execute ABAP Code Inspector from Outside of SAP

Hi all...
For reporting purpose, I would like to use ABAP Code Inspector (transaction SCI) for generating output as a file, it should call from outside of SAP through RFC function module and generate the list (output) as flat file (or XML), does anyone have been done with similar work like this? I wonder if you could share your experience with me...
thanks in advance,
yayan irianto.

I managed to set up the variant, however found a problem.
I used "Search ABAP Statement Patterns" under "Search Functs" and set the pattern like followings.
SELECT + INTO *
SELECT SINGLE + INTO *
However following statements were detected.
SELECT * INTO TABLE IT_DRAW FROM DRAW.
SELECT MANDT INTO TABLE IT_DRAW FROM DRAW.
SELECT SINGLE * INTO TABLE IT_DRAW FROM DRAW.
SELECT SINGLE MANDT INTO TABLE IT_DRAW FROM DRAW.
It's because + means one ABAP token in the code inspector.
Is there anyway to find only "SELECT SINGLE *" and "SELECT *" ?

What exactly is the function of code inspector

Hi,
Pelase let me know the function of code inspector and related transaction with it.
Thanks in advance
Regards
Irfan Hussain

Hi Irfan,
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/frameset.htm
Thanks and Regards,
Ashish.

Transport Organizer Syntax Check using the Code Inspector

dear fellows,
i'm facing a problem when i check the syntax of transport. When i'm using the option to check the syntax within the transaction se01 the system starts no longer the extended check but the code inspector.
is there any possibility to turn this code inspector check off and to get the extended syntax check again?
or on the othe hand, which variant is used for the check and is there any possibility to change the variant that is used?
thanks for your answers,
Robert

Nope... this is SAP standard code so I will reply to the OSS and wait for them to come back to you.
Regards
Juan

Abap code inspector (tx : SCI) to detect certain patterns

Hello Experts,
I want to use SAP Code Inspector to detect common problematic ABAP codes for all developed programs.
But, I don't know how to make the check variant for detecting follwoing three patterns.
SELECT * FROM
SELECT * INTO
SELECT SINGLE * INTO
I guess I can use "Search for ABAP tokens" or "Search for ABAP statements paterns". But, It did'nt work because ' * ' represents any sequence of characters in the code inspector.
Anyone can help me?

I managed to set up the variant, however found a problem.
I used "Search ABAP Statement Patterns" under "Search Functs" and set the pattern like followings.
SELECT + INTO *
SELECT SINGLE + INTO *
However following statements were detected.
SELECT * INTO TABLE IT_DRAW FROM DRAW.
SELECT MANDT INTO TABLE IT_DRAW FROM DRAW.
SELECT SINGLE * INTO TABLE IT_DRAW FROM DRAW.
SELECT SINGLE MANDT INTO TABLE IT_DRAW FROM DRAW.
It's because + means one ABAP token in the code inspector.
Is there anyway to find only "SELECT SINGLE *" and "SELECT *" ?

Code Inspector - Naming conventions &mExtended Naming conventions for Progs

Hi experts,
I had a look into the naming conventions enforced by 'DEFAULT' variant of code inspector (SCI).
the relevant categories are: "Naming Conventions", and "Extended Naming conventions for Programs" under "Programing conventions".
in the "Extended Naming conventions for Programs" category, for functions, (applicable while calling the functions) it says,
importing parameter : I[:type:]_
exporting parameter : E[:type:]_
changing parameter : C[:type:]_
tables parameter : T[:type:]_
but in the "naming conventions" category, for functions (applicable while defining the functions), it says,
importing parameter : P_*
exporting parameter : P_*
changing parameter : P_*
tables parameter : P_*
I felt, while defining the function too, its better to have beginning with I_, E_, C_ or T_ instead of P_
is the 'DEFAULT' variant of code inspector is provided and recommended by SAP?
for easier maintenance and clearer understanding, which naming convention is more suitable, or is there any official guidelines released by SAP for ABAP developers.
appreciate the opinions from experienced abap developers.
thanks,
Madhu_1980

Frank,
Thanks for your answer.
But what about Entity Objects, View Objects, View Links, and Application Modules.
I would like my developers to have an easy way to name them and also find them via intellisense.
So I was thinking in naming them the following way :
Entity Objects :
EO_Employee
EO_Department
View Objects :
VO_Employees
VO_Departments
View Links :
VL_EmployeesToDepartments
Application Module :
AM_HRService
However the use of "_" is not so "Java naming oriented".
So other alternatives would be:
1. take the "_" :
1.1 EOEmployee (I don't like the fact of having 3 capital letters together).
1.2 EoEmployee (I don't like the fact of having Entity Object with a lowercase "o").
2. Use the prefix at the end, but this way I loose the intellisense feature I want:
ex: EmployeeEO
Which naming approach are you using for big projects ?
Thanks,
Claudio.

SAP Code Inspector

Hi Everyone,
In our project we have a requirement to automate the code review checklist preparation to the maximum extent possible.
Code Inspector has some standard checks included into it from which we can select the relevant checks for inspection purpose. My question is, whether we can customize it to add few more checks to meet our requirement or whatever standard check is there is the most we can have??????
SAP Ver 4.6c.
Any links to download relevant materials?
Any one having any custom object build for this purpose they can share it.
It would be of great help.

Hi
http://help.sap.com/saphelp_nw04/helpdata/en/56/fd3b87d203064aa925256ff88d931b/content.htm
see tis link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/50456d27-0a01-0010-ed95-ba71d8f0d74b
http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci918390,00.html?NextURL=http%3A//searchsap.techtarget.com/tip/0%2C289483%2Csid21_gci918390%2C00.html
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.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/sap-teched-03/abap%20troubleshooting
http://help.sap.com/saphelp_erp2004/helpdata/en/56/fd3b87d203064aa925256ff88d931b/frameset.htm
<b>Reward if usefull</b>

ABAP Code Inspector & Security

All:
I am currently looking into the Code Inspector that is built into SAP that allows developers to run test/checks on their code related to performance, syntax, and as noted "security". I am trying to track down what exactly the "security" is being checked. I am running tests on my internal SAP systems to see how it acts, but I wanted to get any feedback from the security community on a few things
1) What "security" checks does the Code Inspector actual check for?
2) Is there an location with updated documentation from SAP (not dated 2002) which speaks to the security componet, not just mentioned it?
3) Any useful use-cases within the security community that your organization/clients are using?
Thanks,
Matt Urban

Hi,
if you display a check variant in SCI there is info linked to each node (icon with I). For example calling C-routine is a security risk. Also dynamic statements are good example of security risk. You need to validate input properly before executing dynamic statement. Not sure about documentation but documentation available in SCI seems OK to me.
On one project we used SCI to check any custom development (not only security). It helped us to increase quality of custom development. Especially, with less skilled developers.
Cheers

Code Inspector/ATC checks for VKOS/VKOI object types

Dear Experts,
I found a strange behavior while executing CI checks on a transport request. TR contained only IMG Activity objects (Object Type VKOS/VKOI). After CI checks it gave errors "Recognized dead code". There is no coding for these kind of object type, I don't know where it was able to find the dead code. On debugging I found that, it is trying to populate Program name concatenatinv " SAPIC " and the object type. ( SAPICVKO). But there is no such program existing. It then gives "Recognized dead code" error.
Has anyone faced such error before? I guess this is error in the standard program.
Thank you.

Other language NUnit test frameworks similar to ABAP Unit (AUnit) commonly have project extensions for storing test results. These are useful for the unit level regression (did a new change break any existing functions). History of test results, help narrow down the nature of a current failure by answering the question of 'When did this break?' or when did it last pass? In systems dependent upon outside components the history can provide a pattern for occasional failures due to factors outside the system under test.
I see that ABAP unit test results can be added into the Code Inspector under the Check Variant.
1. Is it common or recomended to use the Code Inspector (SCI) to store AUnit test results?
2. Is it common or recomended to use Code Inspector Object variants to collect individual AUnit tests for a regresssion style 'TestSuite'?
3. What reporting or tools exists for Code Inspector history?
4. Is Application Logging the better spot for AUnit results history?
(also posted on the wiki.. apologies - I'm new to the forum and wiki)
Will Loew-Blosser

Code Inspector Development

Hi all,
        We have been assigned to make our own code inspector in 4.6 right from scratch , at this point of time we are not able to understand how to proceed.Kindly help with the flow.
Regards
Gaurav Mehrotra

Hi try this
To build a new Code Inspector check, you have to do the following:
·     Create a new global class that extends one of the existing Code Inspector classes
·     Implement the instance constructor
·     Implement the actual check routine in the RUN method
·     Implement method GET_ERROR_TEXT to output message texts
·     Include the new check into the check variant tree
Additionally, if your check has user parameters:
·     Add user parameters as private class attributes to your check class
·     Set flag HAS_ATTRIBUTES in the instance constructor
·     Implement methods GET_ATTRIBUTES and PUT_ATTRIBUTES to get and write away attributes
·     Implement method QUERY_ATTRIBUTES of interface IF_CI_TEST to create the Pop-Up for the parameter input
Hope thsi Helps
Anirban

Code Inspector & ABAP UNIT Testclasses

Hallo all,
I am currently trying to implement automated checks using the code inspector. I especially want to see if all our developers use our naming conventions. Also, we use ABAP Unit tests. Unfortunately, the generated test classes are not compliant with our name conventions (And also these Test classes are not interesting to be checked).
Now, I receive many warnings, mostly from the Unit test implementations.
Now: Is there a way to exclude these local test classes from my object set?
Thanks for you help!
Best regards,
Martin Imme

Other language NUnit test frameworks similar to ABAP Unit (AUnit) commonly have project extensions for storing test results. These are useful for the unit level regression (did a new change break any existing functions). History of test results, help narrow down the nature of a current failure by answering the question of 'When did this break?' or when did it last pass? In systems dependent upon outside components the history can provide a pattern for occasional failures due to factors outside the system under test.
I see that ABAP unit test results can be added into the Code Inspector under the Check Variant.
1. Is it common or recomended to use the Code Inspector (SCI) to store AUnit test results?
2. Is it common or recomended to use Code Inspector Object variants to collect individual AUnit tests for a regresssion style 'TestSuite'?
3. What reporting or tools exists for Code Inspector history?
4. Is Application Logging the better spot for AUnit results history?
(also posted on the wiki.. apologies - I'm new to the forum and wiki)
Will Loew-Blosser

Code Inspector: Enhancement / Adding own rules?

Hi All,
I wonder whether there is a way to add own rules to the Code Inspector.
With own rules I mean checking the coding against our development guidelines, just two examples:
1) Before SELECT ... FOR ALL ENTRIES it needs to be checked, whether the internal table is not initial.
2) No direct table update to SAP tables.
I locked to SCII. I believe it is not a solution to define a new check variant, since I haven't found the possibility there to add own rules (just naming conventions, searching for characters).
Thus, I wonder whether there is any user-exit, BAdI etc. I could use - or do I really have to write my own parser - which would be a nightmare (multiple meanings of statements (INSERT can change an internal table or database table - depending on the table / variable given); considering global variables, method parameters etc.).
Any advise is welcome!
Best regards
Lars

Hi Lars,
Check the below link to customize SCI as per your requirement.
http://sapignite.com/enhancement-of-code-inspector/
<removed by moderator>
Thanks
SA
Edited by: Thomas Zloch on Feb 18, 2011 5:44 PM - please do not beg for points, age old thread by the way

Code inspector variant

Similar Messages

Maybe you are looking for