SAP ECC To SRM Integration via SAP PI

[Former Member]

We are configuring the integration between SAP ECC and SRM through PI.

We have followed all the steps mentioned in this blog:

http://www.saptechnical.com/Tutorials/XI/AAE/v24.htm

and successfully configured the scnario : Send Sourcing Request

uptill now we have only one Receiver Agreement for the Send_Sourcing_Request. Do we need to create another Receiver agreement to send message from SRM to ECC ??

We have defined the connections in PI , pointing towards ECC and SRM and have created two communication channels of type receiver with both the connection name ( as defined in SM59).

[Former Member · Accepted solution]

Hi Hasan,

Yes you need to create one more receiver agreement to send message from SRM to ECC.

Thanks,

Satish.

[Former Member · Accepted solution]

Thanks Satish

Yes , i have created another sender agreement. when message is sent from SRM and received at PI , it is with red flag and the error is :

  <SAP:AdditionalText>No standard agreement found for , SRM, , EHP, http://sap.com/xi/APPL/Global2, PurchaseRequestERPSourcingConfirmation_In</SAP:AdditionalText>

<SAP:Stack>Problem occurred in receiver agreement for sender -SRM to receiver -EHP,http://sap.com/xi/APPL/Global2.PurchaseRequestERPSourcingConfirmation_In: No standard agreement found for , SRM, , EHP, http://sap.com/xi/APPL/Global2, PurchaseRequestERPSourcingConfirmation_In</SAP:Stack>

[Former Member · Accepted solution]

Hi Hasan,

Can you test the configuration in ID using Test Configuration in Tools Menu.

It is configuration issue.

Thanks,

Satish.

[Former Member · Accepted solution]

Thanks Satish

There was problem with my configuration, now it is working fine. The only problem is that when we create multiple PRs consecutively , the messages are received at SRM, but it creates Shopping Cart for one PR but throws error for another

An exception with the type CX_SY_CONVERSION_NO_NUM BER occurred, but was neither handled locally, nor  declared in a RAISING clause

however both the PRS are same, on debugging we find that the Id for the message is creating problem.

For example : successful message id: 201212192324

failed message id: A234E345F9085CD48E

Please not that the PI does send the message successfuly but wen SRM creates a shopping