| B1530 |
* Messages for the program generating coding for mapping and conversion |
| B1531 |
The structure & could not be read |
| B1532 |
Currency amount passed with more than & digits after decimal point |
| B1533 |
The field & has already been assigned to the SAP code |
| B1534 |
The input field has an incorrect domain or an incorrect data type |
| B1535 |
Function module & already exists |
| B1536 |
Currency amount & & in field & could not be converted |
| B1537 |
& initial v., currency amount & in & was transferred without a currency |
| B1538 |
BAPI field contains SAP code. You cannot enter a value. |
| B1539 |
No ISO code found for the country key & in the field & |
| B154 |
Relationship & is not allowed between object types & and & ->F1 |
| B1540 |
No ISO code found for the currency key & in field & |
| B1541 |
No ISO code found for the quantity unit & in field & |
| B1542 |
No ISO code found for the language key & in field & |
| B1543 |
SAP code: Please assign ISO code field on the detail screen |
| B1544 |
Currency amount: Assign currency fields/parameters on the detail screen |
| B1545 |
Function module & has been created |
| B1546 |
No country key found for the ISO code & in field & |
| B1547 |
No currency key found for ISO code & in field & |
| B1548 |
No unit of measure found for ISO code & in field & |
| B1549 |
No language key found for ISO code & in field & |
| B155 |
Please enter an external object type |
| B1550 |
An RFC destination could not be specified for the logical system & |
| B1551 |
No internal key found for the PSP element & in field & |
| B1552 |
No external key found for the PSP element & in field & |
| B1553 |
No internal key found for project definition & in field & |
| B1554 |
No external key found for project definition & in field & |
| B1555 |
No RFC destination could be determined for the method call. |
| B156 |
Please enter a valid type for the related object |
| B1560 |
Get details from previous status records with status & |
| B1561 |
Cannot process IDocs with syntax errors |
| B157 |
Please enter a valid relationship |
| B160 |
Please specify program and editing routine |
| B1600 |
***** Messages for CPIC communication to R/2 ***** |
| B1601 |
RFC destination & for port & is not available |
| B1602 |
No STIMEX received, for details refer to R/2 system log or R/2 EDI log |
| B1603 |
No acknowledgement received, details: R/2 system log or R/2 EDI log |
| B1604 |
No connection to SAP gateway (TXCOM dest. &); for details, SAP system log |
| B1605 |
No connection to R/2 (TXCOM dest. &); for details, see SAP system log |
| B1606 |
Connection terminated (TXCOM dest. &); details, see R/2 or SAP system log |
| B1607 |
R/2 reports incorrect transfer, automatic repetition |
| B1608 |
R/2 rejects logon, for details refer to R/2 system log |
| B1609 |
Local error in R/2, error code returned: & |
| B1610 |
RFC destination &: Parameter & is not maintained |
| B1611 |
Segment type &, version &: No segment name found |
| B1620 |
***** Messages for CCMS Monitoring ***** |
| B1621 |
There are no suitable transaction IDs |
| B1622 |
Internal error in & code &, action could not be carried out. |
| B1623 |
Status & and direction & are not compatible |
| B1624 |
& TIDs found for this monitoring object but threshold value is & |
| B1625 |
Select a work area also |
| B1626 |
& IDocs for this monitoring object found but threshold value is & |
| B1627 |
Dependent entries in the detail table have also been deleted |
| B1628 |
Monitoring object & does not yet exist or has not been specified |
| B1629 |
Monitor object for determining key figure via IDocs of specified criteria |
| B1630 |
& open change pntrs found for this monitor object - threshold value is & |
| B1631 |
Number of IDocs for the defined selection criteria |
| B1632 |
Number of open change pointers using the defined selection criteria |
| B1633 |
Values <> 0 require a complex selection (see long text) |
| B1634 |
Collective nodes for ALE monitoring objects of logical system |
| B1635 |
Number of IDocs change pointers IDocs with the defined selection criteria |
| B1636 |
Number of tRFC calls to IDocs with the defined selection criteria |
| B1638 |
ALE CCMS Monitor: & IDocs in tRFC queue but threshold value is & |
| B1639 |
Problem with CCMS runtime monitoring: function & |
| B1650 |
***** _Messages for Modelling ***** |
| B1651 |
Filter object type & is not valid |
| B1652 |
Reference to message type & for filter object type & is not valid |
| B1653 |
Reference to method & for filter object type & is not valid |
| B1654 |
Reference to message type & is not valid |
| B1655 |
Distribution using classes is not allowed |
| B1656 |
System & occurs as the target system several times |
| B1660 |
***** Messages for the Conversion of Logical System Names ***** |
| B1661 |
Log for test run: &1 -> &2 in system &3 (initiator &4) |
| B1662 |
Log for conversion: &1 -> &2 in system &3 (initiator &4) |
| B1663 |
Maintain another subroutine for program &1 |
| B1664 |
Table buffer in server synchronized after conversion |
| B1665 |
Data inconsistency when running program &1, form routine &2 |
| B1666 |
Converting the logical system name & to the name & |
| B1667 |
A Process is Running for Test Run &1 -> &2 |
| B1668 |
Another Process is Running for Conversion &1 -> &2 |
| B1675 |
No authorization for navigation |
| B1676 |
RFC destination &1 cannot be accessed under the name &2 |
| B1677 |
RFC destination &1 currently not accessible |
| B1678 |
Select a valid node |
| B1679 |
Conversion can only be started after the test run |
| B1680 |
The functions are not available in system &1 |
| B1681 |
The logical system name & has been used by client & |
| B1682 |
The new logical system name & is assigned to the current client & |
| B1683 |
Existence check can only be activated for the test run |
| B1684 |
Synchronize table buffer in server & after the conversion |
| B1685 |
Table &1 not selected for conversion |
| B1686 |
Field &1 in table &2 already contains the name &3 |
| B1687 |
Error in field &1 of table &2. Manual correction required. |
| B1688 |
An Error has Occurred in Program &1 |
| B1689 |
Table &1 was not relevant for conversion |
| B1690 |
&1 Entry/Entries in Field &2 of Table &3 Have Been Converted |
| B1691 |
&1 entry/ies in field &2 of table &3 are for conversion |
| B1692 |
New entry &1 has been entered in field &2 of table &3 |
| B1693 |
New entry &1 has been entered in field &2 of table &3 |
| B1694 |
Partner profile for &1 &2 &3 has been deactivated |