Modification for ECS for invoice and ASN functionality in SUS

[Former Member]

Hello Experts:

Currently I am implementing SRM 5.0 with SUS integration in ECS. I have found some references that specify that if my requirement is to have the creation of Invoices and ASN in SUS, in order to transfer these to EBP I need to do some development on my own. I have to questions regarding this:

1.- The references only talks about Materials, is it possible to do this kind of implementation also for Invoices and ASNs of Services??

2.- Any of you could provide me with some general steps of the activities to be done in order to accomplish this requirement if I am using XI.

Thanks for all the information you can provide me.

Hugo

[Former Member]

Thanks Sanjeev:

So if I require the full capacity of PO, POR, Conf/Service Entry and Invoice coming from SUS to ECC for services, the best choice would be SRM-SUS using the Classic Scenario right? and form direct materials I should use MM-SUS?

My exact requirement is to be able to use de full functionality in SUS for the creation of PO, POR, Conf/Service Entry and Invoice for Materials and Services and to be able to send them to the backend (ECC).

Thanks

Hugo

[Former Member]

for sr no 2

config guides of business scnario

PDP SI - pland drive procurement supplier integration

service procurement

will help you. available at

service.sap.com/ibc-srm

BR

Dinesh

[former_member206968]

Hi

SRM-SUS integration is mainly used for service procurement where the document flow is PO> PO Response> Confirmation/Service Entry-->Invoice.

ASN doesn't carry any meaning for service procurement. You might use ASN if you are procuring direct materials.This is covered by MM-SUS integration.

Also pl. remember that SRM-SUS integration with ECS scenario is supported only to a limited extent by SAP. This means that your SUS confirmations when they come to SRM do not get replicated to ECC backend.

Thanks

Sanjeev