cancel
Showing results for 
Search instead for 
Did you mean: 

Messages are not transferring from PI to SRM

Former Member
0 Kudos

Hi,

Here the  land scape is ECC -PI-SRM, The messages transfer to ECC TO PI, But  messages not transfer  from  PI-SRM ,the scenarios  are Idoc-idoc & Idoc -proxy ,Here  all RFC  connections are working  fine, . In SRM side - T-code  sldcheck  getting the error -  function call  returned  exception code  3, and in SPROXY  T-CODE -  ESR  components are  not displaying, could please provide help .

Regards,

seetharam.

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Hi

here the messages pointing to  pi (upgrade) -old production SRM (non-upgrade), not picking the srm upgrade  and  could please provide help.

suresh_murugan
Explorer
0 Kudos

Hi Joshi,

If i understand correctly your PI system is pointing to incorrect SRM server is that right.

Did you do any upgrade, If so in which system and whats the old and the new version.

You have mentioned that the SLDCHCEK is giving a return code 3 , so is your SRM sever pointing to the correct PI server..

In SRM check the integration engine configuration using the tcode  SXMB_ADM.

Correct PI Server name should be maintained in the  Integration engine configuration in SRM and also the role of the business system should be set as Application system.

Do a full SLD cache refresh once.

Regards,

Suresh

Former Member
0 Kudos

Hi,

In addition to what Hareesh and Vinita pointed out, please refer below links to connect to SRM target via ABAP proxy. (Considering you are using AAE for this as you've SAP PI 7.31-Dual)

1. http://scn.sap.com/thread/3395495

2. http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef4...

Regards

Bibek

vinita_kasliwal
Active Contributor
0 Kudos

Hi M Joshi ,

Please check the below :

1) One RFC of type H to point to PI with all the details.

2) Define the role of the business system in the server that you want to see(Sxmb_Adm)

3)Connection between Business System and System Landscape Directory.

3a)RFC destination LCRSAPRFC of type T for SLD connection.

3b)RFC destination SAPSLDAPI of type T for SLD connection.

4)Maintain the SAP J2EE Connection parameters for LCRSAPRFC and SAPSLDAPI in SAP J2EE Engine

5)Maintain SLD access details in Transaction SLDAPICUST.

Please refer the section 1.3.1, 1.3.2, 1.3.3 and 1.3.4 in the document(as linked provided below)

SLDAPICUST should point to the SLD host server. If you have a central SLD installed on the Dev server, then it is ok that it is using the host and port of the Dev server.

PIAPPLUSER is the normal user that is used in trx SLDAPICUST (the user must have the role SAP_XI_APPL_SERV_USER).

'Lastly, will the gateway Server of SAPSLDAPI and LCRSAPRFC will be the same for both DEV and QAs systems in XI?'

For proxy configuration, refer the following link:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0ac1a33-debf-2c10-45bf-fb19f6e15...

you can also check the assignment between the Business System , technical system and the software component versions in the SLD.A object would only be visible in the SPROXY of an Applicaion system if the corresponding SCWV is installed on the business system.

To add :

Go to the landscape view in the SLD.

Select the Technical System Link

Search your Technical system as Application system

Click on the same

A  tabbed screen appears in the bottom.

Go to installed software tab.

Click ADD NEW PRODUCT

Add your product here. 

Also check the business System assignment in the similar way.

suresh_murugan
Explorer
0 Kudos

Hi,

In SRM check the integration engine configuration using the tcode SXMB_ADM.

Correct PI Server name should be maintained in the  Integration engine configuration in SRM and also the role of the business system should be set as Application system.

Regards,

Suresh

former_member190624
Active Contributor
0 Kudos

Hi,

Seems like your SRM system was not connected to the SLD. Do connection tests for  TCP/IP RFC destinations SAPSLDAPI and LCRSAPRFC.

Thanks

Hari.

Pranil1
Participant
0 Kudos

Hi,

In addition to what Amit has suggested, you can check below troubleshooting guide also.

Refer point 17.1.1.6 which is specific to your error.

Also see points 6.1.1 - 6.1.1.2.7 and check all the prerequisites listed.

SAP NW PI Troubleshooting Guide

Regards,

Pranil.

Former Member
0 Kudos

Hello,

>>SPROXY  T-CODE -  ESR  components are  not displaying, could please provide help

It seems that abap proxy connectivity in SRM is not working. Create RFC destination in SRM to connect PI ESR so that ur porxy gets reflected under sproxy.

BTW, which version of PI u are using?

Thanks

Amit Srivastava

Message was edited by: Amit Srivastava

Former Member
0 Kudos

Hi,

The pi version is 7.31 dual stack.

Regards,

seetharam

former_member184720
Active Contributor
0 Kudos

Hi Joshi - It still remains the same.. Did you create the RFC destination of type "G"(SAP_PROXY_ESR) in SRM? is it working fine?

Former Member
0 Kudos

Hello,

Did u tried implemeting the steps shown in the blog shared above?

If yes, then what's the error u are getting now?

Please be descriptive enough so that people can help u instead of making wild guess abt ur issue.

Thanks

Amit Srivastava