This document describes step by step with screenshots how to connect an ERP6.04 ABAP system to 7.10 PI system.

STEP1 Login to your NWA via: http://<IP or Hostname of PI>:5SN00/nwa and navigate to configuration wizard (SN refers to System number) and execute FQDN:

Configuration Management–>Scenarios–>Configuration Wizard

You are recommended to execute FQDN-Hostname configuration at first. It registers FQDN of your PI to related areas:

/wp-content/uploads/2014/12/1_613749.png


STEP2 – Get certificates of both PI and ERP systems, from STRUST. You can save to your local as binary files. Then exchange them between the systems, via STRUSTSSO2. Add the certificates both to ACL and certificate list. Please keep in mind that those parameters should be set in both systems:

login/accept_sso2_ticket = 1

login/create_sso2_ticket = 2

/wp-content/uploads/2014/12/2_613750.png

STEP3 – Create RFC destinations in the satellite business system. All RFCs should be marked as “Unicode”. The values will be used later in Netweaver Administrator to match the RFCs with the PI system.

After all RFCs will be created we can check them via transaction code SLDCHECK.

1st RFC: <PI_SID>_HTTPDESTINATION

/wp-content/uploads/2014/12/4_613831.png

Logon client is default PI client. In technical settings tab, fill the target host and service no (5SN00) information regarding to the PI system. Path prefix: /sap/xi/engine?type=entry

2nd RFC: INTEGRATION_SERVER_<PI_SID>

/wp-content/uploads/2014/12/7_613814.png

Unbenanntes Bild.png

Technical settings tab is same as the first RFC.

3rd RFC : LCRSAPRFC

/wp-content/uploads/2014/12/8_613762.png

Program ID: LCRSAPRFC_<PI_SID>

4th RFC :SAPSLDAPI

/wp-content/uploads/2014/12/10_613759.png

Program ID: SAPSLDAPI_<PI_SID>

STEP4 – Transaction Code : SLDAPICUST

Provide a PI system user name (SLD_CL_<SID_PI>) to send SLD datas to PI system. Give PI system and port in the related fields. Check the inputs from tcode SLDCHECK afterwards.

/wp-content/uploads/2014/12/12_613755.png

STEP5 – Transaction Code : RZ70

Schedule the background job, which sends ERP system data (satellite business system) to PI system. SLD Bridge refers to PI system.

/wp-content/uploads/2014/12/13_613769.png

STEP6 – Adding ERP ABAP system as a “Business System” to PI SLD. Login to sld:

http://<IP or Hostname of PI>:5SN00/sld

After scheduling RZ70 background job and execute it for the first time, we should be able to see ERP system under “Technical Systems”. Now we will add it as a “Business System“. Navigate to “Bus. System”–>Add new :

/wp-content/uploads/2014/12/14_613763.png

Select ERP ABAP system as “Technical system” from dropdown menu:

/wp-content/uploads/2014/12/15_613761.png

After completing this registration, check from business systems list whether your ERP ABAP system has been added successfully.

STEP7 – Transaction code : SXMB_ADM

Navigate to “Integration Engine Configuration” and choose your PI system as “Corresponding Integ. Server” :

/wp-content/uploads/2014/12/17_613760.png

“Specific configuration” :

/wp-content/uploads/2014/12/18_613764.png

STEP8 – Check your inputs from transaction code SLDCHECK once more :

/wp-content/uploads/2014/12/19_613768.png20.png

STEP9Login to your NWA via: http://<IP or Hostname of PI>:5SN00/nwa and navigate to configuration wizard (SN refers to System number):

Configuration Management–>Scenarios–>Configuration Wizard

Execute “NW PI – AS ABAP (Basic Configuration for Idoc, Proxy): Maintain” job. This job will approve the inputs we had entered before and register them in PI side. You’ll be asked to enter administrative users of both PI and ABAP ERP system.

/wp-content/uploads/2014/12/21_613767.png

I’ve added some example screens to give an idea about the process.

During the execution, useful links and SAP notes will be recommended and advised. One can read and find useful information about integration structure within those links.

/wp-content/uploads/2014/12/22_613770.png

/wp-content/uploads/2014/12/23_613771.png

Some error and warning windows during the execution:

/wp-content/uploads/2014/12/24_613775.png

Reason: Logical name and client tables can not be written. You can skip.

/wp-content/uploads/2014/12/25_613774.png

Reason: SAP_ALL rights to PIAPPLUSER user. You can skip.

/wp-content/uploads/2014/12/27_613772.png

If you will have an IDX structure, you can edit it. Otherwise skip it.

/wp-content/uploads/2014/12/26_613773.png

Reason: You can skip this warning. We don’t want to change the password.

After completion you’ll see this window.

/wp-content/uploads/2014/12/28_613776.png

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply