SAP ABAP Message Class B2 (ALE Basis tools messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SALE2 (Package) Application Link Enabling/ Basis Tools
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SALE2 (Package) Application Link Enabling/ Basis Tools
Attributes
Message class | B2 | |
Short Description | ALE Basis tools messages | |
Changed On | 20140121 | |
Last Changed At | 103712 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Local logical system is not defined | Space: object requires documentation | |
2 | 002 | Be careful when changing the logical system (see long text) | ||
3 | 003 | The logical system is used by another client. | ||
4 | 004 | Caution: logical systems of target and source clients are identical | Space: object requires documentation | |
5 | 005 | The logical system name & has been used by client & | Space: object requires documentation | |
6 | 006 | The new logical system name & is assigned to the current client & | Space: object requires documentation | |
7 | 007 | Cannot use &1 character | Space: object requires documentation | |
8 | 009 | ****** TRANSID ********************************************************** | Space: object requires documentation | |
9 | 01 | Object type & is not allowed | ||
10 | 010 | &1 suitable transaction IDs have been found in the tRFC queue | Space: object requires documentation | |
11 | 011 | No workflow event has been triggered | Space: object requires documentation | |
12 | 012 | No event triggered because the threshold value has not been reached | Space: object requires documentation | |
13 | 019 | ************************************************************************* | Space: object requires documentation | |
14 | 02 | Relationship type & is not allowed | ||
15 | 020 | ** Messages for Transactions BDLSM and BDLST ** | Space: object requires documentation | |
16 | 021 | The conversion matrix can only be edited in system &. | Space: object requires documentation | |
17 | 022 | The table entries were successfully deleted. | Space: object requires documentation | |
18 | 023 | No relevant data was determined in system &1. | Space: object requires documentation | |
19 | 024 | First select lines. | Space: object requires documentation | |
20 | 025 | Conversion process still running. No changes to matrix allowed. | Space: object requires documentation | |
21 | 026 | Transport log of conversion matrix for ALE Basis Customizing data | Space: object requires documentation | |
22 | 027 | The matrix is defined for system &1, and this is system &2. | Space: object requires documentation | |
23 | 028 | The data was imported incorrectly into system &1 and was deleted. | Space: object requires documentation | |
24 | 029 | No conversion matrix was found for this system &1. | Space: object requires documentation | |
25 | 03 | Relationship & is not allowed | ||
26 | 030 | No model view &1 was found in system &2. | Space: object requires documentation | |
27 | 031 | Imported data is consistent in system &. Start conversion. | Space: object requires documentation | |
28 | 032 | Warnings for imported data. Conversion can be started. | Space: object requires documentation | |
29 | 033 | The matrix is defined for system &1, and the target system is &2. | Space: object requires documentation | |
30 | 034 | The data was not distributed into system &1. | Space: object requires documentation | |
31 | 035 | The existing conversion matrix in system &1 was deleted. | Space: object requires documentation | |
32 | 036 | The conversion matrix was inserted into system &1. The data is consistent | Space: object requires documentation | |
33 | 037 | The conversion matrix was inserted in system &1 with warnings. | Space: object requires documentation | |
34 | 038 | Save changes to data first. | Space: object requires documentation | |
35 | 039 | Database error when entering in the table &1 | Space: object requires documentation | |
36 | 04 | Instead of "&", please specify an allowed time unit ->F1 | ||
37 | 040 | Distribution of the conversion matrix for system &1 | Space: object requires documentation | |
38 | 041 | Database error when deleting from table &1. | Space: object requires documentation | |
39 | 042 | A conversion matrix already exists for the system &1 | Space: object requires documentation | |
40 | 043 | No log found for conversion from &1 to &2 | Space: object requires documentation | |
41 | 044 | No program &1 and no form routine &2 was found in the system. | Space: object requires documentation | |
42 | 045 | - Check data imported into client &1 under key &2 | Space: object requires documentation | |
43 | 046 | Client &1 not yet defined | Space: object requires documentation | |
44 | 047 | This function is not possible; an upgrade is running | The short text describes the object sufficiently | |
45 | 050 | Change pointer ID already exists. | Space: object requires documentation | |
46 | 055 | ** Messages for transaction BDCCC ** | Space: object requires documentation | |
47 | 057 | System ID &1, client &2, logical system &3 | Space: object requires documentation | |
48 | 058 | Not uniquely defined message types in the distribution model. | Space: object requires documentation | |
49 | 059 | Not uniquely defined BAPIs in the distribution model. | Space: object requires documentation | |
50 | 060 | No partner profile (LS) for message types | Space: object requires documentation | |
51 | 061 | No partner profile (LS) for BAPIs | Space: object requires documentation | |
52 | 062 | No RFC destination for synchronous BAPIs | Space: object requires documentation | |
53 | 063 | Messages in partner profiles (LS), not in distribution model | The short text describes the object sufficiently | |
54 | 064 | BAPIs in partner profiles (LS), not in distribution model | Space: object requires documentation | |
55 | 065 | BAPIs in synchronous call, not in distribution model | Space: object requires documentation | |
56 | 068 | Data is consistent. | Space: object requires documentation | |
57 | 069 | The outbound port &1 does not exist for the partner &2. | Space: object requires documentation | |
58 | 070 | The RFC destination &1 does not exist for the partner &2. | Space: object requires documentation | |
59 | 071 | The RFC destination &1 for the partner system &2 exists (&3). | Space: object requires documentation | |
60 | 072 | Different outbound port &1 for partner &2 (&3) | Space: object requires documentation | |
61 | 074 | Logical system defined differently in partner system | Space: object requires documentation | |
62 | 075 | Message type &1 exists in the model view &2. | Space: object requires documentation | |
63 | 076 | Method &1.&2 exists in model view &3. | Space: object requires documentation | |
64 | 077 | To partner &2 with message type &1 | Space: object requires documentation | |
65 | 078 | From partner &2 with message type &1 | Space: object requires documentation | |
66 | 079 | To partner &4 with method &1.&2 (message type &3) | Space: object requires documentation | |
67 | 080 | From partner &4 with method &1.&2 (message type &3) | Space: object requires documentation | |
68 | 081 | To partner &3 with method &1.&2 | Space: object requires documentation | |
69 | 082 | No detailed information exists. | Space: object requires documentation | |
70 | 083 | Execute the conversion step. | Space: object requires documentation | |
71 | 084 | Conversion logs exist for &1 | Space: object requires documentation | |
72 | 100 | Maintenance for object & is locked in system &; maintenance system & | Space: object requires documentation | |
73 | 101 | ALE module & is not available | Space: object requires documentation | |
74 | 102 | ALE distribution model is not active | Space: object requires documentation | |
75 | 110 | Logical system name &2 does not match SAP's recommendation | Space: object requires documentation | |
76 | 200 | -->> Extended Consistency Check Messages | The short text describes the object sufficiently | |
77 | 201 | Release information of segment does not match | Space: object requires documentation | |
78 | 202 | Release details of segment match | The short text describes the object sufficiently | |
79 | 203 | Number of fields matches | The short text describes the object sufficiently | |
80 | 204 | Number of fields does not match | Space: object requires documentation | |
81 | 205 | Export length matches | The short text describes the object sufficiently | |
82 | 206 | Export length does not match | Space: object requires documentation | |
83 | 207 | Incorrect field or field missing in position &1 | Space: object requires documentation | |
84 | 208 | Field &1 has incorrect position (&2 not &3) | Space: object requires documentation | |
85 | 209 | Last segment definitions do not match | Space: object requires documentation | |
86 | 210 | The export lengths of field &1 do not match | Space: object requires documentation | |
87 | 211 | Data elements of field &1 do not match | Space: object requires documentation | |
88 | 212 | Could not read remote IDoc type &1 | The short text describes the object sufficiently | |
89 | 213 | The release details of the IDoc type do not match | Space: object requires documentation | |
90 | 214 | Could not read segment &1 of IDoc type &2 remotely | The short text describes the object sufficiently | |
91 | 215 | Remote system &1 has a different release level | Space: object requires documentation | |
92 | 216 | Hierarchy details of segments do not match | Space: object requires documentation | |
93 | 217 | Number of segment retries does not match | Space: object requires documentation | |
94 | 218 | Mandatory flag is different: &1, remote &2 | The short text describes the object sufficiently | |
95 | 219 | The hierarchy level is different, local &1, remote &2 | The short text describes the object sufficiently | |
96 | 220 | Group ID is different &1, remote &2 | The short text describes the object sufficiently | |
97 | 221 | Number of group retries does not match | Space: object requires documentation | |
98 | 222 | Message &2 returned by connection test to system &1 | The short text describes the object sufficiently | |
99 | 50 | Please enter an editing type | ||
100 | 51 | Please specify one editing type only | ||
101 | 52 | No entry in table & for & & & | ||
102 | 53 | & & & has not changed | ||
103 | 54 | & & & has been saved | ||
104 | 55 | & & & already exists | ||
105 | 56 | Please complete & | ||
106 | 57 | & & was saved | ||
107 | 60 | If you press ENTER, & & & will be deleted | ||
108 | 61 | & & & has been deleted | ||
109 | 70 | Please specify cluster and request code | ||
110 | 99 | Caution! SAP no longer supports table T77WS. Please take T77WT |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in |