Unable to see ECC proxies in PI Service Registry

Question

I am trying to consume ECC proxies in PI service registry but I cannot see any ECC backend proxies in PI. I have gone through several blogs, configuration guides and sdn forums to get this to work but could not. In ECC, if I use SOAMANAGER, I can see my proxy and web service in web service administration but I cannot see it in PI. I have done the following:
- System Global Settings
In Service Registry, I have defined proxy class as CO_SERVICES_REGISTRY_FLAT_SI, set to primary, logical port defined as default_port.
- On ECC WS administration, setup end points and binding.
- setup ID configuration objects for this scenario (WS to Proxy -> Proxy to WS Synchronous)
- Proxy creation in ECC also completed.
- Also checked in WSPARAM settings, same as WS Admin Service Registry.
- WSPUBLISH - getting error in ECC: RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No receiver could be determined, Error retrieving Services Registry (SR) version information, Error retreiving physical system from Services Registry, Exception raised during physical system publication. Code.
and in PI getting error:  INTERNAL.PROXY_NOT_ALLOWED_ON_IS Proxy calls are not permitted on sender or receiver side on the IS (client), Error retrieving Services Registry (SR) version information, No Publication possible from Integration Server(IS).
- Created type H RFC destinations in both ECC and PI.
Since WSADMIN, WSCONFIG and LPCONFIG have been combined into SOAMANAGER, are there any other settings I have to do as far as ECC communicating with PI Web Service and PI consuming ECC proxies? Did I miss anything here?
Most of the PI documenation, blogs and guides are outdated for previous versions. We are using SAP EHP 1 for SAP NetWeaver 7.1.
Thank you!

Answer 1

Hi Viswa,
Try to recreate the EEWB project for this...
Assign business transaction and CUSTOMER_H and with ADD_NEW_FIELDS as the type of ehancement.
Shud solve ..
Siva