| /SAPCND/CUSTOMIZING106 | 
							Customizing cache &1 does not contain entries for &2 &3 &4 | 
					
					
							| /SAPCND/CUSTOMIZING126 | 
							Unable to find Include statement for &1 | 
					
					
							| /SAPCND/CUSTOMIZING200 | 
							** Customizing class ** [200-399] | 
					
					
							| /SAPCND/CUSTOMIZING201 | 
							Activation for appl. & view & and table & was successful | 
					
					
							| /SAPCND/CUSTOMIZING202 | 
							Activation for appl. & usage & and table & failed | 
					
					
							| /SAPCND/CUSTOMIZING203 | 
							Active and inactive versions are identical | 
					
					
							| /SAPCND/CUSTOMIZING204 | 
							Conversion of object contents to XMML failed | 
					
					
							| /SAPCND/CUSTOMIZING205 | 
							Conversion of object contents to XMML failed | 
					
					
							| /SAPCND/CUSTOMIZING206 | 
							Runtime error: XSL transformation was interrupted | 
					
					
							| /SAPCND/CUSTOMIZING208 | 
							Delete operation for table &1 failed | 
					
					
							| /SAPCND/CUSTOMIZING209 | 
							Appl. & usage & and table &: Inactive version is inconsistent | 
					
					
							| /SAPCND/CUSTOMIZING210 | 
							There is no active version for XML conversion available | 
					
					
							| /SAPCND/CUSTOMIZING211 | 
							The processed XML document is initial | 
					
					
							| /SAPCND/CUSTOMIZING212 | 
							Generation for application &, Usage & and table & failed | 
					
					
							| /SAPCND/CUSTOMIZING213 | 
							Parameter for XML conversion contains errors | 
					
					
							| /SAPCND/CUSTOMIZING214 | 
							The inactive version was deleted successfully | 
					
					
							| /SAPCND/CUSTOMIZING215 | 
							The inactive vesion could not be deleted | 
					
					
							| /SAPCND/CUSTOMIZING216 | 
							No generation since active and inactive version of &1 &2 &3 identical | 
					
					
							| /SAPCND/CUSTOMIZING400 | 
							** Field catalog maintenance ** 400-499 | 
					
					
							| /SAPCND/CUSTOMIZING401 | 
							Complete all fields available for input | 
					
					
							| /SAPCND/CUSTOMIZING402 | 
							There is already an entry & &. Make a new entry. | 
					
					
							| /SAPCND/CUSTOMIZING403 | 
							Entry is in SAP name space. | 
					
					
							| /SAPCND/CUSTOMIZING404 | 
							Entry is in customer name space. | 
					
					
							| /SAPCND/CUSTOMIZING405 | 
							Entry & is already marked for deletion. | 
					
					
							| /SAPCND/CUSTOMIZING406 | 
							This function is not (yet) supported. | 
					
					
							| /SAPCND/CUSTOMIZING407 | 
							No data was changed. | 
					
					
							| /SAPCND/CUSTOMIZING408 | 
							Data was saved | 
					
					
							| /SAPCND/CUSTOMIZING409 | 
							Entry & & already exists in super application &. | 
					
					
							| /SAPCND/CUSTOMIZING410 | 
							Entry & already exists. Make a new entry. | 
					
					
							| /SAPCND/CUSTOMIZING411 | 
							Condition table & already exists for field &. | 
					
					
							| /SAPCND/CUSTOMIZING412 | 
							Field & is already used in access sequence &. | 
					
					
							| /SAPCND/CUSTOMIZING413 | 
							& condition tables already exist for field &. | 
					
					
							| /SAPCND/CUSTOMIZING414 | 
							Field & is already used in & access sequences. | 
					
					
							| /SAPCND/CUSTOMIZING415 | 
							Data element & is still used for field &. | 
					
					
							| /SAPCND/CUSTOMIZING416 | 
							Data element & is still used for & fields. | 
					
					
							| /SAPCND/CUSTOMIZING417 | 
							Related objects have been generated. | 
					
					
							| /SAPCND/CUSTOMIZING418 | 
							Start of function: &1 (&2 &3 &4) | 
					
					
							| /SAPCND/CUSTOMIZING419 | 
							End of function: &1 (&2 &3 &4) | 
					
					
							| /SAPCND/CUSTOMIZING420 | 
							Field & entered in table &. | 
					
					
							| /SAPCND/CUSTOMIZING421 | 
							Field & deleted from table &. | 
					
					
							| /SAPCND/CUSTOMIZING422 | 
							Relationship &/& entered in table &. | 
					
					
							| /SAPCND/CUSTOMIZING423 | 
							Relationship &/& deleted from table &. | 
					
					
							| /SAPCND/CUSTOMIZING424 | 
							Relationship &/& entered in table &. | 
					
					
							| /SAPCND/CUSTOMIZING425 | 
							Relationship &/& deleted from table &. | 
					
					
							| /SAPCND/CUSTOMIZING426 | 
							Transaction '&' cannot be processed. | 
					
					
							| /SAPCND/CUSTOMIZING427 | 
							Data element & entered in table &. | 
					
					
							| /SAPCND/CUSTOMIZING428 | 
							Data element & deleted from table &. | 
					
					
							| /SAPCND/CUSTOMIZING429 | 
							Combination &3/&4 for "virtual" attribute in rel. &1/&2 not permitted. | 
					
					
							| /SAPCND/CUSTOMIZING430 | 
							You cannot maintain relationships for "virtual" field attribute &. | 
					
					
							| /SAPCND/CUSTOMIZING431 | 
							The following cycle exists: &1&2&3&4 | 
					
					
							| /SAPCND/CUSTOMIZING432 | 
							A cycle is based on the ratio &/&. | 
					
					
							| /SAPCND/CUSTOMIZING433 | 
							Cycle in the data element ratio. | 
					
					
							| /SAPCND/CUSTOMIZING434 | 
							Processing for application & (&). | 
					
					
							| /SAPCND/CUSTOMIZING435 | 
							Save the changed data first. | 
					
					
							| /SAPCND/CUSTOMIZING436 | 
							Internal fields may have a maximum of & digits. | 
					
					
							| /SAPCND/CUSTOMIZING437 | 
							Field & does not exist. | 
					
					
							| /SAPCND/CUSTOMIZING438 | 
							Unreliable categories for subcommunication structure for rel. &1/&2 | 
					
					
							| /SAPCND/CUSTOMIZING439 | 
							Field &1 is still used in &2 ratio(s). | 
					
					
							| /SAPCND/CUSTOMIZING440 | 
							Processing for application & usage & and table &. | 
					
					
							| /SAPCND/CUSTOMIZING441 | 
							Field name &1 contains spaces or special symbols | 
					
					
							| /SAPCND/CUSTOMIZING442 | 
							Field &1 already exists in the global field catalog. | 
					
					
							| /SAPCND/CUSTOMIZING443 | 
							Data element & exceeds maximum field length. | 
					
					
							| /SAPCND/CUSTOMIZING444 | 
							The field & is in SAP namespace! | 
					
					
							| /SAPCND/CUSTOMIZING445 | 
							The field & is in customer namespace! | 
					
					
							| /SAPCND/CUSTOMIZING446 | 
							Data Element &1 does not exist in language &2 | 
					
					
							| /SAPCND/CUSTOMIZING447 | 
							Data Element &1 does not exist in any language | 
					
					
							| /SAPCND/CUSTOMIZING448 | 
							Maintenance of dependency to data element &1 is not permitted | 
					
					
							| /SAPCND/CUSTOMIZING449 | 
							Save new field entries first | 
					
					
							| /SAPCND/CUSTOMIZING450 | 
							The dependency relataionship, &1 is dependent on &2, is not permitted | 
					
					
							| /SAPCND/CUSTOMIZING451 | 
							The dependency relationship, &2 is a dependency of &1, is not permitted | 
					
					
							| /SAPCND/CUSTOMIZING452 | 
							Data element &1 is not active | 
					
					
							| /SAPCND/CUSTOMIZING453 | 
							Relevant table entries were transferred in request/task &1/&2 | 
					
					
							| /SAPCND/CUSTOMIZING454 | 
							Entries cannot be transferred to a transport request | 
					
					
							| /SAPCND/CUSTOMIZING455 | 
							Table entries already exist in request/task &1/&2 | 
					
					
							| /SAPCND/CUSTOMIZING460 | 
							Condition technique field &1 cannot be used as application field | 
					
					
							| /SAPCND/CUSTOMIZING463 | 
							&1 has a dependency on &2 which does not exist in LT_NODE variable | 
					
					
							| /SAPCND/CUSTOMIZING500 | 
							** Generation transaction ** 500-599 | 
					
					
							| /SAPCND/CUSTOMIZING501 | 
							At least one field name for the condition table is initial | 
					
					
							| /SAPCND/CUSTOMIZING502 | 
							At least one explanatory short text for the condition table is initial | 
					
					
							| /SAPCND/CUSTOMIZING503 | 
							Object could not be generated | 
					
					
							| /SAPCND/CUSTOMIZING504 | 
							Condition table was not generated successfully | 
					
					
							| /SAPCND/CUSTOMIZING600 | 
							** Condition table maintenance ** 600-699 | 
					
					
							| /SAPCND/CUSTOMIZING601 | 
							No name can be assigned for a condition table. | 
					
					
							| /SAPCND/CUSTOMIZING602 | 
							Condition table already exists as a generated version | 
					
					
							| /SAPCND/CUSTOMIZING603 | 
							Enter a table name | 
					
					
							| /SAPCND/CUSTOMIZING604 | 
							No field chosen | 
					
					
							| /SAPCND/CUSTOMIZING605 | 
							Condition table saved | 
					
					
							| /SAPCND/CUSTOMIZING606 | 
							Maintain a table description | 
					
					
							| /SAPCND/CUSTOMIZING607 | 
							This condition table is not available | 
					
					
							| /SAPCND/CUSTOMIZING608 | 
							Condition table cannot be deleted | 
					
					
							| /SAPCND/CUSTOMIZING609 | 
							An error occured when saving, all entries are taken back | 
					
					
							| /SAPCND/CUSTOMIZING610 | 
							&1 not possible | 
					
					
							| /SAPCND/CUSTOMIZING611 | 
							Cannot save as included in an access sequence | 
					
					
							| /SAPCND/CUSTOMIZING612 | 
							Processing for application &1, usage &2 and table &3 (&). | 
					
					
							| /SAPCND/CUSTOMIZING613 | 
							Condition table &1 entered in &2 | 
					
					
							| /SAPCND/CUSTOMIZING614 | 
							Condition table &1 deleted from &2 | 
					
					
							| /SAPCND/CUSTOMIZING615 | 
							Short description from &1 entered in &2 | 
					
					
							| /SAPCND/CUSTOMIZING616 | 
							Short description from &1 deleted from &2 | 
					
					
							| /SAPCND/CUSTOMIZING617 | 
							Fields from &1 entered in &2 | 
					
					
							| /SAPCND/CUSTOMIZING618 | 
							Fields from &1 deleted from &2 |