Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-PRX (Application Component) Proxy Generation⤷
SAI_PROXY_GENTIME (Package) ES Tools: Proxy Generation 
Attribute
| Message class |  |
SPRX | |
| Short Description |  |
Proxy Generation | |
| Message Number |  |
270 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20130531 |
Message Text
Help Document
Diagnosis
Multiple metadata entries (that is, multiple ABAP names) were found for a WSDL key (type/name/namespace). The only way to correct this inconsistency is to remove the incorrect metadata.
This problem can occur as a result of the following:
- Proxies have been generated in different systems for the same WSDL key (type/name/namespace), with different ABAP names resulting from the generation procedure, and then transported to a common system.
- A proxy has been generated in a subsequent system as a local object ($TMP); following this, a transport from a previous system has been imported for the same WSDL key. -> You must delete the local object in $TMP, see reference to report below.
Ultimately, this problem is an indication that the organizational allocation of software components/namespaces as regards development systems has not been adhered to.
System Response
Since a proxy is identified by the WSDL key, the assignment of the WSDL key and proxy metadata is no longer unique, that is, it may no longer be possible to load the metadata. Other more severe side effects cannot be ruled out.
Procedure
Case 1: You must delete one of the two proxies in its original system by using transaction SPROXY. You must transport the deletion to the subsequent system.
Case 2: You can use report SXIVERI_PROXY_HASHID_CHECK to find the affected objects and then delete the respective "wrong" proxy locally.
Procedure for System Administration
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in | 620 |
