Message Number list used by SAP ABAP Class CL_SR_SYNCH_SERVICES_FOR_SR (Services Registry: Synch Services for Forwarding)
SAP ABAP Class CL_SR_SYNCH_SERVICES_FOR_SR (Services Registry: Synch Services for Forwarding) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
2 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
3 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
4 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
5 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
6 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
7 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
8 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
9 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
10 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
11 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
12 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
13 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
14 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
15 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
16 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
17 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
18 | Message Number | MSG_CL_ER - 025 | No sufficient authorisations. Ask user administrator | |
19 | Message Number | MSG_CL_ER - 050 | Error: &1&2&3&4 | |
20 | Message Number | MSG_CL_ER - 056 | Original System &1 published in Services Registry &2 | |
21 | Message Number | MSG_CL_ER - 068 | Getting classifications for registry '&1' failed | |
22 | Message Number | MSG_CL_ER - 069 | Getting classification value for registry '&1' failed | |
23 | Message Number | MSG_CL_ER - 227 | Subscription of &1 failed due to missing consumer proxy. | |
24 | Message Number | MSG_CL_ER - 230 | Publication of &1 failed due to missing service definition. | |
25 | Message Number | MSG_CL_ER - 233 | Deletion of binding '&3' from registry '&2' failed &1 | |
26 | Message Number | MSG_CL_ER - 250 | Binding '&1' not found in local Services Registry | |
27 | Message Number | MSG_CL_ER - 251 | Publication with empty Application change key is not possible | |
28 | Message Number | MSG_CL_ER - 251 | Publication with empty Application change key is not possible | |
29 | Message Number | MSG_CL_ER - 251 | Publication with empty Application change key is not possible | |
30 | Message Number | MSG_CL_ER - 252 | Deletion with empty Application change key is not possible | |
31 | Message Number | MSG_CL_ER - 252 | Deletion with empty Application change key is not possible | |
32 | Message Number | MSG_CL_ER - 252 | Deletion with empty Application change key is not possible | |
33 | Message Number | MSG_CL_ER - 252 | Deletion with empty Application change key is not possible | |
34 | Message Number | MSG_CL_ER - 252 | Deletion with empty Application change key is not possible | |
35 | Message Number | MSG_CL_ER - 252 | Deletion with empty Application change key is not possible | |
36 | Message Number | MSG_CL_ER - 252 | Deletion with empty Application change key is not possible | |
37 | Message Number | MSG_CL_ER - 253 | Subscription with empty Application change key is not possible | |
38 | Message Number | MSG_CL_ER - 254 | Notification with empty Application change key is not possible | |
39 | Message Number | MSG_CL_ER - 255 | System with application key '&1' not found in local Services Registry | |
40 | Message Number | MSG_CL_ER - 256 | IBC with ID '&1' not found in local Services Registry | |
41 | Message Number | SRT_WSP2 - 000 | & & & & | |
42 | Message Number | SRT_WSP2 - 000 | & & & & | |
43 | Message Number | SRT_WSP2 - 000 | & & & & | |
44 | Message Number | SRT_WSP2 - 000 | & & & & | |
45 | Message Number | SRT_WSP2 - 000 | & & & & | |
46 | Message Number | SRT_WSP2 - 000 | & & & & | |
47 | Message Number | SRT_WSP2 - 000 | & & & & | |
48 | Message Number | SRT_WSP2 - 000 | & & & & | |
49 | Message Number | SRT_WSP2 - 000 | & & & & | |
50 | Message Number | SRT_WSP2 - 000 | & & & & | |
51 | Message Number | SRT_WSP2 - 000 | & & & & | |
52 | Message Number | SRT_WSP2 - 000 | & & & & | |
53 | Message Number | SRT_WSP2 - 000 | & & & & | |
54 | Message Number | SRT_WSP2 - 000 | & & & & | |
55 | Message Number | SRT_WSP2 - 000 | & & & & | |
56 | Message Number | SRT_WSP2 - 000 | & & & & | |
57 | Message Number | SRT_WSP2 - 000 | & & & & | |
58 | Message Number | SRT_WSP2 - 000 | & & & & | |
59 | Message Number | SRT_WSP2 - 000 | & & & & | |
60 | Message Number | SRT_WSP2 - 000 | & & & & | |
61 | Message Number | SRT_WSP2 - 000 | & & & & | |
62 | Message Number | SRT_WSP2 - 000 | & & & & | |
63 | Message Number | SRT_WSP2 - 000 | & & & & | |
64 | Message Number | SRT_WSP2 - 000 | & & & & | |
65 | Message Number | SRT_WSP2 - 000 | & & & & | |
66 | Message Number | SRT_WSP2 - 000 | & & & & | |
67 | Message Number | SRT_WSP2 - 000 | & & & & | |
68 | Message Number | SRT_WSP2 - 000 | & & & & | |
69 | Message Number | SRT_WSP2 - 000 | & & & & | |
70 | Message Number | SRT_WSP2 - 000 | & & & & | |
71 | Message Number | SRT_WSP2 - 000 | & & & & | |
72 | Message Number | SRT_WSP2 - 000 | & & & & | |
73 | Message Number | SRT_WSP2 - 000 | & & & & | |
74 | Message Number | SRT_WSP2 - 000 | & & & & | |
75 | Message Number | SRT_WSP2 - 000 | & & & & | |
76 | Message Number | SRT_WSP2 - 000 | & & & & | |
77 | Message Number | SRT_WSP2 - 000 | & & & & | |
78 | Message Number | SRT_WSP2 - 526 | Publishing of binding '&3' to registry '&2' failed &1 | |
79 | Message Number | SRT_WSP2 - 527 | Publishing of service definition '&3' to registry '&2' failed &1 | |
80 | Message Number | SRT_WSP2 - 528 | Deletion of bindings of wsd '&3' from registry '&2' failed: '&1' | |
81 | Message Number | SRT_WSP2 - 529 | Deletion of binding '&4' of wsd '&3' from registry '&2' failed &1 | |
82 | Message Number | SRT_WSP2 - 530 | Deletion of service definition '&3' from registry '&2' failed &1 | |
83 | Message Number | SRT_WSP2 - 531 | Deletion of IBC '&3' from registry '&2' failed &1 | |
84 | Message Number | SRT_WSP2 - 532 | Searching for services registry entity in registry '&2' failed &1 | |
85 | Message Number | SRT_WSP2 - 532 | Searching for services registry entity in registry '&2' failed &1 | |
86 | Message Number | SRT_WSP2 - 532 | Searching for services registry entity in registry '&2' failed &1 | |
87 | Message Number | SRT_WSP2 - 532 | Searching for services registry entity in registry '&2' failed &1 | |
88 | Message Number | SRT_WSP2 - 532 | Searching for services registry entity in registry '&2' failed &1 | |
89 | Message Number | SRT_WSP2 - 533 | Publishing of IBC '&3' to registry '&2' failed &1 | |
90 | Message Number | SRT_WSP2 - 534 | Register application failed &1 | |
91 | Message Number | SRT_WSP2 - 534 | Register application failed &1 | |
92 | Message Number | SRT_WSP2 - 534 | Register application failed &1 | |
93 | Message Number | SRT_WSP2 - 534 | Register application failed &1 | |
94 | Message Number | SRT_WSP2 - 535 | Persisting application change key failed: &1 | |
95 | Message Number | SRT_WSP2 - 537 | Searching for registered applications failed &1 | |
96 | Message Number | SRT_WSP2 - 537 | Searching for registered applications failed &1 | |
97 | Message Number | SRT_WSP2 - 538 | Proxy instantiation for registry '&2' failed: &1 | |
98 | Message Number | SRT_WSP2 - 539 | Registry '&2' not found: &1 | |
99 | Message Number | SRT_WSP2 - 562 | Application key and/or application change key are empty: '&1' | |
100 | Message Number | SRT_WSP2 - 563 | Registry must not be empty | |
101 | Message Number | SRT_WSP2 - 564 | Proxy cannot be instantiated for registry '&2': '&1' | |
102 | Message Number | SRT_WSP2 - 589 | Deletion of consumer '&3' from registry '&2' failed &1 | |
103 | Message Number | SRT_WSP2 - 590 | Publishing of consumer '&3' to registry '&2' failed &1 | |
104 | Message Number | SRT_WSP2 - 605 | Get registered applications failed &1 | |
105 | Message Number | SRT_WSP2 - 613 | Getting IBC information for id '&3' for registry '&2' failed &1 | |
106 | Message Number | SRT_WSP2 - 614 | Getting Service Definition '&3' for registry '&2' failed &1 | |
107 | Message Number | SRT_WSP2 - 615 | Getting Bindings for IBC '&3' for registry '&2' failed '&1' | |
108 | Message Number | SRT_WSP2 - 617 | Get bindings failed: Registry '&1', Application Key '&2', Object ID '&3' | |
109 | Message Number | SRT_WSP2 - 617 | Get bindings failed: Registry '&1', Application Key '&2', Object ID '&3' | |
110 | Message Number | SRT_WSP2 - 626 | Error receiving application information of Services Registry | |
111 | Message Number | SRT_WSP2 - 633 | Deletion of Application '&3' from registry '&2' failed &1 | |
112 | Message Number | SRT_WSP2 - 642 | Notification failed for Registry &2 &1 | |
113 | Message Number | SRT_WSP2 - 656 | Getting subscription from registry '&2' failed &1 | |
114 | Message Number | SRT_WSP2 - 656 | Getting subscription from registry '&2' failed &1 | |
115 | Message Number | SRT_WSP2 - 656 | Getting subscription from registry '&2' failed &1 | |
116 | Message Number | SRT_WSP2 - 656 | Getting subscription from registry '&2' failed &1 | |
117 | Message Number | SRT_WSP2 - 657 | Getting notifications from registry '&2' failed &1 | |
118 | Message Number | SRT_WSP2 - 657 | Getting notifications from registry '&2' failed &1 |