MM-SUS-Invoice- ECS Scenario

[Former Member]

Hi Experts,

We have a client requirement for activating SUS functionality. The main objective is Suppliers should able to check their own Invoice Statuses which are created and posted in back end R/3.

We are using Extended Classic Scenario (SRM4.0 and ECC6.0).

My Doubts: I have come to know through some of my friends and SDN forums:

1. To check Invoice status in SUS portal, the Invoice should have originated from SUS. Then only it is possible to check/find status from SUS portal.

2. In Extended Classic Scenario, it is not possible to replicate PO's from R/3 to SUS portal.

3. Is it part of SAP standard Scenario or purely custom development would be required.

If above 2 points are true, is there any alternate solution available for SUS usage for Invoices while using ECS scenario.

Kindly advice.

Regards,

Karnati

[Former Member · Accepted solution]

Hi Karnati,

You are confusing between MM-SUS and SRM-SUS.

In extended classic : PO created in SRM EBP will be routed to SUS via XI. Supplier can then send a POR for this PO. The process stops here. Creating an ASN and invoice is a consulting solution provided by SAP

In classic scenario : PO created in MM will be will be routed to SUS via XI. Supplier can then send a POR for this PO. The process continues with the supplier sending an ASN and invoice.

Regards,

Nikhil

[Former Member]

Hi Nikhil,

Thanks for your response.

But our requirement is combination of MM-SUS , SRM-SUS with custom development for Invoices.

MM-SUS & SRM-SUS:

POs which are generated from R/3 and SRM needs to replicate to SUS.

Invoice originated and posted in R/3 should be replicated to SUS. As you said this would be custom development.

Just I would like is it possible to achieve results with custom development to satisfy above requirements?

Appreciate your response.

Regards,

Karnati

[Former Member]

Hi,

It is not possible to use a combination of MM-SUS and SRM-SUS as both of them operate on different technologies. MM system will receive an incoming document as an IDOC while SRM system receives it in XML format.

Regards,

Nikhil

[Former Member]

Hi Nikhil,

Thanks for your response.

In my scenario, All POs are available in R/3 irrespective of whether it is created and posted in R/3 or it is replicated from SRM/EBP (ECS Scenario).

For this sake, I would like to go for MM-SUS implementation.

My questions is:

1. Can I send all PO's from R/3 to SUS ( POs created in R/3 + POs replicated from EBP/SRM).

2. Can I get Invoice(Invoice with PO Reference) statuses to SUS, if Invoice is created and posted in R/3 with custom development.

3. Can I get Invoice(Non-PO Invoice) status to SUS, if Invoice is created and posted in R/3.

Kindly response and help to understand more about what SUS can and can not do.

Thanks,

Karnati

[Former Member]

Hi,

1. Can I send all PO's from R/3 to SUS ( POs created in R/3 + POs replicated from EBP/SRM) : No. Only POs created in MM can be sent to SUS in MM-SUS scenario.

2. Can I get Invoice(Invoice with PO Reference) statuses to SUS, if Invoice is created and posted in R/3 with custom development. : Invoice created in SUS will be replicated to MM and not the other way round in MM-SUS

3. Can I get Invoice(Non-PO Invoice) status to SUS, if Invoice is created and posted in R/3. : No

Regards,

Nikhil

[Former Member]

Hi Karnati,

SAP SRM extended classic scenario supports SUS only for purchase order and purchase order response in standard. Now, you need to take help of custom solution and XI/PI devlopment (to direct the invoice creation to MM instead of parent system of preceeding purchasing document) to trigger the creation of invoice in MM system.

Once the invoice is created in MM system, the suppliers can track the status of the same in SUS.

Thanks and regards,

Ranjan