| VC070 |
No maintenance authorization for Customer & in Sales area & & & |
| VC071 |
Partner determination error: Function not possible |
| VC072 |
Customer & is not created for Sales area & & & |
| VC073 |
There are no hierarchy nodes to be displayed |
| VC074 |
Function not possible: Maximum number of hierarchy steps (26) exceeded |
| VC075 |
Lowest hierarchy level reached (26): lower steps will be ignored |
| VC076 |
Hierarchy node cannot be removed as invalid assignments would arise |
| VC077 |
Selected hierarchy node is a header node: subhierarchy cannot be removed |
| VC078 |
Select incorrect hierarchy nodes |
| VC079 |
Pricing and rebate indicators updated |
| VC080 |
Attributes (pricing, rebate) are up-to-date for all assignments |
| VC081 |
Date cannot be changed (inconsistent validity periods) |
| VC082 |
Hierarchy type & is not defined |
| VC083 |
Node & is not active or not available for selection date |
| VC084 |
Node & is not available in the hierarchy |
| VC085 |
Hierarchy level & cannot be transferred due to inconsistencies |
| VC086 |
Hierarchy level assignment(s) updated |
| VC087 |
Hierarchy level assignment not updated or not updated for all points |
| VC088 |
Assignment not allowed: incorrect hierarchy structure assignment |
| VC089 |
'Reassigning' can lead to inconsistencies in the hierarchy lvl assignmnt |
| VC090 |
Initial Date Limit(s): a new validity period has been proposed |
| VC091 |
Existing assignments for new nodes are being checked. |
| VC092 |
Node & & & & cannot be allocated, so it has not been selected |
| VC093 |
Assign. can only be displayed: transportation points & & & & not selected |
| VC094 |
Processing subtree for nodes & & & & not possible |
| VC095 |
Processing nodes & & & & not possible because not selected |
| VC096 |
Selection date is in the past: Please select new date |
| VC097 |
Error when posting the customer hierarchy data |
| VC098 |
Please specify selected nodes for node-specific display |
| VC100 |
Sales document types control |
| VC101 |
Saving is not necessary: no changes were made |
| VC102 |
Parameters for Document type & & have been changed |
| VC103 |
Document type & & created |
| VC104 |
Error & blocking &: & & |
| VC105 |
Document & already exists |
| VC106 |
Item category & changed |
| VC107 |
Error & changing &: & & |
| VC108 |
Error & planning &: & & |
| VC109 |
Error & deleting &: & & |
| VC110 |
New schedule line categories should begin with 'Z' |
| VC111 |
Combination not allowed |
| VC112 |
Item usage 'TEXT' is only allowed for item category group 'Blank' |
| VC113 |
Table & cannot be blocked |
| VC114 |
Document type & & deleted |
| VC115 |
Item category & & deleted |
| VC116 |
Schedule line category & & deleted |
| VC117 |
Default indicator for & & & & cannot be reset |
| VC118 |
The new default item category for & & & is & |
| VC119 |
The new default schedule line category for & & is & |
| VC120 |
Default indicator for & & & cannot be reset |
| VC121 |
The new default item category for & & is & |
| VC122 |
Deletion unnecessary: no assignments exist |
| VC123 |
Enter a usage for structure configuration for BOM explosion |
| VC124 |
Internal error creating assignment table: Item categ & (ret code &) |
| VC125 |
No changes made to item category assignments |
| VC126 |
Changed item category assignments saved |
| VC127 |
Partner group & does not contain any payers who cannot be changed |
| VC128 |
Entry & & & missing in table & |
| VC129 |
Item usage must be specified for item category group 'Blank' |
| VC130 |
Defaults for Item category & & changed |
| VC131 |
Customer-specific document types should begin with 'Z or Y' |
| VC132 |
Customer-specific item categories should begin with 'Z or Y' |
| VC133 |
Item category & already exists |
| VC134 |
Item category & & has been created |
| VC135 |
No changes made to the schedule line category assignments |
| VC136 |
Changes to schedule line category assignments have been saved |
| VC137 |
System blocking error for Table & |
| VC138 |
If a storage location is required, a batch check must be carried out |
| VC139 |
Related tables have not been transferred into the transfer order |
| VC140 |
The selected table entries have been transferred to correction |
| VC141 |
A condition type's access sequence in the pricing procedure is incorrect |
| VC142 |
Enter item category |
| VC143 |
An assignment for & already exists |
| VC144 |
Item category & is not allowed as a higher-level item category |
| VC145 |
Possible entries can only be displayed once the doc.type has been entered |
| VC146 |
Possible entries can only be displayed if a matl item category exists |
| VC147 |
Schedule line category & deleted from Table TVEP: please enter it again |
| VC148 |
Defaults for schedule line category & & changed |
| VC149 |
Schedule line category & & has been created |
| VC150 |
Schedule line category & already exists |
| VC151 |
Availability check without transfer of requirements is not allowed |
| VC152 |
Only condition types used for 'Pricing' are allowed |
| VC153 |
The entry & & cannot be deleted |
| VC154 |
No assignment possible as business data are not allowed |
| VC155 |
Deactivation not possible as billing plan is assigned |
| VC156 |
Billing plan only possible if business data active at item |
| VC157 |
The sales document indicator & is not allowed |
| VC158 |
Item categories 7, J, T and g are provided for deliveries |
| VC159 |
The date proposal is not allowed for delivery orders |
| VC160 |
Enter a condition for the individual items overall |
| VC161 |
The conditions must be different |
| VC162 |
Document type & is not allowed as an alternative sales document type |
| VC163 |
Alternative sales document type & is the same as current document type |
| VC164 |
No allowed alternative order types could be determined |
| VC165 |
The system status '&' is not available. |
| VC166 |
The user status '&' for the diagram '&' is not available. |
| VC167 |
Please maintain at first with number '&'. |
| VC168 |
Delivery item numbers could be too big |
| VC169 |
Enter schedule line category |
| VC170 |
Country and transportation zone copied from the address data |