Id | Title |
---|---|
SPRX195 | Object(type|name|namespace) from other namespace missing: &1|&2|&3 |
SPRX196 | Object(type|name|namespace) from other namespace must be changed &1|&2|&3 |
SPRX197 | The Name '&1...&2' is too long, max. length is &3 character |
SPRX198 | No proxy object exists for business object &1 &2 to be enhanced |
SPRX199 | Direction was changed. Regeneration not possible, only deletion. |
SPRX200 | Unable to determine proxy object from transport object &1 &2 |
SPRX201 | No proxy inconsistency for transport object &1 &2 |
SPRX202 | Deletion of proxy object &1 &2 was unsuccessful |
SPRX203 | Inconsistency for transport object &1 &2 corrected |
SPRX204 | Transport object &1 &2 has inconsistency |
SPRX205 | Proxy object &1 &2 deleted |
SPRX206 | Proxy object &1 &2 remains in system |
SPRX207 | Inconsistency for proxy objects remains in system |
SPRX208 | Consumer proxy &1 &2 uses old base class.Regenerate proxy,if it possible. |
SPRX209 | xml namespace is changed for message &1 |
SPRX210 | Simple Transformation |
SPRX211 | XSLT Transformation |
SPRX212 | Method &1 of Class &2 |
SPRX213 | Method &1 of Interface &2 |
SPRX214 | Exception Class &1 |
SPRX215 | Trans: &1(A2X), &2(X2A) &3 &4 |
SPRX216 | No errors occurred |
SPRX217 | Errors occurred |
SPRX218 | Result contains errors &1 &2 &3 &4 |
SPRX219 | There are orphaned transformations for &1 types |
SPRX220 | Orphaned transformations for &1 types have been deleted |
SPRX221 | Deleted transformations for type &1 |
SPRX222 | Found &1 transformations without version information |
SPRX223 | Deleted transformations &1 |
SPRX224 | &1 transformations without version information have been deleted |
SPRX225 | Proxy generation for namespace &1 not permitted in this system. |
SPRX226 | &1 transformations have been deleted |
SPRX227 | Object has been changed: Save and activate before transporting |
SPRX228 | Missing namespace declaration for &1 in path &1&2&3 |
SPRX229 | Names problems occured, names adjusted. See name problems sheet. |
SPRX230 | Deletion of TADIR entry of proxy object &1 &2 was unsuccessful |
SPRX231 | No GTADIR available |
SPRX232 | GTADIR cannot be accesed |
SPRX233 | No entry in GTADIR for &1&2&2&4 |
SPRX234 | No entry in GTADIR for pgmid: &1 object: &2 name: &3 |
SPRX235 | Entry in GTADIR for &1&2&2&4 already exists |
SPRX236 | Unknown GTADIR type &1 |
SPRX237 | Proxy key for &1 &2 successfully entered into GTADIR |
SPRX238 | Proxy key for &1 &2 cannot be entered into GTADIR (conflict with &3 &4) |
SPRX239 | Storing Proxy Keys into GTADIR |
SPRX240 | Skip storing Proxy Keys into GTADIR (no GTADIR) |
SPRX241 | Storing Proxy Keys into GTADIR failed (no GTADIR access) |
SPRX242 | Proxy key for &1 &2 is already in GTADIR |
SPRX243 | class &1 does not exist or is not active |
SPRX244 | same message for fault and in/out parameter is not supported |
SPRX245 | Cannot display query |
SPRX246 | Package of proxy is not transport relevant |
SPRX247 | object &1 &2 was activated |
SPRX248 | Proxy key for &1 &2 is consistent with GTADIR |
SPRX249 | Proxy key for &1 &2 conflicts with &3 &4 |
SPRX250 | Checks concerning Repository are skipped (Repository is not available). |
SPRX251 | Object has error(s) in ESR. Please eliminate it. |
SPRX252 | Error when getting a package for object &1 &2 |
SPRX253 | IFR_HTTP_DEST should not be set in table SPROXSET (->long text). |
SPRX254 | IFR_HTTP_DEST should not be set in table SPROXSET (->long text). |
SPRX255 | Log existing, for details see menue Goto/Show Log |
SPRX256 | Message '&1' in namespace '&2' is not unique in WSDL. |
SPRX257 | Initial value is not a valid name |
SPRX258 | Method is not part of the interface to be called. |
SPRX259 | XML is well-formed. |
SPRX260 | &1 &2 exists in TADIR only, but not in &3 or SPROXHDR |
SPRX261 | Check &1 in TADIR:&2 objects not found in DDIC- or proxy metadata |
SPRX262 | Check orphaned SPROXDAT entries:&1 entries without entry in SPROXHDR |
SPRX263 | Object: &1 &2 &3 &4 has no corresponding entry in SPROXHDR |
SPRX264 | Mode &1 for Object &2 &3 |
SPRX265 | Please specify the method to be called |
SPRX266 | System in "Restricted Object Editing" mode! |
SPRX268 | call transformation error for object &1 &2 |
SPRX269 | Proxy generation terminated: extension of xsd:anyType is not supported |
SPRX276 | Unable to find component &1 |
SPRX280 | Please use the 'Change' mode in SPROXY. |
SPRX286 | Successful with empty result - commit may be required |
SPRX287 | Operation &1 does not exist |
SPRX288 | Port &1 does not exist |
SPRX289 | new package of &3 &4 has different software component (old: &1 new: &2) |
SPRX290 | Check inconsistent inline types:&1 entries without main entry in sproxhdr |
SPRX291 | Main Object: &1 &2 for proxy &3 &4 not found in SPROXHDR |
SPRX292 | package &1 is a SAP package, object &2 is in customer namespace |
SPRX293 | package &1 is a customer package, object &2 is in SAP namespace |
SPRX294 | Check not possible for Proxy &1 &2 |
SPRX295 | Multiple SWCVs for Object (Type Name Namespace SWCV): &1 &2 &3 &4 |
SPRX296 | Variant creation not possible;inbound interface is not service enabled |
SPRX297 | Creation of Service Definition failed |
SPRX298 | Invalid field value |
SPRX299 | SUPPRESS_DIALOG set for transportable package but no TRANSPORT_NUMBER |
SPRX300 | The logical transport object SPRX &1 is missed in the transport request. |
SPRX301 | Insert of object R3TR SPRX &1 into transport request is cancelled. |
SPRX302 | DDIC-Object &1 &2 not activated. |
SPRX303 | Object R3TR &1 &2 is added to the transport request. |
SPRX304 | Proxy object R3TR &1 &2 is missed in the transport request. |
SPRX305 | Insert of object R3TR &1 &2 into transport request is cancelled. |
SPRX306 | Object R3TR &1 &2 is missed in the transport request. |
SPRX307 | There are more than one 'auto-generated' WS definition for &1 &2. |
SPRX308 | There is the 'auto-generated' WS definition &1 &2 for deleted &3 &4. |
SPRX309 | Object SPRX &1 has wrong format |