/SAPCND/CUSTOMIZING - Nachrichten f�r das Customizing
The following messages are stored in message class /SAPCND/CUSTOMIZING: Nachrichten f�r das Customizing.
It is part of development package /SAPCND/CUSTOMIZING in software component AP-PRC-CON. This development package consists of objects that can be grouped under "Customizing Objects for Condition Technique".
It is part of development package /SAPCND/CUSTOMIZING in software component AP-PRC-CON. This development package consists of objects that can be grouped under "Customizing Objects for Condition Technique".
Message Nr ▲ | Message Text |
|---|---|
| 000 | **** Customizing Views 001 - 099 *** |
| 001 | Priority Valuation:Permitted in access mode 'A' only |
| 002 | Entry cannot be deleted because downloaded from external system |
| 003 | Priority valuation is mandatory for access mode 'A' |
| 004 | No Authorization for Maintaining Access Sequences |
| 005 | Requirement with number & does not exist |
| 006 | & entries could not be deleted because downloaded |
| 007 | You have no authorization to change general system settings |
| 008 | You have no authorization to display general system settings |
| 009 | Condition table &1 could not be found. |
| 010 | Standard F4 Help: All condition types. |
| 011 | Implementation Method PREVENT_MAINTENANCE Inconsistent; Param. ES_RETURN |
| 012 | The maximal scale dimension is too large. The maximum permitted is '&' |
| 013 | Application &1 does not correspond with the other items |
| 014 | Table &1 is not in access for condition type &2 |
| 015 | Select other group name as &1 (special characters not permitted) |
| 016 | Only the characteristics' ', 'b' and 'A' are supported |
| 017 | The system settings do not allow changes to be made to object &1 &2 |
| 018 | Access sequence &1 is inconsistent because no access exists |
| 019 | Access sequence &1 is inconsistent because no field exists for access &2 |
| 020 | Maintenance group &1 is inconsistent, as it does not contain any items |
| 021 | Determination procedure &1 is inconsistent because no elements exist |
| 022 | Objects for maintenance group &1 could not be generated |
| 023 | Application log cannot be created, read or displayed |
| 024 | Objects for maintenance group &1 could not be deleted |
| 025 | Objects for config. file could not be created without errors |
| 026 | Initial access ID is not permitted |
| 027 | Objects for usage could not be generated |
| 028 | Objects for task could not be generated without errors |
| 029 | Access in &1 &2 &3 to &4 with multiple-value attributes is not supported |
| 030 | Deletion of group because of ref. in maint. context &1 is not possible |
| 031 | Access sequence &1 is inconsistent; target field &2 missing in access &3 |
| 040 | Assign attribute &1 for formula &2 &3 |
| 041 | Number range limit &1 is greater than &2 |
| 042 | Number range &1 &2 from &3 to &4 overlaps with other entries |
| 043 | Check for valid number range is not possible |
| 044 | Number range from &1 to &2 is only permitted for SAP standard systems |
| 045 | Number range from &1 to &2 is only permitted for customer systems (&3 &4) |
| 046 | Number &1 is outside of permitted areas (&3 &4) |
| 047 | Formula type &1 &2 does not permit numbers |
| 048 | No authorization to maintain user exits |
| 049 | Formula type &1 &2 only permits the number 0 |
| 050 | No authorization to maintain user exits |
| 051 | &1 entries generated for table &2 |
| 052 | You cannot maintain a source field name for an initial constant |
| 053 | If the initial indicator is set, you cannot maintain any constants |
| 054 | You cannot maintain an access type for an initial constant |
| 055 | If indicator is set to initial, only &1 is permitted as a constant |
| 056 | Access type A cannot be maintained for a multiple-value target field |
| 057 | Source field for target field &1 is missing |
| 058 | IPC Customizing buffer cleared for application &1 / usage &2 |
| 100 | ***Reorganization: Customizing Cache |
| 101 | Reorganization of cache for &1 [&2 &3 &4] was started |
| 102 | Reorganization of cache for &1 [&2 &3 &4] was completed successfully |
| 103 | Restructuring of cache for &1 and usage &2 was started |
| 104 | Restructuring of the cache for &1 and usage &2 was completed successfully |
| 105 | Customizing cache &1 does not contain any entries |
| 106 | Customizing cache &1 does not contain entries for &2 &3 &4 |
| 126 | Unable to find Include statement for &1 |
| 200 | ** Customizing class ** [200-399] |
| 201 | Activation for appl. & view & and table & was successful |
| 202 | Activation for appl. & usage & and table & failed |
| 203 | Active and inactive versions are identical |
| 204 | Conversion of object contents to XMML failed |
| 205 | Conversion of object contents to XMML failed |
| 206 | Runtime error: XSL transformation was interrupted |
| 208 | Delete operation for table &1 failed |
| 209 | Appl. & usage & and table &: Inactive version is inconsistent |
| 210 | There is no active version for XML conversion available |
| 211 | The processed XML document is initial |
| 212 | Generation for application &, Usage & and table & failed |
| 213 | Parameter for XML conversion contains errors |
| 214 | The inactive version was deleted successfully |
| 215 | The inactive vesion could not be deleted |
| 216 | No generation since active and inactive version of &1 &2 &3 identical |
| 300 | * Customizing buffer (Java) * |
| 301 | Communication failure: &1 &2 &3 &4 |
| 302 | System failure (runtime error): &1 &2 &3 &4 |
| 303 | Unknown RFC error |
| 304 | Update of Configuration buffer in appl. server &1 successful |
| 305 | Messages for appliction server &1 |
| 306 | Client Dependent Configuration buffer update f. appl. &1 / usage &2 |
| 307 | Client Dependent Configuration buffer update f. application &1 |
| 308 | Client Dependent Configuration buffer update f. usage &1 |
| 309 | Client Dependent Configuration buffer update f. all appl./usages |
| 310 | Client Independent Configuration buffer update f. appl. &1 / usage &2 |
| 311 | Client Independent Configuration buffer update f. application &1 |
| 312 | Client Independent Configuration buffer update f. usage &1 |
| 313 | Client Independent Configuration buffer update f. all appl./usages |
| 314 | Shared Memory Error: &1 &2 &3 &4 |
| 400 | ** Field catalog maintenance ** 400-499 |
| 401 | Complete all fields available for input |
| 402 | There is already an entry & &. Make a new entry. |
| 403 | Entry is in SAP name space. |
| 404 | Entry is in customer name space. |
| 405 | Entry & is already marked for deletion. |
| 406 | This function is not (yet) supported. |
| 407 | No data was changed. |
| 408 | Data was saved |
| 409 | Entry & & already exists in super application &. |
| 410 | Entry & already exists. Make a new entry. |
| 411 | Condition table & already exists for field &. |
| 412 | Field & is already used in access sequence &. |
| 413 | & condition tables already exist for field &. |
| 414 | Field & is already used in & access sequences. |
| 415 | Data element & is still used for field &. |
| 416 | Data element & is still used for & fields. |
| 417 | Related objects have been generated. |
| 418 | Start of function: &1 (&2 &3 &4) |
| 419 | End of function: &1 (&2 &3 &4) |
| 420 | Field & entered in table &. |
| 421 | Field & deleted from table &. |
| 422 | Relationship &/& entered in table &. |
| 423 | Relationship &/& deleted from table &. |
| 424 | Relationship &/& entered in table &. |
| 425 | Relationship &/& deleted from table &. |
| 426 | Transaction '&' cannot be processed. |
| 427 | Data element & entered in table &. |
| 428 | Data element & deleted from table &. |
| 429 | Combination &3/&4 for "virtual" attribute in rel. &1/&2 not permitted. |
| 430 | You cannot maintain relationships for "virtual" field attribute &. |
| 431 | The following cycle exists: &1&2&3&4 |
| 432 | A cycle is based on the ratio &/&. |
| 433 | Cycle in the data element ratio. |
| 434 | Processing for application & (&). |
| 435 | Save the changed data first. |
| 436 | Internal fields may have a maximum of & digits. |
| 437 | Field & does not exist. |
| 438 | Unreliable categories for subcommunication structure for rel. &1/&2 |
| 439 | Field &1 is still used in &2 ratio(s). |
| 440 | Processing for application & usage & and table &. |
| 441 | Field name &1 contains spaces or special symbols |
| 442 | Field &1 already exists in the global field catalog. |
| 443 | Data element & exceeds maximum field length. |
| 444 | The field & is in SAP namespace! |
| 445 | The field & is in customer namespace! |
| 446 | Data Element &1 does not exist in language &2 |
| 447 | Data Element &1 does not exist in any language |
| 448 | Maintenance of dependency to data element &1 is not permitted |
| 449 | Save new field entries first |
| 450 | The dependency relataionship, &1 is dependent on &2, is not permitted |
| 451 | The dependency relationship, &2 is a dependency of &1, is not permitted |
| 452 | Data element &1 is not active |
| 453 | Relevant table entries were transferred in request/task &1/&2 |
| 454 | Entries cannot be transferred to a transport request |
| 455 | Table entries already exist in request/task &1/&2 |
| 460 | Condition technique field &1 cannot be used as application field |
| 463 | &1 has a dependency on &2 which does not exist in LT_NODE variable |
| 500 | ** Generation transaction ** 500-599 |
| 501 | At least one field name for the condition table is initial |
| 502 | At least one explanatory short text for the condition table is initial |
| 503 | Object could not be generated |
| 504 | Condition table was not generated successfully |
| 600 | ** Condition table maintenance ** 600-699 |
| 601 | No name can be assigned for a condition table. |
| 602 | Condition table already exists as a generated version |
| 603 | Enter a table name |
| 604 | No field chosen |
| 605 | Condition table saved |
| 606 | Maintain a table description |
| 607 | This condition table is not available |
| 608 | Condition table cannot be deleted |
| 609 | An error occured when saving, all entries are taken back |
| 610 | &1 not possible |
| 611 | Cannot save as included in an access sequence |
| 612 | Processing for application &1, usage &2 and table &3 (&). |
| 613 | Condition table &1 entered in &2 |
| 614 | Condition table &1 deleted from &2 |
| 615 | Short description from &1 entered in &2 |
| 616 | Short description from &1 deleted from &2 |
| 617 | Fields from &1 entered in &2 |
| 618 | Fields from &1 deleted from &2 |
| 619 | Function &1 terminated by user |
| 620 | This combination of application / usage does not exist. |
| 621 | No key field may follow a non-key field |
| 622 | Error in condition table & in data source |
| 623 | Table name is not in namespace |
| 624 | Original of this table is not in the system |
| 625 | Select an application and an usage |
| 626 | Condition tables may not have more than 10 fields |
| 627 | Only data types RAW or CHAR are permitted. |
| 628 | Total of Field Lengths for All Key Fields is Too Long |
| 629 | Data Type &1 Not Known |
| 630 | Condition tables can not be changed during upgrade |
| 631 | The name of the condition table is inital |
| 632 | Object directory entry was not created |
| 633 | Object generation in dialogue is not allowed during upgrade |
| 634 | Object generation for group &1 required but not allowed during upgrade |
| 635 | Object generation for group &1 failed |
| 636 | Object deletion in dialogue is not allowed during upgrade |
| 700 | ** Report: Where-Used List of Generated Objects ** [700-749] |
| 701 | & uses object & in & (&) |
| 750 | ** Messages for general Customizing Function Modules [750-849] |
| 751 | Parameter &1 must be filled. |
| 752 | Caller &1 &2 is not registered in table /SAPCND/T681Z |
| 753 | Condition table &1 &2 &3 is not registered in table &4. |
| 754 | The generation status of condition table &1 &2 &3 is not at maximum. |
| 755 | Usage &1 is not registered in table /SAPCND/T681V. |
| 756 | The chosen dimension &1 is larger than the largest dimension &2. |
| 757 | The scale base type &2 for usage &1 is not registered in table &3. |
| 758 | The insert operation for table &1 failed |
| 759 | The update operation for table &1 failed |
| 760 | Error when structuring table &1 |
| 761 | Field name &1 is not available in table &2 |
| 762 | Modify operation for table &1 failed |
| 763 | Cycle within inheritance dependencies of &1 |
| 764 | Field &1 in table &2 is initial for value &3 of &4 |
| 765 | Usage &1 has the higher-level usage &2 |
| 766 | Signature for task &1 &2 not found in tadir. |
| 769 | Usage &1 cannot be used in this scenario |
| 770 | Usage &1 can only be used in special scenarios |
| 771 | Field name &1 not found in field catalog of application &2 |
| 772 | Field name &1 cannot be checked |
| 850 | Condition table is not available |
| 851 | Fields for condition table do not exist |
| 852 | Text for condition table does not exist |
| 853 | An inactive version of condition table &1 does not exist |
| 854 | An active version of condition table &1 does not exist |
| 890 | Database access for table &1 failed |
| 891 | CREATE DATA for table &1 failed |
| 892 | Determination of object names for scale tables failed |
| 893 | Determination of scale data records failed |
| 894 | LIN table is not available: Appl. &1, Usage &2, Type &3 |
| 895 | VAL table is not available: Appl. &1, Usage &2, Dimension &3 |
| 896 | Active version of scale table &1 does not exist |