Question Re: SUS - Multiple backend systems (MM & SRM) in Spend Management Q&A

SUS - Multiple backend systems (MM & SRM)

Former Member — Thu, 19 Jan 2012 12:25:30 GMT

I am implementing a SUS client linked to both SRM (seperate client) and MM.

SAP refer to this as the 1:n scenario http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm

All interfaces are working correctly except for SUS PO confirmation --> Backend.

For MM-SUS the PO confirmation message route is:

SUS to PI - PurchaseOrderConfirmation_Out

PI to ERP - ORDRSP.ORDERS02 idoc

For SRM-SUS the PO confirmation message route is:

SUS to PI - PurchaseOrderConfirmation_Out

PI to SRM - PurchaseOrderConfirmation_In

The problem we have is getting PI to send the appropriate message back to the appropriate backend system.

Has anyone implemented this scenario?

If so can you explain how PI deals with this?

Do we need 2 interfaces in place?

Thanks

James

Edited by: J-Wilson on Jan 19, 2012 1:25 PM

Re: SUS - Multiple backend systems (MM & SRM)

Former Member — Thu, 19 Jan 2012 14:08:47 GMT

i nthe XML you have sender and receiver information .. use that in PI to direct it to required system

Re: SUS - Multiple backend systems (MM & SRM)

Former Member — Thu, 19 Jan 2012 15:18:56 GMT

Thanks, we have already used the sender (as you suggested) to route the message correctly. This works to an extent as the confirmations are routed to the appropriate system (ERP or SRM). However, PI is attempting to send the confirmations to both ERP and SRM as idocs. We need PI to send to ERP as idoc and SRM as xml.

Re: SUS - Multiple backend systems (MM & SRM)

Former Member — Thu, 19 Jan 2012 16:16:16 GMT

thats something to do with PI.

they get source XML from SUS. and in PI after deciding target system they have to decide the target. I dont have that much knowledge on PI but i know that they have a place in the integration builder to pass the condition for a field from XML. according to that they need to decide the target interface..

i think SAP must have provided guidelines for PI to configure for SUS.