Skip to content

Commit aa3c786

Browse files
Update function-routine.md
1 parent ae92105 commit aa3c786

File tree

1 file changed

+2
-8
lines changed

1 file changed

+2
-8
lines changed

docs/checks/function-routine.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,24 @@
1-
# code pal for ABAP
2-
31
[code pal for ABAP](../../README.md) > [Documentation](../check_documentation.md) > [FUNCTION Routine Check](function-routine.md)
42

53
## FUNCTION Routine Usage Check
64

75
### What is the Intent of the Check?
86

9-
`FUNCTION` Modules are sub-programs in procedural programming. With the release of Object Oriented ABAP this syntax became obsolete.
7+
This check searches for the usage of FUNCTION Modules (procedural programming) since with the release of Object Oriented ABAP this syntax became obsolete.
108

119
### How does the check work?
1210

1311
This check searches for Function Modules within a function group. However, since Remote Function Calls (RFC) can only be executed via FUNCTION MODULES, these ones (Function Modules with RFC enablement) will not be caught by this check.
1412

1513
Note: This check does not search for the `CALL FUNCTION` statement within your source code (e.g. in a method or program).
1614

17-
### Which attributes can be maintained?
18-
19-
![Attributes](./imgs/function_module_usage.png)
20-
2115
### How to solve the issue?
2216

2317
Use classes and methods instead (Object Oriented ABAP).
2418

2519
### What to do in case of exception?
2620

27-
You can suppress Code Inspector findings generated by this check using the pseudo comment `"#EC CI_FUNCTION`.
21+
In exceptional cases, you can suppress this finding by using the pseudo comment `"#EC CI_FUNCTION` which should be placed after the FUNCTION statement:
2822

2923
```abap
3024
FUNCTION my_function. "#EC CI_FUNCTION

0 commit comments

Comments
 (0)