SAP_GUIDELINES - Nur SAP: Pr�fen interner Richtlinien
The following messages are stored in message class SAP_GUIDELINES: Nur SAP: Pr�fen interner Richtlinien.
It is part of development package S_CHECK_RESULT_MANAGEMENT_SG in software component BC-DWB-TOO-ATF. This development package consists of objects that can be grouped under "SAP ONLY: Check Internal Guidelines - SAP GUIDE Module".
It is part of development package S_CHECK_RESULT_MANAGEMENT_SG in software component BC-DWB-TOO-ATF. This development package consists of objects that can be grouped under "SAP ONLY: Check Internal Guidelines - SAP GUIDE Module".
Message Nr ▲ | Message Text |
|---|---|
| 000 | SAP Guide: Programming guidelines |
| 100 | SAP Guide: Naming Conventions |
| 110 | Declaration local constants: (&1) violates naming convention |
| 111 | Declaration of local variable: (&1) violates naming convention |
| 112 | Declaration local field symbol: (&1) violates naming convention |
| 113 | Definition local type: (&1) violates naming convention |
| 120 | Class pool name: (&1) violates naming convention |
| 121 | Name local classes: (&1) violates naming convention |
| 122 | Declaration of constant in class: (&1) violates naming convention |
| 123 | Declaration of instance attribute: (&1) violates naming convention |
| 124 | Declaration of static attribute: (&1) violates naming convention |
| 125 | Definition of type in classes: (&1) violates naming convention |
| 126 | Interface pool name: (&1) violates naming convention |
| 127 | Name local interface: (&1) violates naming convention |
| 128 | Declaration of constant in interface: (&1) violates naming convention |
| 129 | Declaration of instance attribute: (&1) violates naming convention |
| 130 | Declaration of static attribute: (&1) violates naming convention |
| 131 | Definition of type in interface: (&1) violates naming convention |
| 132 | Method: (&1) violates naming convention |
| 133 | CHANGING parameter in method: (&1) violates naming convention |
| 134 | IMPORTING parameter in method: (&1) violates naming convention |
| 135 | EXPORTING parameter in method: (&1) violates naming convention |
| 136 | RETURNING parameter in method: (&1) violates naming convention |
| 137 | EVENT definition: (&1) violates naming convention |
| 138 | EVENT EXPORTING parameter: (&1) violates naming convention |
| 150 | FUNCTION-POOL: Identifier (&1) is not consistent with TADIR definition |
| 151 | FUNCTION-POOL: (&1) violates naming convention |
| 152 | Function module: (&1) violates naming convention |
| 153 | IMPORTING parameter function module : (&1) violates naming convention |
| 154 | CHANGING parameter function module: (&1) violates naming convention |
| 155 | EXPORTING parameter function module: (&1) violates naming convention |
| 156 | TABLES parameter function module: (&1) violates naming convention |
| 160 | REPORT/PROGRAM: Identifier (&1) is not consistent with TADIR definition |
| 161 | REPORT/PROGRAM: (&1) violates naming convention |
| 162 | FORM: (&1) violates naming convention |
| 163 | CHANGING Parameter FORM: (&1) violates naming convention |
| 164 | USING Parameter FORM: (&1) violates naming convention |
| 165 | TABLES Parameter FORM: (&1) violates naming convention |
| 170 | Declaration global constant: (&1) violates naming convention |
| 171 | Declaration global variable: (&1) violates naming convention |
| 172 | Declaration global field symbol: (&1) violates naming convention |
| 173 | Definition global data type: (&1) violates naming convention |
| 174 | SELECT-OPTION: (&1) violates naming convention |
| 175 | PARAMETERS: (&1) violates naming convention |
| 180 | DEFINE macro name: (&1) violates naming convention |
| 181 | FIELD-GROUPS: (&1) violates naming convention |
| 190 | Syntax error: Check of naming conventions is not possible |
| 191 | Internal problem: Symbol (&1) cannot be processed |
| 192 | Internal problem: Identifier (&1) triggered the message (&2) |