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