Message Number list used by SAP ABAP Class CL_CACS_APPL_DATA_CONTROL (ICM: Application Cloner - Control Class)
SAP ABAP Class CL_CACS_APPL_DATA_CONTROL (ICM: Application Cloner - Control Class) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | CACSAPPK - 065 | Copying number ranges from application &1 to application &2 | |
2 | Message Number | CACSAPPK - 076 | Copying application log &1 &2 &3 | |
3 | Message Number | CACSAPPK - 075 | Copying application logs from application &1 to application &2 | |
4 | Message Number | CACSAPPK - 073 | Condition type &1 is not valid for application &2 | |
5 | Message Number | CACSAPPK - 072 | Copying condition record &1 (condition type &2) | |
6 | Message Number | CACSAPPK - 071 | Condition table &1 has no condition type field - no data edited | |
7 | Message Number | CACSAPPK - 070 | Condition table &1 has no condition number field - no data edited | |
8 | Message Number | CACSAPPK - 069 | Condition table &1 is not application-specific - no data edited | |
9 | Message Number | CACSAPPK - 068 | Copying entries of condition table &1 | |
10 | Message Number | CACSAPPK - 067 | Copying condition records from application &1 to application &2 | |
11 | Message Number | CACSAPPK - 066 | Copying PD-Org assignments from application &1 to application &2 | |
12 | Message Number | CACSAPPK - 077 | No messages found for application log (handle &1) | |
13 | Message Number | CACSAPPK - 064 | Generation of target application &1 is complete - read log | |
14 | Message Number | CACSAPPK - 062 | &2 entries inserted in table &1 | |
15 | Message Number | CACSAPPK - 061 | Copying data from table &1 to table &2 | |
16 | Message Number | CACSAPPK - 060 | Cloning construction- and client-independent data | |
17 | Message Number | CACSAPPK - 059 | Generation was not executed - test run | |
18 | Message Number | CACSAPPK - 058 | Generating target application &1 - messages to follow... | |
19 | Message Number | CACSAPPK - 052 | Tgt applic. &1 is being instantiated for client &2 (remote system "&3") | |
20 | Message Number | CACSAPPK - 051 | Source applic. &1 is being instantiated for client &2 (remote syst. "&3") | |
21 | Message Number | CACSAPPK - 049 | Cloning transaction data | |
22 | Message Number | CACSAPPK - 092 | Setting process information | |
23 | Message Number | CACSAPPK - 199 | Source structure &1 (in TCACS_DESFIELDS) does not exist | |
24 | Message Number | CACSAPPK - 198 | Entries in table TCACS_DESFIELDS will be checked | |
25 | Message Number | CACSAPPK - 174 | Application language &1 does not match process language &2 | |
26 | Message Number | CACSAPPK - 173 | Cloning cross-client data; generation will follow | |
27 | Message Number | CACSAPPK - 105 | Table filter is active | |
28 | Message Number | CACSAPPK - 100 | Copying step of master data is missing | |
29 | Message Number | CACSAPPK - 099 | Copying step of client-dependent data is missing | |
30 | Message Number | CACSAPPK - 098 | Copying step of cross-client data is missing | |
31 | Message Number | CACSAPPK - 096 | Original source applic. &1 is not identical to current source applic. &2 | |
32 | Message Number | CACSAPPK - 095 | Original system ID &1 is not identical to current system ID | |
33 | Message Number | CACSAPPK - 048 | Cloning master data | |
34 | Message Number | CACSAPPK - 086 | A non-current client of the target application requires an RFC | |
35 | Message Number | CACSAPPK - 085 | Run was terminated by user | |
36 | Message Number | CACSAPPK - 084 | No detail found in source application &1 for condition record | |
37 | Message Number | CACSAPPK - 083 | &1 PD-Org assignments copied | |
38 | Message Number | CACSAPPK - 082 | Copying client-dependent entries from application &1 to application &2 | |
39 | Message Number | CACSAPPK - 081 | Copying client-independent entries from application &1 to application &2 | |
40 | Message Number | CACSAPPK - 080 | Copying transaction data entries from application &1 to application &2 | |
41 | Message Number | CACSAPPK - 079 | Copying master data entries from application &1 to application &2 | |
42 | Message Number | CACSAPPK - 078 | Copying copy services from application &1 to application &2 | |
43 | Message Number | CACSAPPK - 014 | P R O D U C T I V E R U N | |
44 | Message Number | CACSAPPK - 026 | Checking that master data is empty | |
45 | Message Number | CACSAPPK - 025 | Checking that client-dependent data is empty | |
46 | Message Number | CACSAPPK - 022 | Target application may be used locally in client &1 | |
47 | Message Number | CACSAPPK - 021 | Target application definition is edited in remote system &1 in client &2 | |
48 | Message Number | CACSAPPK - 020 | Target application definition is edited locally in client &1 | |
49 | Message Number | CACSAPPK - 019 | Source application is read from remote system &1 client &2 | |
50 | Message Number | CACSAPPK - 018 | Source application is read locally from client &1 | |
51 | Message Number | CACSAPPK - 017 | Weak consistency - "Move-corresponding" is used | |
52 | Message Number | CACSAPPK - 016 | Strict consistency - tables must be identical | |
53 | Message Number | CACSAPPK - 015 | T E S T R U N | |
54 | Message Number | CACSAPPK - 027 | Checking that transaction data is empty | |
55 | Message Number | CACSAPPK - 013 | Cloning source application &1 to target application &2 | |
56 | Message Number | CACSAPPK - 012 | Application cloner: process was started | |
57 | Message Number | CACSAPPK - 011 | Source application is identical to target application &1 | |
58 | Message Number | CACSAPPK - 007 | No application field exists for application-dependent table &1 | |
59 | Message Number | CACSAPPK - 006 | Database table &1 does not exist | |
60 | Message Number | CACSAPPK - 006 | Database table &1 does not exist | |
61 | Message Number | CACSAPPK - 005 | Transaction data table &1 is not empty for application &2 | |
62 | Message Number | CACSAPPK - 004 | Master data table &1 is not empty for application &2 | |
63 | Message Number | CACSAPPK - 003 | Client-specific table &1 is not empty for application &2 | |
64 | Message Number | CACSAPPK - 037 | No source table exists for target table &1 | |
65 | Message Number | CACSAPPK - 047 | Cloning client-dependent data | |
66 | Message Number | CACSAPPK - 046 | Checking consistency of client-independent tables only | |
67 | Message Number | CACSAPPK - 045 | Checking consistency of transaction data tables | |
68 | Message Number | CACSAPPK - 044 | Checking consistency of master data tables | |
69 | Message Number | CACSAPPK - 043 | Checking consistency of client-dependent tables | |
70 | Message Number | CACSAPPK - 042 | Source table &1 and target table &2 are strictly consistent | |
71 | Message Number | CACSAPPK - 041 | Source table &1 and target table &2 are inconsistent | |
72 | Message Number | CACSAPPK - 040 | Source table &1 and target table &2 have weak consistency | |
73 | Message Number | CACSAPPK - 039 | External type of source table &1 and target table &2 are different | |
74 | Message Number | CACSAPPK - 038 | Source table &1 and target table &2 have different application dependency | |
75 | Message Number | CACSAPPK - 002 | Cross-client table &1 for application &2 is not empty | |
76 | Message Number | CACSAPPK - 036 | No source table exists for target table &1 - ignoring | |
77 | Message Number | CACSAPPK - 035 | Target table &1 is inactive | |
78 | Message Number | CACSAPPK - 034 | Target table &1 is inactive and is being ignored | |
79 | Message Number | CACSAPPK - 033 | Source table &1 is inactive | |
80 | Message Number | CACSAPPK - 032 | Source table &1 is inactive and is being ignored | |
81 | Message Number | CACSAPPK - 031 | Source table &1 and target table &2 are both inactive - ignoring | |
82 | Message Number | CACSAPPK - 030 | Checking consistency of client-independent tables | |
83 | Message Number | CACSAPPK - 029 | Checking consistency of application tables | |
84 | Message Number | CACSAPPK - 028 | Checking that client-independent data is empty |