Message Number list used by SAP ABAP Class CX_PXN_NODE_INCONSISTENT (Node inconsistent)
SAP ABAP Class CX_PXN_NODE_INCONSISTENT (Node inconsistent) is using
# Object Type Object Name Object Description Note
     
1 Message Number  SPRX - 013 Proxy &1/&2 is assigned to package &3 but has to be assigned to &4
2 Message Number  SPXN - 110 Could not find the referenced Actor &1 within the Contract &2
3 Message Number  SPXN - 113 Receiver determination filter structure must not be set
4 Message Number  SPXN - 109 &1 mode not set
5 Message Number  SPXN - 107 Sender determination filter structure not set
6 Message Number  SPXN - 106 Receiver determination filter structure not set
7 Message Number  SPXN - 105 No consumer is set
8 Message Number  SPXN - 104 No semantic contract is set
9 Message Number  SPXN - 103 Request qname &1 &2 occurs more than once
10 Message Number  SPXN - 102 CommunicationType must not be initial
11 Message Number  SPXN - 101 No communication type assigned
12 Message Number  SPXN - 098 Eliminate Direct Mapping Classes: There are no direct mapping methods
13 Message Number  SPXN - 096 Request &1 of consumer &2 not found or not implemented by this consumer
14 Message Number  SPXN - 093 Request message is missing in operation &1
15 Message Number  SPXN - 087 Contract operations &1 and &2 have the same request but diff. fault(s)
16 Message Number  SPXN - 086 Contract operations &1 and &2 have the same request but diff. response
17 Message Number  SPXN - 084 Contract has inconsistent message scope
18 Message Number  SPXN - 082 The Semantic Contract must have exactly two actors
19 Message Number  SPXN - 169 Message type has to be assigned
20 Message Number  SPXN - 190 Operation &1 of RFC consumer &2 not assigned to contract implementation
21 Message Number  SPXN - 189 No implementation assigned for RFC operation &1
22 Message Number  SPXN - 188 A mapping mode has to be assigned
23 Message Number  SPXN - 182 Service Consumer &1 in Service Group &2 not assigned
24 Message Number  SPXN - 178 Parameter name &1 is used more than once
25 Message Number  SPXN - 172 Comm. type of operation &3 (&1) does not match that of contract (&2)
26 Message Number  SPXN - 171 A valid interface pattern must be assigned
27 Message Number  SPXN - 170 Only one consumer implementation object may be assigned
28 Message Number  SPXN - 075 Mode of source consumer different from mode of operation mapping
29 Message Number  SPXN - 168 RFC Consumer must have at least one method
30 Message Number  SPXN - 155 Error loading object &1 &2
31 Message Number  SPXN - 151 Operation &1: New Exception &2
32 Message Number  SPXN - 150 Parameter changed: Operation &1 Parameter &2 Old: &3 New: &4
33 Message Number  SPXN - 135 No implementation assigned for request &1
34 Message Number  SPXN - 134 Semantic Contract actor name &1 has been changed.
35 Message Number  SPXN - 132 No Role assigned for Actor &1 in Semantic Contract &2.
36 Message Number  SPXN - 114 Sender determination filter structure must not be set
37 Message Number  SPXN - 021 No response allowed
38 Message Number  SPXN - 035 Source method not set within mapping
39 Message Number  SPXN - 028 Value '&1' for facet &2 for type/attribute &3 not allowed (repterm &4)
40 Message Number  SPXN - 027 Wrong representation term &1 for attribute &2 of representation term &3
41 Message Number  SPXN - 026 Idempotency only allowed for synchronous method in non-TUCC interface
42 Message Number  SPXN - 025 Wrong type &1 for attribute &2/ type of representation term &3
43 Message Number  SPXN - 024 Attribute &1 unknown for representation term &2
44 Message Number  SPXN - 023 Obligatory attribute &1 missing for representation term &2
45 Message Number  SPXN - 022 Asynchronous operation must not have any faults
46 Message Number  SPXN - 036 Mapping must either contain synchronous or asynchronous methods
47 Message Number  SPXN - 020 Response missing
48 Message Number  SPXN - 019 Request missing
49 Message Number  SPXN - 018 Required operation with pattern &1 missing for interface with pattern &2
50 Message Number  SPXN - 017 '&1' is not valid for '&2'. Expected values: &3
51 Message Number  SPXN - 009 Type reference is not set
52 Message Number  SPXN - 008 Type is not set (xsd type or type reference)
53 Message Number  SPXN - 007 ABAP name is not set
54 Message Number  SPXN - 006 Node is inconsistent
55 Message Number  SPXN - 045 Ambiguous mapping for method &1
56 Message Number  SPXN - 073 No direct mappings allowed for single target Consumer mappings
57 Message Number  SPXN - 071 Consumer Mapping is a single target mapping, but has targets &1 and &2
58 Message Number  SPXN - 059 Facet &1 for type/attribute &2 not allowed (repterm &3)
59 Message Number  SPXN - 058 Attribute &1 of repr.term &2 must refer a global repr.term type
60 Message Number  SPXN - 057 Request message &1 &2 occurs twice in interface
61 Message Number  SPXN - 053 Base has different xsd facets than restriction (check schema)
62 Message Number  SPXN - 049 Enumeration value provider class only for data elements
63 Message Number  SPXN - 047 Append is dynamic, enhanced type isn't
64 Message Number  SPXN - 080 The Processing Type Domain must have at least one processing type
65 Message Number  SPXN - 043 Mapping missing for method &1
66 Message Number  SPXN - 042 Mapping target &1 inconsistent
67 Message Number  SPXN - 041 Source method does not exist
68 Message Number  SPXN - 040 Consumer Mapping has no source class
69 Message Number  SPXN - 039 ABAP name '&1' is too long, max. &2 characters allowed
70 Message Number  SPXN - 038 Synchronous mapping must have exactly one target method
71 Message Number  SPXN - 037 Asynchronous mapping must have at least one target method