Data not posting to PI from ECC using proxy

[former_member201264]

Hi

Please give me step by step explaination regarding ECC settings and Pi settings for this scenario.

Regards

Sreeni

[former_member201264]

I understand this.

Thank you.

[Former Member]

Hey,

These are the settings that are to be done on the application server.

R3 side

SLDCHECK

Use this transaction to access the SLD of XI.

SLDAPICUST

Create an entry for respective XI server

requires hostname, port username and ip.

Can have multiple enteries for different servers.

But you can check only one entry.

based on the entry that is checked, respective SLD API will be triggered from

SLDCHECK.

SM59 (T type connections).

To connect to the SLD you need 2 types of TCP/IP connections.

1)LCRSAPRFC:-

In this you require the gateway host(ip address) and gatewayservice(sapgw[system no.])

YOu also need to give Program ID.

Entry of corresponding Program ID must be maintained in SMGW.

IN SMGW Click GoTo->logged on Clients.

If entry is not there for corresponding XI.

Create a communication channel in XI, pointing to R3 and give a Program ID

in the channel. Once the channel is activated, corresponding Program ID wil

appear in SMGW.

2)SAPSLDAPI:-

In this case follow the same porcedure as for LCRSAPRFC.

As far as the Program ID is concerned te procedure mentioned above is for

Customized RFC's

The RFC destinations mentioned here are both standard RFC's

Hence for these two RFC's no need to Create Program ID's. you just need to

change the System ID of the Program ID.

Both these RFC's are maintained in the J2ee server of XI.

SPROXY.

In this transcation you can check the Proxies.

If the proxies are not activated (i.e. if the message interfaces are not active)

then you need to maintain one G type RFC destination pointing the resepctive XI server.

In the G tpye RFC destination give the Ip adress of the XI server in the target

host and set the path prefix as /rep.

Goto SPROXY->Goto->connection test-> click on the table SPROXSET.

In this table maintain enteries for ADDRESS_ONLY_FROM_SPROXSET and IFR_HTTP_DEST

The values corresponding to these enteries will be the G tpye RFC destination.

In order to connect R3 to the Integaration server you need to maintain H type

The default RFC is XI_INTEGRATIONSERVER. In you need to give the Target host entry as the

Ip address and Path Prefic as.../sap/XI/engine/?type=entry (this you can get from SXMB_ADM of XI)

You can also create the H type RFc of your own.

goto SXMB_ADM(r3) and open Integration engine configuration.

Goto edit->change global configuration and give the RFC dest name like this:-

Corresponding Integration server:- dest://{h-type rfc destination}

If you do not want to create RFC destination you can directly give

the Integration server address(that you can obtain from SXMB_ADM of XI) in the

Corresponding Integration server field.

regards,

Milan Thaker

[former_member206760]

dear kancham,

first you need to ensure that the proxy connections are OK.

For that type tcode sldcheck in ECC and see that all are greens

also chk tcode sprxoy in ECC and see that your namespace and outbound interface are visible there...it should not give any status message like "no ESR data displayed"

[Former Member]

Hi ,

just tell in detail whats ur problem ? Any activation problem ? Interface problem ?

[Former Member]

Hi,

Refer to this blog

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

Regards,

Balaji.M