| B1695 |
Error when scheduling the batch job for conversion in system &1 |
| B1697 |
The processs is executed in the background (&1 &2) in system &3 |
| B1698 |
No processing available for object &1 |
| B1699 |
Table &1 is excluded from the conversion |
| B1700 |
***** Messages for XPRA programs ***** |
| B1701 |
The report & was executed successfully. |
| B1702 |
Application: & |
| B1703 |
Database error occurred when reading table &. |
| B1704 |
Database error occurred when writing table &. |
| B1710 |
*** Messages for XPRA RBDXBDLT |
| B1711 |
Class type & does not exist in client & |
| B1712 |
Mo message types were found for the classification object & |
| B1713 |
Application ALE (cross-application), client & |
| B1714 |
& & & & |
| B1715 |
Client &: Validity for the ALE distribution model has been initialized |
| B172 |
Please specify one object ID only |
| B1730 |
***Messages for block processing change pointers |
| B1731 |
Setting the block size of message type & has failed |
| B1732 |
Incorrect status for block processing with message type & |
| B1733 |
Resetting block size for message type & has failed |
| B1750 |
**************** Messages for serialized distribution ********** |
| B1751 |
Serialization group & does not exist |
| B1752 |
Error has occurred scheduling check job |
| B1753 |
Serialization group & is being dispatched |
| B1754 |
IDocs in serialization group & are still in the tRFC queue |
| B1755 |
An error has occurred creating/dispatching the control IDoc |
| B1756 |
& IDoc(s) of message type & have been sent |
| B1757 |
Message type & has not been specififed for serialization group & |
| B1758 |
Message types have not been assigned to the serialization group & |
| B1759 |
Check job has been scheduled for serialization group & for &, & |
| B1760 |
Error has occurred when determining receiver for SERDAT |
| B1761 |
No receiver exists for the group & in the distribution model |
| B1762 |
Inbound processing for serialization group & is not defined |
| B1770 |
** Messages for assigning RFC destinations to logical systems |
| B1771 |
There is already an entry for this key. |
| B1772 |
Please select a logical system |
| B1773 |
User is editing the assignments. (You can only display them). |
| B1774 |
Please select an RFC destination |
| B1775 |
An RFC destination has already been assigned for method &.& |
| B1776 |
Entry & does not exist. Check spelling |
| B1777 |
Error has occurred making remote call to method & in system & |
| B1778 |
Error &3 for the remote call of method &1 in system &2, message &4 |
| B1800 |
**************** API message for receiver determination ***************** |
| B1801 |
There is no filter object type for filter message type & |
| B1802 |
The business object type for message type & does not exist |
| B1803 |
No function module has been assigned to the business object type & |
| B1804 |
Object & with object ID & has not been found |
| B1805 |
Filter object &1 is missing for determining receiver of message type &2 |
| B1806 |
Message type & is dependent on itself |
| B1807 |
Filter object &1 is not valid for the BAPI table parameter &2. |
| B1808 |
Filter object &1 is not valid for BAPI (&2,&3) |
| B1809 |
BAPI (&1, &2) is self-dependent |
| B1810 |
Filter object &1 is missing for determining receiver of BAPI (&1, &2) |
| B1811 |
More than one receiving system has been specified for the BAPI (&1, &2) |
| B1860 |
********** Messages for maintaining hierarchy of BAPI parameters ****** |
| B1861 |
Tables &1 and &2 have no shared field reference. |
| B1862 |
Please position the cursor on one table parameter |
| B1863 |
The hierarchy for the BAPI (&1, &2) already exists. |
| B1864 |
No hierarchy for BAPI (&1, &2) exists. |
| B1865 |
Tables &1 and &2 do not have a shared reference field |
| B1866 |
Table parameter &1 already exists in the hierarchy |
| B1867 |
Hierarchy has been saved. |
| B1868 |
Error has occurred when write-accessing database table TBD19. |
| B1869 |
Hierarchy has been deleted |
| B1870 |
Note: The ALE interface must be regenerated afterwards |
| B1871 |
The hierarchy has not been modified |
| B1872 |
You have not selected field references |
| B1873 |
Parameter & does not have parent parameters |
| B1874 |
You cannot modify the hierarchy. Refer to the long text. |
| B1875 |
Hierarchy has not been created |
| B1876 |
The table parameter & is not available in the BAPI interface. |
| B1877 |
Child parameter &1 is not assigned to parent parameter &2. |
| B1878 |
All the BAPI table parameters in the hierarchy have already been used. |
| B1879 |
Name of external structure too long for function module generation |
| B1880 |
ISO code & is not assigned to a country key |
| B1881 |
Country key & has no ISO code |
| B1882 |
ISO code & is not assigned to a currency key in the valid time period |
| B1883 |
Currency key & does not have an ISO code |
| B1884 |
Unit of measure & has no ISO code |
| B1885 |
Language key & does not have an ISO code |
| B1886 |
ISO code has not been assigned to a language key |
| B1887 |
For the ISO code &1 there is more than one SAP currency code for ALE |
| B1888 |
For the ISO code &1 there is no unique SAP currency code for ALE |
| B1889 |
For the currency code &1 ALE communication is not allowed |
| B1890 |
You must select a node |
| B1891 |
The operation cannot be carried out with this node type |
| B1892 |
Processing not possible - use Transaction SM58 |
| B1893 |
No IDocs could be selected |
| B1894 |
The initialization of the logical system has failed |
| B1895 |
Display of logical system & is not implemented |
| B1896 |
Error communicating with system & |
| B1897 |
No IDoc has been selected |
| B1898 |
Error in namespace prefixes of function; see long text |
| B1899 |
Name of internal structure too long for function module generation |
| B190 |
Please specify a valid value |
| B191 |
The default position taken from T77S0 already exists in T528B |
| B1999 |
& & & & |
| B2001 |
Local logical system is not defined |
| B2002 |
Be careful when changing the logical system (see long text) |
| B2003 |
The logical system is used by another client. |