SAP ABAP Message Class WZRE_PRX (Agency Business: SOA messages from proxy implementations)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ WZRE_XI_PROXY (Package) Agency Business: SOA proxy implementations
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ WZRE_XI_PROXY (Package) Agency Business: SOA proxy implementations
Attributes
Message class | WZRE_PRX | |
Short Description | Agency Business: SOA messages from proxy implementations | |
Changed On | 20130531 | |
Last Changed At | 101041 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | **** Messages from Proxy & Service implementations **** | The short text describes the object sufficiently | |
2 | 001 | Mapping inbound class &1 for use case type &2 is not existing | The short text describes the object sufficiently | |
3 | 002 | Application processing class &1 for use case type &2 is not existing | The short text describes the object sufficiently | |
4 | 003 | Mapping outbound class &1 for use case type &2 is not existing | The short text describes the object sufficiently | |
5 | 004 | Severe error during mapping inbound (class &1, method &2) | The short text describes the object sufficiently | |
6 | 005 | Severe error during application processing (class &1, method &2) | The short text describes the object sufficiently | |
7 | 006 | Severe error during mapping outbound (class &1, method &2) | The short text describes the object sufficiently | |
8 | 007 | Severe error during proxy execution (class &1, method &2) | The short text describes the object sufficiently | |
9 | 008 | No proxy class / method for confirmation message is existing | The short text describes the object sufficiently | |
10 | 009 | Confirmation sender class &1 is not existing | The short text describes the object sufficiently | |
11 | 016 | Invoice &1 could not be cancelled, no further information available. | The short text describes the object sufficiently | |
12 | 017 | Determined use case &1 from request does not match use case &2 of ID &3 | The short text describes the object sufficiently | |
13 | 038 | Invoice &1 has different amounts than original invoice &2 | The short text describes the object sufficiently | |
14 | 039 | Item lines of invoice &1 are different from original invoice &2 | The short text describes the object sufficiently | |
15 | 040 | &1 request cannot be executed due to missing implementation of BAdI &2 | The short text describes the object sufficiently | |
16 | 050 | Internal error: Interface proxy name could not be determined | The short text describes the object sufficiently | |
17 | 051 | Internal error: Message header node is missing in inbound PROXY structure | The short text describes the object sufficiently | |
18 | 052 | Internal error: No configuration data for proxy &1 available | The short text describes the object sufficiently | |
19 | 053 | Int. error: No inbound config. found (proxy &1, use case &2, obj. &3) | The short text describes the object sufficiently | |
20 | 054 | Int. error: No outbound config. found (proxy &1, use case &2, obj. &3) | The short text describes the object sufficiently | |
21 | 100 | **** Messages from conversion & transformation classes **** | The short text describes the object sufficiently | |
22 | 101 | SchemeAgencyID &1 for ProductStandardID &2 not supported | The short text describes the object sufficiently | |
23 | 102 | ProductStandardID &1: EAN &2 with SchemeAgencyID &3 already mapped | The short text describes the object sufficiently | |
24 | 103 | ProductTypeCode &1 does not belong to materials (code value 1 expected) | The short text describes the object sufficiently | |
25 | 104 | Message Header: Value &1 for Field &2 is not supported | The short text describes the object sufficiently | |
26 | 150 | **** Messages for FEH/PPO processing **** | The short text describes the object sufficiently | |
27 | 151 | Error in Fail process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
28 | 152 | Error in Finish process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
29 | 153 | Error in Retry process: &1 &2 &3 &4 | The short text describes the object sufficiently | |
30 | 154 | Order ID &1 has wrong format (GUID conversion faield) | The short text describes the object sufficiently | |
31 | 155 | No FEH data found for order ID &1 | The short text describes the object sufficiently | |
32 | 156 | Finish process is not allowed for service operation &1 | The short text describes the object sufficiently | |
33 | 157 | Fatal Error in method &1: field symbol &2 not assigned | The short text describes the object sufficiently | |
34 | 158 | Error in method &1: payload data are not found | The short text describes the object sufficiently | |
35 | 200 | **** Messages from Customizing (View & Runtime) **** | The short text describes the object sufficiently | |
36 | 201 | Org data are determined dynamically. Delete the entered default ID | The short text describes the object sufficiently | |
37 | 202 | Enter the sales area | The short text describes the object sufficiently | |
38 | 203 | Enter purchasing organization and/or purchasing group | The short text describes the object sufficiently | |
39 | 204 | Company code &1 of sales org &2 does not match entered company code &3 | The short text describes the object sufficiently | |
40 | 205 | Enter org data or set flag to determine them dynamically | The short text describes the object sufficiently | |
41 | 206 | Company code &1 of purch. org &2 does not match entered company code &3 | The short text describes the object sufficiently | |
42 | 207 | Enter an identifier. Either the internal or an standardized one. | The short text describes the object sufficiently | |
43 | 208 | Enter or initialize both fields. | The short text describes the object sufficiently | |
44 | 209 | Only one Identification Scheme can be the default one. | The short text describes the object sufficiently | |
45 | 210 | Sales-sided default data are missing for payment type &1. | The short text describes the object sufficiently | |
46 | 211 | Purchasing-sided default data are missing for payment type &1. | The short text describes the object sufficiently | |
47 | 212 | Company code &1 of purch. org &2 does not match entered company code &3 | The short text describes the object sufficiently | |
48 | 213 | No customizing entry could be found for proxy mapping group &1 | The short text describes the object sufficiently | |
49 | 214 | No default mapping group could be found for invoices | The short text describes the object sufficiently | |
50 | 215 | No default mapping group could be found for credit memos | The short text describes the object sufficiently | |
51 | 216 | Proxy mapping group &1 from decentral table is already maintained | The short text describes the object sufficiently | |
52 | 217 | Customizing reader cannot be instanciated | The short text describes the object sufficiently | |
53 | 218 | Default Data with ID &1 cannot be deleted ( used in mapping group &2) | The short text describes the object sufficiently | |
54 | 219 | Identification Scheme &1 cannot be deleted ( used in mapping group &2) | The short text describes the object sufficiently | |
55 | 220 | Sales-sided default data are not allowed for payment type &1. | The short text describes the object sufficiently | |
56 | 221 | Purchasing-sided default data are not allowed for payment type &1. | The short text describes the object sufficiently | |
57 | 222 | No mapping group found for use case &1 | The short text describes the object sufficiently | |
58 | 223 | No identification scheme found for use case &1 | The short text describes the object sufficiently | |
59 | 224 | No data for update available | The short text describes the object sufficiently | |
60 | 225 | No data written to transport: Missing transport request or transport task | The short text describes the object sufficiently | |
61 | 478 | The short text describes the object sufficiently | ||
62 | 500 | **** Messages from invoice request maintenance **** | The short text describes the object sufficiently | |
63 | 501 | Invoice request &1 does not exist | The short text describes the object sufficiently | |
64 | 502 | Invoice request &1 already exists | The short text describes the object sufficiently | |
65 | 503 | Invoice request &1 has been created | The short text describes the object sufficiently | |
66 | 504 | Invoice request &1 has been changed | The short text describes the object sufficiently | |
67 | 505 | Invoice request &1 has been deleted | The short text describes the object sufficiently | |
68 | 506 | Invoice request &1 has been sent to XI as a creation request | The short text describes the object sufficiently | |
69 | 507 | Invoice request &1 has been sent to XI as a deletion request | The short text describes the object sufficiently | |
70 | 508 | Please enter a invoice request ID | The short text describes the object sufficiently | |
71 | 510 | Bill-To-ID of invoice request &1 is missing | The short text describes the object sufficiently | |
72 | 515 | Test program cannot be executed in productive system | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 606 |