Message Number list used by SAP ABAP Program LSCTS_REQUEST_CHECKF03 (Include LSCTS_REQUEST_CHECKF03)
SAP ABAP Program LSCTS_REQUEST_CHECKF03 (Include LSCTS_REQUEST_CHECKF03) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | CUSDIR - 410 | Table &1: Cannot use a generic transport | |
2 | Message Number | TK - 332 | Only edit objects from package &2 in local requests | |
3 | Message Number | TK - 018 | Object component &1 &2 &3 can only be edited via the complete object &4 | |
4 | Message Number | TK - 357 | Object "&1" "&2" "&3" cannot be transported | |
5 | Message Number | TK - 370 | Namespace conflict between object &1 and target package &3 | |
6 | Message Number | TK - 427 | No object definition exists for customizing object &1 | |
7 | Message Number | TK - 527 | Invalid object &1 for transportable workbench request | |
8 | Message Number | TK - 551 | No valid delivery class for table & | |
9 | Message Number | TK - 552 | Table & belongs to delivery class "W" (system table) | |
10 | Message Number | TK - 554 | View & has delivery class "W" (system table) | |
11 | Message Number | TK - 597 | System variants have to start with "SAP&&" or "CUS&&" | |
12 | Message Number | TK - 598 | Application variants may not begin with "SAP&&" or "CUS&&" | |
13 | Message Number | TK - 686 | Object name missing for entry "&1" "&2"; check your entry | |
14 | Message Number | TK - 692 | Object name "&1" has invalid format | |
15 | Message Number | TK - 734 | Object &1 is not permitted in the Customizing request | |
16 | Message Number | TK - 741 | Object belongs to function group with customer exit | |
17 | Message Number | TK - 742 | Address function group &1 as normal function group | |
18 | Message Number | TK - 758 | Object &1 &2 &3 is from a DDL source; no transports possible | |
19 | Message Number | TK - 838 | A relocation with package change cannot contain a package | |
20 | Message Number | TK - 323 | &1 is a table, it cannot be accessed as a view | |
21 | Message Number | TK - 019 | Specify the name of a variant for report &1 | |
22 | Message Number | TK - 159 | You cannot transport the contents of the table &1 | |
23 | Message Number | TK - 176 | &1 belongs to a system object; processing must be via this object | |
24 | Message Number | TK - 276 | & is an application table | |
25 | Message Number | TK - 277 | Table & contains temporary data (transport not possible) | |
26 | Message Number | TK - 281 | Note: & is an application table | |
27 | Message Number | TK - 282 | Note: & is a table for temporary data | |
28 | Message Number | TK - 300 | Object must belong to package &1 | |
29 | Message Number | TK - 304 | Object &3 is not original in this system | |
30 | Message Number | TK - 305 | Relocations cannot contain subobjects | |
31 | Message Number | TK - 306 | Transport objects from package &2 to target &1 only | |
32 | Message Number | TK - 308 | Do not enter test objects in transportable workbench requests | |
33 | Message Number | TK - 309 | Request lock for &1 is in invalid task/request &2 | |
34 | Message Number | TK - 310 | &1 is locked in request/task &2 | |
35 | Message Number | TK - 311 | Unknown syntax "&1" "&2" "&3" | |
36 | Message Number | TK - 316 | Object &1 is not a database table | |
37 | Message Number | TK - 324 | &1 is a view, it cannot be accessed as a table | |
38 | Message Number | TR - 601 | Object name &3 is too long, abbreviate it | |
39 | Message Number | TR - 731 | System objects cannot be transported directly (e.g. T100, TRDIR, TFDIR..) |