SAP ABAP Message Class SPRX (Proxy Generation)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DWB-PRX (Application Component) Proxy Generation
⤷ SAI_PROXY_GENTIME (Package) ES Tools: Proxy Generation
⤷ BC-DWB-PRX (Application Component) Proxy Generation
⤷ SAI_PROXY_GENTIME (Package) ES Tools: Proxy Generation
Attributes
Message class | SPRX | |
Short Description | Proxy Generation | |
Changed On | 20140121 | |
Last Changed At | 103758 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | & & & & | The short text describes the object sufficiently | |
2 | 001 | &1&2&3&4 | The short text describes the object sufficiently | |
3 | 002 | class &1 does not exist | The short text describes the object sufficiently | |
4 | 003 | Specify a complete ID | The short text describes the object sufficiently | |
5 | 004 | No proxy exists for object &1 (namespace &2) | The short text describes the object sufficiently | |
6 | 005 | A proxy already exists for object &1 (namespace &2) | The short text describes the object sufficiently | |
7 | 006 | Proxy generation not permitted for type &1(&2) in this system | Space: object requires documentation | |
8 | 007 | Action terminated | The short text describes the object sufficiently | |
9 | 008 | Enterprise Services Builder address not maintained | Space: object requires documentation | |
10 | 009 | namespace starting with 'urn:sap-com:sprx' is reserved | The short text describes the object sufficiently | |
11 | 010 | WSDL could not be read from the Enterprise Services Builder | Space: object requires documentation | |
12 | 011 | &1 &2 is not a global type | The short text describes the object sufficiently | |
13 | 012 | Wrong Generating Application &1 | The short text describes the object sufficiently | |
14 | 013 | Proxy &1/&2 is assigned to package &3 but has to be assigned to &4 | Space: object requires documentation | |
15 | 014 | Internal error when generating the generation list | The short text describes the object sufficiently | |
16 | 015 | The name &1 is longer that the &2 characters permitted | The short text describes the object sufficiently | |
17 | 016 | The name &1 is already being used | The short text describes the object sufficiently | |
18 | 017 | &1 &2 with the name/using &3 already exists | The short text describes the object sufficiently | |
19 | 018 | Error when reading XML document (document contains syntactic errors) | Space: object requires documentation | |
20 | 019 | Detailed information available (-> Compare Button) | The short text describes the object sufficiently | |
21 | 020 | Starting browser... | The short text describes the object sufficiently | |
22 | 021 | Regeneration only possible using consumer proxy | Space: object requires documentation | |
23 | 022 | Data saved | The short text describes the object sufficiently | |
24 | 023 | Proxy &2 already exists for port type &3 from namespace &4 in package &1 | Space: object requires documentation | |
25 | 024 | Proxy activated | The short text describes the object sufficiently | |
26 | 025 | Proxy deleted | The short text describes the object sufficiently | |
27 | 026 | Proxy was reset to active version | The short text describes the object sufficiently | |
28 | 027 | No documentation exists for object &1 &2 &3 | The short text describes the object sufficiently | |
29 | 028 | Unable to fully move Web service object &1 &2 | Space: object requires documentation | |
30 | 029 | Proxy (re)generated. Do not forget to save and activate | The short text describes the object sufficiently | |
31 | 030 | Proxy is inactive. Do not forget to activate | The short text describes the object sufficiently | |
32 | 031 | Proxy is up-to-date. No changes necessary | The short text describes the object sufficiently | |
33 | 032 | Proxy generation terminated: WSDL error (for <&1> element <&3> missing) | Space: object requires documentation | |
34 | 033 | Proxy generation terminated: WSDL error (for <&1> attribute "&3" missing) | Space: object requires documentation | |
35 | 034 | Proxy generation terminated: WSDL error (Namespace "&1" not defined) | Space: object requires documentation | |
36 | 035 | Proxy generation terminated: WSDL error (node <&1> missing) | Space: object requires documentation | |
37 | 036 | Object type &1 not supported by proxy generation | The short text describes the object sufficiently | |
38 | 037 | WSDL error: Interface contains inbound AND outbound methods | The short text describes the object sufficiently | |
39 | 038 | Proxy generation terminated: WSDL error (<&1> not supported) | Space: object requires documentation | |
40 | 039 | Maintain object in original language & | The short text describes the object sufficiently | |
41 | 040 | Proxy generation terminated: WSDL error ("&1" is not numerical) | Space: object requires documentation | |
42 | 041 | Proxy generation internal error: Object &1 not found | Space: object requires documentation | |
43 | 042 | Proxy generation terminated: WSDL error (interface without methods) | Space: object requires documentation | |
44 | 043 | Field &1 in path &2 &3 &4 not found | Space: object requires documentation | |
45 | 044 | Proxy generation terminated: WSDL error (method "&1" without in/output) | Space: object requires documentation | |
46 | 045 | Proxy generation terminated: WSDL error (object "&1" without name) | Space: object requires documentation | |
47 | 046 | Proxy generation terminated: Message must have exactly one part | Space: object requires documentation | |
48 | 047 | Proxy generation terminated: WSDL error (message "&1", part "&2") | Space: object requires documentation | |
49 | 048 | The name &1 is shorter than the required &2 characters | The short text describes the object sufficiently | |
50 | 049 | Only use letters at location &1 | The short text describes the object sufficiently | |
51 | 050 | Only use letters or numbers at location &1 | The short text describes the object sufficiently | |
52 | 051 | Only use letters, numbers or '_' | The short text describes the object sufficiently | |
53 | 052 | The name &1 is invalid | The short text describes the object sufficiently | |
54 | 053 | Name must begin with &1 | Space: object requires documentation | |
55 | 054 | Proxy is currently locked by another user | The short text describes the object sufficiently | |
56 | 055 | Database inconsistent: object &1 &2 not found | Space: object requires documentation | |
57 | 056 | &1: Error when creating/generating (&2) | Space: object requires documentation | |
58 | 057 | Data for creating object &1 &2 missing | Space: object requires documentation | |
59 | 058 | Data for implementing class missing | Space: object requires documentation | |
60 | 059 | &1: Error when deleting (return code &2 &3 &4) | The short text describes the object sufficiently | |
61 | 060 | Proxy &1 &2 &3 is locked by user &4 | The short text describes the object sufficiently | |
62 | 061 | Proxy cannot be unlocked | The short text describes the object sufficiently | |
63 | 062 | Changes not allowed because of package inconsistencies | Space: object requires documentation | |
64 | 063 | Proxy generation terminated: "mixed content" not supported | Space: object requires documentation | |
65 | 064 | <any>,<anyAttribute> not supported | Space: object requires documentation | |
66 | 065 | Proxy generation terminated: Abstract elements/element replacements | Space: object requires documentation | |
67 | 066 | Proxy generation terminated: <redefine> not supported | Space: object requires documentation | |
68 | 067 | The XSD type &1 does not exactly correspond to the ABAP type &2 | Space: object requires documentation | |
69 | 068 | Restrictions to the value range ignored | Space: object requires documentation | |
70 | 069 | Object not (yet) activated | The short text describes the object sufficiently | |
71 | 070 | Avoid using tables without surrounding tag for individual lines | Space: object requires documentation | |
72 | 071 | Keys and uniqueness relationships ignored | Space: object requires documentation | |
73 | 072 | Item is part of recursion (see long text for additional information) | Space: object requires documentation | |
74 | 073 | Object not (yet) activated (DDIC log => detail button) | Space: object requires documentation | |
75 | 074 | Object still being used; cannot delete object | Space: object requires documentation | |
76 | 075 | Proxy object &1 &2 deleted | The short text describes the object sufficiently | |
77 | 076 | Proxy object &1 &2 not deleted (used elsewhere/other namespace) | Space: object requires documentation | |
78 | 077 | No log exists | The short text describes the object sufficiently | |
79 | 078 | WSDL error: &1 (&2) defined more than once | Space: object requires documentation | |
80 | 079 | object &1 &2 could not be activated->check ddic | The short text describes the object sufficiently | |
81 | 080 | Proxy successfully renamed to &1 &2 | The short text describes the object sufficiently | |
82 | 081 | No connection to Enterprise Services Builder(only generic data visible) | Space: object requires documentation | |
83 | 082 | Character '_' not permitted in the first three places | The short text describes the object sufficiently | |
84 | 083 | Error when communicating with the Enterprise Services Builder | Space: object requires documentation | |
85 | 084 | Cannot generate proxy (object &1 missing in WSDL, see long text) | Space: object requires documentation | |
86 | 085 | Cannot display WSDL document | The short text describes the object sufficiently | |
87 | 086 | HTTP communication contains errors (see long text for diagnosis) | Space: object requires documentation | |
88 | 087 | HTTP communication functioning | The short text describes the object sufficiently | |
89 | 088 | Enterprise Services Builder server not functioning correctly | Space: object requires documentation | |
90 | 089 | Enterprise Services Builder server functioning correctly. Data understood | The short text describes the object sufficiently | |
91 | 090 | HTTP error (return code &1, message "&2") | Space: object requires documentation | |
92 | 091 | Namespace &1 does not exist in the Enterprise Services Builder | Space: object requires documentation | |
93 | 092 | Object &1 does not exist in namespace &2 | Space: object requires documentation | |
94 | 093 | Recursions must be eliminated | Space: object requires documentation | |
95 | 094 | Table type &1 &2 can only be edited context of data type usage | The short text describes the object sufficiently | |
96 | 095 | Proxy generation terminated: WSDL error (decimal points > length) | Space: object requires documentation | |
97 | 096 | &1 &2 cannot be displayed before proxy is activated | Space: object requires documentation | |
98 | 097 | Enterprise Services Builder data not understood | The short text describes the object sufficiently | |
99 | 098 | Proxy consistent | The short text describes the object sufficiently | |
100 | 099 | Main object &3/&4, but not object &1/&2 delivered to customer | Space: object requires documentation | |
101 | 100 | Main object &3/&4 can be transported, object &1/&2 cannot be transported | Space: object requires documentation | |
102 | 101 | 'X' not permitted as first character ('X' indicates enhancements) | The short text describes the object sufficiently | |
103 | 102 | No change possible. Object already used in other proxies | The short text describes the object sufficiently | |
104 | 103 | Object used by an interface from another namespace | Space: object requires documentation | |
105 | 104 | Do not use blank characters | The short text describes the object sufficiently | |
106 | 105 | Object (&2) with the name &3 already exists in system &1 | The short text describes the object sufficiently | |
107 | 106 | Package not specified | Space: object requires documentation | |
108 | 107 | Object activated | The short text describes the object sufficiently | |
109 | 108 | Objects to be changed from external namespaces: | Space: object requires documentation | |
110 | 109 | Objects from other namespaces missing. Unable to save. See long text | Space: object requires documentation | |
111 | 110 | Objects from other namespaces must be regenerated. See long text | Space: object requires documentation | |
112 | 111 | Objects from other namespaces cannot be changed. See long text | Space: object requires documentation | |
113 | 112 | WARNING: An object with the name &1 already exists in system &2 | Space: object requires documentation | |
114 | 113 | Unable to find software component version for namespace &1 | The short text describes the object sufficiently | |
115 | 114 | No documentation available | The short text describes the object sufficiently | |
116 | 115 | PortType (name/namespace) &1 &2 not found in WSDL | The short text describes the object sufficiently | |
117 | 116 | <&4> missing for object &1 (or one of its elements/attributes) | Space: object requires documentation | |
118 | 117 | No portType or more than one portType in WSDL | The short text describes the object sufficiently | |
119 | 118 | Package &1 does not belong to &2 | Space: object requires documentation | |
120 | 119 | No proxy exists for ABAP key object type &1, object name &2 | The short text describes the object sufficiently | |
121 | 120 | Canceled: Interfaces must have the same direction in all methods | The short text describes the object sufficiently | |
122 | 121 | Migration for SAP namespaces not allowed: &1 &2 &3 | The short text describes the object sufficiently | |
123 | 122 | Interface uses external and internal message definitions | Space: object requires documentation | |
124 | 123 | Document not found (path &2&3&4, error code &1) | Space: object requires documentation | |
125 | 124 | Enter a prefix | Space: object requires documentation | |
126 | 125 | Interface definition missing in WSDL document (<portType> missing) | Space: object requires documentation | |
127 | 126 | Namespaces with more than &1 characters are not supported (&2&3&4) | The short text describes the object sufficiently | |
128 | 127 | Object names with more than &1 characters are not supported (&2&3&4) | The short text describes the object sufficiently | |
129 | 128 | Function only possible for XI proxies | The short text describes the object sufficiently | |
130 | 129 | The selected WSDL does not describe the selected proxy object | The short text describes the object sufficiently | |
131 | 130 | Error occurred | The short text describes the object sufficiently | |
132 | 131 | No basis URL exists for the relative URL &1 | The short text describes the object sufficiently | |
133 | 132 | No data type specified for data type enhancement | The short text describes the object sufficiently | |
134 | 133 | Proxy for data type &1 &2 does not exist or cannot be enhanced | The short text describes the object sufficiently | |
135 | 134 | Invalid proxy object: &1, &2, &3, &4 | Space: object requires documentation | |
136 | 135 | Proxy object &1 &2 out-of-date. Regenerate | Space: object requires documentation | |
137 | 136 | Error when creating HTTP client: Destination:&1 Error:&2 | The short text describes the object sufficiently | |
138 | 137 | Error when creating HTTP client: URL:&1 Error:&2 | The short text describes the object sufficiently | |
139 | 138 | Definition of port type '&1' not found in WSDL document | Space: object requires documentation | |
140 | 139 | Object key already being used and cannot be renamed | Space: object requires documentation | |
141 | 140 | You can only change elements of an enhancement by using the enhancement | The short text describes the object sufficiently | |
142 | 141 | Business object & is not available as an active version | The short text describes the object sufficiently | |
143 | 142 | Package &1 has no use access to package interface &2 | Space: object requires documentation | |
144 | 143 | Structure pkg. &1 has no structure relationship with structure pkg. &2 | Space: object requires documentation | |
145 | 144 | Implementing class &1 not yet activated | The short text describes the object sufficiently | |
146 | 145 | Implementing class &1 is inactive | The short text describes the object sufficiently | |
147 | 146 | Component GUID:&1 Name:&2 Version:&3 Description:&4 | The short text describes the object sufficiently | |
148 | 147 | Unable to determine SWCV for &1/&2/&3 @&4 (type/name/namespace @address) | Space: object requires documentation | |
149 | 148 | Enhancement or included or projected component cannot be changed | Space: object requires documentation | |
150 | 149 | Object &1 or object &2 obsolete or inconsistent | Space: object requires documentation | |
151 | 150 | No implementation found for interface &1 | The short text describes the object sufficiently | |
152 | 151 | Class &1 does not implement interface &2 | Space: object requires documentation | |
153 | 152 | Textobject Name:&1 Namespace:&2 not found | The short text describes the object sufficiently | |
154 | 153 | Activate proxy (active version incorrect) | The short text describes the object sufficiently | |
155 | 154 | TextID &1 not found in textcache | The short text describes the object sufficiently | |
156 | 155 | Proxy &1 &2 orphaned (renamed/no longer exists in ESR) | The short text describes the object sufficiently | |
157 | 156 | Referred proxy object &1 &2 not found (Referring object &3 &4) | Space: object requires documentation | |
158 | 157 | Type changed for object &1 &2 | Space: object requires documentation | |
159 | 158 | Logon language &1 does not match original language &2 | Space: object requires documentation | |
160 | 159 | Invalid XSD->ABAP Type Mapping (XSD Type/ABAP Type): &1/&2 | The short text describes the object sufficiently | |
161 | 160 | Invalid URL &1 | The short text describes the object sufficiently | |
162 | 161 | WSDL cannot be converted in doc style; namespace is not unique | The short text describes the object sufficiently | |
163 | 162 | WSDL cannot be converted in doc style; error during serialization | The short text describes the object sufficiently | |
164 | 163 | Error while selecting file: &1 | The short text describes the object sufficiently | |
165 | 164 | Error while uploading file '&1' &2 | The short text describes the object sufficiently | |
166 | 165 | Error while downloading file '&1' &2 | The short text describes the object sufficiently | |
167 | 166 | Internal error splitter control &1 &2 &3 | The short text describes the object sufficiently | |
168 | 167 | Referenced object & is not available in an active version | The short text describes the object sufficiently | |
169 | 168 | Proxy &1 &2 is inactive. Activate before transport release. | Space: object requires documentation | |
170 | 169 | Regenerate proxy &1 &2 (due to inconsistencies with ref. object &3 &4) | Space: object requires documentation | |
171 | 170 | Enhancement &1 inconsistent | Space: object requires documentation | |
172 | 171 | Proxy &1 &2 has no version ID | The short text describes the object sufficiently | |
173 | 172 | Logical port template is inconsistent; regenerate and activate it | The short text describes the object sufficiently | |
174 | 173 | Business object &1 has errors | The short text describes the object sufficiently | |
175 | 174 | Package &1 cannot be changed by regeneration in &2 | The short text describes the object sufficiently | |
176 | 175 | Prefix &1 cannot be changed by regeneration in &2 | The short text describes the object sufficiently | |
177 | 176 | Proxy object &1 &2 changed | The short text describes the object sufficiently | |
178 | 177 | Proxy object &1 &2 not changed | The short text describes the object sufficiently | |
179 | 178 | Proxy not usable as web service client; regenerate | The short text describes the object sufficiently | |
180 | 179 | Inconsistent Proxy data, message name used more than once &1 &2 | The short text describes the object sufficiently | |
181 | 180 | Proxy object &1 &2 is used by another proxy object. | Space: object requires documentation | |
182 | 181 | Runtime Version &1 does not allow asynchronous method | Space: object requires documentation | |
183 | 182 | Runtime Version &1 does not allow more than one method | Space: object requires documentation | |
184 | 183 | User action in background mode is not allowed. | The short text describes the object sufficiently | |
185 | 184 | You are not authorized to execute this object | The short text describes the object sufficiently | |
186 | 185 | Object &1 &2 is not referred | The short text describes the object sufficiently | |
187 | 186 | The default value &1 is not supported for type &2 by the proxy runtime | Space: object requires documentation | |
188 | 187 | SubID(parent|type|name|namespace) not found:&1|&2|&3|&4 | The short text describes the object sufficiently | |
189 | 188 | Invalid schema: node '&1' must not have parent node '&2' | The short text describes the object sufficiently | |
190 | 189 | Invalid schema: unexpected node '&1' within node '&2' | The short text describes the object sufficiently | |
191 | 190 | Invalid schema: expected node '&1' within node '&2' | The short text describes the object sufficiently | |
192 | 191 | Invalid schema: expected node '&1' or '&2' within node '&3' | The short text describes the object sufficiently | |
193 | 192 | Invalid schema: expected node '&1' or '&2' or '&3' within node '&4' | The short text describes the object sufficiently | |
194 | 193 | Invalid schema: unknown node '&1' | The short text describes the object sufficiently | |
195 | 194 | business object &1 references &2 &3 | The short text describes the object sufficiently | |
196 | 195 | Object(type|name|namespace) from other namespace missing: &1|&2|&3 | The short text describes the object sufficiently | |
197 | 196 | Object(type|name|namespace) from other namespace must be changed &1|&2|&3 | The short text describes the object sufficiently | |
198 | 197 | The name '&1...&2' is too long, max. length is &3 character | The short text describes the object sufficiently | |
199 | 198 | No proxy object exists for business object &1 &2 to be enhanced | The short text describes the object sufficiently | |
200 | 199 | Direction was changed. Regeneration not possible, only deletion. | Space: object requires documentation | |
201 | 200 | Unable to determine proxy object from transport object &1 &2 | Space: object requires documentation | |
202 | 201 | No inconsistency for transport object &1 &2 | The short text describes the object sufficiently | |
203 | 202 | Deletion of proxy object &1 &2 was unsuccessful | Space: object requires documentation | |
204 | 203 | Inconsistency for transport object &1 &2 corrected | The short text describes the object sufficiently | |
205 | 204 | Transport object &1 &2 has inconsistency | Space: object requires documentation | |
206 | 205 | Proxy object &1 &2 deleted | Space: object requires documentation | |
207 | 206 | Proxy object &1 &2 remains in system | The short text describes the object sufficiently | |
208 | 207 | Inconsistency for proxy objects remains in system | Space: object requires documentation | |
209 | 208 | Consumer proxy &1 &2 uses old base class. Please activate proxy. | Space: object requires documentation | |
210 | 209 | xml namespace is changed for message &1 | Space: object requires documentation | |
211 | 210 | Simple transformation | The short text describes the object sufficiently | |
212 | 211 | XSLT transformation | The short text describes the object sufficiently | |
213 | 212 | Method &1 of Class &2 | The short text describes the object sufficiently | |
214 | 213 | Method &1 of Interface &2 | The short text describes the object sufficiently | |
215 | 214 | Exception class &1 | The short text describes the object sufficiently | |
216 | 215 | Trans: &1(A2X), &2(X2A) &3 &4 | The short text describes the object sufficiently | |
217 | 216 | No errors occurred | The short text describes the object sufficiently | |
218 | 217 | Errors occurred | The short text describes the object sufficiently | |
219 | 218 | Result contains errors &1 &2 &3 &4 | The short text describes the object sufficiently | |
220 | 219 | There are orphaned transformations for &1 types | The short text describes the object sufficiently | |
221 | 220 | Orphaned transformations for &1 types have been deleted | The short text describes the object sufficiently | |
222 | 221 | Deleted transformations for type &1 | The short text describes the object sufficiently | |
223 | 222 | Found &1 transformations without version information | The short text describes the object sufficiently | |
224 | 223 | Deleted transformations &1 | The short text describes the object sufficiently | |
225 | 224 | &1 transformations without version information have been deleted | The short text describes the object sufficiently | |
226 | 225 | Proxy generation for namespace &1 not permitted in this system. | The short text describes the object sufficiently | |
227 | 226 | &1 transformations have been deleted | The short text describes the object sufficiently | |
228 | 227 | Object has been changed: Save and activate before transporting | The short text describes the object sufficiently | |
229 | 228 | Missing namespace declaration for &1 in path &1&2&3 | The short text describes the object sufficiently | |
230 | 229 | Names problems occured, names adjusted. See name problems sheet. | Space: object requires documentation | |
231 | 230 | Deletion of TADIR entry of proxy object &1 &2 was unsuccessful | The short text describes the object sufficiently | |
232 | 231 | No GTADIR available | The short text describes the object sufficiently | |
233 | 232 | GTADIR cannot be accesed | The short text describes the object sufficiently | |
234 | 233 | No entry in GTADIR for &1&2&2&4 | The short text describes the object sufficiently | |
235 | 234 | No entry in GTADIR for pgmid: &1 object: &2 name: &3 | The short text describes the object sufficiently | |
236 | 235 | Entry in GTADIR for &1&2&2&4 already exists | The short text describes the object sufficiently | |
237 | 236 | Unknown GTADIR type &1 | The short text describes the object sufficiently | |
238 | 237 | Proxy key for &1 &2 successfully entered into GTADIR | The short text describes the object sufficiently | |
239 | 238 | Proxy key for &1 &2 cannot be entered into GTADIR (conflict with &3 &4) | Space: object requires documentation | |
240 | 239 | Storing Proxy Keys into GTADIR | The short text describes the object sufficiently | |
241 | 240 | Skip storing Proxy Keys into GTADIR (no GTADIR) | The short text describes the object sufficiently | |
242 | 241 | Storing Proxy Keys into GTADIR failed (no GTADIR access) | Space: object requires documentation | |
243 | 242 | Proxy key for &1 &2 is already in GTADIR | The short text describes the object sufficiently | |
244 | 243 | class &1 does not exist or is not active | The short text describes the object sufficiently | |
245 | 244 | same message for fault and in/out parameter is not supported | The short text describes the object sufficiently | |
246 | 245 | Cannot display query | The short text describes the object sufficiently | |
247 | 246 | Package of proxy is not transport relevant | The short text describes the object sufficiently | |
248 | 247 | object &1 &2 was &3 | The short text describes the object sufficiently | |
249 | 248 | Proxy key for &1 &2 is consistent with GTADIR | The short text describes the object sufficiently | |
250 | 249 | Proxy key for &1 &2 conflicts with &3 &4 | The short text describes the object sufficiently | |
251 | 250 | Checks concerning repository are skipped (repository is not available). | The short text describes the object sufficiently | |
252 | 251 | Object has error(s) in ESR. Please eliminate it. | Space: object requires documentation | |
253 | 252 | Error when getting a package for object &1 &2 | The short text describes the object sufficiently | |
254 | 253 | IFR_HTTP_DEST should not be set in table SPROXSET (->long text). | Space: object requires documentation | |
255 | 254 | IFR_HTTP_DEST should not be set in table SPROXSET (->long text). | Space: object requires documentation | |
256 | 255 | Log existing, for details see menue Goto/Show Log | The short text describes the object sufficiently | |
257 | 256 | Message '&1' in namespace '&2' is not unique in WSDL document. | The short text describes the object sufficiently | |
258 | 257 | Initial value is not a valid name | The short text describes the object sufficiently | |
259 | 258 | Method is not part of the interface to be called. | The short text describes the object sufficiently | |
260 | 259 | XML is well-formed. | The short text describes the object sufficiently | |
261 | 260 | &1 &2 exists in TADIR only, but not in &3 or SPROXHDR | The short text describes the object sufficiently | |
262 | 261 | Check &1 in TADIR:&2 objects not found in DDIC- or proxy metadata | The short text describes the object sufficiently | |
263 | 262 | Check orphaned SPROXDAT entries:&1 entries without entry in SPROXHDR | The short text describes the object sufficiently | |
264 | 263 | Object: &1 &2 &3 &4 has no corresponding entry in SPROXHDR | The short text describes the object sufficiently | |
265 | 264 | Mode &1 for Object &2 &3 | The short text describes the object sufficiently | |
266 | 265 | Please specify the method to be called | The short text describes the object sufficiently | |
267 | 266 | System in "Restricted Object Editing" mode! | Space: object requires documentation | |
268 | 267 | no active data for object &1 &2 | Space: object requires documentation | |
269 | 268 | CALL TRANFORMATION error for object &1 &2 | The short text describes the object sufficiently | |
270 | 269 | Proxy generation terminated: extension of xsd:anyType is not supported | Space: object requires documentation | |
271 | 270 | Ambigious hashID:&1 Type:&2 Name:&3 Namespace:&4 | Space: object requires documentation | |
272 | 271 | Generated object (type:name) &1:&2 not found in proxy metadata | The short text describes the object sufficiently | |
273 | 272 | Generated object (type:name) &1&2 not found in proxy table SPROXDAT | The short text describes the object sufficiently | |
274 | 273 | &1 &2 exists in TADIR only, but not in &3 or SPROXHDR | The short text describes the object sufficiently | |
275 | 274 | Number of table rows differs: &1[&2] <-> &3[&4] | The short text describes the object sufficiently | |
276 | 275 | Number of table lines equal: &1[&2] <-> &3[&4] | The short text describes the object sufficiently | |
277 | 276 | Unable to find component &1 | The short text describes the object sufficiently | |
278 | 277 | User &1 has no authorization (&2) in this system | The short text describes the object sufficiently | |
279 | 278 | Import overwrites any existing metadata | Space: object requires documentation | |
280 | 279 | Test: &1 not in proxy metadata. &2 &3 found in DDIC | The short text describes the object sufficiently | |
281 | 280 | Please use the 'edit' mode in SPROXY. | The short text describes the object sufficiently | |
282 | 281 | DDIC object (type:name) &1&2 found in proxy metadata | The short text describes the object sufficiently | |
283 | 282 | No inconsistencies found | The short text describes the object sufficiently | |
284 | 283 | Check &1 in TADIR:&2 objects not found in DDIC- or proxy metadata | The short text describes the object sufficiently | |
285 | 284 | Check orphaned SPROXDAT entries:&1 entries without entry in SPROXHDR | The short text describes the object sufficiently | |
286 | 285 | Object: &1 &2 &3 &4 has no corresponding entry in SPROXHDR | The short text describes the object sufficiently | |
287 | 286 | Successful with empty result - commit may be required | Space: object requires documentation | |
288 | 287 | Operation &1 does not exist | The short text describes the object sufficiently | |
289 | 288 | Port &1 does not exist | The short text describes the object sufficiently | |
290 | 289 | new package of &3 &4 has different software component (old: &1 new: &2) | Space: object requires documentation | |
291 | 290 | Check inconsistent inline types:&1 entries without main entry in sproxhdr | The short text describes the object sufficiently | |
292 | 291 | Main Object: &1 &2 for proxy &3 &4 not found in SPROXHDR | The short text describes the object sufficiently | |
293 | 292 | package &1 is a SAP package, object &2 is in customer namespace | The short text describes the object sufficiently | |
294 | 293 | Package &1 is a customer package, object &2 is in SAP namespace | Space: object requires documentation | |
295 | 294 | Check not possible for Proxy &1 &2 | Space: object requires documentation | |
296 | 295 | Multiple SWCVs for object (type name namespace SWCV): &1 &2 &3 &4 | The short text describes the object sufficiently | |
297 | 296 | Variant creation not possible; inbound interface is not service enabled | The short text describes the object sufficiently | |
298 | 297 | Creation of service definition failed | The short text describes the object sufficiently | |
299 | 298 | Invalid field value | Space: object requires documentation | |
300 | 299 | SUPPRESS_DIALOG set for transportable package but no TRANSPORT_NUMBER | Space: object requires documentation | |
301 | 300 | The logical transport object SPRX &1 is missed in the transport request. | Space: object requires documentation | |
302 | 301 | Insert of object R3TR SPRX &1 into transport request is cancelled. | Space: object requires documentation | |
303 | 302 | DDIC-Object &1 &2 not activated. | The short text describes the object sufficiently | |
304 | 303 | Object R3TR &1 &2 is added to the transport request. | The short text describes the object sufficiently | |
305 | 304 | Proxy object R3TR &1 &2 is missed in the transport request. | Space: object requires documentation | |
306 | 305 | Insert of object R3TR &1 &2 into transport request is cancelled. | Space: object requires documentation | |
307 | 306 | Object R3TR &1 &2 is missed in the transport request. | Space: object requires documentation | |
308 | 307 | There are more than one 'auto-generated' WS definition for &1 &2. | Space: object requires documentation | |
309 | 308 | There is the 'auto-generated' WS definition &1 &2 for deleted &3 &4. | Space: object requires documentation | |
310 | 309 | Object SPRX &1 has wrong format | Space: object requires documentation | |
311 | 310 | Service Variant &1 not found | The short text describes the object sufficiently | |
312 | 311 | optional field &1 has been added to type &2 | The short text describes the object sufficiently | |
313 | 312 | mandatory field &1 has been added to type &2 | The short text describes the object sufficiently | |
314 | 313 | operation &1 has been added to service | The short text describes the object sufficiently | |
315 | 314 | Value must be specified for field &1 | The short text describes the object sufficiently | |
316 | 315 | unknown attribute &1 with mustUnderstand ="true" in wsdl | The short text describes the object sufficiently | |
317 | 316 | Configuration profiles have changed | The short text describes the object sufficiently | |
318 | 317 | Variant inconsistent: web service definition missing | The short text describes the object sufficiently | |
319 | 318 | event not possible for synchronous methods | The short text describes the object sufficiently | |
320 | 319 | Change from event proxy to consumer proxy or vice versa is impossible | The short text describes the object sufficiently | |
321 | 320 | SWCs of Proxy &1 &2 are different in backend and repository: &3 and &4 | Space: object requires documentation | |
322 | 321 | Actuality of Proxy &1 &2 cannot be checked, because repository is down. | Space: object requires documentation | |
323 | 322 | Field is also used in response | Space: object requires documentation | |
324 | 323 | hidden field &1 in type &2 has been made mandatory or has illegal state | The short text describes the object sufficiently | |
325 | 324 | base service not released, variant creation not possible | The short text describes the object sufficiently | |
326 | 325 | Base service interface inactive, variant creation not possible | The short text describes the object sufficiently | |
327 | 326 | Service has no active version | The short text describes the object sufficiently | |
328 | 327 | Variant has no web service definition and must be deleted | The short text describes the object sufficiently | |
329 | 328 | Invalid URN Namespace: &1 Reason: &2 &3 &4 | Space: object requires documentation | |
330 | 329 | Service Variant created (Name/Namespace/ABAP Name):&1/&2/&3 | The short text describes the object sufficiently | |
331 | 330 | Proxy &1 &2 does not exist for the 'auto-generated' WS definition &3 &4. | The short text describes the object sufficiently | |
332 | 331 | Variant creation not possible for external definitions | The short text describes the object sufficiently | |
333 | 332 | There is a visible mandatory subfield->hidden state not allowed | The short text describes the object sufficiently | |
334 | 333 | state &1 not possible | Space: object requires documentation | |
335 | 334 | State 'hidden' always with fixed value propagation for leaf elements | The short text describes the object sufficiently | |
336 | 335 | Proxy &1 &2: Package &3 is not a Subpackage of &4 | The short text describes the object sufficiently | |
337 | 336 | state 'visible' not possible | Space: object requires documentation | |
338 | 337 | Object with this q-name exists already in &1 with base service &2 | The short text describes the object sufficiently | |
339 | 338 | message part refers a type, not an element | The short text describes the object sufficiently | |
340 | 339 | namespace &1 is not assigned to ESR-> generation not possible | Space: object requires documentation | |
341 | 340 | namespace &1 is not assigned to MDR-> creation as MDR proxy not possible | Space: object requires documentation | |
342 | 341 | TADIR entries for proxy &1/&2 inconsistent, missing proxy &3/&4 | Space: object requires documentation | |
343 | 342 | TADIR entries for proxy &1/&2 inconsistent, missing SPRX &3/&4 | Space: object requires documentation | |
344 | 343 | TADIR entries for proxy &1/&2 inconsistent, field: TADIR-&3 value:&4 | Space: object requires documentation | |
345 | 344 | TADIR for proxy &1/&2 is consistent | The short text describes the object sufficiently | |
346 | 345 | namespace &1 is not editable | The short text describes the object sufficiently | |
347 | 346 | &1 is for generated objects only | Space: object requires documentation | |
348 | 347 | Notifying runtime for object &1 &2 | The short text describes the object sufficiently | |
349 | 348 | Test ID is initial and not editable | The short text describes the object sufficiently | |
350 | 349 | Error in check before release, for details see longtext. | Space: object requires documentation | |
351 | 350 | Code Inspector is cancelled. | The short text describes the object sufficiently | |
352 | 351 | Delete transformations for &1 &2 | The short text describes the object sufficiently | |
353 | 352 | Delete transformation &1 | The short text describes the object sufficiently | |
354 | 353 | Main object or subobject of an external definition can not be migrated | The short text describes the object sufficiently | |
355 | 354 | Main object of an inline type. Inline type first have to be converted. | The short text describes the object sufficiently | |
356 | 355 | Inline type can not be migrated. First convert inline to global type. | The short text describes the object sufficiently | |
357 | 356 | Operation &1 does not have an request message | Space: object requires documentation | |
358 | 357 | Table type ESR key &1 &2 has to be adjusted to &3 &4 | Space: object requires documentation | |
359 | 358 | &1 &2 activated with errors for dependend objects (Details -> DDIC log) | The short text describes the object sufficiently | |
360 | 359 | Message type &1 has an invalid split path: &2 | Space: object requires documentation | |
361 | 360 | Table[Line]: &1 field:&2 actual:'&3' not equal to target:'&4' | The short text describes the object sufficiently | |
362 | 361 | Proxy inconsistent | The short text describes the object sufficiently | |
363 | 362 | Proxy &1/&2 is assigned to package &3 but has to be assigned to &4 | Space: object requires documentation | |
364 | 363 | File does not contain a definition of type &1 | The short text describes the object sufficiently | |
365 | 364 | The value '&1' does not match the value present in your file (&2) | The short text describes the object sufficiently | |
366 | 365 | The semantic contract referenced in the file does not match your choice | The short text describes the object sufficiently | |
367 | 366 | The file you are trying to upload is not a valid model definition file | The short text describes the object sufficiently | |
368 | 367 | Proxy is up to date | The short text describes the object sufficiently | |
369 | 368 | Runtime test is not available for objects of type &1 | The short text describes the object sufficiently | |
370 | 369 | Name &1 reserved | The short text describes the object sufficiently | |
371 | 370 | Incompatible variant change | The short text describes the object sufficiently | |
372 | 371 | Service Interface &1 &2 has no active operations | The short text describes the object sufficiently | |
373 | 372 | Object inconsistent &1/&2 because refered Object &3/&4 was not found | The short text describes the object sufficiently | |
374 | 373 | Fault messages of operation &1 are not unique | The short text describes the object sufficiently | |
375 | 374 | XML offset &1, XML path &2&3&4 | The short text describes the object sufficiently | |
376 | 375 | Main program &1, program &2, line &3 | The short text describes the object sufficiently | |
377 | 376 | Proxy &1 &2 &3 must not be changed (ZDM upgrade running) | The short text describes the object sufficiently | |
378 | 400 | Errormessages for Checks 400 - 499 | The short text describes the object sufficiently | |
379 | 401 | SPROXY/DDIC: Structure &1 Number of fields are different &2/&3 | The short text describes the object sufficiently | |
380 | 402 | SPROXY/DDIC: Structure &1 Field &2 does not exist in DDIC | The short text describes the object sufficiently | |
381 | 403 | SPROXY/DDIC: Structure &1 Field &2 Different fieldnames &3/&4 | The short text describes the object sufficiently | |
382 | 404 | SPROXY/DDIC: Structure &1 Field &2 Different datatypes &3/&4 | The short text describes the object sufficiently | |
383 | 405 | SPROXY/DDIC: Structure &1 Field &2 Different length &3/&4 | The short text describes the object sufficiently | |
384 | 406 | SPROXY/DDIC: Structure &1 Field &2 Different decimals &3/&4 | The short text describes the object sufficiently | |
385 | 407 | SPROXY/DDIC: Structure &1 is not active | The short text describes the object sufficiently | |
386 | 408 | SPROXY/DDIC: Dataelement &1 is not active | The short text describes the object sufficiently | |
387 | 409 | SPROXY/DDIC: Tabletype &1 is not active | The short text describes the object sufficiently | |
388 | 410 | SPROXY/DDIC: Dataelement &1 Different names &2/&3 | The short text describes the object sufficiently | |
389 | 411 | SPROXY/DDIC: Dataelement &1 Different datatypes &2/&3 | The short text describes the object sufficiently | |
390 | 412 | SPROXY/DDIC: Dataelement &1 Different length &2/&3 | The short text describes the object sufficiently | |
391 | 413 | SPROXY/DDIC: Dataelement &1 Different decimals &2/&3 | The short text describes the object sufficiently | |
392 | 414 | SPROXY/DDIC: Structure &1 Field &2 Different component type &3/&4 | The short text describes the object sufficiently | |
393 | 450 | &1 &2: Number of methods are different &3/&4 | The short text describes the object sufficiently | |
394 | 451 | Method &1, Parameter &2: Types are different &3/&4 | The short text describes the object sufficiently | |
395 | 452 | Method &1: Parameter &2 not found in class library | The short text describes the object sufficiently | |
396 | 453 | Method &1: Exception &2 not found in class library | The short text describes the object sufficiently | |
397 | 454 | &1 &2: Method &3 not found in class library | The short text describes the object sufficiently | |
398 | 455 | Method &1: Number of parameters are different &2/&3 | The short text describes the object sufficiently | |
399 | 456 | Check cannot be executed | The short text describes the object sufficiently | |
400 | 460 | IDOC-WSDL must only be used as external WSDL | The short text describes the object sufficiently | |
401 | 461 | IDOC-WSDL must define one operation | The short text describes the object sufficiently | |
402 | 462 | Operation in IDOC-WSDL must have request and response and no fault | The short text describes the object sufficiently | |
403 | 463 | Messages within IDOC-WSDL must be in namesapce &1 | The short text describes the object sufficiently | |
404 | 464 | IDoc WSDL is not supported | The short text describes the object sufficiently | |
405 | 465 | Reserved namespace &1 not supported | The short text describes the object sufficiently | |
406 | 499 | Repository not available | The short text describes the object sufficiently | |
407 | 500 | No connection to exchange profile or address-logindata are missing | The short text describes the object sufficiently | |
408 | 501 | Requested Repository is down. | The short text describes the object sufficiently | |
409 | 502 | User has no authorization to read objects in the Repository | The short text describes the object sufficiently | |
410 | 503 | Error occurs during the processing of the request on Repository server | The short text describes the object sufficiently | |
411 | 504 | Error occurs on Repository server during calculation of the wsdl | The short text describes the object sufficiently | |
412 | 505 | Unable to determine SWCV for &1 . | The short text describes the object sufficiently | |
413 | 506 | Invalid HTTP-destination. | The short text describes the object sufficiently | |
414 | 803 | Value '&1' is not a valid text ID (too long) | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 620 |