SAP ABAP Message Class KE (KE)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE (Package) Profitability Analysis
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE (Package) Profitability Analysis
Attributes
Message class | KE | |
Short Description | ||
Changed On | 20110908 | |
Last Changed At | 171818 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | <<<<<<<<<<<<<< Reserved for CO-PA basic data >>>>>>>>>>>>>>>>> | ||
2 | 001 | Tables already exist for operating concern & | Space: object requires documentation | |
3 | 002 | Error reading Table & - system error | ||
4 | 003 | & & has been saved | ||
5 | 004 | Operating concerns were not upgraded automatically | Space: object requires documentation | |
6 | 005 | Error saving Table & | ||
7 | 006 | Operating concern & will be updated automatically | Space: object requires documentation | |
8 | 007 | Error generating client-specific objects | Space: object requires documentation | |
9 | 008 | Programm error: RKE_CHECK_GENERATION called recursively | Space: object requires documentation | |
10 | 009 | Program error: program & can no longer be used | Space: object requires documentation | |
11 | 010 | Entry &1 deleted from table &2 | Space: object requires documentation | |
12 | 011 | Table & was reorganized | Space: object requires documentation | |
13 | 012 | Object &1/&2 cannot be deleted | Space: object requires documentation | |
14 | 013 | Do not use SAP operating concern & productively | Space: object requires documentation | |
15 | 014 | Action was cancelled | Space: object requires documentation | |
16 | 015 | No active version of the object &1 &2 exists | Space: object requires documentation | |
17 | 016 | Fields have been reset. | Space: object requires documentation | |
18 | 017 | Error deleting structure & | ||
19 | 018 | Field &1 does not exist in table &2 | Space: object requires documentation | |
20 | 019 | Table &1 is currently being processed by user &2 | ||
21 | 020 | The field name must consist of at least 6 characters | Space: object requires documentation | |
22 | 021 | Maintain dependencies for field "&" | Space: object requires documentation | |
23 | 022 | Check table & for field & does not exist - system error | ||
24 | 023 | Client-dependent environment generated for operating concern & | Space: object requires documentation | |
25 | 024 | Operating concern &1 had not been adapted. The action has been cancelled | Space: object requires documentation | |
26 | 025 | Contact the system administrator: there is a performance problem in CO-PA | Space: object requires documentation | |
27 | 026 | Application "&1" is not supported | Space: object requires documentation | |
28 | 027 | Error activating lock object for Table & | ||
29 | 028 | Error saving lock object for Table & | ||
30 | 029 | Table & does not exist -> lock object could not be created | ||
31 | 030 | Transaction &2 cannot be used for operating concern &1 | Space: object requires documentation | |
32 | 031 | The field name cannot exceed 5 characters | ||
33 | 032 | Enter a text for the operating concern | Space: object requires documentation | |
34 | 033 | Save changes first | Space: object requires documentation | |
35 | 034 | This function is not possible since operating concern "&1" already exists | Space: object requires documentation | |
36 | 035 | Error generating environment (function module &) | ||
37 | 036 | Internal system error when locking table & | ||
38 | 037 | Enter the description and the type of profitability analysis | Space: object requires documentation | |
39 | 038 | For characteristic &1, text field &2 has been replaced by &3 | Space: object requires documentation | |
40 | 039 | Attributes could not be saved. Header information is therefore incomplete | Space: object requires documentation | |
41 | 040 | It is not possible to change the type of profitability analysis | Space: object requires documentation | |
42 | 041 | Operating concern "&1" cannot be used | Space: object requires documentation | |
43 | 042 | Abend while index for segment table & was being generated | ||
44 | 043 | Lines can only be inserted in one place | ||
45 | 044 | Automatic adjustment not possible for operating concern & | Space: object requires documentation | |
46 | 045 | Index for segment table & not active -> Activate manually | ||
47 | 046 | Program error: Parameter & is too short | Space: object requires documentation | |
48 | 047 | No objects need to be generated -> see log | ||
49 | 048 | Activation ended due to errors -> see log | ||
50 | 049 | Entry & & is not contained in Table TKENR - system error | ||
51 | 050 | Inconsistencies exist in tables for op. concern & | ||
52 | 051 | Field & cannot be deselected | ||
53 | 052 | Field & may not be changed | ||
54 | 053 | You cannot insert fields or lines here | ||
55 | 054 | Error saving transport request & - system error | ||
56 | 055 | & & does not exist for generation of quantity units - system error | ||
57 | 056 | Characteristic field cannot be selected | ||
58 | 057 | Characteristic field cannot be selected | ||
59 | 058 | No further characteristics can be added | ||
60 | 059 | System error: Invalid callup of method/form "&1" | Space: object requires documentation | |
61 | 060 | During the plan data transfer, only record type & was processed | ||
62 | 061 | Activation has warnings -> generation continued | ||
63 | 062 | For field &-&, no active foreign key relationship exists | ||
64 | 063 | No foreign key relationship was generated for field &1-&2 | Space: object requires documentation | |
65 | 064 | Characteristic & has no check table | ||
66 | 065 | Activate operating concern & and generate the environment beforehand | ||
67 | 066 | Generate operating concern & | ||
68 | 067 | Not all objects were activated -> generation continued | ||
69 | 068 | Table & was reset | ||
70 | 069 | & entries were processed | ||
71 | 070 | Initialization cannot be performed yet | ||
72 | 071 | Type and length are incompatible with field & | ||
73 | 072 | Assign a new function group to view "&" | ||
74 | 073 | You may not create/change operating concerns in SAP system & | ||
75 | 074 | View "&" is not active or view modules have not been generated | ||
76 | 075 | Technical settings for table & were saved | ||
77 | 076 | Characteristic field & cannot be selected | ||
78 | 077 | After generating, reset the new characteristics | ||
79 | 078 | Field & already exists with another quantity/value flag | ||
80 | 079 | Transaction & is locked --> use Transaction KEA0 | ||
81 | 080 | Operating concern & is currently locked. Wait a moment, then try again | ||
82 | 081 | Operating concern & has not yet been generated | ||
83 | 082 | Table & does not exist in the database system | ||
84 | 083 | Check table & is not active in the ABAP/4 Repository | ||
85 | 084 | Maintenance modules for view & were generated before the last activation | ||
86 | 085 | Characteristic & must also be in segment level for costing-based CO-PA | ||
87 | 086 | Deleting a record type can lead to inconsistencies if data already exists | ||
88 | 088 | Type of Profitability Analysis was set to "account-based" | ||
89 | 089 | Type of Profitability Analysis was set to "costing-based" | ||
90 | 090 | Screen & & and & generated | ||
91 | 091 | Select a name beginning with EP for operating concern & | ||
92 | 092 | Error creating TADIR entry for derivation rule table & | ||
93 | 093 | The function "account-based Profitability Analysis" is not allowed | ||
94 | 094 | System error: Field & not found in the internal CO-PA field catalog | ||
95 | 095 | Errors were found in the derivation structures | ||
96 | 096 | Error in derivation structure &2 with derivation rule table &1 | ||
97 | 097 | Program error: inconsistency between screen and internal field table | ||
98 | 098 | Processing error occurred in callup of function & | Space: object requires documentation | |
99 | 099 | Enter a value | Space: object requires documentation | |
100 | 100 | The characteristic value &1 is not permitted for characteristic &2 | Space: object requires documentation | |
101 | 101 | Caution: Changing the currency key may result in data inconsistencies | ||
102 | 102 | Caution: Changing fiscal year variant may result in data inconsistencies | ||
103 | 103 | Caution: Changing the period type may result in data inconsistencies | ||
104 | 104 | Enter operating concerns with four characters only | ||
105 | 105 | Do not use special characters when entering operating concern | ||
106 | 106 | Operating concern & only allows the activity flag & | ||
107 | 107 | Only one type of profitability analysis was activated | ||
108 | 108 | Active flag was changed | ||
109 | 109 | Value "&1" is not allowed for characteristic "&2" | Space: object requires documentation | |
110 | 110 | <<<<<< Reorg. view maintenance >>>>>> | ||
111 | 111 | View maintenance modules may not be deleted (see long text) | ||
112 | 112 | Function group & cannot be deleted | ||
113 | 113 | <<<free as of 2.2>>> | ||
114 | 114 | You are not authorized to change the operating concern | ||
115 | 115 | No table entries exist for the specified selection data | Space: object requires documentation | |
116 | 116 | Online start & abended | Space: object requires documentation | |
117 | 117 | Program & was executed online | Space: object requires documentation | |
118 | 118 | No set value could not be found for table & row & | Space: object requires documentation | |
119 | 119 | Inconsistent data record &1 was not converted in table &2 | Space: object requires documentation | |
120 | 120 | Automatic number assignment not possible with record type & | ||
121 | 121 | Document number range is nearly full for record type & | ||
122 | 122 | Document number range is full for record type & | ||
123 | 123 | Table & does not contain any data, no conversion carried out | Space: object requires documentation | |
124 | 124 | Table TKB9E could not be converted correctly | Space: object requires documentation | |
125 | 125 | Record & in TKB9E was already converted | Space: object requires documentation | |
126 | 126 | Controlling area & is not assigned to an operating concern | Space: object requires documentation | |
127 | 127 | CO object(s) archived | The short text describes the object sufficiently | |
128 | 128 | CO object(s) deleted | The short text describes the object sufficiently | |
129 | 129 | CO object(s) reloaded | The short text describes the object sufficiently | |
130 | 130 | <<<<<< Regenerate table structures >>>>>> | ||
131 | 131 | Operating concern & does not exist | ||
132 | 132 | Oject & not contained in TKENR (system error) | ||
133 | 133 | Model table & is not active | ||
134 | 134 | Table & does not exist | ||
135 | 135 | Changed table & was saved | ||
136 | 136 | No differences found -> Table & was not changed | ||
137 | 137 | Changed table & was saved -> Conversion required | ||
138 | 138 | Changed table & was activated | ||
139 | 139 | Structure of table & changed | ||
140 | 140 | Initialization of the fields in table "&1" (NOT_NULL) | Space: object requires documentation | |
141 | 141 | Initialization of the fields in table "&1" (test mode) | Space: object requires documentation | |
142 | 142 | There is no database object for table "&1" | Space: object requires documentation | |
143 | 143 | The initialization indicator for field "&1" has been set | Space: object requires documentation | |
144 | 144 | All fields in table "&1" have already been initialized | Space: object requires documentation | |
145 | 145 | Initialization indicator for field "&1" is not set | Space: object requires documentation | |
146 | 146 | &2 line item(s) reloaded | The short text describes the object sufficiently | |
147 | 147 | &2 segment level(s) archived | The short text describes the object sufficiently | |
148 | 148 | &2 segment level(s) deleted | The short text describes the object sufficiently | |
149 | 149 | &2 segment level(s) reloaded | The short text describes the object sufficiently | |
150 | 150 | <<<<<<<<<<<<<< Database reorg. >>>>>>>>>>>>>>>>>>>>>>> | ||
151 | 151 | Choose one archive file to be processed | ||
152 | 152 | Period selection cannot be reduced | ||
153 | 153 | Logical database PAK and archiving program RKEPAK00 generated | ||
154 | 154 | You are not authorized to use operating concern & | ||
155 | 155 | You are not authorized to archive actual data | ||
156 | 156 | You are not authorized to archive plan data | ||
157 | 157 | The name range RK4* is reserved for generated CO-PA programs | ||
158 | 158 | Archiving object & was created | ||
159 | 159 | Select one fiscal year only when specifying the periods | ||
160 | 160 | You did not wish to have a log generated -> You cannot choose this option | ||
161 | 161 | You are already processing scenario &1 | Space: object requires documentation | |
162 | 162 | Saved | Space: object requires documentation | |
163 | 163 | No source objects have been selected | Space: object requires documentation | |
164 | 164 | No target systems have been selected | Space: object requires documentation | |
165 | 165 | &1 objects were sent to &2 logical system(s) | Space: object requires documentation | |
166 | 166 | Scenario &1 does not exist | Space: object requires documentation | |
167 | 167 | Scenario &1 was deleted | Space: object requires documentation | |
168 | 168 | No errors found when the partner profiles were checked | Space: object requires documentation | |
169 | 169 | Scenario &1 is locked by user &2 | Space: object requires documentation | |
170 | 170 | <<<<<<<<<<<<<< Parallel Build Summarization Level >>>>>> | Space: object requires documentation | |
171 | 171 | Fields GJAHR and PERDE have to be in summarization level & | Space: object requires documentation | |
172 | 172 | UPDATE_LGPS_ERROR &1 &2 &3 &4 | Space: object requires documentation | |
173 | 173 | Snapshot table is empty | Space: object requires documentation | |
174 | 174 | Errors occurred during send | Space: object requires documentation | |
175 | 175 | Archiving object & was changed | Space: object requires documentation | |
176 | 176 | &2 data object(s) processed | The short text describes the object sufficiently | |
177 | 177 | &2 line item(s) archived | The short text describes the object sufficiently | |
178 | 178 | Archiving run was interrupted | The short text describes the object sufficiently | |
179 | 179 | &2 line item(s) deleted | The short text describes the object sufficiently | |
180 | 180 | <<<<<<< Messages for repair XPRAs >>>>>>>>>>>>>>>>>>>>>>> | Space: object requires documentation | |
181 | 181 | Transaction &1 already exists | Space: object requires documentation | |
182 | 182 | Transaction &1 was created | Space: object requires documentation | |
183 | 183 | Transaction &1 was created without an entry in table TADIR | Space: object requires documentation | |
184 | 184 | Transaction &1 could not be created | Space: object requires documentation | |
185 | 185 | Field &1 has already been defined | Space: object requires documentation | |
186 | 186 | System error: model entry &1 not found in table &2 | Space: object requires documentation | |
187 | 187 | System error: &1 was not entered in table &2 | Space: object requires documentation | |
188 | 188 | Field &1 was defined with use &2 | Space: object requires documentation | |
189 | 189 | Index &1_&2 was not deleted | Space: object requires documentation | |
190 | 190 | Index &1_&2 was deleted | Space: object requires documentation | |
191 | 191 | &1 entries in table &2 have been changed | Space: object requires documentation | |
192 | 192 | All the tables CE4xxxx_yyyy have been changed successfully | Space: object requires documentation | |
193 | 193 | Errors occurred while tables CE4xxxx_yyyy were being updated | Space: object requires documentation | |
194 | 194 | Foreign key relationship reorganized in table &1. Table saved | Space: object requires documentation | |
195 | 195 | The characteristic dependencies (&1) have been adjusted | Space: object requires documentation | |
196 | 196 | The characteristic compound cannot be reorganized for characteristic &1 | Space: object requires documentation | |
197 | 197 | The characteristic compound cannot be reorganized for characteristic &1 | Space: object requires documentation | |
198 | 198 | The characteristic compound for characteristic &V1& has been reorganized | Space: object requires documentation | |
199 | 199 | Operating concern "&1" cannot be edited | Space: object requires documentation | |
200 | 200 | Specify the number of source fields (between 1 and 3) | ||
201 | 201 | Specify the number of target fields (between 1 and 10) | ||
202 | 202 | Field & is not a valid entry | ||
203 | 203 | For operating concern &, no table has been defined | ||
204 | 204 | Derivation rule & has been held | ||
205 | 205 | A derivation rule has already been defined with the name & | ||
206 | 206 | Sequence & has already been assigned to another derivation rule | ||
207 | 207 | Derivation structure name 'Z' is not allowed | ||
208 | 208 | The upper limit of the interval is below the lower limit | ||
209 | 209 | Enter all of the target fields | ||
210 | 210 | Enter all of the source fields | ||
211 | 211 | Use field & once only | ||
212 | 212 | Define the ranges in such a way that they do not overlap | ||
213 | 213 | Check the range limits ("from" value cannot exceed "to" value) | ||
214 | 214 | Derivation rule & exists already from & to & | ||
215 | 215 | Error in CO-PA derivation rule & | ||
216 | 216 | Derivation structure & does not exist | ||
217 | 217 | Fields have already been defined for derivation rule & | ||
218 | 218 | Derivation structure & has been changed | ||
219 | 219 | Derivation structure & has been deleted | ||
220 | 220 | Derivation structure & cannot be deleted | ||
221 | 221 | Derivation structure & cannot be changed | ||
222 | 222 | Place cursor on a source field or a target field | ||
223 | 223 | Derivation structure & cannot be saved | ||
224 | 224 | No records exist for derivation structure & | ||
225 | 225 | Derivation rule & (& to &) has been deleted | ||
226 | 226 | Place the cursor on a line which contains ranges | ||
227 | 227 | Error saving foreign currency key Table & | ||
228 | 228 | Error reading screen & & | ||
229 | 229 | Error reading data element & | ||
230 | 230 | Error reading domain & | ||
231 | 231 | Error generating screen & & | ||
232 | 232 | Error saving screen & & | ||
233 | 233 | No errors detected | ||
234 | 234 | Derivation rule & (& to &) has been created | ||
235 | 235 | Derivation rule & (& to &) has been changed | ||
236 | 236 | The "to"-range overlaps with existing ranges | ||
237 | 237 | The new lower limit in the range cannot be lower than the original one | ||
238 | 238 | The new upper limit in the range cannot be greater than the original one | ||
239 | 239 | Change or delete the lines you have copied | ||
240 | 240 | Change or delete the line you have copied | ||
241 | 241 | The data was not saved as it had not been changed | ||
242 | 242 | Copying is not possible | ||
243 | 243 | Derivation structure & has been saved | ||
244 | 244 | Limit the number of target fields | ||
245 | 245 | Entering & is not allowed | ||
246 | 246 | Derivation structure & has not been activated | ||
247 | 247 | Derivation rule & has been split | ||
248 | 248 | Derivation rule has not been split | ||
249 | 249 | The data was not updated | ||
250 | 250 | Derivation structure &1 is currently locked by user &2 | ||
251 | 251 | Derivation structure &1 is currently locked by user &2 | ||
252 | 252 | Error has occurred in lock routine | ||
253 | 253 | Program & does not exist | ||
254 | 254 | Derivation structure & does not exist | ||
255 | 255 | Derivation structure & does not exist | ||
256 | 256 | System error: Table number not contained in permitted range | ||
257 | 257 | System error: Screen number not contained in permitted range | ||
258 | 258 | System error: Entry & does not exist in Table TKEAS | ||
259 | 259 | Error in CO-PA derivation rule & | ||
260 | 260 | Error in CO-PA derivation rule & | ||
261 | 261 | Entry & is not allowed | ||
262 | 262 | Customer &3 was expected instead of customer &2 at hierarchy level &1 | Space: object requires documentation | |
263 | 263 | The function is currently locked by user & | ||
264 | 264 | Maintain either error file or error session | ||
265 | 265 | You may not maintain both the error file and the error session | ||
266 | 266 | Do not enter an batch input session for plan data | ||
267 | 267 | Enter an error file for plan data | ||
268 | 268 | CO-PA derivation: Characteristic &1 does not exist in op. concern &2 | ||
269 | 269 | Derivation table & does not contain a field "&" | ||
270 | 270 | Name range (prefix RKE5) is reserved for user exit in CO-PA valuation | ||
271 | 271 | Enter a business area | ||
272 | 272 | Repository Switch not active, & cannot be executed | ||
273 | 273 | Inconsistent data following user exit! | ||
274 | 274 | Application &1, client &2: Error executing XPRA &3 | ||
275 | 275 | Application &, all clients: Error executing XPRA & | ||
276 | 280 | Table & contains no fields | ||
277 | 281 | Table & is not active or does not exist | ||
278 | 282 | The table name for the internal structure must begin with CE1 | ||
279 | 283 | Table & cannot be used as an external table | ||
280 | 284 | Input file and error file cannot have the same path name | ||
281 | 285 | Actual dat is not allowed in account-based Profitability Analysis | Space: object requires documentation | |
282 | 286 | Make at least one selection | Space: object requires documentation | |
283 | 287 | Sender structure & already exists | Space: object requires documentation | |
284 | 288 | Give your sender structures different names | Space: object requires documentation | |
285 | 289 | Enter a sender structure | Space: object requires documentation | |
286 | 290 | No standard cost estimate could be found for material "&" | Space: object requires documentation | |
287 | 291 | Error during valuation using product costing | Space: object requires documentation | |
288 | 292 | Error reading the material cost estimate for sales order "&" | Space: object requires documentation | |
289 | 293 | Error reading the material cost estimate for product "&" | Space: object requires documentation | |
290 | 294 | Deleting the profitability segment will lead to inconsistent data | ||
291 | 295 | Assignment to a profitability segment is not allowed | ||
292 | 296 | The status of the material cost estimate for material "&" is not allowed | Space: object requires documentation | |
293 | 297 | Profit center & is not allowed | ||
294 | 298 | Data in Profitability Analysis is inconsistent! | ||
295 | 299 | No operating concern could be found | ||
296 | 300 | No operating concern has been assigned to controlling area & | ||
297 | 301 | Record type '&' has not been defined (Table TVGA) | ||
298 | 302 | More than one ledger has been assigned | ||
299 | 303 | Valuation is not possible | ||
300 | 304 | No number range has been defined for record type & | ||
301 | 305 | No internal number range has been defined | ||
302 | 306 | The number range does not exist | ||
303 | 307 | The number range is not internal | ||
304 | 308 | No external number range has been defined | ||
305 | 309 | The number range is full | ||
306 | 310 | Document number & is not contained in the permitted range | ||
307 | 311 | Field & is not contained in dictionary table & | ||
308 | 312 | System error: No operating concern has been set | ||
309 | 313 | Costing sheet & does not exist | ||
310 | 314 | Quantity field & is not contained in operating concern & | ||
311 | 315 | Please select at least one segment | ||
312 | 316 | Dataset & cannot be opened by the system | ||
313 | 317 | Field 'Company code' does not contain a value | ||
314 | 318 | The transferred client does not correspond to system client | ||
315 | 319 | The transferred ledger does not correspond to internal ledger | ||
316 | 320 | Version cannot be used in Release 2.0 | ||
317 | 321 | No date set | ||
318 | 322 | No period set | ||
319 | 323 | The derived op. concern does not correspond to the database tables | ||
320 | 324 | The transferred CO area does not correspond to the CO area found | ||
321 | 325 | No relevant entry could be found in Table T001B | ||
322 | 326 | Posting date is not allowed | ||
323 | 327 | Incorrect entry -> please check | ||
324 | 328 | Incorrect entry -> please check | ||
325 | 329 | System error: Field & cannot be used for derivation | ||
326 | 330 | Maintain control indicators for CO area & in & | ||
327 | 331 | Assignment group & is not contained in Table T258Z | ||
328 | 332 | Field & is not contained in CO-PA structure & | ||
329 | 333 | Field & is not contained in Table & | ||
330 | 334 | Do not use assignment group & | ||
331 | 335 | You are not authorized to create a derivation structure | ||
332 | 336 | Valuation is not defined | ||
333 | 337 | Characteristic & must be renamed! Change valuation accordingly! | ||
334 | 338 | Profitability Analysis is not active! | ||
335 | 339 | You are not authorized to work in this operating concern | Space: object requires documentation | |
336 | 340 | Incorrect entry in the definition of the CO-PA valuation strategy | Space: object requires documentation | |
337 | 341 | Incorrect entry in the definition of the CO-PA valuation strategy | Space: object requires documentation | |
338 | 342 | Incorrect entry in the definition of the CO-PA valuation strategy | Space: object requires documentation | |
339 | 343 | Enter a quantity | ||
340 | 344 | Enter a plant | ||
341 | 345 | Enter a product | ||
342 | 346 | The system could not find a product cost estimate | ||
343 | 347 | Costing variant & does not exist in the system | ||
344 | 348 | No valuation segment exists in the material master record for product & | ||
345 | 349 | Valuation with material cost estimate: error with product "&1" | Space: object requires documentation | |
346 | 350 | Valuation with material cost estimate: error with product "&1" | Space: object requires documentation | |
347 | 351 | Valuation with material cost estimate: error with product "&1" | Space: object requires documentation | |
348 | 352 | Enter only one valuation method per line | ||
349 | 353 | Enter a valuation method | ||
350 | 354 | Maintain an application for the costing sheet | ||
351 | 355 | Maintain a costing sheet for the application | ||
352 | 356 | Enter a quantity field | ||
353 | 357 | Version & is not defined in CO-PA | Space: object requires documentation | |
354 | 358 | Version &1 does not exist in operating concern &2 | Space: object requires documentation | |
355 | 359 | Plan data transfer only possible with a version | ||
356 | 360 | Enter a plan version | ||
357 | 361 | No versions are required for actual data | ||
358 | 362 | Enter either a material type or a material number | ||
359 | 363 | You can enter either the material type OR the material number | ||
360 | 364 | Manual costing is not allowed for costing variant & | Space: object requires documentation | |
361 | 365 | Costing variant saved without date | ||
362 | 366 | Costing variant saved with date | ||
363 | 367 | Costing variant saved without date | ||
364 | 368 | Costing variant saved with date | ||
365 | 369 | Costing variant stored with costing date | ||
366 | 370 | Costing variant stored with costing date | ||
367 | 371 | Costing variant stored with start of period | ||
368 | 372 | Costing variant stored with start of period | ||
369 | 373 | Costing variant stored with start of period | ||
370 | 374 | Period flag may not be used | ||
371 | 375 | Period flag may not be used | ||
372 | 376 | Costing variant stored with start of period | ||
373 | 377 | Costing variant stored with start of period | ||
374 | 378 | Costing variant stored with start of period | ||
375 | 379 | Maintain either period or period flag | ||
376 | 380 | No product costing estimate could be found | ||
377 | 381 | Revaluation and valuation only possible for plan data in cstg-based CO-PA | Space: object requires documentation | |
378 | 382 | Error when changing period type for transfer of plan data | ||
379 | 383 | Plan data can only be transferred with record type 'F' | ||
380 | 384 | Caution: You are changing the operating concern assignment | ||
381 | 385 | Error revaluing quantity unit | ||
382 | 386 | Neither company code nor controlling area have been filled | ||
383 | 387 | Profitability segment number & does not exist | ||
384 | 388 | File & already transferred to CO-PA | ||
385 | 389 | Caution: File & only processed as of record & | ||
386 | 390 | View V_T258E locked -> No processing allowed | ||
387 | 391 | Assign condition type & in CO-PA | ||
388 | 392 | Operating concern assignment deleted only | ||
389 | 393 | Weekly planning can only be used with plan data in costing-based CO-PA | Space: object requires documentation | |
390 | 394 | Enter valid plan /actual indicator | ||
391 | 395 | Assign the controlling area to an operating concern | ||
392 | 396 | Inconsistency between a document field and the prof. segment number | Space: object requires documentation | |
393 | 397 | Error deriving the controlling area from the profit center | ||
394 | 398 | Valuation is not possible | ||
395 | 399 | No valuation possible using a cost estimate from plant & | ||
396 | 400 | Value for characteristic & does not exist | ||
397 | 401 | Foreign key relationship for field & is incorrect | ||
398 | 402 | Characteristic value selection for characteristic & is not supported | ||
399 | 403 | No texts exist for values of characteristic & | ||
400 | 404 | Selection condition not supported | ||
401 | 405 | Check table for field & contains too many entries | ||
402 | 406 | User exit & already exists -> No regeneration | ||
403 | 407 | Valuation strategy &1 is still assigned to a point of valuation | Space: object requires documentation | |
404 | 408 | No valuation exists | Space: object requires documentation | |
405 | 409 | User exit must start with 'U' | ||
406 | 410 | Incorrect assignment of condition type & to CO-PA value fields | ||
407 | 411 | Plant & not assigned to controlling area & | ||
408 | 412 | Plant & is not assigned to company code & | ||
409 | 413 | Plant & is not assigned to operating concern & | ||
410 | 414 | Do not use!!!!!!!!! -- 6/29/95 | ||
411 | 415 | Company code & is not assigned to operating concern & | ||
412 | 416 | Controlling area & is not assigned to operating concern & | ||
413 | 417 | Sales organization & is not assigned to company code & | ||
414 | 418 | Sales organization & is not assigned to operating concern & | ||
415 | 419 | Weekly planning is not valid for operating concern & | ||
416 | 420 | Profit center & is not assigned to operating concern & | ||
417 | 421 | Sales organization & is not assigned to controlling area & | ||
418 | 422 | Enter a quantity unit for CO-PA valuation | Space: object requires documentation | |
419 | 423 | Characteristic group & does not exist | Space: object requires documentation | |
420 | 424 | Characteristic & does not exist in operating concern & | ||
421 | 425 | Item & in billing document & cannot be posted to CO-PA | ||
422 | 426 | Billing document &, item & has already been posted to CO-PA | ||
423 | 427 | You did not wish to have a log generated -> You cannot choose this option | ||
424 | 428 | Characteristic value & is not valid | ||
425 | 429 | Characteristic & does not exist in operating concern & | ||
426 | 430 | The selected valuation strategy is not allowed in the plan | ||
427 | 431 | Reversed invoice & cannot be posted to CO-PA | ||
428 | 432 | Enter an application to list possible entries | ||
429 | 433 | Table & generated without errors | ||
430 | 434 | Error generating table & | ||
431 | 435 | Costing key & does not exist | ||
432 | 436 | The type of characteristic & does not fit the type of th key field | ||
433 | 437 | The assignment to quantity field & is unclear! | ||
434 | 438 | Val. strategy &: Combination of val. time & and appl. & is not allowed | ||
435 | 439 | The assignment of variable and fixed costs is incorrect | ||
436 | 440 | Press F4 to display the valid characteristics | ||
437 | 441 | Display valid field names using F4 | ||
438 | 442 | Press F4 to display the valid characteristics | ||
439 | 443 | The assignment group does not belong to this operating concern | ||
440 | 444 | Valuation is not possible for record type & | ||
441 | 445 | Billing document item & & cannot be cancelled | ||
442 | 446 | Accounting document item & & cannot be cancelled | ||
443 | 447 | Billing document & cannot be posted to CO-PA | ||
444 | 448 | Value or quantity field is not correct | ||
445 | 449 | Inconsistency during processing of IDoc "&" | ||
446 | 450 | Table & is not active or does not exist | ||
447 | 451 | Table & contains data elements without texts | ||
448 | 452 | Table & contains no fields | ||
449 | 453 | Field &1 is not a non-key field in Table &2 | ||
450 | 454 | Field &1 does not exist in Table &2 | ||
451 | 455 | Tables cannot have more than 5 key fields! | ||
452 | 456 | Offset entered (&1) is too large for the field &2 in Table &3 | ||
453 | 457 | Field length entered (&1) and the offset (&2) are inconsistent | ||
454 | 458 | Saving/changing of derivation structures; number assignment | ||
455 | 459 | Display error: Table number & is already being used | ||
456 | 460 | Incoming sales order only allowed in costing-based CO-PA | ||
457 | 461 | Do not choose an organizational unit | ||
458 | 462 | You have not yet assigned a table number | ||
459 | 463 | Controlling area & is not assigned to an operating concern | ||
460 | 464 | Data element & is not unique in operating concern & | ||
461 | 465 | Error updating table &1: Key &2, data element &3, characteristic &4 | ||
462 | 466 | No characteristic can be assigned to table &1, data element &2 | ||
463 | 467 | The object & is not a table | ||
464 | 468 | Error deleting the TADIR entry for derivation structure & | ||
465 | 469 | Summarization "&1" is not possible for business transaction "&" | ||
466 | 470 | Document &, item & has already been posted to CO-PA | Space: object requires documentation | |
467 | 471 | Error reading with currency type & during actual data update | ||
468 | 472 | Inconsistency in currency translation in Profitability Analysis | ||
469 | 473 | Currency type is not allowed for actual data update | ||
470 | 474 | Plan/actual indicator in external file does not match | ||
471 | 475 | Inconsistency occurred during processing of FI/CO document | Space: object requires documentation | |
472 | 476 | Error creating the document in Profitability Analysis | Space: object requires documentation | |
473 | 477 | Line item & canceled even though currency type & is inactive | Space: object requires documentation | |
474 | 478 | Caution: Be sure to save the proposal for the field assignment | Space: object requires documentation | |
475 | 479 | Costing-based Profitability Analysis is not active! | Space: object requires documentation | |
476 | 480 | Transfer of incoming sales orders is not active | Space: object requires documentation | |
477 | 481 | Inconsistency during transfer of incoming sales orders | Space: object requires documentation | |
478 | 482 | Error in CO-PA valuation: quantity unit is missing | Space: object requires documentation | |
479 | 490 | Incorrect assignment of condition type & to CO-PA value fields | ||
480 | 491 | Assignment to an original cost element is not necessary | ||
481 | 494 | Assignment to a profitability segment: required assignment "&" missing | Space: object requires documentation | |
482 | 495 | Item has not been assigned to a profitability segment | Space: object requires documentation | |
483 | 496 | Check the assignment to a profitability segment (characteristic "&") | ||
484 | 497 | Check the assignment to a profitability segment | ||
485 | 498 | Assignment to a profitability segment has no effect for account & | Space: object requires documentation | |
486 | 499 | Profitability segment number & does not exist in operating concern &! | ||
487 | 500 | Table & not contained in data dictionary | ||
488 | 501 | Text table for characteristic & not found (check table &) | ||
489 | 502 | Table & does not belong to op. concern & | ||
490 | 503 | No attributes exist for operating concern & | Space: object requires documentation | |
491 | 504 | Operating concern &1 is not activated in client &2 | Space: object requires documentation | |
492 | 505 | Operating concern & does not exist | ||
493 | 506 | Maintain Fiscal Year Variant $ | ||
494 | 507 | Special period $ is not valid -> Check entry | ||
495 | 508 | The alternative period type has not been set up for use | ||
496 | 509 | Fiscal year variant $ has not been defined (Table T009) | ||
497 | 510 | Ledger & has not been assigned to operating concern & (Table TKEBL) | Space: object requires documentation | |
498 | 511 | The date format is incorrect | ||
499 | 512 | With &, only options EQ, BT, LE and GE are supported | Space: object requires documentation | |
500 | 513 | With &, only 'I' is supported as SIGN | Space: object requires documentation | |
501 | 514 | With &, only options EQ and BT are supported | Space: object requires documentation | |
502 | 515 | With &, from-period 000 is not supported | Space: object requires documentation | |
503 | 516 | Extend number range (see long text) | ||
504 | 517 | Number range is full (see long text) | ||
505 | 518 | Maintain number range for planning record type & | ||
506 | 519 | Table & contains data elements without texts | ||
507 | 520 | Data has not changed | ||
508 | 521 | Tables & and & do not belong together. | ||
509 | 522 | Cost element &1 is not defined for period &2 | ||
510 | 523 | System error: No texts in table &1 in language &2 | Space: object requires documentation | |
511 | 524 | Value &1 is not allowed for parameter &2 | Space: object requires documentation | |
512 | 525 | No text exists in language &2 for operating concern &1 | Space: object requires documentation | |
513 | 526 | Operating concern &1 does not exist in client &2 | Space: object requires documentation | |
514 | 527 | Currency type &1 is not allowed | Space: object requires documentation | |
515 | 528 | "&1" has not been defined for operating concern &2 | Space: object requires documentation | |
516 | 529 | Currency type &1 is not defined | Space: object requires documentation | |
517 | 530 | System error: No entries in table & | Space: object requires documentation | |
518 | 531 | Tables TKEB and TKEBL were already converted | Space: object requires documentation | |
519 | 532 | Tables TKEB and TKEBL converted | Space: object requires documentation | |
520 | 533 | Table TKEVS was converted | Space: object requires documentation | |
521 | 534 | Help text for warning when no summarization level was found | Space: object requires documentation | |
522 | 535 | Help text for error message when no summarization level was found | Space: object requires documentation | |
523 | 536 | Help text for warning when no summarization data was found | Space: object requires documentation | |
524 | 537 | Help text for error message when no summarization data was found | Space: object requires documentation | |
525 | 538 | Create database index 4 for table COEP/COEJ -> see long text | Space: object requires documentation | |
526 | 539 | Create database index 3 for table &2 -> see long text | Space: object requires documentation | |
527 | 540 | Date &1 is not valid | Space: object requires documentation | |
528 | 541 | Operating concern &1 is not defined for account-based CO-PA | Space: object requires documentation | |
529 | 542 | Higher-level characteristic &1 not contained in operating concern &2 | Space: object requires documentation | |
530 | 543 | Field &1 not contained in nametab for table &2 | Space: object requires documentation | |
531 | 544 | Nametab for table &2 must not contain field &1 | Space: object requires documentation | |
532 | 545 | Profitability segment number & not found in operating concern & | Space: object requires documentation | |
533 | 548 | Error building summarization levels -> see long text | Space: object requires documentation | |
534 | 549 | Program state is invalid -> see long text | Space: object requires documentation | |
535 | 550 | <<<<<<< Conversion to 7 digit periods >>>>>>>> | ||
536 | 551 | Entry should have template ___.____ | ||
537 | 552 | Entry should have template ___/____ | ||
538 | 553 | Entry should have template ___-____ | ||
539 | 554 | Entry should have template ____.___ | ||
540 | 555 | Entry should have template ____.___ | ||
541 | 559 | Enter a date falling within the range 1990 - 2050 | Space: object requires documentation | |
542 | 560 | <<<<<<< View maintenance for characteristic groups>>>>>> | ||
543 | 561 | Enter row number > 0 | ||
544 | 562 | Display valid field names using F4 | ||
545 | 563 | Characteristic & already exists in the characteristic group | ||
546 | 564 | Characteristic & has been selected for deletion | ||
547 | 565 | Characteristic group & contains no rows -> cannot be saved | ||
548 | 566 | Characteristic group does not exist -> Check your entry | ||
549 | 567 | Characteristic &1 of char. group &2 cannot be used for transaction &3 | ||
550 | 568 | Characteristic group & must contain char. BUKRS for the record type & | Space: object requires documentation | |
551 | 569 | No characteristics can be displayed | Space: object requires documentation | |
552 | 580 | <--------- Function group KEAK_02 ... bis 589 ---------> | Space: object requires documentation | |
553 | 581 | Data record already exists | Space: object requires documentation | |
554 | 582 | The key fiedl PAOBJNR is missing from the date record to be updated | Space: object requires documentation | |
555 | 590 | Enter one to six source fields | ||
556 | 591 | Enter one to six target fields | ||
557 | 600 | <<<<<<<<<< Maintain operating concern using SAP-EIS tool >>>>>>>>> | ||
558 | 601 | You are not authorized to perform this function | ||
559 | 602 | The data structures of operating concern & were saved/activated | ||
560 | 603 | The data structures of operating concern & were not saved/activated | ||
561 | 604 | The environment was generated completely | Space: object requires documentation | |
562 | 605 | The environment was generated, warnings were issued | Space: object requires documentation | |
563 | 606 | The environment has not been generated completely | Space: object requires documentation | |
564 | 607 | Secondary index &2 was not created for table &1 | Space: object requires documentation | |
565 | 608 | Secondary index &2 activated for table &1 | Space: object requires documentation | |
566 | 609 | A secondary index (&2) already exists for table &1 | Space: object requires documentation | |
567 | 610 | Secondary index &2 has not been created for table & | Space: object requires documentation | |
568 | 611 | Secondary index &2 for table &1 was activated with warnings | Space: object requires documentation | |
569 | 612 | Secondary index &2 for table &1 was not activated | Space: object requires documentation | |
570 | 613 | Secondary index (&2) for table & saved | Space: object requires documentation | |
571 | 614 | Characteristics/value fields were not created -> function not possible | ||
572 | 615 | Characteristics/value fields already exist -> function not possible | ||
573 | 616 | Tables not been created in the database system ->Function cannot be exec. | ||
574 | 617 | Attributes have not been created -> Function cannot be executed | ||
575 | 618 | Attributes already exist -> Function cannot be executed | ||
576 | 619 | The function is not possible because the data structures are not active | ||
577 | 620 | You are not authorized to perform this function | ||
578 | 621 | No attributes exist for reference operating concern & | ||
579 | 622 | Attributes saved | ||
580 | 623 | Error saving attributes | ||
581 | 624 | Caution: Inconsistencies could result if you change the attributes -> F1 | ||
582 | 625 | The operating concern contains data. Entries in Table & were not deleted. | ||
583 | 626 | The attributes in client & were deleted. | ||
584 | 627 | Caution! Client-specific Customizing settings will be deleted. | ||
585 | 628 | & & & & | ||
586 | 629 | The data structures for the operating concern were created in client & | ||
587 | 630 | Caution! You are changing/deleting cross-client settings | Space: object requires documentation | |
588 | 631 | Internal error in form/method "&" | Space: object requires documentation | |
589 | 632 | Enter the type of Profitability Analysis | ||
590 | 633 | Enter the operating concern you wish to copy | ||
591 | 634 | You must generate the data structures and environment following changes | ||
592 | 635 | You are not authorized to maintain settings which affect all clients | ||
593 | 636 | Leave the field "Copy from" blank | ||
594 | 637 | Data structures for operating concern & are not active | ||
595 | 638 | SAP operating concern &2 can only be activated in system &1 | Space: object requires documentation | |
596 | 639 | You cannot maintain the data structure now -- gen. tool being worked on | ||
597 | 640 | Controlling area and op. concern have different fiscal year variants | ||
598 | 641 | Operating concern & can only be activated | ||
599 | 642 | Attributes still exist for operating concern & | ||
600 | 643 | Operating concern & is still assigned to a controlling area | ||
601 | 644 | Costing sheet & is still being used | ||
602 | 645 | Costing sheet & is still being used | ||
603 | 646 | User &1 is locking table &2 | ||
604 | 647 | Attributes for operating concern &1 locked by &2 | ||
605 | 648 | Objects for the environment of operating concern & still exist | ||
606 | 649 | System error: Field &1 is not in field catalog &2 | Space: object requires documentation | |
607 | 650 | <<<<<<<<<< Reorg. of field catalog >>>>>>>>>> | ||
608 | 651 | No characteristics/value fields defined for operating concern & | ||
609 | 652 | Reference table & is not active in the ABAP/4 Dictionary | ||
610 | 653 | Select one option only | ||
611 | 654 | Field catalog & could not be locked. Reorganization terminated | ||
612 | 655 | CO-PA field catalog was reorganized. | ||
613 | 656 | Key figure BONUS is not allowed in operating concern &. | ||
614 | 657 | View & is not active. Usage will be deleted in the field catalog | ||
615 | 658 | The field catalogs for operating concern & have been reorganized | ||
616 | 659 | References in Table & were reorganized and table was saved | ||
617 | 660 | Error saving table & | ||
618 | 661 | Table & does not exist | ||
619 | 662 | Table & converted for new release and saved | ||
620 | 663 | Table & was activated | ||
621 | 664 | Table & activated with warnings | ||
622 | 665 | Table & was not activated | Space: object requires documentation | |
623 | 666 | Field & was not entered in the field catalog TKEF | Space: object requires documentation | |
624 | 667 | Fixed field &1 from table &2 is not predefined | Space: object requires documentation | |
625 | 668 | Field &1 of table &2 is not in the field catalog TKEF | Space: object requires documentation | |
626 | 669 | System error: control table IKCG was not filled | Space: object requires documentation | |
627 | 670 | Data structures do not exist for operating concern & | Space: object requires documentation | |
628 | 671 | Field & could not be inserted in the field catalog TKEF | Space: object requires documentation | |
629 | 672 | Field & could not be updated in the field catalog TKEF | Space: object requires documentation | |
630 | 673 | The data structures are currently locked by user & | Space: object requires documentation | |
631 | 674 | Table & was generated and saved | Space: object requires documentation | |
632 | 675 | System error: exception raised in function module & | Space: object requires documentation | |
633 | 676 | No SAP objects can be created in this system | Space: object requires documentation | |
634 | 677 | The operating concern name &1 is not allowed | Space: object requires documentation | |
635 | 678 | Operating concern &1 already exists | Space: object requires documentation | |
636 | 679 | You cannot copy a customer-defined operating concern to an SAP op.concern | Space: object requires documentation | |
637 | 680 | <<<<<<<< Messages for "Maintain operating concern" cont'd <<<<<<<<<< | ||
638 | 681 | Error generating the environment -> operating concern is partly active | ||
639 | 682 | The internal field table for operating concern & was not created | ||
640 | 683 | The data structures for operating concern & were deleted | ||
641 | 684 | The data structures for operating concern & were not deleted | ||
642 | 685 | System error: TKEF and TKES are inconsistent for & | Space: object requires documentation | |
643 | 686 | System error: incompatible update of TKEF entry & | Space: object requires documentation | |
644 | 687 | Field & is predefined and therefore cannot be deleted | Space: object requires documentation | |
645 | 688 | Substitute fields for &1 could not be created | Space: object requires documentation | |
646 | 689 | No active version exists for table/structure & | Space: object requires documentation | |
647 | 690 | No active version exists for data element & | Space: object requires documentation | |
648 | 691 | Product hierarchy field &1 cannot be adapted to the new structure | Space: object requires documentation | |
649 | 692 | Operating concern &1 may only be activated | Space: object requires documentation | |
650 | 693 | Changes to Customizing are not permitted | Space: object requires documentation | |
651 | 694 | Creation of new operating concerns not permitted | Space: object requires documentation | |
652 | 695 | Foreign key relationship for field &1-&2 has been created/changed | Space: object requires documentation | |
653 | 696 | Foreign key relationship for field &1-&2 has been deleted | Space: object requires documentation | |
654 | 697 | Program error occurred during adjustment of operating concern &1 | Space: object requires documentation | |
655 | 698 | System error: Application log cannot be opened | Space: object requires documentation | |
656 | 699 | Changes to the cross-client Customizing are not permitted | Space: object requires documentation | |
657 | 700 | <<<<<<<<<< Reserved for DB interface/summariz. levels (700-799) >>>>>>>>> | ||
658 | 701 | Names K8* are reserved for generated tables (CO-PA summarization levels) | ||
659 | 702 | Names RK3* are reserved for generated reports(CO-PA summarization levels) | ||
660 | 703 | User & is processing the summarization levels | ||
661 | 704 | The summarization levels are not used -> inconsistencies exist | ||
662 | 705 | The summarization levels are not used -> inconsistencies exist | ||
663 | 706 | There are no summarization levels to be processed | ||
664 | 707 | Inconsistency in catalog of summarization levels -> Call up maintenance | ||
665 | 708 | The summarization levels were not activated | ||
666 | 709 | You are not authorized to change summarization levels | ||
667 | 710 | There are no summarization levels to be processed | ||
668 | 711 | The summarization levels could not be activated | ||
669 | 712 | The summarization levels could not be activated | ||
670 | 713 | The summarization levels could not be activated | ||
671 | 714 | The summarization levels could not be activated | ||
672 | 715 | The summarization levels were not activated | ||
673 | 716 | Summarization levels are not yet supported for the application &1 &2 &3 | ||
674 | 717 | The summarization levels were not activated | ||
675 | 718 | You are not authorized to update the summarization levels | ||
676 | 719 | Update program is active -> repeat function later | ||
677 | 720 | Summarization levels not allowed for aspect & | ||
678 | 721 | Field &1 is not in the field list for operating concern &2 | ||
679 | 722 | Syntax error in line &1 of the generated program &2 | ||
680 | 723 | Error &1 during generation of program &2 | ||
681 | 724 | Internal error -> contact your system administrator | ||
682 | 725 | Error reading the NAMETAB for table & | ||
683 | 726 | Field &1 is not in table &2 in the Dictionary | ||
684 | 727 | Error &1 while inserting the table &2 in the Dictionary | ||
685 | 728 | Error (&1/&2) activating table &3 in the Dictionary | ||
686 | 729 | Name range for generated programs is temporarily full | ||
687 | 730 | Lock problem! | ||
688 | 731 | Syntax error in the generated program -> see & | ||
689 | 732 | This function is only supported for blocking factor 1 | Space: object requires documentation | |
690 | 733 | & is currently not supported by fast rollup | ||
691 | 734 | The temporary Join product must have at least one column | ||
692 | 735 | Naming range CEJ* is reserved for generated tables (CO-PA summ. levels) | ||
693 | 736 | Requested field & not contained in the semi-temporary Join product | ||
694 | 737 | Conditions of time (field &) are not allowed | ||
695 | 738 | Field & supposed to be NOT ZERO -> this is not allowed | ||
696 | 739 | Table &1: field list cannot be determined | ||
697 | 740 | Field &1 does not exist in table &2 | ||
698 | 741 | Internal error: Client or period block is not in the projection | ||
699 | 742 | Internal error: Summarization level &1 is inconsistent | Space: object requires documentation | |
700 | 743 | First build the JOIN product using report RKETRERJ | Space: object requires documentation | |
701 | 744 | Restart not possible because CEJ has been rebuilt in the meantime | Space: object requires documentation | |
702 | 745 | No more periods need to be edited | Space: object requires documentation | |
703 | 746 | >>> reserved for fast roll-up of summrization levels in CO-PA | ||
704 | 747 | >>> reserved for fast roll-up of summrization levels in CO-PA | ||
705 | 748 | >>> reserved for fast roll-up of summrization levels in CO-PA | ||
706 | 749 | >>> reserved for fast roll-up of summrization levels in CO-PA | ||
707 | 750 | Error deleting the data from summarization level & -> see long text | ||
708 | 751 | No summarization levels exist for &1 &2 &3 | ||
709 | 752 | No suitable summarization level exists | ||
710 | 753 | You are not authorized to analyze the access log | Space: object requires documentation | |
711 | 754 | Operating concern & is not defined for costing-based Prof. Analysis | Space: object requires documentation | |
712 | 755 | Operating concern & is not defined for account-based Prof. Analysis | Space: object requires documentation | |
713 | 756 | New fields could not be added | Space: object requires documentation | |
714 | 757 | No entries found | Space: object requires documentation | |
715 | 758 | ORDER-BY clauses are not permitted for reading actual data | Space: object requires documentation | |
716 | 759 | No condition can be attached to TIMESTMP for reading actual data | Space: object requires documentation | |
717 | 760 | No conditions can be attached to field &1 | Space: object requires documentation | |
718 | 761 | The read mode &1 is not supported in account-based Profitability Analysis | Space: object requires documentation | |
719 | 762 | Only the long text is displayed from program RKETREPROP | Space: object requires documentation | |
720 | 763 | Error occurred during conversion of period requirement | Space: object requires documentation | |
721 | 764 | The selection criterion for "&1" cannot be executed | Space: object requires documentation | |
722 | 765 | Operating concern "&1" does not exist | Space: object requires documentation | |
723 | 766 | Table "&1" does not exist | Space: object requires documentation | |
724 | 767 | Table "&1" is empty | Space: object requires documentation | |
725 | 768 | Table "&1" is not empty | Space: object requires documentation | |
726 | 769 | Generated program "&1" does not exist | Space: object requires documentation | |
727 | 770 | Do not use form routine/function module &1 | Space: object requires documentation | |
728 | 771 | Fatal error during conversion | Space: object requires documentation | |
729 | 773 | Initial entries were reset during save | Space: object requires documentation | |
730 | 774 | Entries were reset to the SAP standard settings | Space: object requires documentation | |
731 | 776 | Information on transport | Space: object requires documentation | |
732 | 777 | You must specify a company code if the company code currency is used | Space: object requires documentation | |
733 | 778 | Level & already exists -> enter a different number | ||
734 | 779 | Field & must contain a fixed value | ||
735 | 780 | Characteristic value &1 does not exist for characteristic &2 | ||
736 | 781 | Field & was deleted from the reference structure | ||
737 | 782 | Field & was added to the reference structure | ||
738 | 783 | You do not have adequate authorization | ||
739 | 784 | Include characteristic &2 in summarization level &3 -> See long text | Space: object requires documentation | |
740 | 786 | Error in the definition of the time fields | ||
741 | 787 | Field & is not used | ||
742 | 788 | Field & needs to be added to the definition | ||
743 | 789 | Aspect contains fields with aggregation <> SUM | ||
744 | 790 | & is not an allowed field name for index | ||
745 | 791 | Entry required | ||
746 | 792 | Field name & is found twice in the index | ||
747 | 793 | Enter at least one field in the index | ||
748 | 794 | &1 indices were deleted for field &2 | ||
749 | 795 | Do not define more than 15 indices | ||
750 | 796 | No indexes maintained | ||
751 | 797 | Field usage changed | ||
752 | 799 | Invalid program state in the summarization levels | ||
753 | 800 | <<<<<<<<<<<<<<<<<<<<<<<Distribution>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> | ||
754 | 801 | Field & does not exist in structure & | ||
755 | 802 | Segment & does not exist. | ||
756 | 803 | There is no message type in Table TKEBB for operating concern &. | ||
757 | 804 | No logical system was entered in table T000 | ||
758 | 805 | The combination you have entered is not allowed. | ||
759 | 806 | Message types are not the same | ||
760 | 807 | Please select using period range/year. | ||
761 | 808 | Please select using period/year (week/year). | ||
762 | 809 | Message type & was created for operating concern &. | ||
763 | 810 | Error in RFC: & | Space: object requires documentation | |
764 | 811 | You do not have authorization for distribution | ||
765 | 812 | Table EDIMAP updated for message type CODCMT | ||
766 | 813 | Segment number & is not found in Table & | ||
767 | 814 | Line item was already posted in the target system | ||
768 | 815 | This function is only allowed for periodic roll-up | ||
769 | 816 | This function is only allowed for transaction-specific distribution | ||
770 | 817 | You cannot select plan data by item number | ||
771 | 818 | Incorrect output mode in the partner agreement | ||
772 | 819 | Structures CEST1 and E1KEFXA do not match | ||
773 | 820 | Variant cannot be saved with "Additional selections" | ||
774 | 821 | Only long text from function module RKE_EXECUTE_WITH_DATA is displayed | Space: object requires documentation | |
775 | 830 | *********** N E T C H A N G E ****************** | ||
776 | 831 | Data is already locked by another user | ||
777 | 832 | System error occurred during locking | ||
778 | 833 | Number range & is full for operating concern &, segment & | ||
779 | 834 | Number range was not found for operating concern &, record type & | ||
780 | 835 | Error occurred during value input | ||
781 | 836 | You are not authorized to carry out realignments | ||
782 | 850 | ********* Rollup Summarization operating concerns ******************** | ||
783 | 851 | The attributes of the operating concerns involved are not the same | ||
784 | 852 | Different methods of creating are not allowed | ||
785 | 853 | Different sorting characteristics are not allowed | ||
786 | 854 | For method "2", enter sorting characteristics | ||
787 | 855 | Mode "3" is only allowed with method "4" | ||
788 | 856 | For mode "5" you must enter a file name | ||
789 | 857 | Only enter a file name for mode "5" | ||
790 | 858 | In mode "5" you can only transfer actual data | ||
791 | 859 | This combination of parameters is not allowed | ||
792 | 860 | Not initialized | ||
793 | 861 | You cannot create using methods "1" and "4" | ||
794 | 862 | You can only delete for the entire operating concern | ||
795 | 863 | Data cannot be read from the archive using the current structure | The short text describes the object sufficiently | |
796 | 870 | <<<<<<<<<<<<<<<<<<< Archiving >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> | The short text describes the object sufficiently | |
797 | 871 | &2 profitability segment(s) from &3 table(s) archived | The short text describes the object sufficiently | |
798 | 872 | &2 profitability segment(s) from &3 table(s) deleted | The short text describes the object sufficiently | |
799 | 873 | &2 profitability segment(s) from &3 table(s) reloaded | The short text describes the object sufficiently | |
800 | 874 | Archiving environment of profitability area & generated without errors | The short text describes the object sufficiently | |
801 | 875 | Error when generating archiving environment for profitability segment & | The short text describes the object sufficiently | |
802 | 876 | Costing-based Profitability Analysis is not implemented | The short text describes the object sufficiently | |
803 | 880 | Data can only be deleted with authorization K_KEA_TC | Space: object requires documentation | |
804 | 881 | Select at least one field in the settings block | Space: object requires documentation | |
805 | 882 | Operating concern & does not exist | Space: object requires documentation | |
806 | 883 | Transaction data has been deleted from operating concern & | Space: object requires documentation | |
807 | 885 | The characteristic cannot be maintained with this program | Space: object requires documentation | |
808 | 886 | Enter a transaction code | Space: object requires documentation | |
809 | 887 | Enter an IMG activity | Space: object requires documentation | |
810 | 888 | Maintain at least one field | Space: object requires documentation | |
811 | 889 | Characteristic &1 cannot be generated in structure COPABBSEG | Space: object requires documentation | |
812 | 890 | You are not permitted to create a batch input folder in the test run | Space: object requires documentation | |
813 | 891 | Operating concern &2 does not contain value field &1 | Space: object requires documentation | |
814 | 893 | Industry '&1' not permitted. Save not possible. | Space: object requires documentation | |
815 | 894 | Errors occurred when saving the program version | Space: object requires documentation | |
816 | 895 | View &1 may only be started in the display mode in the customer system | Space: object requires documentation | |
817 | 896 | Important: An error occurred when generating Include &1 | Space: object requires documentation | |
818 | 897 | Include &1 was successfully generated | Space: object requires documentation | |
819 | 898 | Characteristic or value field already exists in another field catalog | Space: object requires documentation | |
820 | 899 | Do not use operating concern maintenance any more | Space: object requires documentation | |
821 | 950 | <<<<<<<<<<<<<<<<<<<<Reserved for CATT>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> | ||
822 | 951 | Line item & entered incorrectly in Table & | ||
823 | 952 | Error accessing function module & | ||
824 | 953 | Sales qty in Table & does not correspond to planned sales qty |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in |