SAP ABAP Message Class RSDS (New DataSource)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSDS (Package) Apollo DataSource
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSDS (Package) Apollo DataSource
Attributes
Message class | RSDS | |
Short Description | New DataSource | |
Changed On | 20140121 | |
Last Changed At | 101755 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Internal error; new DataSource | The short text describes the object sufficiently | |
2 | 001 | Access method & does not exist | Space: object requires documentation | |
3 | 002 | Interface &1 not implemented by method &2 | The short text describes the object sufficiently | |
4 | 003 | Data saved | The short text describes the object sufficiently | |
5 | 004 | DataSource &1(&2) not changeable | The short text describes the object sufficiently | |
6 | 005 | Save DDIC object &1 (&2) | The short text describes the object sufficiently | |
7 | 006 | No DataSource for code ID &1 | The short text describes the object sufficiently | |
8 | 007 | Generate program for code ID &1 | The short text describes the object sufficiently | |
9 | 008 | Method &1 for DataSource &2 source system &3 not defined | The short text describes the object sufficiently | |
10 | 009 | Data package &1 received; processing is starting | The short text describes the object sufficiently | |
11 | 010 | Inbound processing of data package &1 finished | The short text describes the object sufficiently | |
12 | 011 | Conversion exit &1 does not exist | The short text describes the object sufficiently | |
13 | 012 | Error '&4' at conversion exit &1 (field &2, value &3) | The short text describes the object sufficiently | |
14 | 013 | Error '&3&4' on assignment field &1 value &2 | The short text describes the object sufficiently | |
15 | 014 | Field value check field &1: Value &2 is not internal (&3) | The short text describes the object sufficiently | |
16 | 015 | Field value check field &1: value &2 is not internal | The short text describes the object sufficiently | |
17 | 016 | Error '&1&2' when assigning application structure, line &3, contents "&4" | The short text describes the object sufficiently | |
18 | 017 | &1 is not a date | The short text describes the object sufficiently | |
19 | 018 | &1 does not match the user-dependent date format --> long text | Space: object requires documentation | |
20 | 019 | Data package &1 does not exist | The short text describes the object sufficiently | |
21 | 020 | Data package &1 stored in the main memory | The short text describes the object sufficiently | |
22 | 021 | Saving data package &1... | The short text describes the object sufficiently | |
23 | 022 | InfoObject &1 is not available | The short text describes the object sufficiently | |
24 | 023 | Field '&1' could not be added | The short text describes the object sufficiently | |
25 | 024 | The segment with the ID '&1' does not exist | The short text describes the object sufficiently | |
26 | 025 | Reference field &1 added automatically | The short text describes the object sufficiently | |
27 | 026 | The field with the position &1 of the segment &1 does not exist | The short text describes the object sufficiently | |
28 | 027 | Field name &1 of segment &2 exists multiple times | The short text describes the object sufficiently | |
29 | 028 | Unspecified Error | Space: object requires documentation | |
30 | 029 | Error &2 from the DDIC | Space: object requires documentation | |
31 | 030 | &2 records for data package &1 updated successfully, &3 records filtered | The short text describes the object sufficiently | |
32 | 031 | Activation access method &1 failed | The short text describes the object sufficiently | |
33 | 032 | Segment &1 has no field to be transferred | Space: object requires documentation | |
34 | 033 | &1: no conversion exit entered | Space: object requires documentation | |
35 | 034 | The OLTP source &1 for source system &2 not present | The short text describes the object sufficiently | |
36 | 035 | Inconsistent metadata: Non-permitted data record in &1 | The short text describes the object sufficiently | |
37 | 036 | &1: Invalid value &2 for domain &3 | The short text describes the object sufficiently | |
38 | 037 | The check did not return any errors or warnings | The short text describes the object sufficiently | |
39 | 038 | Select exactly one field | The short text describes the object sufficiently | |
40 | 039 | &1: Invalid field name | The short text describes the object sufficiently | |
41 | 040 | Missing field name (segment &1, position &2) | The short text describes the object sufficiently | |
42 | 041 | &1: Conversion exit is not being executed | The short text describes the object sufficiently | |
43 | 042 | Long text is not maintained in the language &1 | The short text describes the object sufficiently | |
44 | 043 | Medium text is not maintained in language &1 | The short text describes the object sufficiently | |
45 | 044 | Short text is not maintained in language &1 | The short text describes the object sufficiently | |
46 | 045 | Long text for segment &2 is not maintained in the language &1 | The short text describes the object sufficiently | |
47 | 046 | The short text for segment &2 is not maintained in language &1 | The short text describes the object sufficiently | |
48 | 047 | &1: The short text is not maintained in language &2 | The short text describes the object sufficiently | |
49 | 048 | Version &1 already exists | The short text describes the object sufficiently | |
50 | 049 | DataSource &1(&2): Version &3 does not exist | The short text describes the object sufficiently | |
51 | 050 | Version Comparison DataSource &3(&4): &1 - &2 | The short text describes the object sufficiently | |
52 | 051 | Difference Table &3-&4 field &4: &1-&2 | The short text describes the object sufficiently | |
53 | 052 | Missing data record in version &1 table &2: &3 = &4 | The short text describes the object sufficiently | |
54 | 053 | Before loading, the DataSource must be activated | The short text describes the object sufficiently | |
55 | 054 | Version &1 could not be generated | The short text describes the object sufficiently | |
56 | 055 | Extractor &1 cannot be called synchronously | The short text describes the object sufficiently | |
57 | 056 | No differences between versions &1 - &2 | The short text describes the object sufficiently | |
58 | 057 | Creation of DataSources for SAP source system &1 is not permitted | Space: object requires documentation | |
59 | 058 | Access method &1 is not compatible with multi-segment sources | Space: object requires documentation | |
60 | 059 | Character-like PSA with access method &1 not permitted | Space: object requires documentation | |
61 | 060 | DataSource &1(&2) already exists | The short text describes the object sufficiently | |
62 | 061 | DataSource &1(&2) saved | The short text describes the object sufficiently | |
63 | 062 | DataSource &1(&2) does not exist in object version &3 | The short text describes the object sufficiently | |
64 | 063 | Non-permitted data type '&1' | The short text describes the object sufficiently | |
65 | 064 | Specify a data type | The short text describes the object sufficiently | |
66 | 065 | DataSource &1(&2) deleted | The short text describes the object sufficiently | |
67 | 066 | DataSource &1(&2) was migrated | The short text describes the object sufficiently | |
68 | 067 | Action for emulated DataSource &1(&2) not possible | The short text describes the object sufficiently | |
69 | 068 | DataSource &1(&2) cannot be migrated | The short text describes the object sufficiently | |
70 | 069 | Cancellation by User | The short text describes the object sufficiently | |
71 | 070 | The emulated DataSource &1(&2) cannot be changed | The short text describes the object sufficiently | |
72 | 071 | Creation of PSA &1 failed | The short text describes the object sufficiently | |
73 | 072 | Postprocessing PSA &1 failed (rc = &2) | Space: object requires documentation | |
74 | 073 | Error while saving DataSource &1(&2) | The short text describes the object sufficiently | |
75 | 074 | 3.x DataSource &1(&2) was recovered | The short text describes the object sufficiently | |
76 | 075 | DataSource &1(&2) cannot be recovered | The short text describes the object sufficiently | |
77 | 076 | Error during saving of the shadow object of DataSource &1 | The short text describes the object sufficiently | |
78 | 077 | Generated extraction &1... | The short text describes the object sufficiently | |
79 | 078 | Direct extraction &1... | The short text describes the object sufficiently | |
80 | 079 | Conversion &1... | The short text describes the object sufficiently | |
81 | 080 | Only one segment possible for data type &1 | The short text describes the object sufficiently | |
82 | 081 | The maximum number of segments is limited to 99 | The short text describes the object sufficiently | |
83 | 082 | The maximum number of segments for hierarchies is 5 | The short text describes the object sufficiently | |
84 | 083 | &1: Selection fields are only permitted in the primary segment | The short text describes the object sufficiently | |
85 | 084 | No primary segment defined | The short text describes the object sufficiently | |
86 | 085 | Definition of field object ID is required for data type &1 | The short text describes the object sufficiently | |
87 | 086 | Multi-segment extraction not possible without join field "object ID" | The short text describes the object sufficiently | |
88 | 087 | Missing field &1 (object ID) in segment &2 | The short text describes the object sufficiently | |
89 | 088 | Cancelled by user | The short text describes the object sufficiently | |
90 | 089 | &1: Data type &2 deviates from data element (&3) | The short text describes the object sufficiently | |
91 | 090 | &1: Length &2 deviates from data element (&3) | The short text describes the object sufficiently | |
92 | 091 | &1: Data type &2 deviates from domain (&3) | The short text describes the object sufficiently | |
93 | 092 | &1: Length &2 deviates from domain (&3) | The short text describes the object sufficiently | |
94 | 093 | &1: invalid data type &2 | Space: object requires documentation | |
95 | 094 | &1: Missing currency field / unit field &2 | The short text describes the object sufficiently | |
96 | 095 | &1: Invalid type &2 (currency field/unit field) | The short text describes the object sufficiently | |
97 | 096 | DataSource &1(&2) replicated | The short text describes the object sufficiently | |
98 | 097 | &1: Reference to currency field/unit field &2 is obsolete | The short text describes the object sufficiently | |
99 | 098 | The field positions cannot be changed | The short text describes the object sufficiently | |
100 | 099 | &1: Amount field in internal format; check settings | Space: object requires documentation | |
101 | 100 | &1: Explicit external length is less than implicit external length | Space: object requires documentation | |
102 | 101 | &1: External length specification will be ignored | Space: object requires documentation | |
103 | 102 | &1: Amount fields must have 2 decimal places | Space: object requires documentation | |
104 | 103 | &1: Output length but no conversion exit defined | Space: object requires documentation | |
105 | 104 | &1: Conversion exit &2 does not exist | Space: object requires documentation | |
106 | 105 | DataSource activated | The short text describes the object sufficiently | |
107 | 106 | DataSource &1 (&2) could not be activated | The short text describes the object sufficiently | |
108 | 107 | Generating access method &1... | The short text describes the object sufficiently | |
109 | 108 | Generation of conversion exits and PSA update... | The short text describes the object sufficiently | |
110 | 109 | No data passed on due to single record error during extraction | The short text describes the object sufficiently | |
111 | 110 | Data package &1, segment &2 being saved... | The short text describes the object sufficiently | |
112 | 111 | Data package &1, segment &2 was updated successfully | The short text describes the object sufficiently | |
113 | 112 | Data package &1, segment &2 was stored in main memory | The short text describes the object sufficiently | |
114 | 113 | Inbound processing of data package &1, segment &2 complete | The short text describes the object sufficiently | |
115 | 114 | &1: Only internal format can be selected if character PSA | Space: object requires documentation | |
116 | 115 | Beginning extraction request &1... | The short text describes the object sufficiently | |
117 | 116 | DataSource &1(&2): Objects ISFS and RSDS exist concurrently | The short text describes the object sufficiently | |
118 | 117 | Only one field is allowed for each segment as a language field | The short text describes the object sufficiently | |
119 | 118 | Only one field is allowed for each segment as a lower limit (validity) | The short text describes the object sufficiently | |
120 | 119 | Only one field is allowed per segment as upper limit (validity) | The short text describes the object sufficiently | |
121 | 120 | Extraction for this DataSource not possible | Space: object requires documentation | |
122 | 121 | There still seems to be data in the PSA despite 'No data found' error | The short text describes the object sufficiently | |
123 | 122 | The DataSource &1(&2) does not exist | The short text describes the object sufficiently | |
124 | 123 | The language field &1 in segment &2 is missing | The short text describes the object sufficiently | |
125 | 124 | The language field &1 in segment &2 is not of type 'LONG' | The short text describes the object sufficiently | |
126 | 125 | The field of validity (lower limit) &1 in segment &2 is missing | The short text describes the object sufficiently | |
127 | 126 | The field of validity &1 in segment &2 is not of type 'DATS' | The short text describes the object sufficiently | |
128 | 127 | The field of validity (upper limit) &1 in segment &2 is missing | The short text describes the object sufficiently | |
129 | 128 | The function cannot be executed | The short text describes the object sufficiently | |
130 | 129 | Data structures were changed. Start transaction beforehand | Space: object requires documentation | |
131 | 130 | DataSource &1(&2) does not have a valid application structure | The short text describes the object sufficiently | |
132 | 131 | Unable to initialize queue using request &1 | The short text describes the object sufficiently | |
133 | 132 | &1: Selection fields permitted in segment '0001' only | The short text describes the object sufficiently | |
134 | 133 | Code line has errors: "&1&2&3&4" | The short text describes the object sufficiently | |
135 | 134 | Syntax error in routine "&1&2, line &3 of generated program" | The short text describes the object sufficiently | |
136 | 135 | Unable to Delete DataSource &1(&2) | The short text describes the object sufficiently | |
137 | 136 | Error while replicating DataSource &1(&2) of object version &3 | The short text describes the object sufficiently | |
138 | 137 | Unable to process DataSource &1(&2) | The short text describes the object sufficiently | |
139 | 138 | Function &1 is not supported | The short text describes the object sufficiently | |
140 | 139 | No storage instance for access method & | The short text describes the object sufficiently | |
141 | 140 | Difference &1 &2, &3: &4 | The short text describes the object sufficiently | |
142 | 141 | &1 &2 missing in version &3 | The short text describes the object sufficiently | |
143 | 142 | No PSA exists for DataSource &1(&2) | The short text describes the object sufficiently | |
144 | 143 | &1: Field name is longer than 16 characters | The short text describes the object sufficiently | |
145 | 144 | Error while determining request numbers to be extracted | The short text describes the object sufficiently | |
146 | 145 | DataSource with data type &1 is not supported | The short text describes the object sufficiently | |
147 | 146 | Real-time extraction without transferring package number | The short text describes the object sufficiently | |
148 | 147 | Content release type (type of source system) is not maintained | The short text describes the object sufficiently | |
149 | 148 | Content version (release of source system) is not maintained | The short text describes the object sufficiently | |
150 | 149 | Operation &1 is not supported for TLOGO type &2 | The short text describes the object sufficiently | |
151 | 150 | Search string &1 contains non-permitted characters | The short text describes the object sufficiently | |
152 | 151 | &1: Missing reference to currency field/unit field | Space: object requires documentation | |
153 | 152 | DataSource &1(&2): Object type RSDS is not possible (long text) | Space: object requires documentation | |
154 | 153 | SAP Content System: Migration only possible "with export" | The short text describes the object sufficiently | |
155 | 154 | Cannot display delivery version | Space: object requires documentation | |
156 | 155 | &1: Template InfoObject &2 does not exist | The short text describes the object sufficiently | |
157 | 156 | Invalid object version &1 | The short text describes the object sufficiently | |
158 | 157 | &1: Unit field &2 is obsolete and is being deleted | The short text describes the object sufficiently | |
159 | 158 | &1: Fixed value cannot be maintained and is being deleted | The short text describes the object sufficiently | |
160 | 159 | &1: Fixed currency &2 does not exist | The short text describes the object sufficiently | |
161 | 160 | &1: Fixed unit &2 does not exist | The short text describes the object sufficiently | |
162 | 161 | Migration of DataSource &1(&2) failed | The short text describes the object sufficiently | |
163 | 162 | Recovery of DataSource 3.x &1(&2) is not possible | Space: object requires documentation | |
164 | 163 | Export DataSource &1(&2) in myself system: Object type RSDS not possible | The short text describes the object sufficiently | |
165 | 164 | DataSource &1(&2) with external original system deleted as replicate only | Space: object requires documentation | |
166 | 165 | 3.x DataSource &1(&2) does not exist | The short text describes the object sufficiently | |
167 | 166 | DataSource &1(&2) already exists as Content version | The short text describes the object sufficiently | |
168 | 167 | Unable to convert value &1 with currency &2 to internal format | The short text describes the object sufficiently | |
169 | 168 | Change of application component for source system &1 is not supported | The short text describes the object sufficiently | |
170 | 169 | Version comparison with content version not possible (source system &1) | The short text describes the object sufficiently | |
171 | 170 | Active version of emulated 3.x DataSource &1(&2) cannot be displayed | Space: object requires documentation | |
172 | 171 | Character field &1, value '&2' contains illegal characters | Space: object requires documentation | |
173 | 172 | Character field &1, value '&2' contains characs. that cannot be displayed | Space: object requires documentation | |
174 | 173 | &1: Packed numbers should have an odd number of digits | Space: object requires documentation | |
175 | 174 | DataSource &1(&2) is not a 3.x DataSource: Migration is not possible | The short text describes the object sufficiently | |
176 | 175 | DataSource &1(&2) already exists: Migration is not possible | Space: object requires documentation | |
177 | 176 | Extract source package &1... | The short text describes the object sufficiently | |
178 | 177 | DataSource &1(&2) cannot exist as object type RSDS | Space: object requires documentation | |
179 | 178 | DataSource &1(&2): Data type &3 not supported by object type &4 | The short text describes the object sufficiently | |
180 | 179 | DataSource &1(&2) must be activated | The short text describes the object sufficiently | |
181 | 180 | DataSource &1(&2): Object type RSDS not supported in BAPI source system | Space: object requires documentation | |
182 | 181 | Caution when loading without using PSA | Space: object requires documentation | |
183 | 182 | DataSource &1(&2): Extraction method 'CA' -> only as object type RSDS | The short text describes the object sufficiently | |
184 | 183 | D version in source system missing for DataSource &1(&2) | Space: object requires documentation | |
185 | 184 | Delta field &1 does not exist in the field list of segment &2 | Space: object requires documentation | |
186 | 185 | Delta field &1 must have type "DATS" for delta method "Date" | The short text describes the object sufficiently | |
187 | 186 | Delta field &1 is not a selection field | The short text describes the object sufficiently | |
188 | 187 | Delta field &1 must be numeric for delta method "num. pointer" | The short text describes the object sufficiently | |
189 | 188 | Delta field &1 does not exist in the field list | The short text describes the object sufficiently | |
190 | 189 | Data format of delta field &1 not compatible with timestamp | Space: object requires documentation | |
191 | 190 | &1: No conversion performed from external format | Space: object requires documentation | |
192 | 191 | &1: External length specification for date should have 10 characters | The short text describes the object sufficiently | |
193 | 192 | &1: External length specification for time should have 8 characters | The short text describes the object sufficiently | |
194 | 193 | Changes to &1 are not compatible with database | Space: object requires documentation | |
195 | 194 | Changing "Typed PSA" property creates new PSA version | Space: object requires documentation | |
196 | 195 | &1: Check of internal format not supported with this adapter | Space: object requires documentation | |
197 | 196 | '&1' is not a selection field (DataSource '&2', source system '&3') | Space: object requires documentation | |
198 | 197 | &1: Field name with two underscores reserved for navigation attributes | The short text describes the object sufficiently | |
199 | 198 | Request &1 not extracted; request is in obsolete version of DataSource | Space: object requires documentation | |
200 | 199 | Selection condition is inconsistent and creates empty amount | Space: object requires documentation | |
201 | 200 | Invalid name &1 for DataSource (source system) | The short text describes the object sufficiently | |
202 | 201 | Cannot create documentation link for source system '&1' | Space: object requires documentation | |
203 | 202 | Cannot create documentation link for release/version '&1' | Space: object requires documentation | |
204 | 203 | Cannot maintain documentation links: System type &1 (not 'SAP') | The short text describes the object sufficiently | |
205 | 204 | No documentation link exists for DataSource &1 | The short text describes the object sufficiently | |
206 | 205 | Activation of DataSource &1(&2), context: &3 | The short text describes the object sufficiently | |
207 | 206 | DataSource &1: Shadow version content type &2, version &3 missing | The short text describes the object sufficiently | |
208 | 207 | Segment &1 of structure proposal missing in DataSource | Space: object requires documentation | |
209 | 208 | Field &1 of structure proposal missing in segment &2 of DataSource | Space: object requires documentation | |
210 | 209 | Duplicate data records returned; indicator is not checked | Space: object requires documentation | |
211 | 210 | Proof of origin required in source systems PI_BASIS 2006.1 and higher | The short text describes the object sufficiently | |
212 | 211 | No access method in source system &2 for data type &1 | The short text describes the object sufficiently | |
213 | 212 | &1: Field name &2 is reserved and should not be used | Space: object requires documentation | |
214 | 213 | Confict with DataSource in source system; postprocessing required | Space: object requires documentation | |
215 | 214 | No (further) field found in search for '&1' | The short text describes the object sufficiently | |
216 | 215 | &1: Field has type &2, but no reference field with domain &3/&4 | The short text describes the object sufficiently | |
217 | 216 | &1: Domain &2 does not exist | The short text describes the object sufficiently | |
218 | 217 | Replication not possible because &1 is not a replicating source system | The short text describes the object sufficiently | |
219 | 218 | More than three fields are over 255 characters long | The short text describes the object sufficiently | |
220 | 219 | The 'Load without PSA (by direct access)' flag will be deleted | Space: object requires documentation | |
221 | 220 | Could not check destination &1 of external system &2 | The short text describes the object sufficiently | |
222 | 221 | Last extracted request is '&1', not '&2' | The short text describes the object sufficiently | |
223 | 222 | DataSource &1 &2 is not configured for generic delta | The short text describes the object sufficiently | |
224 | 223 | Exception NOT_FOUND with module RSA8_GET_POINTER_FOR_REQUEST | Space: object requires documentation | |
225 | 224 | To date &1 earlier than From date &2 | The short text describes the object sufficiently | |
226 | 225 | &1: Conversion exit &2 can only be used for character fields | The short text describes the object sufficiently | |
227 | 226 | Hierarchy DataSource &1(&2) cannot be used as a template | Space: object requires documentation | |
228 | 227 | Hierarchy DataSource &1(&2) cannot be migrated | Space: object requires documentation | |
229 | 228 | Unknown File Extension | Space: object requires documentation | |
230 | 229 | File type not supported (only CSV and XLS supported) | The short text describes the object sufficiently | |
231 | 230 | Column separator not recognized. Specify the separator | The short text describes the object sufficiently | |
232 | 231 | &1: Data type &2 is not suitable for external sources | Space: object requires documentation | |
233 | 232 | Content Versions Created for DataSource &1(&2) | The short text describes the object sufficiently | |
234 | 233 | File ending &1 does not match current adapter &2; Ending &3 expected | The short text describes the object sufficiently | |
235 | 234 | Specify a delta field if you are using a generic delta | The short text describes the object sufficiently | |
236 | 235 | You are not authorized to read all files (S_RS_DS, subobject FILE) | The short text describes the object sufficiently | |
237 | 236 | Saving data package &1 in remote HANA-DB... | The short text describes the object sufficiently | |
238 | 237 | &1: Field is too long (too many characters) | The short text describes the object sufficiently | |
239 | 238 | Content version of DataSource &1(&2) created | The short text describes the object sufficiently | |
240 | 239 | Secondary index &1 (PSA table &2) does not match DataSource key | The short text describes the object sufficiently | |
241 | 240 | Delta selections for field &1 are invalid (LOW &2 > HIGH &3) | Space: object requires documentation | |
242 | 241 | Currently used adapter &1 is invalid. Reason: &2 | The short text describes the object sufficiently | |
243 | 242 | Request &1 in PSA &2 is inconsistent | The short text describes the object sufficiently | |
244 | 243 | Request &1 in PSA has zero records | The short text describes the object sufficiently | |
245 | 244 | Field &1 has digressive output length and cannot be used as a delta field | The short text describes the object sufficiently | |
246 | 245 | Range limit (&2) of delta field &1 reached. No further delta possible. | The short text describes the object sufficiently | |
247 | 249 | Caller (Depth &1): Program &2, Include &3, Row &4 | The short text describes the object sufficiently | |
248 | 250 | Start imact of DataSource D versions: &1 deleted, &2 written | The short text describes the object sufficiently | |
249 | 251 | End impact handling of DataSource D versions | The short text describes the object sufficiently | |
250 | 252 | Delete dependent D versions with class &1 | The short text describes the object sufficiently | |
251 | 253 | Write dependent D versions with class &1 | The short text describes the object sufficiently | |
252 | 254 | Activate PSA '&1' | The short text describes the object sufficiently | |
253 | 255 | Create PSA index | The short text describes the object sufficiently | |
254 | 256 | Adapter-specific activations | The short text describes the object sufficiently | |
255 | 257 | Delete PSA &1 | The short text describes the object sufficiently | |
256 | 258 | Start impact handling (activation): Transformation | The short text describes the object sufficiently | |
257 | 259 | End impact handling (activation): Transformation | The short text describes the object sufficiently | |
258 | 260 | Replication of D versions from source system &1 | The short text describes the object sufficiently | |
259 | 261 | Template &1 has been copied | The short text describes the object sufficiently | |
260 | 300 | Internal error during generation of the Web Service | The short text describes the object sufficiently | |
261 | 301 | Error generating Web service &1 | The short text describes the object sufficiently | |
262 | 302 | Error while determining name | The short text describes the object sufficiently | |
263 | 303 | Error when deleting the queue | The short text describes the object sufficiently | |
264 | 304 | Cancellation by User | The short text describes the object sufficiently | |
265 | 305 | Generation of Web Service terminated (missing user confirmation) | The short text describes the object sufficiently | |
266 | 306 | Delta mod &1 is not supported | The short text describes the object sufficiently | |
267 | 307 | Error during selection of data | The short text describes the object sufficiently | |
268 | 308 | No (further) data available | The short text describes the object sufficiently | |
269 | 309 | No profile selected for Web service | The short text describes the object sufficiently | |
270 | 310 | DDIC &1 does not exist | The short text describes the object sufficiently | |
271 | 311 | Error while activating/deleting Web service: No destination maintained | Space: object requires documentation | |
272 | 312 | Web service: Incompatible structure change applied | The short text describes the object sufficiently | |
273 | 313 | Internal error while deleting Web Service | The short text describes the object sufficiently | |
274 | 314 | Naming conflict: Service name &1 is already used in DataSource &2(&3) | The short text describes the object sufficiently | |
275 | 315 | Service name &1: length minimum 5 characters, maximum 15 characters | The short text describes the object sufficiently | |
276 | 316 | Cannot find suitable generation namespace for DataSource &1 | The short text describes the object sufficiently | |
277 | 317 | Service name &1 not allowed; use characters A-Z, 0-9, '_' only | The short text describes the object sufficiently | |
278 | 318 | Content DS &1: Name '&2' <> service name '&3' (first 2 chars. are diff.) | The short text describes the object sufficiently | |
279 | 319 | Naming conflict: Service name &1 is already being used in DataSource &2 | The short text describes the object sufficiently | |
280 | 320 | DataSource &1(&2): Missing assignment of data, request &3 | The short text describes the object sufficiently | |
281 | 321 | Delta method &1: Only use ' ', FIL0 or FIL1 | The short text describes the object sufficiently | |
282 | 322 | Load process for DataSource &1(&2) could not be interrupted | The short text describes the object sufficiently | |
283 | 323 | Function must be implemented in external system | The short text describes the object sufficiently | |
284 | 324 | No logical port defined | The short text describes the object sufficiently | |
285 | 325 | No extraction object defined (adapter WEBS_PULL). | The short text describes the object sufficiently | |
286 | 326 | Source system &1 is not type Web Service | The short text describes the object sufficiently | |
287 | 327 | Settings for source system &1 were saved | The short text describes the object sufficiently | |
288 | 400 | Source system &2 not available. Object not converted (see long text) | Space: object requires documentation | |
289 | 401 | No mapping in RSLOGSYSMAP for source system &1 | The short text describes the object sufficiently | |
290 | 501 | Source system &1 is not a BAPI source system | The short text describes the object sufficiently | |
291 | 502 | Data type &1 not allowed for BAPI source systems (only D, M, T) | The short text describes the object sufficiently | |
292 | 503 | Data type of DataSource &1(&2) is not a hierarchy | The short text describes the object sufficiently | |
293 | 550 | Error when uploading DataSource &1(&2) | The short text describes the object sufficiently | |
294 | 551 | Name determination failed for ODP &1 | The short text describes the object sufficiently | |
295 | 552 | DataSource &1(&2): Error accessing adapter | The short text describes the object sufficiently | |
296 | 553 | No (further) ODP found searching for &1 | The short text describes the object sufficiently | |
297 | 554 | Source system &1: metadata upload with errors | The short text describes the object sufficiently | |
298 | 555 | Source system &1: metadata upload completed | The short text describes the object sufficiently | |
299 | 556 | DataSources exist already; ODP context &1 cannot be changed | The short text describes the object sufficiently | |
300 | 557 | Saving DataSource &1(&2) | The short text describes the object sufficiently | |
301 | 558 | Source system &1 does not support usage of remote tree | The short text describes the object sufficiently | |
302 | 559 | Source system &1: no valid ODP context found | The short text describes the object sufficiently | |
303 | 560 | Source system &1: ODP context &2 not found | The short text describes the object sufficiently | |
304 | 561 | No value help for ODP logsys &1 | The short text describes the object sufficiently | |
305 | 562 | &1 is not an ODP source system | The short text describes the object sufficiently | |
306 | 563 | No Content objects available for source system &1 (context &2) | The short text describes the object sufficiently | |
307 | 564 | Content installation not supported for source system &1 (context &2) | The short text describes the object sufficiently | |
308 | 565 | Source system &1 (context &2): remote authority check not supported | The short text describes the object sufficiently | |
309 | 566 | No context found for ODP source system &1 | The short text describes the object sufficiently | |
310 | 567 | ODP &1 not found in source system &2 | The short text describes the object sufficiently | |
311 | 568 | DataSource type &1 does not match ODP semantics &2 | The short text describes the object sufficiently | |
312 | 569 | Datasource cannot be created manually in source system &1 | The short text describes the object sufficiently | |
313 | 570 | No RFC destination found for source system &1 | The short text describes the object sufficiently | |
314 | 571 | Destination &1: ping waiting time (&2 seconds) exceeded | The short text describes the object sufficiently | |
315 | 572 | ODP source system &1: no background destination found | The short text describes the object sufficiently | |
316 | 573 | ODP source system &1: no dialog destination found | The short text describes the object sufficiently | |
317 | 574 | Error when creating emulated D-Version for ODP &1 | The short text describes the object sufficiently | |
318 | 575 | Specify a valid ODP | The short text describes the object sufficiently | |
319 | 576 | Specify ODP semantics | The short text describes the object sufficiently | |
320 | 577 | Start metadata upload in source system &1 | The short text describes the object sufficiently | |
321 | 578 | Delta state inconsistent in the source system (Delta vs. Init) | Space: object requires documentation | |
322 | 600 | Error &1 occurred during HTTP call for destination &2 (see long text) | Space: object requires documentation | |
323 | 601 | Error &1 occurred during HTTP communication to &2 (see long text) | Space: object requires documentation | |
324 | 602 | Error in HANA DB system: &1&2&3&4 | The short text describes the object sufficiently | |
325 | 603 | Sending confirmation to HANA database system... | The short text describes the object sufficiently | |
326 | 604 | Confirmation sent to HANA database system | The short text describes the object sufficiently | |
327 | 605 | Implement SAP Note 1688750 in source system &1 | The short text describes the object sufficiently | |
328 | 666 | &1&2&3&4 | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 400 |