VT - Vertriebstabellen
The following messages are stored in message class VT: Vertriebstabellen.
It is part of development package VA0C in software component SD-SLS-GF. This development package consists of objects that can be grouped under "Customizing R/3 sales".
It is part of development package VA0C in software component SD-SLS-GF. This development package consists of objects that can be grouped under "Customizing R/3 sales".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** General messages for sales and distribution tables |
| 001 | Source = A forbids specification of subsequent screen group and panel |
| 002 | Source = & forbids specification of subsequent parameters |
| 003 | Source = & requires specification of subsequent parameters |
| 004 | Source = & allows only saving operations that are not negative |
| 005 | The storage operation '0' allowed for Source=A has been set |
| 006 | Source = & requires a subsequent FCode. Is BLANK allowed? |
| 007 | Source = F requires a FORM routine without subsequent parameters |
| 008 | Source was set on F because only one FORM routine was specified |
| 009 | Source = & not defined |
| 010 | Source = Z requires a storage operation not equal to 0 |
| 011 | Source = & allows only negative storage operations |
| 012 | Please use transaction 'VFBS' to maintain next screen processing |
| 013 | Maintaining this table is currently forbidden |
| 014 | Substitution of serviceable item matl with service product not consistent |
| 015 | For safety reasons deletion is only allowed in a work area |
| 016 | For safety reasons deletion is only allowed in a screen group |
| 017 | Changes were not adopted, because no correction was entered |
| 018 | Billing quantity G or H is not permitted for billing relevant M |
| 020 | In language & the conversion & already exists for & |
| 021 | Sales document type & is not defined |
| 022 | Order type '&' is not defined for sales area <'&','&','&'> |
| 023 | Sales area conversion table has been updated |
| 024 | System error when updating sales areas |
| 099 | Required entry not made |
| 100 | In table & there is no field & |
| 109 | No processing location specified |
| 110 | Only one of the & fields may be filled |
| 111 | Do not make multiple entries for the processing location |
| 112 | The screen in the function module requires the input of a routine |
| 120 | Transaction & code not defined |
| 121 | Screen & does not exist |
| 122 | Menu & not defined in TSTC |
| 130 | Date type &2 already exists in language &1 |
| 160 | The entered number range & does not exist |
| 161 | Internal and external number ranges may not be identical |
| 162 | Number range & not defined for external number assignment |
| 163 | Number range & not defined for internal number assignment |
| 164 | Number range object & does not exist |
| 165 | Functional area is not possible for account assignment category &1 |
| 200 | Transaction type & already exists |
| 269 | Account assignment category & has not been defined |
| 300 | Sales organization & is not defined |
| 301 | Dunning type & not defined in company code & |
| 302 | Table & could not be locked |
| 303 | Copying control module & newly created |
| 304 | Copying control module & successfully created |
| 305 | Copying control module & does not exist |
| 306 | Item category and classification type are defined |
| 307 | End of list screen has been reached |
| 308 | Beginning of list screen has been reached |
| 309 | New table entry generated |
| 310 | Sales document type & is not available |
| 311 | Checking is in process: Entry & & & is missing from TVCPA |
| 312 | Check completed |
| 313 | Delivery type '&' is not available |
| 314 | The text ID & already defined for this text group |
| 315 | Text object & does not have the text ID &. |
| 316 | Text object & not defined |
| 317 | Combination not allowed |
| 318 | Plant is already allocated to company code & |
| 319 | The combination (text object &, text ID &) is not defined |
| 320 | You can only enter one original language |
| 321 | The probability must be between 0 and 100% |
| 322 | A probability of < 100% is only allowed in inquiries and quotations |
| 323 | The combination of ( & , & ) is missing from Table TVKOV |
| 324 | The referenced distribution channel & cannot be converted |
| 325 | Schedule line category & is not defined |
| 326 | Output type & not defined |
| 327 | Distribution channel is proposed |
| 328 | Referenced sales org. & and distribution channel & do not exist |
| 329 | Referenced sales org & and division & do not exist |
| 330 | Referenced division & cannot be changed |
| 331 | Sales organization & does not exist |
| 332 | The reference sales organization & cannot be converted |
| 333 | Plant & is not defined |
| 334 | Please set the print parameters in Customizing |
| 335 | Sales areas are blocked by other users: You can only display them |
| 336 | System error: Blocking unsuccessful, can only be displayed |
| 337 | No addresses maintained up to now |
| 338 | Sales organization & is referenced by sales organiz.& |
| 339 | Distribution channel & is referenced by distribution channel & |
| 340 | Division & is referenced by division & |
| 341 | Distribution channel & is still required as a customer distrib. channel |
| 342 | Division & is still required as a customer division |
| 343 | The customer for inter-company billing missing in SOrg & |
| 344 | Organizational data for inter-company billing missing in plant & |
| 345 | SOrg belongs to CCode & and the plant to CCode & |
| 346 | Sales organization & is still required for conversion |
| 347 | Sales organization & is still used for division conversion |
| 348 | Sales organization & is still used for distribution channel conversion |
| 349 | Sales organization & is used for sales area conversion |
| 350 | Partner function & does not exist |
| 351 | Enter either a sales document or billing type only |
| 352 | The sales org. is part of company code &, plant & is part of comp.code & |
| 353 | The combination ( & , & ) is missing in TVKOS |
| 354 | Only enter an order type for assembly types '2' or '3' |
| 355 | Component avail.check/dialog control only allowed for assembly processing |
| 356 | Order type $ is not defined |
| 357 | If necessary, enter a configuration strategy |
| 358 | A configuration strategy is not necessary when |
| 359 | Configuration strategy & is not defined in Table 476 |
| 360 | Manual application/alternative is only allowed for struct.scope = A/B |
| 361 | Order type $ contains category $ which is not allowed |
| 362 | Order type $ has external number assignment |
| 363 | Assembly requires assignment category E or D or valuated special stock |
| 364 | Control for type matching is only allowed if scope of structure = D |
| 365 | Avail.and action f.configur.mats.only poss. when type matching is active |
| 366 | You need to enter an order type for assembly types '2' and '3' |
| 367 | Enter either an assembly type or order change management only |
| 368 | Sub-items for manual strategy are not supported |
| 369 | Account assignment category & has not been defined |
| 370 | In autom. single-segment planning, the transfer of requir. must be active |
| 371 | Autom. individual requ. planning requires an account assignment category |
| 372 | Account assignment category & does not result in make-to-order production |
| 373 | Assembly type '2' does not allow unit or product costing |
| 374 | Switching to assembly type &1 is not valid |
| 375 | Issue of a warning is not supported for product selection |
| 376 | The development class of condition table & & is local |
| 377 | Automatic calculation only possible if calculation is allowed |
| 378 | Automatic calculation only possible with a calculation variant |
| 379 | Calculation variant is not valid for automatic calculation |
| 380 | Automatic costing is only valid for product costing |
| 381 | The costing variant is not valid for this costing method |
| 382 | Transfer of preliminary costing only permitted for stat. assembly |
| 383 | Variant &2 has not been defined for transaction &1 |
| 384 | Order type &1 is not permitted |
| 385 | If default item cat. activated: Target billing type must be credit memo |
| 386 | If default item category activated: Billing quantity must be E or F |
| 387 | Only special stock with separate valuation can be marked. |
| 388 | Condition type & can only be used once per country/region. |
| 389 | Choose a condition table in the SAP namespace. |
| 400 | The entry has been saved |
| 401 | Check the existing conversion for distribution channel and division |
| 402 | If configuration is copied, you are not permitted to explode BOM |
| 500 | *** Conditions: Control tables *** |
| 501 | Maintain the item data |
| 502 | Maximum number of 999 accesses in module pool & already reached |
| 503 | Condition maintenance for application & has not been defined |
| 504 | Enter a subtotal between 1 and 7 for step & |
| 505 | Condition type & may only be used once |
| 506 | Table & is not defined |
| 507 | Defaults adopted from the Data Dictionary |
| 508 | Table & not defined |
| 509 | Field & not defined |
| 510 | Select a document field for & |
| 511 | Data division (T685&) not defined for usage |
| 512 | The numeric constant entered is longer than the target field |
| 513 | Please do not set a source value for the initial value indicator |
| 514 | System error: Entry & missing from table & |
| 515 | System error: Entry & & & missing from table & |
| 516 | Please use transactions VK01, VK02 or VK03 |
| 517 | All access sequences successfully generated |
| 518 | Activate only between 0.00 and 8.00 |
| 519 | Entry & & & missing in table & |
| 520 | Condition type & not defined |
| 521 | Usage & not defined |
| 522 | Application & not defined |
| 523 | Usage & and application & not defined |
| 524 | There are no access sequences to optimize |
| 525 | Requirement & not defined |
| 526 | Formula & not defined |
| 527 | Condition type & is not defined |
| 528 | Item & is already listed. |
| 529 | Item & & is already listed |
| 530 | Error found in access sequence & |
| 531 | The condition types are being processed: They can only be displayed |
| 532 | Access sequences are being processed: They can only be displayed |
| 533 | Pricing procedures are being processed: They can only be displayed |
| 534 | All access sequences are already active |
| 535 | Unexpected FCODE = & |
| 536 | Referenced by pricing procedure &: Cannot be deleted |
| 537 | Referenced by access sequence &: Cannot be deleted |
| 538 | Referenced by condition type &: Cannot be deleted |
| 539 | Unit of measure & not defined |
| 540 | Please do not enter a unit of measure for a value scale |
| 541 | Access sequence & only reads the pre-step |
| 542 | Cursor not properly positioned on a condition type |
| 543 | There are no access sequences for condition type & |
| 544 | Access sequences defined by the user must begin with Y or Z |
| 545 | Please test with new entries only in module pool 'T' |
| 546 | Condition type & already listed |
| 547 | Initialization error for view & |
| 548 | Maintenance error for view & |
| 549 | Access sequence lies in the customer sector: It can only be displayed |
| 550 | Access sequence & is not defined |
| 551 | Procedure & is not defined |
| 552 | Enter a table |
| 553 | Account key & not defined |
| 554 | System error: Object could not be blocked |
| 555 | Enter a condition type |
| 556 | Access sequence & is within the SAP sector: It can only be displayed |
| 557 | SAP access sequences cannot begin with Y or Z |
| 558 | Please enter a module pool between 'A' and 'M' |
| 559 | Please enter a module pool between 'N' and 'Z'. |
| 560 | Output type & does not require any mail texts |
| 561 | A text already exists for output category &, language & |
| 562 | No text exists in language & for output & |
| 563 | An access sequence is not defined for the header condition |
| 564 | Access sequence & for output & is revoked |
| 565 | Tax determination procedure & does not exist |
| 566 | Do not use scale formulas for subsequent refunds |
| 567 | Output type & requires a message title |
| 568 | Access sequence & lies in the SAP sector. |
| 569 | Access sequence & lies in the customer sector. |
| 570 | Access sequences cannot be changed in the delivery system |
| 571 | Referenced by condition type & in client &: Cannot be deleted |
| 572 | %A No maintenance authorization for usage & application & |
| 573 | %A No display authorization for usage & application & |
| 574 | Enter a unit of measure |
| 575 | Group condition with calculat.type 'B' and grp.cond.routine not defined |
| 576 | Access sequence is not defined for condition category |
| 577 | GrpCndRoutine without rounding diff. not defined for calculation rule & |
| 578 | Calculation type & is not defined for application |
| 579 | Calculation type or scale basis is not defined for condition class |
| 580 | Calculation type or scale basis is not defined for group conditions |
| 581 | Scale basis and calculation type must be identical |
| 582 | Unit of measure & is not defined for scale basis |
| 583 | Billing quantity & is not defined for delivery-related billing |
| 584 | Billing quantity & is not defined for the pro forma invoice |
| 585 | Qty/value pos/neg & not defined for billing type & |
| 586 | Condition update is not defined for condition class & |
| 587 | Condition update is not defined for calculation type & |
| 588 | Data field "Quantity/Value pos/neg" has the value ' ' |
| 589 | '+' or '-' only allowed in connection with completion rule for item cat. |
| 590 | Be careful when using Pricing type & |
| 591 | Condition class & has not been designed for structure condition & |
| 592 | Calculation type & has not been designed for structure condition & |
| 593 | Structure condition & should not be a header condition |
| 594 | Group condition routines not designed for structure condition & |
| 595 | You cannot change values manually for structure condition & |
| 596 | Structure condition & does not have an access sequence |
| 597 | Structure condition & should not be a group condition |
| 598 | You cannot enter & manually for structure condition & |
| 599 | Cumulation condition & should be a statistical value |
| 600 | Sales function & & & not defined |
| 601 | Condition type & should be assigned to calculation type 36 |
| 602 | Structure condition & should be a group condition |
| 603 | Condition category & only valid for condition class & |
| 604 | Condition category & has not been desigend for structure condition & |
| 605 | You cannot specify a pricing procedure for condition category & |
| 606 | The Field From &1 must be smaller than the current level number &2 |
| 607 | The field To &1 must be smaller than the current level number &2 |
| 608 | For milestone billing, the system only allows pricing types D, G and K |
| 609 | You should use the counter only for manual item conditions |
| 610 | Condition category & is not valid for condition class & |
| 611 | Unfavorable sequence of fields - Possible performance problems |
| 612 | Exclusion group & does not only contain group conditions |
| 613 | Inv. corr. requests with sls doc. cat. K must have pricing det. type 'E' |
| 614 | During inv. correction requests, second item must be a debit memo item |
| 615 | An invoice correction request must be created with ref. to an invoice |
| 616 | Rounding difference is always settled for group cond. w/o grp key rout. |
| 617 | Inv. corr. requests with sls doc cat L must have pricing det. type 'F' |
| 618 | During inv. correction requests, first item must be a credit memo item |
| 619 | Only characteristic ' ' and G can be used as price source |
| 620 | Quantity/value pos/neg field must be ' ' for credit memos to billing docs |
| 621 | The assignment and reference number fields must be ' ' or E |
| 622 | Scale type 'D' cannot be used for group condition 'X' |
| 623 | The system selects several records because they have the same evaluation |
| 624 | Enter a priority for the field marked as free |
| 625 | The same evaluation is not possible for accesses for volume-based rebates |
| 626 | For rebates, each field must be relevant to the access |
| 627 | A release block is not possible for condition class & |
| 628 | Access type C is not defined for key fields |
| 629 | Standard proposal for CTyp &1 Req = &2, Calfor = &3 Basfor = &4 |
| 630 | Standard proposal for CTyp &1, Manu = X Subtot = &2, Req =&3 Calfor =&4 |
| 631 | Standard proposal for CTyp &1 stat = X, Subtot = &2 Req = &3, Basfor=&4 |
| 632 | Standard proposal for CTyp &1 Mand = X Req = &2 Basfor = &3 AccKey = &4 |
| 633 | Standard proposal for CTyp &1, Stat = X Req = &2 Acckey = &3 |
| 634 | Determined values can only be transmitted in & |
| 635 | Pricing type & is not defined in application & |
| 636 | Enter calculation type (condition type has calc. type &2, period &3) |
| 637 | Enter calculation type (condition type has calculation type &2) |
| 638 | Maintain separate max. values for accruals (cond. type &1, calc. type A) |
| 639 | Calculation type not allowed (valid values &2 and A) |
| 640 | This function is not supported in maintaining access sequences |
| 641 | Access sequence is still being used in procedure '&' ! |
| 642 | Procedure '&' is not set up for text object '&' |
| 643 | You cannot choose 'Display' and 'Mandatory text' for the same text |
| 644 | The function has terminated |
| 645 | The system does not save the data |
| 646 | Table & is blocked by user &: Display only |
| 647 | Processing status & does not exist |
| 648 | Update document flow for quantity-related completion |
| 649 | Enter a valid name for the procedure |
| 650 | Different calculation type not allowed (cond. type &1 has calc.type &2) |
| 651 | Different calculation type not allowed (cond. type &1 has calc.type &2) |
| 652 | Period calculation rule &1 not supported for this application |
| 653 | Scale base type &1 not supported for this application |
| 654 | Choose a condition exclusion procedure |
| 655 | Maintain both condition exclusion groups |
| 656 | Maintain two different condition exclusion groups |
| 657 | Only fill one cond. exclusion group with this cond. exclusion procedure |
| 658 | Fill condition exclusion group 1 |
| 659 | Hierarchical access combined with customer hierarchies not possible |
| 660 | Access sequence &1 inconsistent; target field &3 missing in access &2 |
| 661 | Hierarchical access combined with target field &3 not possible |
| 662 | Internal error &2 when saving access sequence &1 (see long text) |
| 663 | Do you want access to table field &1 with the initial direct value? |
| 664 | Access sequence A not possible (access sequence &1, access &2, field &3) |
| 665 | Pricing for condition type &1, access sequence &2 not possible |
| 666 | You are not authorized to execute the report |
| 667 | Access sequence does not exist (check your entries) |
| 668 | Error updating table T682V |
| 669 | A total of &1 records were updated |
| 670 | Could not calculate group conditions using CPF |
| 671 | Calculation type "T" cannot be used with CPF |
| 672 | Counter greater 99 is not supported |
| 673 | Access number greater 999 is not supported. |
| 676 | Access type A is not available (access sequence &1, access &2) |
| 677 | Multi-value attributes are not supported |
| 678 | Data determination in the access is not supported: Condition &1 |
| 679 | Combination of group logic and price elements is not supported |
| 680 | Combination of group logic and scale information not supported |
| 681 | Scale information only supported for requested price result |
| 682 | Condition category 'T': use only without optimized inventory management |
| 683 | Condition class & is not defined for application |
| 684 | Settings for group condition are not identical for appl. V and TX for &1. |
| 685 | You cannot select 'Relevant for Account Determination'. |
| 700 | The use of partners is not allowed for output not dependent on partners |
| 800 | Group is used in sales documents, so the sold-to party cannot be changed |
| 801 | Group is used in deliveries, so the ship-to party cannot be changed |
| 802 | Group is used in billing, so the payer cannot be changed |
| 803 | Partner grp & doesn't contain any sold-to parties which can't be changed |
| 804 | Partner grp & doesn't contain any ship-to parties which can't be changed |
| 805 | Partner group & does not contain any payers which cannot be changed |
| 806 | The cost center is not defined |
| 807 | Maintain in Customizing SD: Functions: Partner Determination (TCODE VOPA) |
| 808 | Function module ZZ_SD_USEREXIT_PARTNER does not exist |
| 809 | Account assignment category & is invalid |
| 810 | Cost center &1 does not belong to company code &2 |
| 811 | The flag Extend Data must not be selected |
| 812 | Acc. assignment category &1 only allowed for valuated sales order stock |
| 813 | Account assignmt cat. &1 is not permitted for evaluated sales order stock |
| 814 | The pricing procedure for account determination must be empty. |
| 815 | No errors were found in Customizing. |
| 816 | Billing quantity 'F' must be used for item category billing relevance 'F' |
| 817 | For delivery-related billing, the field 'Quantity pos/neg' must be '+'. |
| 818 | If access sequence not available, scale type 'D' not possible. |
| 819 | A maximum of 99 condition supplements are permitted in pricing procedure. |
| 820 | Calculation type reference cond. type not equal to calc. type cond. type |
| 821 | Final Settlement and Correction flds must be maint. in rebate settlement |
| 822 | Relevant billing type for final settlement must be: Final settlement='A' |
| 823 | Relevant billing type for final settlement must be: Rel. to rebate ='X' |
| 824 | Canc. of billing type for final settlement must be: Rel. to rebate ='X' |
| 825 | Relevant billing type for correctin must be: Relevant to rebate ='B' |
| 826 | Relevant billing type for correction must be: Relevant to rebate ='X' |
| 827 | Canc. of billing type for correction must be: Relevant to rebate ='X' |
| 828 | Relevant billing type for partial settlement must be: Rel.to rebate = 'C' |
| 829 | Relevant billing type for partial settlement must be: Rel.to rebate = 'X' |
| 830 | Canc. of billing type for partial settlement must be: Rel.to rebate = 'X' |
| 831 | Relevant billing type for manual accrual must be: Rel. to rebate ='D' |
| 832 | Relevant billing type for manual accrual must be: Rel. to rebate ='X' |
| 833 | Canc.of bill.type for man.accr.sal.ord.type must be: Rel. to rebate ='X' |
| 834 | Calculation rule &1 is only permitted for condition class &2 |
| 840 | Enter account key starting with a Z |
| 841 | Enter condition key starting with a Z |
| 850 | Specify reason for rejection |