| SPRX310 |
Service Variant &1 not found |
| SPRX311 |
optional field &1 has been added to type &2 |
| SPRX312 |
mandatory field &1 has been added to type &2 |
| SPRX313 |
operation &1 has been added to service |
| SPRX314 |
Value must be specified for field &1 |
| SPRX315 |
unknown attribute &1 with mustUnderstand ="true" in wsdl |
| SPRX316 |
Configuration Profiles have changed |
| SPRX317 |
Variant inconsistent: WebService Definition missing |
| SPRX318 |
event not possible for synchronous methods |
| SPRX319 |
Change from event proxy to client proxy or vice versa is impossible |
| SPRX320 |
SWCs of Proxy &1 &2 are different in BackEnd and Repository: &3 and &4 |
| SPRX321 |
Actuality of Proxy &1 &2 cannot be checked, because Repository is down. |
| SPRX322 |
Field is also used in response |
| SPRX323 |
hidden field &1 in type &2 has been made mandatory or has illegal state |
| SPRX324 |
base service not released, variant creation not possible |
| SPRX325 |
Base service interface inactive, variant creation not possible |
| SPRX326 |
Service has no active version |
| SPRX327 |
Variant has no Web Service Definition and must be deleted |
| SPRX328 |
Invalid URN Namespace: &1 Reason: &2 &3 &4 |
| SPRX329 |
Service Variant created (Name/Namespace/ABAP Name):&1/&2/&3 |
| SPRX331 |
Variant creation not possible for external definitions |
| SPRX332 |
There is a visible mandatory subfield->hidden state not allowed |
| SPRX333 |
state &1 not possible |
| SPRX334 |
State 'Hidden' always with fixed value propagation for leaf elements |
| SPRX335 |
Proxy &1 &2: Package &3 is not a Subpackage of &4 |
| SPRX336 |
state 'Visible' not possible |
| SPRX337 |
Object with this q-name exists already in &1 with base service &2 |
| SPRX338 |
message part refers a type, not an element |
| SPRX341 |
TADIR entries for proxy &1/&2 inconsistent, missing proxy &3/&4 |
| SPRX342 |
TADIR entries for proxy &1/&2 inconsistent, missing SPRX &3/&4 |
| SPRX343 |
TADIR entries for proxy &1/&2 inconsistent, field: TADIR-&3 value:&4 |
| SPRX344 |
TADIR for proxy &1/&2 is consistent |
| SPRX349 |
Error in check before release, for details see longtext. |
| SPRX350 |
Code Inspector is cancelled. |
| SPRX356 |
Operation &1 does not have an request message |
| SPRX400 |
Errormessages for Checks 400 - 499 |
| SPRX401 |
SPROXY/DDIC: Structure &1 Number of fields are different &2/&3 |
| SPRX402 |
SPROXY/DDIC: Structure &1 Field &2 does not exist in DDIC |
| SPRX403 |
SPROXY/DDIC: Structure &1 Field &2 Different fieldnames &3/&4 |
| SPRX404 |
SPROXY/DDIC: Structure &1 Field &2 Different datatypes &3/&4 |
| SPRX405 |
SPROXY/DDIC: Structure &1 Field &2 Different length &3/&4 |
| SPRX406 |
SPROXY/DDIC: Structure &1 Field &2 Different decimals &3/&4 |
| SPRX407 |
SPROXY/DDIC: Structure &1 is not active |
| SPRX408 |
SPROXY/DDIC: Dataelement &1 is not active |
| SPRX409 |
SPROXY/DDIC: Tabletype &1 is not active |
| SPRX410 |
SPROXY/DDIC: Dataelement &1 Different names &2/&3 |
| SPRX411 |
SPROXY/DDIC: Dataelement &1 Different datatypes &2/&3 |
| SPRX412 |
SPROXY/DDIC: Dataelement &1 Different length &2/&3 |
| SPRX413 |
SPROXY/DDIC: Dataelement &1 Different decimals &2/&3 |
| SPRX414 |
SPROXY/DDIC: Structure &1 Field &2 Different component type &3/&4 |
| SPRX450 |
&1 &2: Number of methods are different &3/&4 |
| SPRX451 |
Method &1, Parameter &2: Types are different &3/&4 |
| SPRX452 |
Method &1: Parameter &2 not found in class library |
| SPRX453 |
Method &1: Exception &2 not found in class library |
| SPRX454 |
&1 &2: Method &3 not found in class library |
| SPRX455 |
Method &1: Number of parameters are different &2/&3 |
| SPRX456 |
Check cannot be executed |
| SPRX500 |
No connection to exchange profile or address-logindata are missing |
| SPRX501 |
Requested Repository is down. |
| SPRX502 |
User has no authorization to read objects in the Repository |
| SPRX503 |
Error occurs during the processing of the request on Repository server |
| SPRX504 |
Error occurs on Repository server during calculation of the wsdl |
| SPRX505 |
Unable to determine SWCV for &1 . |
| SPRX506 |
Invalid HTTP-destination. |
| SPRX800 |
No implementation found for &1 &2 &3 |
| SPRX801 |
Destroyed header data |
| SPRX802 |
Tag &1 not found |
| SPRX803 |
Value '&1' is not a valid text ID (too long) |
| SPR_BI_MESSAGES000 |
Input: &1 lines of data |
| SPR_BI_MESSAGES001 |
Begin loading &1 lines of data by generic dataloader |
| SPR_BI_MESSAGES002 |
End of data loading by generic dataloader |
| SPR_BI_MESSAGES003 |
Start of business partner data load |
| SPR_BI_MESSAGES004 |
Start of system status data load |
| SPR_BI_MESSAGES005 |
End of business partner data load |
| SPR_BI_MESSAGES006 |
End of system status data load |
| SPR_BI_MESSAGES007 |
Start of component hierarchy processing |
| SPR_BI_MESSAGES008 |
End of component hierarchy processing |
| SPR_BI_MESSAGES009 |
Start of masterdata processing |
| SPR_BI_MESSAGES010 |
End of masterdata processing |
| SPR_BI_MESSAGES011 |
Start of extending unchanged data |
| SPR_BI_MESSAGES012 |
End of extending unchanged data |
| SPR_BI_MESSAGES013 |
Extend date is initial |
| SPR_BI_MESSAGES014 |
Found &1 message entries to extend |
| SPR_BI_MESSAGES015 |
Extending message state validity till date: &1, time: &2 |
| SPR_BI_MESSAGES016 |
&1 lines of data created, starting data load |
| SPR_BI_MESSAGES017 |
Error occured while processing message with GUID &1 |
| SPR_BI_MESSAGES018 |
Start of multilevel categories data load |
| SPR_BI_MESSAGES019 |
End of multilevel categories data load |
| SPTA001 |
& & & & |
| SPTA002 |
Enter a server group for parallel processing |
| SPTA003 |
Error during parallel processing of object &1 (see long text) |
| SPTA004 |
Server group &1 does not exist or has too few resources |
| SPTA005 |
No resources available for server group &v1 |
| SPTA006 |
Error during parallel processing (->long text) |
| SPTA007 |
Error in initialization of parallel processing (see long text) |
| SPTA008 |
Parallel processing terminated due to too many errors |
| SPTA020 |
Parallel processing has been started with &1 work processes |
| SPTA021 |
Parallel Processing has been completed |
| SPTV001 |
SAP IDs must start with a letter other than Y or Z |
| SPTV002 |
Customer-specific names (IDs) must start with Y, Z, or special character |