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