Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
When you start using ABAP proxies some people enjoy creating them so much (actually not creating but generating or regenerating) that they forget to do some basic checks that they would normally do with other types of communication.
In this blog I'll try to show a few ways how to make sure that our ABAP proxy environment not only works perfecly but also does not contain any errors or garbage.
SAP helps us with cleaning our proxy systems in many ways and one of them is by using report SXI_CHECK_INTERFACE_PROXYS
If you execute this report on your application system connected to your XI you can see many errors or warnings that you should have a look at as shown in the picture below:
But before running this report make sure you have a look at SAP Note: 953136 - SXI_CHECK_INTERFACE_PROXYS: Output changes
Another very helpful report - SXIVERI_PROXY_DDIC_CHECK will do even more. It compares proxy structures with Data Dictionary. This way you can be sure that you don't transport any garbage from development system to your test and production landscapes.
But there is a little trick. The report may show you that some DDID structures are not used in proxies. For those of you who didn't know that when you try to delete a proxy generated structure via SE11 you will see a nice message that informes you that it is not possible to do so:
However if you logon to your system in German language and change parameter p_del to X (you need to be in debugging mode) you will be able to delete proxy generated structures directly from the report as shown in the picture below:
For more information about this report have a look at: SAP Note 783088 - Generated proxy class cannot be deleted
One more SAP note that needs to be taken into consideration when you want to have a clean ABAP Proxy environment is:
SAP Note 886682 - Proxy inconsistencies
It will show you how to deal with:
a) Proxy orphans
b) Inconsistent proxy references
c) Duplicate HashIDs
I hope this little collection will help some of you to clean your ABAP Proxy landscapes which can only improve your developemnt time due to eliminating possible error situations.