B2 - Nachrichten der ALE-Basis-Tools
The following messages are stored in message class B2: Nachrichten der ALE-Basis-Tools.
It is part of development package SALE2 in software component BC-MID-ALE. This development package consists of objects that can be grouped under "Application Link Enabling/ Basis Tools".
It is part of development package SALE2 in software component BC-MID-ALE. This development package consists of objects that can be grouped under "Application Link Enabling/ Basis Tools".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Dedicated logical system is not defined. |
| 01 | Object type & is not allowed |
| 002 | Be careful when changing the logical system (see long text) |
| 02 | Relationship type & is not allowed |
| 003 | The logical system is used by another client. |
| 03 | Relationship & is not allowed |
| 004 | Caution: logical systems of target and source clients are identical |
| 04 | Instead of "&", please specify an allowed time unit ->F1 |
| 005 | The logical system name & has been used by client & |
| 006 | The new logical system name & is assigned to the current client & |
| 007 | Cannot use &1 character |
| 009 | ****** TRANSID ********************************************************** |
| 010 | &1 suitable transaction IDs have been found in the tRFC queue |
| 011 | No workflow event has been triggered |
| 012 | No event triggered because the threshold value has not been reached |
| 019 | ************************************************************************* |
| 020 | ** Messages for Transactions BDLSM and BDLST ** |
| 021 | The conversion matrix can only be edited in system &. |
| 022 | The table entries were deleted |
| 023 | No relevant data was determined in system &1. |
| 024 | First select lines. |
| 025 | Conversion process still running. No changes to matrix allowed. |
| 026 | Transport log of conversion matrix for ALE Basis Customizing data |
| 027 | The matrix is defined for system &1, and this is system &2. |
| 028 | The data was imported incorrectly into system &1 and was deleted. |
| 029 | No conversion matrix was found for this system &1. |
| 030 | No model view &1 was found in system &2. |
| 031 | Imported data is consistent in system &. Start conversion. |
| 032 | Warnings for imported data. Conversion can be started. |
| 033 | The matrix is defined for system &1, and the target system is &2. |
| 034 | The data was not distributed into system &1. |
| 035 | The existing conversion matrix in system &1 was deleted. |
| 036 | The conversion matrix was inserted into system &1. The data is consistent |
| 037 | The conversion matrix was inserted in system &1 with warnings. |
| 038 | Save changes to data first. |
| 039 | Database error when entering in the table &1 |
| 040 | Distribution of the conversion matrix for system &1 |
| 041 | Database error when deleting from table &1. |
| 042 | A conversion matrix already exists for the system &1 |
| 043 | No log found for conversion from &1 to &2 |
| 044 | No program &1 and no form routine &2 was found in the system. |
| 045 | - Check data imported into client &1 under key &2 |
| 046 | Client &1 not yet defined |
| 047 | This function is not possible; an upgrade is running |
| 050 | Change pointer ID already exists. |
| 50 | Please enter an editing type |
| 51 | Please specify one editing type only |
| 52 | No entry in table & for & & & |
| 53 | & & & has not changed |
| 54 | & & & has been saved |
| 055 | ** Messages for transaction BDCCC ** |
| 55 | & & & already exists |
| 56 | Please complete & |
| 057 | System ID &1, client &2, logical system &3 |
| 57 | & & was saved |
| 058 | Not uniquely defined message types in the distribution model. |
| 059 | Not uniquely defined BAPIs in the distribution model. |
| 060 | No partner profile (LS) for message types |
| 60 | If you press ENTER, & & & will be deleted |
| 061 | No partner profile (LS) for BAPIs |
| 61 | & & & has been deleted |
| 062 | No RFC destination for synchronous BAPIs |
| 063 | Messages in partner profiles (LS), not in distribution model |
| 064 | BAPIs in partner profiles (LS), not in distribution model |
| 065 | BAPIs in synchronous call, not in distribution model |
| 068 | Data is consistent. |
| 069 | The outbound port &1 does not exist for the partner &2. |
| 070 | The RFC destination &1 does not exist for the partner &2. |
| 70 | Please specify cluster and request code |
| 071 | The RFC destination &1 for the partner system &2 exists (&3). |
| 072 | Different outbound port &1 for partner &2 (&3) |
| 074 | Logical system defined differently in partner system |
| 075 | Message type &1 exists in the model view &2. |
| 076 | Method &1.&2 exists in model view &3. |
| 077 | To partner &2 with message type &1 |
| 078 | From partner &2 with message type &1 |
| 079 | To partner &4 with method &1.&2 (message type &3) |
| 080 | From partner &4 with method &1.&2 (message type &3) |
| 081 | To partner &3 with method &1.&2 |
| 082 | No detailed information exists. |
| 083 | Execute the conversion step. |
| 084 | Conversion logs exist for &1 |
| 99 | Caution! SAP no longer supports table T77WS. Please take T77WT |
| 100 | Maintenance for object & is locked in system &; maintenance system & |
| 101 | ALE module & is not available |
| 102 | ALE distribution model is not active |
| 110 | Logical system name &2 does not match SAP's recommendation |
| 200 | -->> Extended Consistency Check Messages |
| 201 | Release information of segment does not match |
| 202 | Release details of segment match |
| 203 | Number of fields matches |
| 204 | Number of fields does not match |
| 205 | Export length matches |
| 206 | Export length does not match |
| 207 | Incorrect field or field missing in position &1 |
| 208 | Field &1 has incorrect position (&2 not &3) |
| 209 | Last segment definitions do not match |
| 210 | The export lengths of field &1 do not match |
| 211 | Data elements of field &1 do not match |
| 212 | Could not read remote IDoc type &1 |
| 213 | The release details of the IDoc type do not match |
| 214 | Could not read segment &1 of IDoc type &2 remotely |
| 215 | Remote system &1 has a different release level |
| 216 | Hierarchy details of segments do not match |
| 217 | Number of segment retries does not match |
| 218 | Mandatory flag is different: &1, remote &2 |
| 219 | The hierarchy level is different, local &1, remote &2 |
| 220 | Group ID is different &1, remote &2 |
| 221 | Number of group retries does not match |
| 222 | Message &2 returned by connection test to system &1 |