cancel
Showing results for 
Search instead for 
Did you mean: 

PopUp appearing in SRM system while SPROXY

Former Member
0 Kudos

HI ALL,

we are working on SRM to PI to SUS interface.

when i check SPROXY t-code in SRM system.i am getting a PopUp which is not allowing to move forward.

seems some issue in connectivity .please check provide the suggestions

i have attached the screenshot please check

thanks

Shakif

Accepted Solutions (0)

Answers (5)

Answers (5)

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

No matter if the RFC   SAP_PROXY_ESR is needed or not,

please, perform a SLDCHECK and paste the screenshot. also paste an screenshot of transaction SLDAPICUST --> when you test the configuration.

regards

Rodrigo

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

Aside from what Michal mentioned, it is also possible that you are using two destinations

e.g

Type G -> SAP_PROXY_ESR

Type H -> INTEGRATION_SERVER

Only one needs to be maintained, in our case, we deleted the type G and used the type H instead.

Regards,

Mark

0 Kudos

Hi Mark,

For the purpose you need, which is to create proxies from Tcode SPROXY, you have to connect the R/3 system with ESR.

You have to do this by creating an RFC destination of type G in R/3 system.

Here's a link form the SAP Help Portal with the settings (check the label <
Connecting to Enterprise Services Repository>)

http://help.sap.com/saphelp_nwpi71/helpdata/DE/8f/770f41218ff023e10000000a155106/content.htm

Don´t delete the destination of type H, it is used to connect with the ABAP Stack of PI.

Regards.

Rodrigo.

markangelo_dihiansan
Active Contributor
0 Kudos

Hello Rodrigo,

I'm sorry but I have to disagree To connect ECC to PI, you only need three rfc destination

two type T's (SAPSLDAPI and LCRSAPRFC) and either a type H or a type G (SAP_PROXY_ESR). Ultimately, the configuration in sxmb_adm -> integration engine configuration tells which will be used (type H or type G). So only one needs to be existing otherwise it will prompt

Hope this helps,

Mark

Former Member
0 Kudos

Hi Mark,

Even I faced the same error even though we created the destination of type H still it prompted that No connection to ESR exists until I create the connection to the ESR with the destination of type G (SAP_PROXY_ESR) and then the connection to ESR got established..

I was wondering when this new connection came in picture as I was under assumption this only required for java stack PI system..but i don't think..would be glad if you can explain which verison requires these connections...

Sorry Shakif for requesting the clarifications here...but for your problem to resolve i am sure you need to create the RFC destination SAP_PROXY_ESR with type G as already above..

Thanks & HTH

Rajesh

markangelo_dihiansan
Active Contributor
0 Kudos

Hello Rajesh,

We are on PI 7.1/7.11. Here is a screenshot from our ECC

We are only using one type H which points to our XI system

And the two type T (SAPSLDAPI and LCRSAPRFC)

Sproxy screenshot:

Hope this helps,

Mark

0 Kudos

Hi Mark,

In my other reply I left a wrong URL, the correct is:

http://help.sap.com/saphelp_nw73/helpdata/en/3b/dec6eaf3ac42fba8f92f2413ec930f/content.htm

The RFC destination LCRSAPRFC is required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile.

The RFC destination SAPSLDAPI is required for the connection to the SLD. It is used by the ABAP API.

Only RFC SAP_PROXY_ESR is used to connect to ESR (PI).

http://help.sap.com/saphelp_nw04s/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm

Regards.

Rodrigo.

markangelo_dihiansan
Active Contributor
0 Kudos

Thank you Rodrigo,

Here is the blog that we followed to enable ours

http://scn.sap.com/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

I guess, moving to versions 7.3 and above, the link you have pointed should be followed.

Regards,

Mark

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

yes,with PI 7.3 you can use the same docuement.

but i recommend you follow the links below to ensure you have all configured in the ecc system

POINT:"(4) Check parameters maintained in transaction SLDAPICUST"

http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm

and

http://help.sap.com/saphelp_nwce711/helpdata/en/bb/e8e8f27dba483faa754b10048fb036/content.htm

once you checked those link, go to SRROXY or SE80, position at:

you can press the button to validate it everithing is OK. just follow the steps.

note: when you press that button it will sugguest you con configure the

SAP_PROXY_ESR using port 80XX insted of 5XX00 but the real one is 5XX00


Former Member
0 Kudos

yes we created a RFC type G ..then the problem is solved

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

could yo solve it?

0 Kudos

Hi Mohamed,

Recently I had the same problem, the user used in the RFC destination SAP_PROXY_ESR was blocked.

Regards.

Rodrigo.

ambrish_mishra
Active Contributor
0 Kudos

The answer lies in the screenshot itself which says No connection to ESR.

Click on run connection test and you should be able to decipher the issue.

cheers,

Ambrish

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

that means that the password/user for ESR is not correct,

and you need to change it in the RFC dest,

Regards,

Michal Krawczyk