Message Number list used by SAP ABAP Function Module TR_CHECK_TRESN (TR_CHECK_TRESN)
SAP ABAP Function Module
TR_CHECK_TRESN (TR_CHECK_TRESN) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | TR - 309 | Name too long for cross-type reservation (maximum &1) | ||
| 2 | TR - 734 | &1 &2 is not a valid object ID for reservations | ||
| 3 | TR - 727 | Name range occupied by object &1 &2 in package &3 | ||
| 4 | TR - 726 | Name range &1 overlaps with existing reservation &2 &3 | ||
| 5 | TR - 341 | Generation namespace: Naming convention is not checked automatically | ||
| 6 | TR - 337 | Package &1 does not exist in this SAP system | ||
| 7 | TR - 324 | Reservation conflicts with reservation for &2 | ||
| 8 | TR - 323 | Namespace for object type &2 overlaps with other namespaces | ||
| 9 | TR - 317 | You can only make cross-type reservations for namespaces | ||
| 10 | TR - 310 | Cross-type reservations only possible as R3TR ALLE | ||
| 11 | TR - 256 | Generic name &1 for object &2 is in customer name range | ||
| 12 | TR - 298 | Value &1 not valid for mode flag | ||
| 13 | TR - 297 | Your entry in field &1 is incomplete or contains invalid values | ||
| 14 | TR - 296 | Enter a complete key for the reservation | ||
| 15 | TR - 291 | Choose another package for reservation &1 &2 &3 | ||
| 16 | TR - 285 | &1 &2 &3 is not a valid key for reservations | ||
| 17 | TR - 284 | Name &1 is longer than the maximum object name length permitted | ||
| 18 | TR - 259 | No longer possible to edit application-specific messages | ||
| 19 | TR - 258 | Enter generic namespace &1 without "*" | ||
| 20 | TR - 257 | Generic name &1 for object &2 is in SAP name range |