| VC171 |
Address data maintenance only possible in the detail screen |
| VC172 |
External capacity planning is not allowed for item category &1 |
| VC200 |
Text control |
| VC201 |
Please select a text object |
| VC202 |
You can only select one text object |
| VC203 |
System error occurred reading Internal table ( & ) |
| VC204 |
The entry already exists |
| VC205 |
Text determination procedure & has not been specified |
| VC206 |
Sales document type & does not exist |
| VC207 |
System error posting an internal table ( & ) |
| VC208 |
Access sequence & does not exist |
| VC209 |
Item category & does not exist |
| VC210 |
Delivery type & does not exist |
| VC211 |
Billing type & does not exist |
| VC212 |
Account group & does not exist |
| VC213 |
Text type & not yet created |
| VC214 |
The language must be clearly specified |
| VC215 |
Include & does not exist |
| VC216 |
No access sequences can be defined for text object '&' |
| VC217 |
Only text types can be defined for contact persons |
| VC218 |
No separate text procedures can be defined for text object '&' |
| VC219 |
Deletion not allowed (text ID & used in procedure &, client &) |
| VC220 |
Only special text objects are allowed |
| VC221 |
The language does not come from the partner function AG for MVKE |
| VC222 |
This combination (&,&) already exists |
| VC223 |
Language & is not defined |
| VC224 |
Partner function & not defined |
| VC225 |
This combination (&,&) is not defined |
| VC226 |
Access generated |
| VC227 |
Text determination procedure & already exists |
| VC228 |
Enter a number for the text determination procedure |
| VC229 |
Access sequence & already exists |
| VC230 |
Enter a number for the access sequence |
| VC231 |
Copying control module & does not exist |
| VC232 |
Text ID & in Procedure & & does not exist in TTXID |
| VC233 |
Text determination procedure & does not exist in Table & |
| VC234 |
Text ID & is already present in the text determination procedure |
| VC235 |
A unit must be assigned to the time period entered |
| VC236 |
Please maintain the unit only in the existing time period |
| VC237 |
Calendar ID and time period cannot be maintained at the same time |
| VC238 |
Calendar ID and time period cannot be maintained at the same time |
| VC239 |
The cancellation period can only be assigned a positive value |
| VC240 |
Deleting not allowed: the entry is being used in another position |
| VC241 |
There are no pop-up windows for billing document texts |
| VC242 |
The FORM routine & is not active or not available |
| VC243 |
'Last of month' field and calendar ID cannot be maintained at one time |
| VC244 |
The rule for the contract start date refers to the contract start date |
| VC245 |
The rule for the contract end date refers to the contract end date |
| VC246 |
The cancellation base date cannot result from the contract end date |
| VC247 |
Please process table entry transfer manually |
| VC248 |
Text type & is not defined for text determination procedure & |
| VC249 |
No text edit control possible for order type & |
| VC250 |
Partner control |
| VC251 |
Please select a partner object |
| VC252 |
You have selected more than one object: please select only one |
| VC253 |
System error occurred reading Internal table ( & ) |
| VC254 |
The entry already exists |
| VC255 |
Partner determination procedure & does not exist |
| VC256 |
Sales document type & does not exist |
| VC257 |
System error posting an internal table ( & ) |
| VC258 |
Partner determ. procedure & already used in partner object & |
| VC259 |
Item category & does not exist |
| VC260 |
Transport into delivery system is only possible using & |
| VC261 |
Maintaining new partner functions in & is only possible in central functn |
| VC262 |
Please process table entry transfer manually |
| VC263 |
Partner function & has not been created |
| VC264 |
Partner function & cannot be used for partner procedures |
| VC265 |
Only customer partner functions can be defined as sources |
| VC266 |
Origin & is not provided for partner type & |
| VC267 |
Partner function does not exist in the customer partner determtn procdr |
| VC268 |
Origin & is not permitted for partner function & |
| VC269 |
Deletion not allowed: Function & is used elsewhere |
| VC270 |
Partner determination procedure & not defined for customer master |
| VC271 |
Partner determination procedure & not defined for sales document headers |
| VC272 |
Partner determination procedure & not defined for sales document items |
| VC273 |
Partner determination procedure & is not defined for deliveries |
| VC274 |
Partner determination procedure & not defined for billing header(s) |
| VC275 |
Partner determination procedure & is not defined for billing items |
| VC276 |
Partner determination procedure & is not defined for sales activities |
| VC277 |
Partner determination procedure & is not available for shipments |
| VC278 |
Shipping type & not yet created |
| VC279 |
Shipments must have a forwarding agent |
| VC280 |
Sales documents require a sold-to party that cannot be changed |
| VC281 |
Sales document items may not have a sold-to party |
| VC282 |
Deliveries require a ship-to party that cannot be changed |
| VC283 |
Billing items may not have a payer |
| VC284 |
A payer which cannot be changed is required for billing documents |
| VC285 |
'Ship-To Party' is a mandatory partner function for outbound deliveries |
| VC290 |
Assignment only makes sense for customer functions |
| VC291 |
Another partner function has already been converted to & |
| VC292 |
Function & is not used in Procedure & |
| VC293 |
Function & is a higher-level function than Function & |
| VC294 |
Partner function & does not exist |
| VC295 |
Object & cannot be blocked: It will be displayed |
| VC296 |
Entries saved |
| VC297 |
Partner & is not defined |
| VC298 |
Please maintain the field 'Sequence' |
| VC299 |
Sort sequences of previously determined partners are inconsistent |
| VC2HL_BO001 |
Close current configuration before starting a new configuration |
| VC2HL_BO002 |
Profile not set for material &1 |