Message Number list used by SAP ABAP Class CX_PXN_INVALID_DATA (Invalid data)
SAP ABAP Class CX_PXN_INVALID_DATA (Invalid data) is using
# Object Type Object Name Object Description Note
     
1 Message Number  SPRX - 364 The value '&1' does not match the value present in your file (&2)
2 Message Number  SPRX - 133 Proxy for data type &1 &2 does not exist or cannot be enhanced
3 Message Number  SPXN - 163 Package '&1' not found
4 Message Number  SPXN - 138 No WSDL in cache
5 Message Number  SPXN - 158 Datatype &1 is not a code - &2 cannot be set
6 Message Number  SPXN - 156 WSDL invald. Cmmunication type '&1' not supported
7 Message Number  SPXN - 154 WSDL invalid. Valid Semantic Contract has to be set
8 Message Number  SPXN - 153 WSDL invalid. Response Message Type needs name and namespace
9 Message Number  SPXN - 152 WSDL invalid. Request Message Type has to be set
10 Message Number  SPXN - 149 WSDL invalid. &1 name has to be set
11 Message Number  SPXN - 148 WSDL invalid. There must be at least one processing type
12 Message Number  SPXN - 147 WSDL invalid. &1 names must be unique in same Proxy Object
13 Message Number  SPXN - 146 WSDL invalid. Only one processing type can be set as default
14 Message Number  SPXN - 145 WSDL invalid. Name for processing type is missing
15 Message Number  SPXN - 144 WSDL invalid. &1 has to be filled
16 Message Number  SPXN - 143 WSDL does not match Semantic Contract &1
17 Message Number  SPXN - 142 Actor &1 not found
18 Message Number  SPXN - 139 Wrong Message type - XML QName of Message must be &1{&2}
19 Message Number  SPXN - 200 File does not contain a valid NPM definition
20 Message Number  SPXN - 164 ACO Metadata is invalid
21 Message Number  SPXN - 165 Function name in ACO metadata (&1) does not match expected name (&2)
22 Message Number  SPXN - 166 Mapping '&1' does not exist
23 Message Number  SPXN - 167 Class &1 is an Event Provider, not a Consumer
24 Message Number  SPXN - 171 A valid interface pattern must be assigned
25 Message Number  SPXN - 173 WSDL invalid. Initial communication type not supported
26 Message Number  SPXN - 174 Could not find the RFC Consumer '&1'
27 Message Number  SPXN - 175 Could not find the operation '&2' at RFC Consumer '&1'
28 Message Number  SPXN - 177 No RFC operation assigned to operation &1
29 Message Number  SPXN - 183 RFC consumer operation incompatible: used function modules do not match
30 Message Number  SPXN - 184 RFC consumer operation incompatible: sync / async flag does not match
31 Message Number  SPXN - 185 RFC consumer operation incompatible: defined parameter &1 not found
32 Message Number  SPXN - 186 RFC consumer operation incompatible: request parameter &1 not found
33 Message Number  SPXN - 187 RFC consumer operation incompatible: response parameter &1 not found
34 Message Number  SPXN - 194 Target consumer &1 of consumer mapping &2 is no RFC consumer
35 Message Number  SPXN - 197 Object not valid
36 Message Number  SPXN - 036 Mapping must either contain synchronous or asynchronous methods
37 Message Number  SPXN - 056 Object &1 &2 already used
38 Message Number  SPXN - 055 Name &1 already used
39 Message Number  SPXN - 051 Elements and Attributes of Enhancements must be optional
40 Message Number  SPXN - 050 Object has no target method &1 &2
41 Message Number  SPXN - 049 Enumeration value provider class only for data elements
42 Message Number  SPXN - 048 Qualified name '&1' is invalid; namespace is initial
43 Message Number  SPXN - 046 Consumer class &1 does not exist
44 Message Number  SPXN - 038 Synchronous mapping must have exactly one target method
45 Message Number  SPXN - 060 You can't assign Service Consumer and RFC Consumer to the same mapping
46 Message Number  SPXN - 035 Source method not set within mapping
47 Message Number  SPXN - 034 Method &1 of class &2 is not a method of a consumer proxy
48 Message Number  SPXN - 032 Qualified name invalid; '&1' too long
49 Message Number  SPXN - 031 Qualified name '&1' is invalid; contains not permitted characters
50 Message Number  SPXN - 030 '&1' contains invalid character '&2'; only a(A)-z(Z), 0-9, "_" permitted
51 Message Number  SPXN - 029 First character '&1' of '&2' is invalid; only a(A)-z(Z) permitted
52 Message Number  SPXN - 001 Data is invalid, &1 is no valid value for &2.
53 Message Number  SPXN - 136 Multiple classifications for life cycle status are not allowed
54 Message Number  SPXN - 062 PortType {&2}&1 not found in WSDL
55 Message Number  SPXN - 063 PortType must be specified
56 Message Number  SPXN - 065 Error reading WSDL from &1
57 Message Number  SPXN - 073 No direct mappings allowed for single target Consumer mappings
58 Message Number  SPXN - 076 Invalid xpath &1: &2 at pos &3
59 Message Number  SPXN - 077 Invalid Split Path
60 Message Number  SPXN - 078 Invalid data; see previous error for further information
61 Message Number  SPXN - 079 New value same as old value
62 Message Number  SPXN - 083 Wrong scope
63 Message Number  SPXN - 088 Object &1 &2 does not exist or has no active version
64 Message Number  SPXN - 094 Actors name is already used
65 Message Number  SPXN - 102 CommunicationType must not be initial
66 Message Number  SPXN - 129 Role &1 is not valid.
67 Message Number  SPXN - 130 Actor &1 not found for Semantic Contract &2.
68 Message Number  SPXN - 131 Semantic Contract &1 is not valid.