SAP ABAP Message Class SPXN (Proxy Generation)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DWB-PRX (Application Component) Proxy Generation
⤷ SAI_PROXY_GENTIME_MDR (Package) Proxy Generation Meta Data Repository
⤷ BC-DWB-PRX (Application Component) Proxy Generation
⤷ SAI_PROXY_GENTIME_MDR (Package) Proxy Generation Meta Data Repository
Attributes
Message class | SPXN | |
Short Description | Proxy Generation | |
Changed On | 20140121 | |
Last Changed At | 103800 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 001 | Data is invalid, &1 is no valid value for &2. | The short text describes the object sufficiently | |
3 | 002 | Object is invalid or inconsistent | The short text describes the object sufficiently | |
4 | 003 | Object &1 &2 is invalid | The short text describes the object sufficiently | |
5 | 004 | Object &1 &2 &3 is invalid | The short text describes the object sufficiently | |
6 | 005 | Object cannot be locked | The short text describes the object sufficiently | |
7 | 006 | Node is inconsistent | The short text describes the object sufficiently | |
8 | 007 | ABAP name is not set | The short text describes the object sufficiently | |
9 | 008 | Type is not set (xsd type or type reference) | The short text describes the object sufficiently | |
10 | 009 | Type reference is not set | The short text describes the object sufficiently | |
11 | 010 | Access to obsolete node was rejected | The short text describes the object sufficiently | |
12 | 011 | Read only data, cannot be changed | The short text describes the object sufficiently | |
13 | 012 | Switch not possible | The short text describes the object sufficiently | |
14 | 013 | Node cannot be deleted | The short text describes the object sufficiently | |
15 | 014 | Error occurred | The short text describes the object sufficiently | |
16 | 015 | Call of &1 not allowed for this object | The short text describes the object sufficiently | |
17 | 016 | Generating application &1 for namespace &2 not allowed | The short text describes the object sufficiently | |
18 | 017 | '&1' is not valid for '&2'. Expected values: &3 | The short text describes the object sufficiently | |
19 | 018 | Required operation with pattern &1 missing for interface with pattern &2 | The short text describes the object sufficiently | |
20 | 019 | Request missing | The short text describes the object sufficiently | |
21 | 020 | Response missing | The short text describes the object sufficiently | |
22 | 021 | No response allowed | The short text describes the object sufficiently | |
23 | 022 | Asynchronous operation must not have any faults | The short text describes the object sufficiently | |
24 | 023 | Obligatory attribute &1 missing for representation term &2 | The short text describes the object sufficiently | |
25 | 024 | Attribute &1 unknown for representation term &2 | The short text describes the object sufficiently | |
26 | 025 | Wrong type &1 for attribute &2/ type of representation term &3 | The short text describes the object sufficiently | |
27 | 026 | Idempotency only allowed for synchronous method in non-TUCC interface | The short text describes the object sufficiently | |
28 | 027 | Wrong representation term &1 for attribute &2 of representation term &3 | The short text describes the object sufficiently | |
29 | 028 | Value '&1' for facet &2 for type/attribute &3 not allowed (repterm &4) | The short text describes the object sufficiently | |
30 | 029 | First character '&1' of '&2' is invalid; only a(A)-z(Z) permitted | The short text describes the object sufficiently | |
31 | 030 | '&1' contains invalid character '&2'; only a(A)-z(Z), 0-9, "_" permitted | The short text describes the object sufficiently | |
32 | 031 | Qualified name '&1' is invalid; contains not permitted characters | The short text describes the object sufficiently | |
33 | 032 | Qualified name invalid; '&1' too long | The short text describes the object sufficiently | |
34 | 033 | Object has a warning | The short text describes the object sufficiently | |
35 | 034 | Method &1 of class &2 is not a method of a consumer proxy | The short text describes the object sufficiently | |
36 | 035 | Source method not set within mapping | The short text describes the object sufficiently | |
37 | 036 | Mapping must either contain synchronous or asynchronous methods | The short text describes the object sufficiently | |
38 | 037 | Asynchronous mapping must have at least one target method | The short text describes the object sufficiently | |
39 | 038 | Synchronous mapping must have exactly one target method | The short text describes the object sufficiently | |
40 | 039 | ABAP name '&1' is too long, max. &2 characters allowed | The short text describes the object sufficiently | |
41 | 040 | Consumer Mapping has no source class | The short text describes the object sufficiently | |
42 | 041 | Source method does not exist | The short text describes the object sufficiently | |
43 | 042 | Mapping target &1 inconsistent | The short text describes the object sufficiently | |
44 | 043 | Mapping missing for method &1 | The short text describes the object sufficiently | |
45 | 044 | Inline objects not supported: &1 | The short text describes the object sufficiently | |
46 | 045 | Ambiguous mapping for method &1 | The short text describes the object sufficiently | |
47 | 046 | Consumer class &1 does not exist | The short text describes the object sufficiently | |
48 | 047 | Append is dynamic, enhanced type isn't | The short text describes the object sufficiently | |
49 | 048 | Qualified name '&1' is invalid; namespace is initial | The short text describes the object sufficiently | |
50 | 049 | Enumeration value provider class only for data elements | Space: object requires documentation | |
51 | 050 | Object has no target method &1 &2 | The short text describes the object sufficiently | |
52 | 051 | Elements and Attributes of Enhancements must be optional | The short text describes the object sufficiently | |
53 | 052 | Base has different representation term &1 | The short text describes the object sufficiently | |
54 | 053 | Base has different xsd facets than restriction (check schema) | The short text describes the object sufficiently | |
55 | 054 | Activation of proxy not possible | The short text describes the object sufficiently | |
56 | 055 | Name &1 already used | The short text describes the object sufficiently | |
57 | 056 | Object &1 &2 already used | The short text describes the object sufficiently | |
58 | 057 | Request message &1 &2 occurs twice in interface | The short text describes the object sufficiently | |
59 | 058 | Attribute &1 of repr.term &2 must refer a global repr.term type | The short text describes the object sufficiently | |
60 | 059 | Facet &1 for type/attribute &2 not allowed (repterm &3) | The short text describes the object sufficiently | |
61 | 060 | You can't assign Service Consumer and RFC Consumer to the same mapping | The short text describes the object sufficiently | |
62 | 061 | Abap Length must be greater than xsd length | The short text describes the object sufficiently | |
63 | 062 | PortType {&2}&1 not found in WSDL | Space: object requires documentation | |
64 | 063 | PortType must be specified | Space: object requires documentation | |
65 | 064 | Change may result in inconsistent existing enhancements | Space: object requires documentation | |
66 | 065 | Error reading WSDL from &1 | The short text describes the object sufficiently | |
67 | 066 | This action is not allowed for an inactive object | The short text describes the object sufficiently | |
68 | 067 | Object must be saved and activated | The short text describes the object sufficiently | |
69 | 068 | Qname of table and linetype are identical | The short text describes the object sufficiently | |
70 | 069 | A default value can only be set for simple content elements | The short text describes the object sufficiently | |
71 | 070 | Referred type &1 &2 not found | The short text describes the object sufficiently | |
72 | 071 | Consumer Mapping is a single target mapping, but has targets &1 and &2 | The short text describes the object sufficiently | |
73 | 072 | Mapping is used in Consumer Mapping &1, this change is not possible | The short text describes the object sufficiently | |
74 | 073 | No direct mappings allowed for single target Consumer mappings | The short text describes the object sufficiently | |
75 | 074 | Can not use Package &1. | Space: object requires documentation | |
76 | 075 | Mode of source consumer different from mode of operation mapping | Space: object requires documentation | |
77 | 076 | Invalid xpath &1: &2 at pos &3 | Space: object requires documentation | |
78 | 077 | Invalid Split Path | Space: object requires documentation | |
79 | 078 | Invalid data; see previous error for further information | The short text describes the object sufficiently | |
80 | 079 | New value same as old value | The short text describes the object sufficiently | |
81 | 080 | The Processing Type Domain must have at least one processing type | The short text describes the object sufficiently | |
82 | 081 | This type is a helper type, change impossible | Space: object requires documentation | |
83 | 082 | The Semantic Contract must have exactly two actors | The short text describes the object sufficiently | |
84 | 083 | Wrong scope | Space: object requires documentation | |
85 | 084 | Contract has inconsistent message scope | Space: object requires documentation | |
86 | 085 | Parameter error when calling &1(&2) | The short text describes the object sufficiently | |
87 | 086 | Contract operations &1 and &2 have the same request but diff. response | Space: object requires documentation | |
88 | 087 | Contract operations &1 and &2 have the same request but diff. fault(s) | Space: object requires documentation | |
89 | 088 | Object &1 &2 does not exist or has no active version | The short text describes the object sufficiently | |
90 | 089 | Contract actor name &1 has to be changed to &2 | The short text describes the object sufficiently | |
91 | 090 | Contract operation &1 is missing in actor &2 | The short text describes the object sufficiently | |
92 | 091 | Contract operation &1 in actor &2 has to be deleted | The short text describes the object sufficiently | |
93 | 092 | Contract operation &1 has to be moved to actor &2 | The short text describes the object sufficiently | |
94 | 093 | Request message is missing in operation &1 | The short text describes the object sufficiently | |
95 | 094 | Actors name is already used | The short text describes the object sufficiently | |
96 | 095 | Implementation invalid: &1 does not match contract data (&2 &3) | The short text describes the object sufficiently | |
97 | 096 | Request &1 of consumer &2 not found or not implemented by this consumer | Space: object requires documentation | |
98 | 097 | Consumer Mapping &1 is not a single target mapping | The short text describes the object sufficiently | |
99 | 098 | Eliminate Direct Mapping Classes: There are no direct mapping methods | The short text describes the object sufficiently | |
100 | 099 | Contract &1 has no actor &2 | The short text describes the object sufficiently | |
101 | 100 | Contract &1 has no request message &2 | The short text describes the object sufficiently | |
102 | 101 | No communication type assigned | The short text describes the object sufficiently | |
103 | 102 | CommunicationType must not be initial | The short text describes the object sufficiently | |
104 | 103 | Request qname &1 &2 occurs more than once | The short text describes the object sufficiently | |
105 | 104 | No semantic contract is set | The short text describes the object sufficiently | |
106 | 105 | No consumer is set | The short text describes the object sufficiently | |
107 | 106 | Receiver determination filter structure not set | The short text describes the object sufficiently | |
108 | 107 | Sender determination filter structure not set | The short text describes the object sufficiently | |
109 | 108 | Schema defined external can not be changed | The short text describes the object sufficiently | |
110 | 109 | &1 mode not set | The short text describes the object sufficiently | |
111 | 110 | Could not find the referenced Actor &1 within the Contract &2 | The short text describes the object sufficiently | |
112 | 111 | Message &1 in Contract &2 is missing in current Contract Implementation | The short text describes the object sufficiently | |
113 | 112 | Message &1 in current Contract Implementation is missing in Contract &2 | The short text describes the object sufficiently | |
114 | 113 | Receiver determination filter structure must not be set | The short text describes the object sufficiently | |
115 | 114 | Sender determination filter structure must not be set | The short text describes the object sufficiently | |
116 | 115 | Reference to base structure &1 was adjusted | The short text describes the object sufficiently | |
117 | 116 | The name of the referenced actor was changed to &1 | The short text describes the object sufficiently | |
118 | 117 | Reference to context type &1 was adjusted | The short text describes the object sufficiently | |
119 | 118 | Reference to type &1 was adjusted | The short text describes the object sufficiently | |
120 | 119 | The actor's name has been changed to &1 | The short text describes the object sufficiently | |
121 | 120 | Consumer /Provider message type &1 has been deleted | The short text describes the object sufficiently | |
122 | 121 | Message type &1 added. Assign a new Consumer / Provider Implementation | The short text describes the object sufficiently | |
123 | 122 | Operation &1 has been deleted | The short text describes the object sufficiently | |
124 | 123 | Operation &1 has been added. | The short text describes the object sufficiently | |
125 | 124 | Semantic Contract &1 or its Actor &2 does not exist | The short text describes the object sufficiently | |
126 | 125 | Consumer &1 does not exist | The short text describes the object sufficiently | |
127 | 126 | Filter structure &1 of &2 is not valid | The short text describes the object sufficiently | |
128 | 127 | Current Scope &1 does not match Scope &2 of its referenced object | Space: object requires documentation | |
129 | 128 | All external message types must belong to the same package | Space: object requires documentation | |
130 | 129 | Role &1 is not valid. | The short text describes the object sufficiently | |
131 | 130 | Actor &1 not found for Semantic Contract &2. | The short text describes the object sufficiently | |
132 | 131 | Semantic Contract &1 is not valid. | The short text describes the object sufficiently | |
133 | 132 | No Role assigned for Actor &1 in Semantic Contract &2. | The short text describes the object sufficiently | |
134 | 133 | Role &1 is already assigned and cannot be deleted. | The short text describes the object sufficiently | |
135 | 134 | Semantic Contract actor name &1 has been changed. | Space: object requires documentation | |
136 | 135 | No implementation assigned for request &1 | The short text describes the object sufficiently | |
137 | 136 | Multiple classifications for life cycle status are not allowed | Space: object requires documentation | |
138 | 137 | Referred object &1 &2 has release status '&3' | Space: object requires documentation | |
139 | 138 | No WSDL in cache | The short text describes the object sufficiently | |
140 | 139 | Wrong Message type - XML QName of Message must be &1{&2} | The short text describes the object sufficiently | |
141 | 140 | Object must be saved | The short text describes the object sufficiently | |
142 | 141 | Object with generating application '&1' cannot be regenerated | The short text describes the object sufficiently | |
143 | 142 | Actor &1 not found | The short text describes the object sufficiently | |
144 | 143 | WSDL does not match Semantic Contract &1 | The short text describes the object sufficiently | |
145 | 144 | WSDL invalid. &1 has to be filled | The short text describes the object sufficiently | |
146 | 145 | WSDL invalid. Name for processing type is missing | The short text describes the object sufficiently | |
147 | 146 | WSDL invalid. Only one processing type can be set as default | The short text describes the object sufficiently | |
148 | 147 | WSDL invalid. &1 names must be unique in same Proxy Object | The short text describes the object sufficiently | |
149 | 148 | WSDL invalid. There must be at least one processing type | The short text describes the object sufficiently | |
150 | 149 | WSDL invalid. &1 name has to be set | The short text describes the object sufficiently | |
151 | 150 | Parameter changed: Operation &1 Parameter &2 Old: &3 New: &4 | The short text describes the object sufficiently | |
152 | 151 | Operation &1: New Exception &2 | The short text describes the object sufficiently | |
153 | 152 | WSDL invalid. Request Message Type has to be set | The short text describes the object sufficiently | |
154 | 153 | WSDL invalid. Response Message Type needs name and namespace | The short text describes the object sufficiently | |
155 | 154 | WSDL invalid. Valid Semantic Contract has to be set | The short text describes the object sufficiently | |
156 | 155 | Error loading object &1 &2 | The short text describes the object sufficiently | |
157 | 156 | WSDL invald. Cmmunication type '&1' not supported | The short text describes the object sufficiently | |
158 | 157 | Usage of &1 &2 is not permitted (&3) - check package interface | The short text describes the object sufficiently | |
159 | 158 | Datatype &1 is not a code - &2 cannot be set | The short text describes the object sufficiently | |
160 | 159 | Specify Source Consumer and Method before adding a Target Consumer | The short text describes the object sufficiently | |
161 | 160 | ABAP name &1 is invalid, name must start with &2 | The short text describes the object sufficiently | |
162 | 161 | ABAP name &1 is in customer namespace, use name from SAP namespace | The short text describes the object sufficiently | |
163 | 162 | ABAP name &1 is in SAP namespace, use name from customer namespace | The short text describes the object sufficiently | |
164 | 163 | Package '&1' not found | The short text describes the object sufficiently | |
165 | 164 | ACO Metadata is invalid | The short text describes the object sufficiently | |
166 | 165 | Function name in ACO metadata (&1) does not match expected name (&2) | The short text describes the object sufficiently | |
167 | 166 | Mapping '&1' does not exist | The short text describes the object sufficiently | |
168 | 167 | Class &1 is an Event Provider, not a Consumer | The short text describes the object sufficiently | |
169 | 168 | RFC Consumer must have at least one method | The short text describes the object sufficiently | |
170 | 169 | Message type has to be assigned | The short text describes the object sufficiently | |
171 | 170 | Only one consumer implementation object may be assigned | The short text describes the object sufficiently | |
172 | 171 | A valid interface pattern must be assigned | The short text describes the object sufficiently | |
173 | 172 | Comm. type of operation &3 (&1) does not match that of contract (&2) | The short text describes the object sufficiently | |
174 | 173 | WSDL invalid. Initial communication type not supported | The short text describes the object sufficiently | |
175 | 174 | Could not find the RFC Consumer '&1' | The short text describes the object sufficiently | |
176 | 175 | Could not find the operation '&2' at RFC Consumer '&1' | The short text describes the object sufficiently | |
177 | 176 | Name &1 is not valid ( for package &2 or in itself) | The short text describes the object sufficiently | |
178 | 177 | No RFC operation assigned to operation &1 | The short text describes the object sufficiently | |
179 | 178 | Parameter name &1 is used more than once | The short text describes the object sufficiently | |
180 | 179 | Object must be maintained in it's own context | Space: object requires documentation | |
181 | 180 | There is no matching consumer in the service group for request &1 | The short text describes the object sufficiently | |
182 | 181 | More than one match for request message &1 in service group | The short text describes the object sufficiently | |
183 | 182 | Service Consumer &1 in Service Group &2 not assigned | Space: object requires documentation | |
184 | 183 | RFC consumer operation incompatible: used function modules do not match | The short text describes the object sufficiently | |
185 | 184 | RFC consumer operation incompatible: sync / async flag does not match | The short text describes the object sufficiently | |
186 | 185 | RFC consumer operation incompatible: defined parameter &1 not found | The short text describes the object sufficiently | |
187 | 186 | RFC consumer operation incompatible: request parameter &1 not found | The short text describes the object sufficiently | |
188 | 187 | RFC consumer operation incompatible: response parameter &1 not found | The short text describes the object sufficiently | |
189 | 188 | A mapping mode has to be assigned | Space: object requires documentation | |
190 | 189 | No implementation assigned for RFC operation &1 | The short text describes the object sufficiently | |
191 | 190 | Operation &1 of RFC consumer &2 not assigned to contract implementation | The short text describes the object sufficiently | |
192 | 191 | Signature is incompatible (parameter mismatch) | The short text describes the object sufficiently | |
193 | 192 | Signature is incompatible (different synchronicity) | The short text describes the object sufficiently | |
194 | 193 | Signature is incompatible (different RFC function name) | The short text describes the object sufficiently | |
195 | 194 | Target consumer &1 of consumer mapping &2 is no RFC consumer | The short text describes the object sufficiently | |
196 | 195 | RFC operation &1 has been deleted | The short text describes the object sufficiently | |
197 | 196 | RFC operation &1 has been added | The short text describes the object sufficiently | |
198 | 197 | Object not valid | The short text describes the object sufficiently | |
199 | 198 | Property is defined by external schema | Space: object requires documentation | |
200 | 199 | anyAttribute not supported; attribute is ignored | The short text describes the object sufficiently | |
201 | 200 | File does not contain a valid NPM definition | The short text describes the object sufficiently | |
202 | 201 | Signature is incompatible | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 740 |