SPXN - Proxy Generation
The following messages are stored in message class SPXN: Proxy Generation.
It is part of development package SAI_PROXY_GENTIME_MDR in software component BC-DWB-PRX. This development package consists of objects that can be grouped under "Proxy Generation: Meta Data Repository".
It is part of development package SAI_PROXY_GENTIME_MDR in software component BC-DWB-PRX. This development package consists of objects that can be grouped under "Proxy Generation: Meta Data Repository".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Data is invalid, &1 is no valid value for &2. |
| 002 | Object is invalid or inconsistent |
| 003 | Object &1 &2 is invalid |
| 004 | Object &1 &2 &3 is invalid |
| 005 | Object cannot be locked |
| 006 | Node is inconsistent |
| 007 | ABAP name is not set |
| 008 | Type is not set (xsd type or type reference) |
| 009 | Type reference is not set |
| 010 | Access to obsolete node was rejected |
| 011 | Read only data, cannot be changed |
| 012 | Switch not possible |
| 013 | Node cannot be deleted |
| 014 | Error occurred |
| 015 | Call of &1 not allowed for this object |
| 016 | Generating application &1 for namespace &2 not allowed |
| 017 | '&1' is not valid for '&2'. Expected values: &3 |
| 018 | Required operation with pattern &1 missing for interface with pattern &2 |
| 019 | Request missing |
| 020 | Response missing |
| 021 | No response allowed |
| 022 | Asynchronous operation must not have any faults |
| 023 | Obligatory attribute &1 missing for representation term &2 |
| 024 | Attribute &1 unknown for representation term &2 |
| 025 | Wrong type &1 for attribute &2/ type of representation term &3 |
| 026 | Idempotency only allowed for synchronous method in non-TUCC interface |
| 027 | Wrong representation term &1 for attribute &2 of representation term &3 |
| 028 | Value '&1' for facet &2 for type/attribute &3 not allowed (repterm &4) |
| 029 | First character '&1' of '&2' is invalid; only a(A)-z(Z) permitted |
| 030 | '&1' contains invalid character '&2'; only a(A)-z(Z), 0-9, "_" permitted |
| 031 | Qualified name '&1' is invalid; contains not permitted characters |
| 032 | Qualified name invalid; '&1' too long |
| 033 | Object has a warning |
| 034 | Method &1 of class &2 is not a method of a consumer proxy |
| 035 | Source method not set within mapping |
| 036 | Mapping must either contain synchronous or asynchronous methods |
| 037 | Asynchronous mapping must have at least one target method |
| 038 | Synchronous mapping must have exactly one target method |
| 039 | ABAP name '&1' is too long, max. &2 characters allowed |
| 040 | Consumer Mapping has no source class |
| 041 | Source method does not exist |
| 042 | Mapping target &1 inconsistent |
| 043 | Mapping missing for method &1 |
| 044 | Inline objects not supported: &1 |
| 045 | Ambiguous mapping for method &1 |
| 046 | Consumer class &1 does not exist |
| 047 | Append is dynamic, enhanced type isn't |
| 048 | Qualified name '&1' is invalid; namespace is initial |
| 049 | Enumeration value provider class only for data elements |
| 050 | Object has no target method &1 &2 |
| 051 | Elements and Attributes of Enhancements must be optional |
| 052 | Base has different representation term &1 |
| 053 | Base has different xsd facets than restriction (check schema) |
| 054 | Activation of proxy not possible |
| 055 | Name &1 already used |
| 056 | Object &1 &2 already used |
| 057 | Request message &1 &2 occurs twice in interface |
| 058 | Attribute &1 of repr.term &2 must refer a global repr.term type |
| 059 | Facet &1 for type/attribute &2 not allowed (repterm &3) |
| 060 | You can't assign Service Consumer and RFC Consumer to the same mapping |
| 061 | Abap Length must be greater than xsd length |
| 062 | PortType {&2}&1 not found in WSDL |
| 063 | PortType must be specified |
| 064 | Change may result in inconsistent existing enhancements |
| 065 | Error reading WSDL from &1 |
| 066 | This action is not allowed for an inactive object |
| 067 | Object must be saved and activated |
| 068 | Qname of table and linetype are identical |
| 069 | A default value can only be set for simple content elements |
| 070 | Referred type &1 &2 not found |
| 071 | Consumer Mapping is a single target mapping, but has targets &1 and &2 |
| 072 | Mapping is used in Consumer Mapping &1, this change is not possible |
| 073 | No direct mappings allowed for single target Consumer mappings |
| 074 | Can not use Package &1. |
| 075 | Mode of source consumer different from mode of operation mapping |
| 076 | Invalid xpath &1: &2 at pos &3 |
| 077 | Invalid Split Path |
| 078 | Invalid data; see previous error for further information |
| 079 | New value same as old value |
| 080 | The Processing Type Domain must have at least one processing type |
| 081 | This type is a helper type, change impossible |
| 082 | The Semantic Contract must have exactly two actors |
| 083 | Wrong scope |
| 084 | Contract has inconsistent message scope |
| 085 | Parameter error when calling &1(&2) |
| 086 | Contract operations &1 and &2 have the same request but diff. response |
| 087 | Contract operations &1 and &2 have the same request but diff. fault(s) |
| 088 | Object &1 &2 does not exist or has no active version |
| 089 | Contract actor name &1 has to be changed to &2 |
| 090 | Contract operation &1 is missing in actor &2 |
| 091 | Contract operation &1 in actor &2 has to be deleted |
| 092 | Contract operation &1 has to be moved to actor &2 |
| 093 | Request message is missing in operation &1 |
| 094 | Actors name is already used |
| 095 | Implementation invalid: &1 does not match contract data (&2 &3) |
| 096 | Request &1 of consumer &2 not found or not implemented by this consumer |
| 097 | Consumer Mapping &1 is not a single target mapping |
| 098 | Eliminate Direct Mapping Classes: There are no direct mapping methods |
| 099 | Contract &1 has no actor &2 |
| 100 | Contract &1 has no request message &2 |
| 101 | No communication type assigned |
| 102 | CommunicationType must not be initial |
| 103 | Request qname &1 &2 occurs more than once |
| 104 | No semantic contract is set |
| 105 | No consumer is set |
| 106 | Receiver determination filter structure not set |
| 107 | Sender determination filter structure not set |
| 108 | Schema defined external can not be changed |
| 109 | &1 mode not set |
| 110 | Could not find the referenced Actor &1 within the Contract &2 |
| 111 | Message &1 in Contract &2 is missing in current Contract Implementation |
| 112 | Message &1 in current Contract Implementation is missing in Contract &2 |
| 113 | Receiver determination filter structure must not be set |
| 114 | Sender determination filter structure must not be set |
| 115 | Reference to base structure &1 was adjusted |
| 116 | The name of the referenced actor was changed to &1 |
| 117 | Reference to context type &1 was adjusted |
| 118 | Reference to type &1 was adjusted |
| 119 | The actor's name has been changed to &1 |
| 120 | Consumer /Provider message type &1 has been deleted |
| 121 | Message type &1 added. Assign a new Consumer / Provider Implementation |
| 122 | Operation &1 has been deleted |
| 123 | Operation &1 has been added. |
| 124 | Semantic Contract &1 or its Actor &2 does not exist |
| 125 | Consumer &1 does not exist |
| 126 | Filter structure &1 of &2 is not valid |
| 127 | Current Scope &1 does not match Scope &2 of its referenced object |
| 128 | All external message types must belong to the same package |
| 129 | Role &1 is not valid. |
| 130 | Actor &1 not found for Semantic Contract &2. |
| 131 | Semantic Contract &1 is not valid. |
| 132 | No Role assigned for Actor &1 in Semantic Contract &2. |
| 133 | Role &1 is already assigned and cannot be deleted. |
| 134 | Semantic Contract actor name &1 has been changed. |
| 135 | No implementation assigned for request &1 |
| 136 | Multiple classifications for life cycle status are not allowed |
| 137 | Referred object &1 &2 has release status '&3' |
| 138 | No WSDL in cache |
| 139 | Wrong Message type - XML QName of Message must be &1{&2} |
| 140 | Object must be saved |
| 141 | Object with generating application '&1' cannot be regenerated |
| 142 | Actor &1 not found |
| 143 | WSDL does not match Semantic Contract &1 |
| 144 | WSDL invalid. &1 has to be filled |
| 145 | WSDL invalid. Name for processing type is missing |
| 146 | WSDL invalid. Only one processing type can be set as default |
| 147 | WSDL invalid. &1 names must be unique in same Proxy Object |
| 148 | WSDL invalid. There must be at least one processing type |
| 149 | WSDL invalid. &1 name has to be set |
| 150 | Parameter changed: Operation &1 Parameter &2 Old: &3 New: &4 |
| 151 | Operation &1: New Exception &2 |
| 152 | WSDL invalid. Request Message Type has to be set |
| 153 | WSDL invalid. Response Message Type needs name and namespace |
| 154 | WSDL invalid. Valid Semantic Contract has to be set |
| 155 | Error loading object &1 &2 |
| 156 | WSDL invald. Cmmunication type '&1' not supported |
| 157 | Usage of &1 &2 is not permitted (&3) - check package interface |
| 158 | Datatype &1 is not a code - &2 cannot be set |
| 159 | Specify Source Consumer and Method before adding a Target Consumer |
| 160 | ABAP name &1 is invalid, name must start with &2 |
| 161 | ABAP name &1 is in customer namespace, use name from SAP namespace |
| 162 | ABAP name &1 is in SAP namespace, use name from customer namespace |
| 163 | Package '&1' not found |
| 164 | ACO Metadata is invalid |
| 165 | Function name in ACO metadata (&1) does not match expected name (&2) |
| 166 | Mapping '&1' does not exist |
| 167 | Class &1 is an Event Provider, not a Consumer |
| 168 | RFC Consumer must have at least one method |
| 169 | Message type has to be assigned |
| 170 | Only one implementation object may be assigned per communication type |
| 171 | A valid interface pattern must be assigned |
| 172 | Comm. type of operation &3 (&1) does not match that of contract (&2) |
| 173 | WSDL invalid. Initial communication type not supported |
| 174 | Could not find the RFC Consumer '&1' |
| 175 | Could not find the operation '&2' at RFC Consumer '&1' |
| 176 | Name &1 is not valid ( for package &2 or in itself) |
| 177 | No RFC operation assigned to operation &1 |
| 178 | Parameter name &1 is used more than once |
| 179 | Object must be maintained in it's own context |
| 180 | There is no matching consumer in the service group for request &1 |
| 181 | More than one match for request message &1 in service group |
| 182 | Service Consumer &1 in Service Group &2 not assigned |
| 183 | RFC consumer operation incompatible: used function modules do not match |
| 184 | RFC consumer operation incompatible: sync / async flag does not match |
| 185 | RFC consumer operation incompatible: defined parameter &1 not found |
| 186 | RFC consumer operation incompatible: request parameter &1 not found |
| 187 | RFC consumer operation incompatible: response parameter &1 not found |
| 188 | A mapping mode has to be assigned |
| 189 | No implementation assigned for RFC operation &1 |
| 190 | Operation &1 of RFC consumer &2 not assigned to contract implementation |
| 191 | Signature is incompatible (parameter mismatch) |
| 192 | Signature is incompatible (different synchronicity) |
| 193 | Signature is incompatible (different RFC function name) |
| 194 | Target consumer &1 of consumer mapping &2 is no RFC consumer |
| 195 | RFC operation &1 has been deleted |
| 196 | RFC operation &1 has been added |
| 197 | Object not valid |
| 198 | Property is defined by external schema |
| 199 | anyAttribute not supported; attribute is ignored |
| 200 | File does not contain a valid NPM definition |
| 201 | Signature is incompatible |
| 202 | Event operation &1 must not have any response type |
| 203 | Event operation &1 must not have any fault message type |
| 204 | Communication type of implementation doesn't match with contract |
| 205 | Service Group not possible - only Event Providers may be assigned |
| 206 | Contract op. &1 and &2 have the same request but diff. communication type |
| 207 | Communication Type has been adjusted |
| 208 | Entry with name &1 namespace &2 already exists |
| 209 | Entry with name &1 namespace &2 not found |
| 210 | Failed to create transformation &1 |
| 211 | Failed to delete transformation &1 |
| 212 | Failed to read transformation &1 |
| 213 | Failed to activate transformation &1 |
| 214 | Invalid name for business feature &1 |
| 215 | Invalid WSDL: Unexpected element &1:&2 |
| 216 | Invalid WSDL: Unexpected attribute &1:&2 |
| 217 | Invalid leading BO. Multiple classification values. |
| 218 | Invalid semantic version. Multiple classification values. |