VC - SD Customizing
The following messages are stored in message class VC: SD Customizing.
It is part of development package VS0C in software component SD-MD-MM. This development package consists of objects that can be grouped under "Customizing R/3 Sales and Distribution master data".
It is part of development package VS0C in software component SD-MD-MM. This development package consists of objects that can be grouped under "Customizing R/3 Sales and Distribution master data".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ******* 001-009 : hierarchical display of product hierarchy ******* |
| 001 | The product hierarchy is too long, please shorten it |
| 002 | Definition of hierarchy levels for the product hierarchy is not valid |
| 003 | Please enter a product hierarchy without empty groups |
| 004 | Please maintain the Group definition & (level: &) |
| 005 | Please select the entry to be copied |
| 006 | Select one entry only |
| 007 | First delete the dependent subgroups for hierarchy & |
| 008 | You must select a line for this function |
| 009 | Ctry/reg & in shipping point & and ctry/reg & in the address do not match |
| 010 | 'Item rel. for delivery' only allowed from item categories A and B |
| 011 | Check the country/region key for the address |
| 012 | There are no hierarchy nodes available for display! |
| 013 | Specify restrictions for nodes (or country/region) |
| 014 | ******** 015-099: Customer hierarchy ********************************** |
| 015 | You have no authorization to change hierarchy data |
| 016 | You have no authorization to display hierarchy data |
| 020 | ******* 021-099 : Customer hierarchy ***** |
| 021 | Sales area & & & is not defined for customer |
| 022 | Higher-level sales area & & & not defined for customer |
| 023 | Specify dependent and higher-level sales area |
| 024 | You only have authorization for displaying class & |
| 025 | You have no authorization for Classification & |
| 026 | Data can only be displayed because it is blocked by another user |
| 027 | System error blocking Table & |
| 028 | Data has been saved |
| 029 | Hierarchy type &: There are no active assignments for & |
| 030 | No errors were found in the assignments |
| 031 | Inconsistent sales areas cannot be assigned |
| 032 | Errors have been found in the assignments |
| 033 | No assignments have been changed |
| 034 | Error inserting Assignment & |
| 035 | Error deleting Assignment & |
| 036 | Hierarchy type is missing: Assignments cannot be made |
| 037 | Error updating Assignment & |
| 038 | Node cannot be deleted: invalid assignments would occur |
| 039 | Customer & for Sales area & & & does not exist |
| 040 | Validity date is missing: Hierarchy will be determined for today's date |
| 041 | Selection date lies in the past: Data will only be displayed |
| 042 | Customer & has not been created |
| 043 | Assignment of customer & to & is not defined |
| 044 | Sales area (VKORG/VTWEG/SPART) is incomplete |
| 045 | Sales area without customer number is not defined |
| 046 | Specify customer number |
| 047 | Assignment cannot be made: Higher-level customer & does not exist |
| 048 | Assignment of sales areas is not defined (THIOZ) |
| 049 | Assignment cannot be made: Higher-level sales area is incomplete |
| 050 | Valid-from date cannot lie in the past |
| 051 | Validity period is not allowed (From-date lies after the to-date) |
| 052 | The assignment is also active outside of the given time period |
| 053 | The assignment is already active in the given time period |
| 054 | Different higher-level assignments exist outside of the given time period |
| 055 | Incorrect assignments cannot be processed |
| 056 | Select hierarchy node |
| 057 | Assignment not possible: Customer & does not exist |
| 058 | Node & will be assigned to the same level |
| 059 | Select hierarchy header nodes for higher-level assignment |
| 060 | Selected sub-hierarchy contains all nodes and cannot be extended |
| 061 | Nodes cannot be added: unpermitted assignments would occur |
| 062 | Hierarchy contains no allowed alternative higher-level assignments |
| 063 | Higher-level node already maintained as a subordinate node |
| 064 | Assigned node is also a higher-level node |
| 065 | You cannot assign node to itself |
| 066 | Assignment has different attributes outside of the given time period |
| 067 | No authorization for displaying customers |
| 068 | No authorization for maintaining customers |
| 069 | No display authorization for Customer & in Sales area & & & |
| 070 | No maintenance authorization for Customer & in Sales area & & & |
| 071 | Partner determination error: Function not possible |
| 072 | Customer & is not created for Sales area & & & |
| 073 | There are no hierarchy nodes to be displayed |
| 074 | Function not possible: Maximum number of hierarchy steps (26) exceeded |
| 075 | Lowest hierarchy level reached (26): lower steps will be ignored |
| 076 | Hierarchy node cannot be removed as invalid assignments would arise |
| 077 | Selected hierarchy node is a header node: subhierarchy cannot be removed |
| 078 | Select incorrect hierarchy nodes |
| 079 | Pricing and rebate indicators updated |
| 080 | Attributes (pricing, rebate) are up-to-date for all assignments |
| 081 | Date cannot be changed (inconsistent validity periods) |
| 082 | Hierarchy type & is not defined |
| 083 | Node & is not active or not available for selection date |
| 084 | Node & is not available in the hierarchy |
| 085 | Hierarchy level & cannot be transferred due to inconsistencies |
| 086 | Hierarchy level assignment(s) updated |
| 087 | Hierarchy level assignment not updated or not updated for all points |
| 088 | Assignment not allowed: incorrect hierarchy structure assignment |
| 089 | 'Reassigning' can lead to inconsistencies in the hierarchy lvl assignmnt |
| 090 | Initial Date Limit(s): a new validity period has been proposed |
| 091 | Existing assignments for new nodes are being checked. |
| 092 | Node & & & & cannot be allocated, so it has not been selected |
| 093 | Assign. can only be displayed: transportation points & & & & not selected |
| 094 | Processing subtree for nodes & & & & not possible |
| 095 | Processing nodes & & & & not possible because not selected |
| 096 | Selection date is in the past: Please select new date |
| 097 | Error when posting the customer hierarchy data |
| 098 | Please specify selected nodes for node-specific display |
| 099 | No order type or sales organization entered. |
| 100 | Sales document types control |
| 101 | Saving is not necessary: no changes were made |
| 102 | Parameters for Document type & & have been changed |
| 103 | Document type & & created |
| 104 | Error & blocking &: & & |
| 105 | Document & already exists |
| 106 | Item category & changed |
| 107 | Error & changing &: & & |
| 108 | Error & planning &: & & |
| 109 | Error & deleting &: & & |
| 110 | New schedule line categories should begin with 'Z' |
| 111 | Combination not allowed |
| 112 | Item usage 'TEXT' is only allowed for item category group 'Blank' |
| 113 | Table & cannot be blocked |
| 114 | Document type & & deleted |
| 115 | Item category & & deleted |
| 116 | Schedule line category & & deleted |
| 117 | Default indicator for & & & & cannot be reset |
| 118 | The new default item category for & & & is & |
| 119 | The new default schedule line category for & & is & |
| 120 | Default indicator for & & & cannot be reset |
| 121 | The new default item category for & & is & |
| 122 | Deletion unnecessary: no assignments exist |
| 123 | Enter a usage for structure configuration for BOM explosion |
| 124 | Internal error creating assignment table: Item categ & (ret code &) |
| 125 | No changes made to item category assignments |
| 126 | Changed item category assignments saved |
| 127 | Partner group & does not contain any payers who cannot be changed |
| 128 | Entry & & & missing in table & |
| 129 | Item usage must be specified for item category group 'Blank' |
| 130 | Defaults for Item category & & changed |
| 131 | Customer-specific document types should begin with 'Z or Y' |
| 132 | Customer-specific item categories should begin with 'Z or Y' |
| 133 | Item category & already exists |
| 134 | Item category & & has been created |
| 135 | No changes made to the schedule line category assignments |
| 136 | Changes to schedule line category assignments have been saved |
| 137 | System blocking error for Table & |
| 138 | If a storage location is required, a batch check must be carried out |
| 139 | Related tables have not been transferred into the transfer order |
| 140 | The selected table entries have been transferred to correction |
| 141 | A condition type's access sequence in the pricing procedure is incorrect |
| 142 | Enter item category |
| 143 | An assignment for & already exists |
| 144 | Item category & is not allowed as a higher-level item category |
| 145 | Possible entries can only be displayed once the doc.type has been entered |
| 146 | Possible entries can only be displayed if a matl item category exists |
| 147 | Schedule line category & deleted from Table TVEP: please enter it again |
| 148 | Defaults for schedule line category & & changed |
| 149 | Schedule line category & & has been created |
| 150 | Schedule line category & already exists |
| 151 | Availability check without transfer of requirements is not allowed |
| 152 | Only condition types used for 'Pricing' are allowed |
| 153 | The entry & & cannot be deleted |
| 154 | No assignment possible as business data are not allowed |
| 155 | Deactivation not possible as billing plan is assigned |
| 156 | Billing plan only possible if business data active at item |
| 157 | The sales document indicator & is not allowed |
| 158 | Item categories 7, J, T and g are provided for deliveries |
| 159 | The date proposal is not allowed for delivery orders |
| 160 | Enter a condition for the individual items overall |
| 161 | The conditions must be different |
| 162 | Document type & is not allowed as an alternative sales document type |
| 163 | Alternative sales document type & is the same as current document type |
| 164 | No allowed alternative order types could be determined |
| 165 | The system status '&' is not available. |
| 166 | The user status '&' for the diagram '&' is not available. |
| 167 | Please maintain at first with number '&'. |
| 168 | Delivery item numbers could be too big |
| 169 | Enter schedule line category |
| 170 | Country/Region and transportation zone copied from the address data |
| 171 | Address data maintenance only possible in the detail screen |
| 172 | External capacity planning is not allowed for item category &1 |
| 173 | You cannot use special characters, only letters and digits. |
| 174 | Only one default allowed for order type '&1' and sales organization '&2' |
| 200 | Text control |
| 201 | Please select a text object |
| 202 | You can only select one text object |
| 203 | System error occurred reading Internal table ( & ) |
| 204 | The entry already exists |
| 205 | Text determination procedure & has not been specified |
| 206 | Sales document type & does not exist |
| 207 | System error posting an internal table ( & ) |
| 208 | Access sequence & does not exist |
| 209 | Item category & does not exist |
| 210 | Delivery type & does not exist |
| 211 | Billing type & does not exist |
| 212 | Account group & does not exist |
| 213 | Text type & not yet created |
| 214 | The language must be clearly specified |
| 215 | Include & does not exist |
| 216 | No access sequences can be defined for text object '&' |
| 217 | Only text types can be defined for contact persons |
| 218 | No separate text procedures can be defined for text object '&' |
| 219 | Deletion not allowed (text ID & used in procedure &, client &) |
| 220 | Only special text objects are allowed |
| 221 | The language does not come from the partner function AG for MVKE |
| 222 | This combination (&,&) already exists |
| 223 | Language & is not defined |
| 224 | Partner function & not defined |
| 225 | This combination (&,&) is not defined |
| 226 | Access generated |
| 227 | Text determination procedure & already exists |
| 228 | Enter a number for the text determination procedure |
| 229 | Access sequence & already exists |
| 230 | Enter a number for the access sequence |
| 231 | Copying control module & does not exist |
| 232 | Text ID & in Procedure & & does not exist in TTXID |
| 233 | Text determination procedure & does not exist in Table & |
| 234 | Text ID & is already present in the text determination procedure |
| 235 | A unit must be assigned to the time period entered |
| 236 | Please maintain the unit only in the existing time period |
| 237 | Calendar ID and time period cannot be maintained at the same time |
| 238 | Calendar ID and time period cannot be maintained at the same time |
| 239 | The cancellation period can only be assigned a positive value |
| 240 | Deleting not allowed: the entry is being used in another position |
| 241 | There are no pop-up windows for billing document texts |
| 242 | The FORM routine & is not active or not available |
| 243 | 'Last of month' field and calendar ID cannot be maintained at one time |
| 244 | The rule for the contract start date refers to the contract start date |
| 245 | The rule for the contract end date refers to the contract end date |
| 246 | The cancellation base date cannot result from the contract end date |
| 247 | Please process table entry transfer manually |
| 248 | Text type & is not defined for text determination procedure & |
| 249 | No text edit control possible for order type & |
| 250 | Partner control |
| 251 | Please select a partner object |
| 252 | You have selected more than one object: please select only one |
| 253 | System error occurred reading Internal table ( & ) |
| 254 | The entry already exists |
| 255 | Partner determination procedure & does not exist |
| 256 | Sales document type & does not exist |
| 257 | System error posting an internal table ( & ) |
| 258 | Partner determ. procedure & already used in partner object & |
| 259 | Item category & does not exist |
| 260 | Transport into delivery system is only possible using & |
| 261 | Maintaining new partner functions in & is only possible in central functn |
| 262 | Please process table entry transfer manually |
| 263 | Partner function & has not been created |
| 264 | Partner function & cannot be used for partner procedures |
| 265 | Only customer partner functions can be defined as sources |
| 266 | Origin & is not provided for partner type & |
| 267 | Partner function does not exist in the customer partner determtn procdr |
| 268 | Origin & is not permitted for partner function & |
| 269 | Deletion not allowed: Function & is used elsewhere |
| 270 | Partner determination procedure & not defined for customer master |
| 271 | Partner determination procedure & not defined for sales document headers |
| 272 | Partner determination procedure & not defined for sales document items |
| 273 | Partner determination procedure & is not defined for deliveries |
| 274 | Partner determination procedure & not defined for billing header(s) |
| 275 | Partner determination procedure & is not defined for billing items |
| 276 | Partner determination procedure & is not defined for sales activities |
| 277 | Partner determination procedure & is not available for shipments |
| 278 | Shipping type & not yet created |
| 279 | Shipments must have a forwarding agent |
| 280 | Sales documents require a sold-to party that cannot be changed |
| 281 | Sales document items may not have a sold-to party |
| 282 | Deliveries require a ship-to party that cannot be changed |
| 283 | Billing items may not have a payer |
| 284 | A payer which cannot be changed is required for billing documents |
| 285 | 'Ship-To Party' is a mandatory partner function for outbound deliveries |
| 290 | Assignment only makes sense for customer functions |
| 291 | Another partner function has already been converted to & |
| 292 | Function & is not used in Procedure & |
| 293 | Function & is a higher-level function than Function & |
| 294 | Partner function & does not exist |
| 295 | Object & cannot be blocked: It will be displayed |
| 296 | Entries saved |
| 297 | Partner & is not defined |
| 298 | Please maintain the field 'Sequence' |
| 299 | Sort sequences of previously determined partners are inconsistent |
| 300 | Conditions, Pricing |
| 301 | Function & does not exist |
| 302 | Initialization error for View & |
| 303 | Maintenance error for view & |
| 304 | Both groups need to be defined |
| 305 | Procedure & requires two groups |
| 306 | Date function no available for partner type & |
| 307 | You must transport the element to the production system (see long text) |
| 308 | The TADIR-GENFLAG was set successfully for R3TR FUGR 089C |
| 309 | The TADIR-GENFLAG could not be set successfully for R3TR FUGR 089C |
| 310 | Accrual billing document type & does not exist. |
| 311 | Only accrual billing document types w/o cancellation billing type allowed |
| 319 | Number range & is an internal number range |
| 320 | Number range & & is not available. |
| 321 | Number range & & is an external number range. |
| 322 | The most recently used billing date is &. |
| 323 | Every date in the billing due list is less than &. |
| 350 | Copy control, Graphics |
| 351 | Table & is blocked. It can only be displayed. |
| 352 | ABEND due to system error |
| 400 | Incompletion log |
| 401 | Procedure & does not exist |
| 402 | Procedure & already exists |
| 403 | Procedure & saved |
| 404 | Procedure & deleted |
| 405 | Procedure & referred to elsewhere |
| 406 | & |
| 407 | Procedure & is already assigned to item category & |
| 408 | Procedure & is already assigned to Schedule line category & |
| 409 | Procedure & is already assigned to Partner function & |
| 410 | Procedure & already has texts assigned to it |
| 411 | Procedure & is already assigned to Sales document type & |
| 412 | Procedure & will be deleted when you press 'Enter' |
| 413 | Select one object only for processing |
| 414 | Enter an incompletion procedure for editing |
| 415 | Incompletion procedure & is already defined for another object |
| 416 | Enter an incompletion procedure |
| 417 | Incompletion procedure & is not defined for sales document types |
| 418 | Incompletion procedure & is not defined for items |
| 419 | Incompletion procedure & is not defined for schedule lines |
| 420 | Changes will not be saved when you press 'Enter' |
| 421 | Procedure is still being used: Object & cannot be blocked |
| 422 | Procedure is still being used: usages will be deleted |
| 423 | Incompletion procedure & is not defined for sales activities |
| 424 | Status group & does not exist |
| 449 | * 450-499 Direct-Input Cusotmer |
| 450 | Currency & does not exist (TCURC) |
| 451 | Currency & is no longer valid (TCURC) |
| 452 | You do not have authorization for mass changes of currencies |
| 453 | No customer data found for the selection criteria |
| 454 | The new currency must differ from the old currency |
| 455 | The selected customers could not be blocked |
| 456 | Select customers and / or sales organizations |
| 457 | Conversion to currency & successfully completed |
| 458 | There are no data for currency conversion. |
| 459 | There is no master data for currency conversion available. |
| 460 | Currency conversion finished |
| 461 | For non-specified suppliers it is only possible to have an old currency |
| 462 | Supplier & could not be blocked |
| 463 | You can only enter an old currency if the customer is not registered |
| 500 | Route definition/determination |
| 501 | Leg & and leg & are not compatible |
| 502 | Leg & is not defined |
| 503 | Leg & is already part of the route |
| 504 | Leg & already exists |
| 505 | Legs are not compatible - please correct |
| 506 | Warning: Incorrect leg saved in the route |
| 507 | Warning: No shipping conditions exist |
| 508 | Warning: No transportation groups exist |
| 509 | Shipping point & is not defined |
| 510 | Shipping point &2 cannot be used for plant &1 |
| 511 | Office of exit & is not specified |
| 512 | Please process table entry transfer manually |
| 513 | No routes found for the selection specified. |
| 551 | Maintain Table TFRM |
| 552 | Only group numbers up to 99 are allowed for routines in this class |
| 553 | Text module & could not be created |
| 554 | Place the cursor on a valid group number |
| 555 | There is no long text |
| 556 | All routines have been successfully activated |
| 557 | You can only delete deactivated routines |
| 558 | Include number & either does not exist or is not active |
| 559 | You can only make changes in client 0 |
| 560 | You do not have the authorization to create SAP standard routines |
| 561 | TADIR entry could not be created |
| 570 | Choose an entry |
| 590 | Text modules have been changed to document text modules |
| 600 | ******* 500-550 : EDI in SD ****************************************** |
| 601 | New key assignment for partner type & has not been maintained |
| 602 | Enter a customer number |
| 603 | Standard partner function & cannot be deleted |
| 604 | Partner function & is not defined for use in EDI |
| 650 | ************************ Contracts processing *************************** |
| 651 | Maintain either percentage rate or percentage rate table access |
| 652 | Please maintain condition type |
| 653 | Please maintain the baseline date rule for the price increase cycle |
| 654 | Please maintain the price increase cycle |
| 700 | ******************** Product hierarchy 700 - 720 ************************ |
| 701 | The product hierarchy structure has an unallowable number of levels |
| 702 | The template should contain only ' ' or separators other than ' ' |
| 703 | The template is smaller than a possible value entry |
| 704 | Node is followed by spaces: not allowed |
| 705 | Please create the preceding node first |
| 706 | A product hierarchy node cannot contain spaces |
| 707 | The node cannot be inserted |
| 708 | Please delete the succeeding node first |
| 709 | You have created too many levels (a maximum of 9 levels is allowed) |
| 710 | The data element must have the prefix 'PRODH' |
| 711 | The node includes editing mask characters |
| 712 | The mask is too long, layout does not look good |
| 713 | Deletions will be saved immediately to the data bank |
| 714 | The product hierarchy struture length is &, but must be & |
| 715 | Account assignment group &1 does not exist |
| 721 | ************* Scheduled shipping date 721 - 750 ************************* |
| 722 | The function is not possible without a number range |
| 751 | ************* Potential planning 751 - 770 ****************************** |
| 752 | Client & is not a competitor |
| 753 | Please maintain routine POTENTIAL_PROT_SET in program & |
| 754 | Select a valid line |
| 771 | ************* Repairs processing 771-820 ******************************** |
| 772 | You must also enter a procedure for the point in time |
| 773 | A repair indicator can only be assigned once per point in time |
| 774 | Repair indicator &2 is not required at time &1 |
| 775 | Procedure -&1- only possible manually |
| 776 | Manual flag only possible in combination with the report back indicator |
| 800 | No value help supported for this field |
| 801 | Access sequence exists for text & in text determination procedure & |
| 802 | Text edit control does not work for & ! |
| 803 | Pricing date proposal C only needed if contract data are allowed |
| 804 | Valid from date is proposed from the contract data |
| 821 | ****** _Reference det. for consumer master 821 - 850 ****************** |
| 822 | No company code exists for sales area &1 &2 &3 |
| 823 | Problems when executing out dialog boxes |
| 824 | Problems when reading the sales area data |
| 825 | Problems when adding a reference customer to the company code |
| 826 | Problems when reading the customer master data |
| 827 | The reference customer & cannot be a consumer |
| 828 | Company code & does not exist |
| 829 | Company code & does not exist with reference customer & |
| 830 | Problems when reading the sales area data |
| 831 | No reference customer maintained |
| 832 | Reference customer &2 already exists for company code &1 |
| 833 | Enter the sales organization |
| 834 | Enter the distribution channel |
| 835 | Customer &1 for sls org. &2 dist. chnl &3 division &4 not created |
| 836 | Problems deleting the sales area data |
| 837 | Problems deleting the company code data |
| 838 | Reference customer is not current reference customer ->not deleted |
| 839 | Problems inserting the reference customers for the sales area |
| 840 | At least one sales area should be maintained for reference customer & |
| 841 | At least one company code must be maintained for reference customer & |
| 842 | Reference customer & does not exist |
| 843 | Reference customer & deleted |
| 844 | Reference customer & created |
| 845 | A reference customer has been created |
| 847 | Reference customer & will not be deleted |
| 848 | & can not be used as a reference customer |
| 849 | Transaction VOTX is outdated. Use VOTXN instead |
| 860 | Text ID & already exists. Enter a new text ID |
| 861 | Run number & already exists. Enter a new run number |
| 862 | Enter both run number and text ID |
| 863 | First enter a run number and a text ID |
| 864 | Enter a text ID |
| 865 | Enter a run number |
| 870 | Deletion of Material Group &1 is not possible |
| 871 | Deletion of Customer Groups &1 is not possible |
| 872 | Deletion of Sales Districts &1 is not possible |
| 880 | Custom routine & does not exist. Check and try again. |
| 881 | Assign a factory calendar |
| 885 | Duplicate factory calendar source exists. Choose a different source. |
| 890 | ******* 891 - 899 : Number Range Customizing ********************** |
| 891 | Number Range Interval is required! |
| 892 | Number Range Interval with external number assignment not allowed |