Code Inspector errors

[Former Member]

Metrics and Statisitics

FANOUT Structural Metrics

Warnings

Message Code KW_FANOUTS

FANOUT value on processing block level is 14 => exceeds limit 10

Above is the code inspector error i am getting. not sure about the FAN OUT can some one help me how to get rid of the above error.

[Former Member]

You could choose to turn off that check...if you want to know what fanout is about, press the blue information ICON...it reports source code cross-linking.

[Former Member]

Hello,

Below is what i am seeing in the information button.

CA CL_CI_TEST_METRIC_STRUCT 0000

____________________________________________________

Code Inspector

FANOUT Structural Metrics

Short Description

Structural metrics measure the level of cross linking of different parts of the source code. FANOUT is a structural metric that counts the number of distinct references from one source element (modularization unit) to another one. That means method invocations, function calls, and form routine calls are counted.

Metrics

FANOUT on development object level

FANOUT on subroutine level

<<<<<<<<<<<<

Please let me know how to get rid of this error.......is there any way or any statement will work ........

any "#EC ...... pseudo code is there

Configuration

The calculation of FANOUT on development object and subroutine level can be selected.

Choose 'Show warnings' to get a warning message when a given threshold is exceeded for one modularization unit or development object.

Known Issues

The calculation of FANOUT on subroutine level is relatively slow. For large programs or function groups (> 100.000 lines of code) this calculation may take several seconds.

Edited by: sugunav on Jun 30, 2010 5:02 PM

[Former Member]

Hi,

In simple terms, the check looks at code modules (methods, function modules) and flags up if they are called from a large number of places.

Regards,

Nick

[Former Member]

Hello Nick,

yes what u said is right ........

So what shuld i do now.........to get rid of that error

[Former Member]

Hi,

Well, now you understand what the check is showing, you need to decide, in the context of the code it has highlighted whether it represents a risk or not.

For example, if I create a subroutine to create a standard report header and call it from every report I write it would be flagged by this check, but is not a risk to the stability of the code and would not have a bad impact if you changed the header. In this case I would do nothing.

Regards,

Nick

[Former Member]

Thank u