SAP ABAP Message Class CACSAPPK (Messages for Application Cloner)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ CACSMTD (Package) ICM: TCACS_MTDTAB Environment
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ CACSMTD (Package) ICM: TCACS_MTDTAB Environment
Attributes
Message class | CACSAPPK | |
Short Description | Messages for Application Cloner | |
Changed On | 20130531 | |
Last Changed At | 104828 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 001 | No tables found for application &1 | The short text describes the object sufficiently | |
3 | 002 | Cross-client table &1 for application &2 is not empty | The short text describes the object sufficiently | |
4 | 003 | Client-specific table &1 is not empty for application &2 | The short text describes the object sufficiently | |
5 | 004 | Master data table &1 is not empty for application &2 | The short text describes the object sufficiently | |
6 | 005 | Transaction data table &1 is not empty for application &2 | The short text describes the object sufficiently | |
7 | 006 | Database table &1 does not exist | The short text describes the object sufficiently | |
8 | 007 | No application field exists for application-dependent table &1 | The short text describes the object sufficiently | |
9 | 008 | RFC destination client &1 is different from selected client &2 | The short text describes the object sufficiently | |
10 | 009 | RFC destination Sysid &1 is different from selected Sysid &2 | The short text describes the object sufficiently | |
11 | 010 | Error while generating application &2 in table &1 | The short text describes the object sufficiently | |
12 | 011 | Source application is identical to target application &1 | The short text describes the object sufficiently | |
13 | 012 | Application cloner: process was started | The short text describes the object sufficiently | |
14 | 013 | Cloning source application &1 to target application &2 | The short text describes the object sufficiently | |
15 | 014 | P R O D U C T I V E R U N | The short text describes the object sufficiently | |
16 | 015 | T E S T R U N | The short text describes the object sufficiently | |
17 | 016 | Strict consistency - tables must be identical | The short text describes the object sufficiently | |
18 | 017 | Weak consistency - "Move-corresponding" is used | The short text describes the object sufficiently | |
19 | 018 | Source application is read locally from client &1 | The short text describes the object sufficiently | |
20 | 019 | Source application is read from remote system &1 client &2 | The short text describes the object sufficiently | |
21 | 020 | Target application definition is edited locally in client &1 | The short text describes the object sufficiently | |
22 | 021 | Target application definition is edited in remote system &1 in client &2 | The short text describes the object sufficiently | |
23 | 022 | Target application may be used locally in client &1 | The short text describes the object sufficiently | |
24 | 023 | Cloning cross-client data | The short text describes the object sufficiently | |
25 | 024 | Checking that application data is empty | The short text describes the object sufficiently | |
26 | 025 | Checking that client-dependent data is empty | The short text describes the object sufficiently | |
27 | 026 | Checking that master data is empty | The short text describes the object sufficiently | |
28 | 027 | Checking that transaction data is empty | The short text describes the object sufficiently | |
29 | 028 | Checking that client-independent data is empty | The short text describes the object sufficiently | |
30 | 029 | Checking consistency of application tables | The short text describes the object sufficiently | |
31 | 030 | Checking consistency of client-independent tables | The short text describes the object sufficiently | |
32 | 031 | Source table &1 and target table &2 are both inactive - ignoring | The short text describes the object sufficiently | |
33 | 032 | Source table &1 is inactive and is being ignored | The short text describes the object sufficiently | |
34 | 033 | Source table &1 is inactive | The short text describes the object sufficiently | |
35 | 034 | Target table &1 is inactive and is being ignored | The short text describes the object sufficiently | |
36 | 035 | Target table &1 is inactive | The short text describes the object sufficiently | |
37 | 036 | No source table exists for target table &1 - ignoring | The short text describes the object sufficiently | |
38 | 037 | No source table exists for target table &1 | The short text describes the object sufficiently | |
39 | 038 | Source table &1 and target table &2 have different application dependency | The short text describes the object sufficiently | |
40 | 039 | External type of source table &1 and target table &2 are different | The short text describes the object sufficiently | |
41 | 040 | Source table &1 and target table &2 have weak consistency | The short text describes the object sufficiently | |
42 | 041 | Source table &1 and target table &2 are inconsistent | The short text describes the object sufficiently | |
43 | 042 | Source table &1 and target table &2 are strictly consistent | The short text describes the object sufficiently | |
44 | 043 | Checking consistency of client-dependent tables | The short text describes the object sufficiently | |
45 | 044 | Checking consistency of master data tables | The short text describes the object sufficiently | |
46 | 045 | Checking consistency of transaction data tables | The short text describes the object sufficiently | |
47 | 046 | Checking consistency of client-independent tables only | The short text describes the object sufficiently | |
48 | 047 | Cloning client-dependent data | The short text describes the object sufficiently | |
49 | 048 | Cloning master data | The short text describes the object sufficiently | |
50 | 049 | Cloning transaction data | The short text describes the object sufficiently | |
51 | 050 | Error in update of generation status in table &1 for application &2 | The short text describes the object sufficiently | |
52 | 051 | Source applic. &1 is being instantiated for client &2 (remote syst. "&3") | The short text describes the object sufficiently | |
53 | 052 | Tgt applic. &1 is being instantiated for client &2 (remote system "&3") | The short text describes the object sufficiently | |
54 | 053 | Source application and target application must be different | The short text describes the object sufficiently | |
55 | 054 | Target application &1 already exists | The short text describes the object sufficiently | |
56 | 055 | No selection made | The short text describes the object sufficiently | |
57 | 056 | Client-independent copying can only be executed separately | The short text describes the object sufficiently | |
58 | 057 | RFC error: &1 | The short text describes the object sufficiently | |
59 | 058 | Generating target application &1 - messages to follow... | The short text describes the object sufficiently | |
60 | 059 | Generation was not executed - test run | The short text describes the object sufficiently | |
61 | 060 | Cloning construction- and client-independent data | The short text describes the object sufficiently | |
62 | 061 | Copying data from table &1 to table &2 | The short text describes the object sufficiently | |
63 | 062 | &2 entries inserted in table &1 | The short text describes the object sufficiently | |
64 | 063 | Error while inserting table &1 | The short text describes the object sufficiently | |
65 | 064 | Generation of target application &1 is complete - read log | The short text describes the object sufficiently | |
66 | 065 | Copying number ranges from application &1 to application &2 | The short text describes the object sufficiently | |
67 | 066 | Copying PD-Org assignments from application &1 to application &2 | The short text describes the object sufficiently | |
68 | 067 | Copying condition records from application &1 to application &2 | The short text describes the object sufficiently | |
69 | 068 | Copying entries of condition table &1 | The short text describes the object sufficiently | |
70 | 069 | Condition table &1 is not application-specific - no data edited | The short text describes the object sufficiently | |
71 | 070 | Condition table &1 has no condition number field - no data edited | The short text describes the object sufficiently | |
72 | 071 | Condition table &1 has no condition type field - no data edited | The short text describes the object sufficiently | |
73 | 072 | Copying condition record &1 (condition type &2) | The short text describes the object sufficiently | |
74 | 073 | Condition type &1 is not valid for application &2 | The short text describes the object sufficiently | |
75 | 074 | Condition record &1 was not found | The short text describes the object sufficiently | |
76 | 075 | Copying application logs from application &1 to application &2 | The short text describes the object sufficiently | |
77 | 076 | Copying application log &1 &2 &3 | The short text describes the object sufficiently | |
78 | 077 | No messages found for application log (handle &1) | The short text describes the object sufficiently | |
79 | 078 | Copying copy services from application &1 to application &2 | The short text describes the object sufficiently | |
80 | 079 | Copying master data entries from application &1 to application &2 | The short text describes the object sufficiently | |
81 | 080 | Copying transaction data entries from application &1 to application &2 | The short text describes the object sufficiently | |
82 | 081 | Copying client-independent entries from application &1 to application &2 | The short text describes the object sufficiently | |
83 | 082 | Copying client-dependent entries from application &1 to application &2 | The short text describes the object sufficiently | |
84 | 083 | &1 PD-Org assignments copied | The short text describes the object sufficiently | |
85 | 084 | No detail found in source application &1 for condition record | The short text describes the object sufficiently | |
86 | 085 | Run was terminated by user | The short text describes the object sufficiently | |
87 | 086 | A non-current client of the target application requires an RFC | The short text describes the object sufficiently | |
88 | 087 | Application log error - no message could be added | The short text describes the object sufficiently | |
89 | 088 | Checking RFC destination &1 - log on if necessary | The short text describes the object sufficiently | |
90 | 089 | XML transformation error for table &1 | The short text describes the object sufficiently | |
91 | 090 | Application field exists for application-independent table &1 | The short text describes the object sufficiently | |
92 | 091 | Invalid table &1 - neither external nor application-dependent | The short text describes the object sufficiently | |
93 | 092 | Setting process information | The short text describes the object sufficiently | |
94 | 093 | Client-independent data must be copied first | The short text describes the object sufficiently | |
95 | 094 | Original source client &1 is not identical to the current source client | The short text describes the object sufficiently | |
96 | 095 | Original system ID &1 is not identical to current system ID | The short text describes the object sufficiently | |
97 | 096 | Original source applic. &1 is not identical to current source applic. &2 | The short text describes the object sufficiently | |
98 | 097 | Client-independent data was cloned first | The short text describes the object sufficiently | |
99 | 098 | Copying step of cross-client data is missing | Space: object requires documentation | |
100 | 099 | Copying step of client-dependent data is missing | Space: object requires documentation | |
101 | 100 | Copying step of master data is missing | Space: object requires documentation | |
102 | 101 | Cannot update process data in table CACS_CLONE | The short text describes the object sufficiently | |
103 | 102 | Execute application cloner with transaction CACS_CLONE | The short text describes the object sufficiently | |
104 | 103 | No process information found for application &1 | The short text describes the object sufficiently | |
105 | 104 | Process steps of application &1 | The short text describes the object sufficiently | |
106 | 105 | Table filter is active | The short text describes the object sufficiently | |
107 | 106 | Instantiating commission application &1 | The short text describes the object sufficiently | |
108 | 107 | Application eraser: process was started | The short text describes the object sufficiently | |
109 | 108 | Deleting commission application &1 | The short text describes the object sufficiently | |
110 | 109 | Deleting table entries of transaction data from application &1 | The short text describes the object sufficiently | |
111 | 110 | Deleting data from table &1 | The short text describes the object sufficiently | |
112 | 111 | &2 entries deleted from table &1 - WHERE condition '&3' | The short text describes the object sufficiently | |
113 | 112 | Error while deleting entries of table &1 | The short text describes the object sufficiently | |
114 | 113 | Deleting application logs from commission application &1 | The short text describes the object sufficiently | |
115 | 114 | Deleting application log &1 &2 &3 | The short text describes the object sufficiently | |
116 | 115 | Deleting copy service from commission application &1 | The short text describes the object sufficiently | |
117 | 116 | Deleting transaction data | The short text describes the object sufficiently | |
118 | 117 | Master data will be deleted | The short text describes the object sufficiently | |
119 | 118 | Deleting master data entries from commission application &1 | The short text describes the object sufficiently | |
120 | 119 | Deleting PD-ORG assignments from commission application &1 | The short text describes the object sufficiently | |
121 | 120 | &1 PD-ORG assignment(s) deleted | The short text describes the object sufficiently | |
122 | 121 | Deleting condition records from commission application &1 | The short text describes the object sufficiently | |
123 | 122 | Deleting condition record &1 (condition type &2) | The short text describes the object sufficiently | |
124 | 123 | Error while deleting condition record &1 from table &2 | The short text describes the object sufficiently | |
125 | 124 | Deleting cross-client entries from commission application &1 | The short text describes the object sufficiently | |
126 | 125 | Deleting client-specific data | The short text describes the object sufficiently | |
127 | 126 | Deleting number ranges from commission application &1 | The short text describes the object sufficiently | |
128 | 127 | Deleting cross-client data | The short text describes the object sufficiently | |
129 | 128 | Deleting generation of commission application | The short text describes the object sufficiently | |
130 | 129 | Deleting cross-client entries from commission application &1 | The short text describes the object sufficiently | |
131 | 130 | Internal error in process step control | The short text describes the object sufficiently | |
132 | 131 | Deleting entries of conditions table &1 | The short text describes the object sufficiently | |
133 | 132 | Cannot delete client assignment &1 of commission application &2 | The short text describes the object sufficiently | |
134 | 133 | Deleting client assignment of commission application | The short text describes the object sufficiently | |
135 | 134 | Commission application will be deleted | The short text describes the object sufficiently | |
136 | 135 | Error while deleting commission application &2 from table &1 | The short text describes the object sufficiently | |
137 | 136 | Commission application &1 is not used in client &2 | The short text describes the object sufficiently | |
138 | 137 | Client &1 is defined as "productive" | The short text describes the object sufficiently | |
139 | 138 | Client &1 does not exist | The short text describes the object sufficiently | |
140 | 139 | You can only delete separately | Space: object requires documentation | |
141 | 140 | Deleting generated objects from commission application &1 | The short text describes the object sufficiently | |
142 | 141 | Deleting generated views | The short text describes the object sufficiently | |
143 | 142 | Generated view &1 cannot be deleted | The short text describes the object sufficiently | |
144 | 143 | Generated view &1 was successfully deleted | The short text describes the object sufficiently | |
145 | 144 | Deleting generated tables and structures | The short text describes the object sufficiently | |
146 | 145 | Generated view &1 does not exist on database | The short text describes the object sufficiently | |
147 | 146 | Generated table &1 does not exist on database | The short text describes the object sufficiently | |
148 | 147 | Cannot delete generated table &1 | The short text describes the object sufficiently | |
149 | 148 | Generated table &1 was deleted successfully | The short text describes the object sufficiently | |
150 | 149 | Deleting DataSources | The short text describes the object sufficiently | |
151 | 150 | Generated DataSource &1 does not exist on database | The short text describes the object sufficiently | |
152 | 151 | Generation object &1 &2 does not exist | The short text describes the object sufficiently | |
153 | 152 | Check if generated objects are empty | The short text describes the object sufficiently | |
154 | 153 | Generated (construction) objects will be deleted | The short text describes the object sufficiently | |
155 | 154 | Generated objects can only be deleted in productive mode | The short text describes the object sufficiently | |
156 | 155 | Deletion of generated tables - generation level "&1" | The short text describes the object sufficiently | |
157 | 156 | Generated table type &1 does not exist on database | The short text describes the object sufficiently | |
158 | 157 | Cannot delete generated table type &1 | The short text describes the object sufficiently | |
159 | 158 | Generated table type &1 was successfully deleted | The short text describes the object sufficiently | |
160 | 159 | Deleting generated table type &1 (for table &2) | The short text describes the object sufficiently | |
161 | 160 | Cannot delete generated program &1 | The short text describes the object sufficiently | |
162 | 161 | Deleting generated programs | The short text describes the object sufficiently | |
163 | 162 | Generated program &1 does not exist | The short text describes the object sufficiently | |
164 | 163 | Program &1 was successfully deleted | The short text describes the object sufficiently | |
165 | 164 | Deleting generated function groups | The short text describes the object sufficiently | |
166 | 165 | Generated function group &1 does not exist | The short text describes the object sufficiently | |
167 | 166 | Cannot delete generated function group &1 | The short text describes the object sufficiently | |
168 | 167 | Generated function group &1 was successfully deleted | The short text describes the object sufficiently | |
169 | 168 | Deleting generated classes/interfaces | The short text describes the object sufficiently | |
170 | 169 | Generated classes/interfaces &1 do not exist | The short text describes the object sufficiently | |
171 | 170 | Unexpected class type '&1' for class &2 | The short text describes the object sufficiently | |
172 | 171 | Cannot delete generated class/interface &1 | The short text describes the object sufficiently | |
173 | 172 | Generated class/interface &1 was successfully deleted | The short text describes the object sufficiently | |
174 | 173 | Cloning cross-client data; generation will follow | The short text describes the object sufficiently | |
175 | 174 | Application language &1 does not match process language &2 | The short text describes the object sufficiently | |
176 | 175 | Generated table &1 will be deleted | The short text describes the object sufficiently | |
177 | 176 | Foreign key relationships will be deleted | The short text describes the object sufficiently | |
178 | 177 | Cannot delete foreign key relationships for table &1 | The short text describes the object sufficiently | |
179 | 178 | Generation of application can only be executed alone | The short text describes the object sufficiently | |
180 | 179 | Tables will be emptied for package &1 | The short text describes the object sufficiently | |
181 | 180 | Package &1 is not assigned to application &2 | The short text describes the object sufficiently | |
182 | 181 | Package builder will be started | The short text describes the object sufficiently | |
183 | 182 | Commission application &1 will be used to create package &2 | The short text describes the object sufficiently | |
184 | 183 | Entries for package &1 will be deleted | The short text describes the object sufficiently | |
185 | 184 | Package &1 is invalid | The short text describes the object sufficiently | |
186 | 185 | Package &1 will be generated | The short text describes the object sufficiently | |
187 | 186 | Entries for package &1 will be created | The short text describes the object sufficiently | |
188 | 187 | Cross-client entries for package &1 will be created | The short text describes the object sufficiently | |
189 | 188 | Client-specific entries for package &1 will be created | The short text describes the object sufficiently | |
190 | 189 | Master data entries for package &1 will be created | The short text describes the object sufficiently | |
191 | 190 | Transaction data entries will be created for package &1 | The short text describes the object sufficiently | |
192 | 191 | Entries for table &1 will be copied from application &2 to package &3 | The short text describes the object sufficiently | |
193 | 192 | &1 entries were copied | The short text describes the object sufficiently | |
194 | 193 | Key for entry &1 | The short text describes the object sufficiently | |
195 | 194 | Entries can only be transported for productive run | The short text describes the object sufficiently | |
196 | 195 | Generated table &1 will be ignored | The short text describes the object sufficiently | |
197 | 196 | Transport entry is not specified | The short text describes the object sufficiently | |
198 | 197 | Transport entry &1 is specified | The short text describes the object sufficiently | |
199 | 198 | Entries in table TCACS_DESFIELDS will be checked | The short text describes the object sufficiently | |
200 | 199 | Source structure &1 (in TCACS_DESFIELDS) does not exist | The short text describes the object sufficiently | |
201 | 200 | Number range object & would have been deleted for all applications | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 700 |