cancel
Showing results for 
Search instead for 
Did you mean: 

how to design the landscape of sap pi in integrating with two sap pi system

Former Member
0 Kudos

hello experts,

Please explain about the design of landscape according to the standard SAP system,  as per the clients requirement we have to design the system,

using the two PI system.                                       CRM--->                                                             <-----CRM

                        

                                                            PROXY

BW--->      SAP PI    < ---------->  SAP PI               <------BW

                             

    

ECC--->                                                       <-------ECC

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

hello sir,

how to manage the current secnario, do i have to develop the interface between ECC and Pi and Also another interface between PI to PI connection as far as my knowledge the connection between two PI can only be possible by the PROXY adapter.

And also suggest which adapter  would be suitable for ECC to PI and PI to PI.

Please explain what will the first step to start the integration.?

Former Member
0 Kudos

Hi Mohit,

It should have been cleared now as explained by Harish.

ECC to PI. (ECC i sending data by IDOC):

Create below objects:

Receiver determination(second PI business system)

interface deter, receiver agreement,

And now here comes logic for PI to PI one:

in the above scenario, create soap receiver CC with XI message protocol and refer type "H" destination(which you will have to create on first PI box, which will have target host name details of second PI box)--refer thread link sent by Muniyappan and reply by Rajeev Gupta.

So this completes your ECC to first PI and first PI to second PI configuration.

Create second scenario on second PI system:

As the message is already sent by first PI box to Second PI box integration engine,no need of sender adapter, sender agreement.

Create receiver determination(bank legacy one)

Receiver CC and agreement.

--Divyesh

Former Member
0 Kudos

hello Divyesh,

I appreciate your response to this post, but the secnario s little different then what you r suggesting , i have told that :-

ECC(RFC)------->PI(ANY ADAPTER)<------------>PI(ANY ADAPTER)------->ENET(IDOC)

please suggest now.

Former Member
0 Kudos

Hi Mohit,

your requirement is now:

ECC(RFC)------->PI(ANY ADAPTER)<------------>PI(ANY ADAPTER)------->ENET(IDOC)

ECC to PI. (ECC i sending data by IDOC):

Create below objects:

Sender RFC adapter

Receiver determination(second PI business system)

interface deter, receiver agreement,

And now here comes logic for PI to PI one:

in the above scenario, create soap receiver CC with XI message protocol and refer type "H" destination(which you will have to create on first PI box, which will have target host name details of second PI box)--refer thread link sent by Muniyappan and reply by Rajeev Gupta.

So this completes your ECC to first PI and first PI to second PI configuration.

Create second scenario on second PI system:

As the message is already sent by first PI box to Second PI box integration engine:

no need of sender adapter and sender agreement.

Create receiver determination(bank legacy one)

Receiver CC of IDOC type and receiver agreement

--Divyesh

Former Member
0 Kudos

RFC(ECC) is sender Adapter not IDOC. IDOC is reciever adapter at last reciever(ENET).. please check.

Former Member
0 Kudos

hello divyesh,

please try to explain step by step. Please dont just through at me As i am very new for this scenario.

Thanks

Mohit

Former Member
0 Kudos

Hi Mohit,

It is already complete steps on objects you need to create in ID.

Please search SDN for any specific question you have.

--Divyesh

Harish
Active Contributor
0 Kudos

Hi Mohit,

the possible options to connect two pi systems

xi adapter when both pi system is dual stack

Xi over soap for single and dual stack and sender pi in on 7.3+ versio

soap connection for any version or stack

the preferred option is xi over soap and the reason is compatibility with future release and single stack version. Easy traceability of message because it can have same msg I'd on both system.

hope this help

Harish

Former Member
0 Kudos

hello sir,

how to manage the current secnario, do i have to develop the interface between ECC and Pi and Also another interface between PI to PI connection as far as my knowledge the connection between two PI can only be possible by the PROXY adapter.

And also suggest which adapter  would be suitable for ECC to PI and PI to PI.

Please explain what will the first step to start the integration.?

Harish
Active Contributor
0 Kudos
  • Hi Mohit,

your configuration can be like

ECC -(IDOC/RFC/PROXY)--> PI --(XI/SOAP)-> PI ---> Receiver system

So from ECC you can send data via proxy, idoc or RFC and you do not need the sender communication channel (except for ICO).

Configuration object

First PI

  • Receiver Determination
  • Interface determination
  • Receiver agreement
  • Receiver channel (XI or SOAP)

Second PI

  • Sender agreement in case of SOAP scenario or ICO
  • Receiver determination
  • Interface determination
  • Receiver agreement
  • receiver channel

I hope it clear your doubt

regards,

Harish

Former Member
0 Kudos

hello Sir,

That means two interfaces needs two be designed and like i have RFC adapter in ECC and  XI adapter shud be used in PI?

And In PI to PI section only Proxy can be used.

Harish
Active Contributor
0 Kudos

Hi Mohit,

Yes you need two interfaces one is interface on first PI and second on second PI.

for PI to PI communication you can use XI adapter (proxy also use XI protocol/adapter), but you need to make sure that receiver interface name, namespace and SWCV of first PI is same as sender interface name, namespace and SWCV.

Former Member
0 Kudos

hello sir,

By the client side they want the the adapter shud be IDOC and they want the message shud be in XML format.

How will be this possible.?

Sir If u have any document Concerning this then please share into my mailID:- mohit.sappi@gmail.com

Muniyappan
Active Contributor
0 Kudos

Hi Mohit,

please don't ask anything to send it to your mail id. you can ask to share the links in this thread only. so that it can help others.

and no need call anyone Sir. just use their name.

Regards,

Muni.

Harish
Active Contributor
0 Kudos

Hi Mohit,

Please check the below links

Introduction to IDoc-XI-File scenario and compl... | SCN

you need to use receive XI adapter in place of File adapter and in second PI use the same interface name, namespace and swcv.

hope it wil help

Former Member
0 Kudos

hello Harish,

Thanks for various response its will be very helpful, but I m Still in little doubt as :-

                                                        PROXY

ECC(RFC)------->PI(ANY ADAPTER)<------------>PI(ANY ADAPTER)------->ENET(IDOC)

This is the exact picture of the system.

please put some more light on this, and tell me the exact solution because i am getting confuse by various suggestions.

Harish
Active Contributor
0 Kudos

Hi Mohit,

                                                        PROXY

ECC(RFC)------->PI(ANY ADAPTER) it can be only XI or soap<------------>PI(ANY ADAPTER) (if you are connecting to SAP then IDOC adapter)------->ENET(IDOC)

hope it help

Harish

Former Member
0 Kudos

Hi,

We have implemented many scenarios where PI of business environment talks with PI of another business environment.

Most commonly used protocols.

1)SOAP

2)FTP

I would recommend you to either go with SFTP/PGP or SOAP in secured manner.

Regards

Venkat

Muniyappan
Active Contributor
0 Kudos

Hi,

did you check

Regards,

Muni.