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