SAP PO for Beginners Part 4 – PI to ECC Adapter Connectivity Configuration. This is the fourth post in my blog series on “SAP PO – Cycle Arrangement for Amateurs”. In this post we will see the setup steps associated with interfacing PO and ECC framework through IDoc, RFC and Intermediary Connectors.
To put it plainly, underneath is the substance we will expand in this instructional exercise:
- Proxy (SOAP XI3.0) Adapter Connectivity
- RFC Adapter Connectivity
- IDOC Adapter Connectivity
Prior to going into the availability arrangement between SAP ECC (ABAP) to Drain PO (Single Stack), we want to see what are the connectors engaged with interfacing with ECC ABAP framework. SAP PO for Beginners Part 4 – PI to ECC Adapter Connectivity Configuration.
IDoc
Let’s assume we really want to send the client ace data at whatever point its saved or rolled out certain improvements. All things considered, we don’t need to construct fields which should be communicated and keep up with a similar in SAP PO by making information types and message types, rather in ECC, we have standard IDocs that are accessible which can be imported in SAP PO too in ESR. To broaden the standard IDoc, they can do likewise by expanding it. In SAP PO, we have IDOC_AAE connector for association.
Proxy
Say from ECC, we want to send huge number of records and ought to be of continuous to the collector, then, at that point, Intermediary association is suggested. For intermediary association, in SAP PO we use Cleanser connector with message convention as XI 3.0. Intermediaries are mostly utilized when the size of the info information is colossal. For instance, assume in ECC we have a table where we have 1 million records, and we want to send this entire information to an outsider framework utilizing PI.
In these cases, we will make a design in PI which will contain the construction of the table records.
Then, at that point, we will have administration interface which will utilize the design we have made. When we have the assistance interface , we want to make the intermediary structure in ECC utilizing exchange SPROXY.
Thus, in ECC we will compose a program which will choose every one of the 1 million columns utilizing select question, then, at that point, the program will call the intermediary structure and sends the entire information to the coordination motor of PI. We don’t have to make a shipper correspondence channel for sending the information to PI.
RFC
RFC based connector associations are very little broadly utilized in undertakings, because of its temperament of transmission, as it is utilized exclusively for Simultaneous correspondence. One of the hindrances of RFC connector in SAP PI is that it sits on Java Motor of PI. Thus, at whatever point you should call a RFC, the solicitation goes by means of Java Motor to the pertinent SAP R/3 which is compromise.
Thus, we had an outline on when to involve which connector in SAP PO for associating with ECC ABAP frameworks. How about we begin with network arrangement.
1. Intermediary (Cleanser XI3.0) Connector network
In any case, we will see the plan that ought to be done in ECC structure.
- Make Coherent Framework in ECC Framework for PO framework utilizing Tcode BD54.
In the above screenshot we can see that we have created logical systems for PO systems (Dev, QA & Prod).
- Create RFC Destination in SM59 of Type G, which will point to the PO system.
- Go to Tcode SM59 and select the Type G – HTTP Connections for External Server and click on Create icon.
- Provide the RFC destination name and description and with two more additional details: Target Host, Service No. & Path prefix. These are the main parameters involved in connection to SAP PO system.
- Target host – SAP PO host name
Service no – BASIS team knows it
- Path Prefix – /XISOAPAdapter/MessageServlet?ximessage=true
- Now go to SXMB_ADM transaction, hit “Integration Engine Configuration” and click on Configuration icon.
Category – Runtime – IS_URL –
i. Subparameter =
ii. Current Value = dest://(RFC Destination which we created in above step)
The value should be in below format:
dest://SAP_PO_ESR. (SAP_PO_ESR is the type G destination you created earlier)
Thus, what we have done is the association RFC objective creation for conveying from ECC to PO. One more RFC of Type G RFC objective should be made for associating the made items from SPROXY to ESR storehouse.
- This RFC objective is utilized by exchange SPROXY to import Undertaking Storehouse protests and produce Intermediary objects. You can name the RFC objective SAP_PROXY_ESR.
- Same way create another Type G connection.
- Target Host – PO system
Service (port)
Path Prefix – /rep
- Next step is to create SLD access data from ECC system via Tcode SLDAPICUST .
- Go to transaction SLDAPICUST and add the SLD HTTP Destination name.
- There are two ways to connect to SLD, one is via direct hostname connection and another one is via HTTP destination that has to be created separately for SLD access.
- In our configuration, we used first method, where we entered the PO hostname and port with required user access maintained.
- Up until this point, we have kept up with the outbound associations, and that implies from ECC to PO. Presently we want to make one more RFC objective in PO NWA (NetWeaver Manager) which will guide the intermediary association toward ECC framework.
Navigate to PO NWA -> Configuration -> Infrastructure -> Destination
Maintain the URL as – http://<ECC_host>:<port>/sap/xi/engine?type=entry and the necessary logon credentials of ECC system.
ALL Associations Connected with Intermediary Correspondence IS Finished. Testing time. Testing should be possible in SM59 in the RFC objective you made – SAP_PO_ESR.
Click on Association Test and check whether reaction code is 200 which implies ready to interface.
2. IDOC_AAE Connectivity
For IDoc correspondences, similarly we want to make RFC objections yet of Type T.
Notice a Program ID, Passage Host as SAP PO server’s host name and Entryway Administration of PO (like sapgw00). ProgramID gave here will be utilized in foundation setups of PO framework.
Note: Go to Unicode Tab here and select radio button “UNICODE”.
Make Port in WE21 of type Value-based RFC and dole out RFC which we made in above step.
We have kept up with the essential associations and presently its in PO NWA side, where we really want to keep up with the HTTP objective to acknowledge the IDoc associations coming from ECC RFC objective. Give the Objective Host (ECC framework), framework no. also, the fundamental logon accreditations.
Note :- Another objective should be made with same settings as above for metadata XI_IDOC_DEFAULT_Destination_
- Next step is to setup connectivity between PO to ECC, for INBOUND IDOC transmissions.
- Navigate to PO NWA -> Configuration -> Infrastructure -> Application Resources.
- Search for “InboundRA” of type Resource Adapter
- Click on Properties tab
- Give value for parameter ProgramID same as we have given in RFC destination we created in ECC system.
- Give value for parameter “MaxReaderThreadCount” between 5 to 10.
- Give value for parameter “Local” as “true”.
3. RFC Adapter Connectivity
- For utilizing Shipper RFC Connector, we want to make RFC Objective of Type T in Tcode SM59. While making the ProgramID in RFC objective creation it will be utilized at Source RFC Correspondence Divert in PO.
- For getting RFC connector, we really want to give properties of target ECC framework like Application Server, Framework Number, Client, Logon Client and secret word and so on straightforwardly in collector correspondence channel. Thus, no arrangement is required.
Trust this instructional exercise provided you with a fair thought of the various Connectors in SAP PI/PO. Assuming you have any inquiries, if it’s not too much trouble, go ahead and put it in the remarks areas underneath. Additionally, assuming that you have any ideas, criticism positive or negative, kindly put in the remarks area.
YOU MAY LIKE THIS
SAP SD (Sales & Distribution) Training Course Admission Details
ALE and IDoc in SAP ABAP: A Deep Dive
SAP ABAP Training Institute in Pune, SAP ABAP Courses Online
WhatsApp us