| B1437 |
The maintenance transaction & is not defined in own system & |
| B1438 |
No application object type planned for the function module |
| B1439 |
Cross-system checking is active. |
| B144 |
Entries for external object types are not allowed (acc. to table T77EO) |
| B1440 |
Cross-system checking is inactive. |
| B1441 |
There are no inspection results available for the selected line. |
| B1442 |
There are no receiver systems defined in the distribution model |
| B1443 |
Select at least one system. |
| B1444 |
The table for the listing data for message type & is not defined. |
| B1445 |
Distribution-relevant class type for table & is not defined. |
| B1446 |
Class & is not defined for class type &. |
| B1447 |
To display the test results choose 'Edit -> Detail' |
| B1448 |
***** Messages for the conversion pre-production => production ***** |
| B1449 |
Table &: & of & entries in field & converted (client-independent) |
| B145 |
Symbols entered are not allowed |
| B1450 |
Table &: & of & entries in field & converted (client-dependent) |
| B1451 |
The logical system & is already allocated to another system |
| B1452 |
The logical system & is not taken into account in any conversion |
| B1453 |
The logical system name &1 has been converted to name &2 in client &3 |
| B1454 |
The logical system & has not yet been defined |
| B1455 |
The logical system name & already exists |
| B1456 |
The new logical system name & is the same as the old name & |
| B1457 |
Error creating program & |
| B1458 |
Syntax error in program & line & |
| B1459 |
Conversion of logical system name & for name & in client & |
| B146 |
Entries in the field Ext are allowed in * lines 01-12 only |
| B1460 |
***** Messages for ALE Recovery Tool ***** |
| B1461 |
No system selected |
| B1462 |
No documentation is available for object & in language &. |
| B1463 |
Please choose the participating systems first. |
| B1464 |
Please check system settings before starting the process. |
| B1465 |
The processing type of some IDocs has not been defined. |
| B1466 |
IDoc & no longer exists in system &. |
| B1467 |
The process "Determine recovery objects" has been started in system &. |
| B1468 |
System & has been reset to the status on & at &. |
| B1469 |
An error has occurred when checking IDoc dispatch for system &. |
| B147 |
Profile ID 'O' (object-oriented) or 'S' (status-oriented) allowed |
| B1470 |
An error has occurred during message transmission. |
| B1471 |
A tRFC entry with ID && has been deleted in system &. |
| B1472 |
No data could be selected for partner system &. |
| B1473 |
ALE recovery tool converts status |
| B1474 |
No log found |
| B1477 |
Read the online documentation before carrying out the transaction |
| B1478 |
No logical system name has been defined for client & |
| B1479 |
Table &: & of & entries in field & converted (client-dependent) |
| B1480 |
***** Messages for BAPIs <-> ALE generating tool ***** |
| B1481 |
BAPI &.& does not exist in the system |
| B1482 |
Reference type & is not a structure and therefore it is not allowed |
| B1483 |
For the message type & there is no IDoc type & |
| B1484 |
Only some of the objects in the interface have been released |
| B1485 |
The release of the interface has been partly reset |
| B1486 |
The objects in the interface have been released |
| B1487 |
The release of the interface has been reset |
| B1488 |
Reset of data filtering deactivates all filter functions |
| B1489 |
Version &2 of segment &3 released for release &1 |
| B149 |
Color/shape value must be specified |
| B1490 |
Segment & is not a BAPI segment |
| B1491 |
The BAPI does not support packet processing in the current release |
| B1492 |
The ALE outbound interface is incomplete |
| B1493 |
The inbound ALE interface is incomplete |
| B1494 |
Parameter & in the function module has no reference field/structure |
| B1495 |
**** Object & does not belong to the selected category ***** |
| B1496 |
Method & of object & has not yet been released. |
| B1497 |
Process has been cancelled by user |
| B1498 |
You cannot use the tool for dialog method & |
| B1499 |
Message type & is not available in the system |
| B150 |
Line 001 is missing for event & |
| B1500 |
The IDoc interface is not complete for message type & |
| B1501 |
BAPI & has been called successfully |
| B1502 |
No existing function module for object & and method & |
| B1503 |
Message type & already exists in system |
| B1504 |
Packet & is not available in the System |
| B1505 |
Function group & does not exist in system |
| B1506 |
For object & the method & does not exist |
| B1507 |
There is not an ALE interface for object & and method & |
| B1508 |
Function module & does not exist |
| B1509 |
For object & and method & the message type & already exists |
| B151 |
Infotype must be specified |
| B1510 |
syntax error in line & of function module & |
| B1511 |
The BAPI must have a RETURN parameter |
| B1512 |
& does not exist |
| B1513 |
& has been released and cannot be deleted |
| B1514 |
& has been deleted |
| B1515 |
& has been generated |
| B1516 |
The field & of structure & has more than 1000 characters |
| B1517 |
Predecessor & exists |
| B1518 |
& already exists |
| B1519 |
& & |
| B152 |
Function code must be specified |
| B1520 |
& is the current version and has not been generated |
| B1521 |
IDoc type & already exists in packet & |
| B1522 |
Internal syntax error in template &, line & |
| B1523 |
Function module & already exists in group &. |
| B1524 |
& does not exist and has not been deleted |
| B1525 |
Changes in segment & for new definition are not compatible |
| B1526 |
& already exists and has not been generated |
| B1527 |
An error has occurred assigning data (&) |
| B1528 |
& is still being used and has not been deleted |
| B1529 |
& has not been generated. Further processing is not possible |
| B153 |
Infotype & is not allowed for object type & |