For all ABAP’ers, Project-Leads and SAP Customers in general,

I am collecting a


Statistic of the size of custom developments in SAP R/3 ERP system

for science-based data and evaluation.

For that matter, I have created a small procedure and guideline, and the complete check can usually been done in less then 5 minutes.

If you’re done with that, please submit your results as a private message within the SAP SCN or by direct eMail to the mail address, which you can find on my profile’s public information.

Your results shall have the following information

  • Number of operative statements from the result of the code inspector
  • SAP Release, if available
  • Modules mainly in use, if available, such as: MM / WM / FI / CO … in that manner
  • Industry area of the business
  • The system ID on which you’re executing the statistic. If your company runs several systems, you may do this on all available D-Boxes / Q-Boxes
  • The FIRST LETTER of your company name, to avoid duplicate statistics (when providing industry area), otherwise please provide the FIRST TWO LETTERS

Your submitted results will be kept anonymously and any references to a company will be removed immediatly, including the source domain name of the eMail from which the result was sent from.

All contributors will receive a complete result of the anonymous statistics

so you can compare and rank/classify your own system.

Thank you for your collaboration!

And this is, how you do it!

Code inspector

Use transaction SCI in the development system (or Q/A box)

Create a personal

Check variant ZMS_COUNT_STATISTICS

Press the “Create” button on the bottom of that screen.

Depending of the version of the Code-Inspector, you can find the Statements Statistics in two different places:

Expand the tree “Metric and Statistics” –> “Statement Statistics”  or

Expand the tree “General Checks” –> “Statement Statistics”.

or

Set the check box on “Statement Statistics” and click on the parameter-button

In the small dialog that now opens, check the boxes like this:

This will perform a pure count on the coding lines, not taking the complexity as such into account, where you’d then disable the “Without Multiple-Use…” checkbox. However, the results must be comparable across the Customer’s installations and therefore please use exactly these checkboxes, as the results may very pretty much.

Then save the Check variant with the Save button or F11 

Back in the entry screen, create an

Object Set  ZALL_CUSTOM_DEVELOPMENTS

Click on the Create-Button in the middle part of the screen.

In the description fill in

All custom developments excluding generated tabmaintenance

And choose all customer packages, including any namespaces that you may use for your own custom developments.

It may look like this and should always include all packages  Y*   and   Z*

Click on the “Parameter selection” button for the “Package” select option.

Add further customer namespaces, when you’re using it.

Choose the menu option

Important: Edit–>Exclude View Maintenace once

once.

If it already shows up with  Edit –> Include View Maintenance …  it’s okay, because then the generated function groups are excluded from the checks. This is very important, because the table maintenance produces a lot of operative statements. The overall result can vary up to 6 times larger!

Then save the Object set

Now you can finally create the

Inspection ZALL_CUSTOM_DEVELOPMENTS

To do so, press the “Create” button in the upper section of the entry screen.

Within the maintenance there, refer to the both sets that you’ve created previously.

Save the inspection set now:

And then execute the run in background, by choosing

In the job planning screen, choose “Immediate” in execute the job.

  then plan the job:

Retrieving the Code Inspector result

When your job is done, display the inspection set again (when entering it new from the Code Inspector). You will then find the button “Results”, which you can press:

The second button from the right.

An expand the result to see the statistics:

And now you got the number (here as an example) of at  1,540,034 statements in the customer namespace.

Please remember to include the following information to your statistics submission:

  • Number of operative statements from the result of the code inspector
  • SAP Release, if available
  • Modules mainly in use, if available, such as: MM / WM / FI / CO … in that manner
  • Industry area of the business
  • The system ID on which you’re executing the statistic. If your company runs several systems, you may do this on all available D-Boxes / Q-Boxes
  • The FIRST LETTER of your company name, to avoid duplicate statistics (when providing industry area), otherwise please provide the FIRST TWO LETTERS

With many many thanks for your contribution.

   Florin Wach

   Systems-Integration

   Senior Workflow-Engineer

To report this post you need to login first.