SUS-MM - Mandatory Follow on Documents

[Former Member]

Dear Gurus,

After several discussion, We are going to implement SRM 7.0 with ECS and MM-SUS. In our case it fits with our requirements with less need of development than using the SRM-SUS.

I would like to confirm if it is optional for the suppliers to create in SUS each of the follow on document against the PO (so that they can also just sent out the invoice without sending out before the PO response and the ASN) or if the system requires them to post before the PO response, after the ASN and finally the invoice with no possibility to skip one or more of them.

Thanks in advance for clarify.

Best Regards,

Valentino

[Former Member]

ASN optional or mandatory is determined by confirmation control key maintained in ECC PO.

So without ASN also the supplier can submit the invoice in SUS if GR is done in ECC (for GR based IV option in ECC PO).

PO response is always optional as per standard SAP.

With Regards,

Malay

[Former Member]

Hi Malay,

I was testing the scenario MM-SUS as below:

I created a PO without marking the flag "Order acknoledgmet" in the PO confirmation tab.

Than Entered in SUS portal as supplier and and it was possible to create invoice against the PO as you stated without enterin the POR and ASN.

The issue I faced is that the invoice status remained as "Waiting for preceding documents" even if i posted the goods receipt against the ECC PO. .

Is any trick to leave optional the POR and ASN and allow post the invoice from SUS?

Thanks in advance for clarify.

Valentino

[Former Member]

Please check if you have sent the GR notification from ECC to SUS via the program RPODDELVRY.

With Regards,

Malay

[Former Member]

Hi Malay,

Thanks for your answer, it helped.

Unfortunately I'm still on a testing system with no access to the spro.

What I would need exactly to confirm if it is possible in MM-SUS to configure the PO confirmation control key to achieve the below result?

1.   1. A PO is sent to SUS and the supplier can process for this PO POR, ASN and invoices.

2.   2. Anyway POR and ASN creation  is always optional: their creation is allowed but is not mandatory. That means that the invoice creation and posting is possible even if no POR and ASN have been created.

I cannot access the spro to see how the confirmation control key it is customized in the testing environment, but so far I face the below result that is not exactly what I expect:

1. Acknowledgment required checkbox selected in the PO → the POR and ASN creation is mandatory.

2.   2. Acknowledgment required checkbox not selected → the POR and ASN creation in not possible at all. No follow on document are expected and the supplier can only display the PO.

Could you please confirm the first result mentioned above is possible with MM-SUS?

Thanks in advance

Best Regards,

Valentino

[Former Member]

POR and ASN can be optional or mandatory depending on Confirmation control key.

The confirmation control key can be configured in such a way that ASN is required and ASN can only follow POR.

In this case ASN can be created only after POR and GR in ECC can only be created if vendor has sent ASN in SUS and thereafter invoice will follow (for GR-based IV). This is is what happening in your case at present.

If in confirmation control key configuration ASN is not required and POR is possible, then the result you are expecting is possible in MM-SUS.

With Regards,

Malay

[Former Member]

Hello Malay,

Nice to see your inputs in this SDN Forum.

I would like to draw your attention to a problem I am currently facing.

I am on SRM 7.1 with ECC 6.0 Ehp5 and PI 7.1.

The scenario is MM-SUS p2p.

PO created in ECC and successfully transferred to SUS via PI. Supplier can login and Confirm or Create an ASN against the ECC PO. Both are happening successfully in SUS(at least documents can be seen in BBP_PD). However there is no XML being generated in SUS for both these.

SUS PO has status Confirmed and ASN has status Sent after processing.

After suggestions seen in SDN I maintained Event Definitions in SUS for all the outbound docs.

Conf. Cont. Key is maintained in Vendor Mater and PO both as 0001 and Ack. Reqrd. is ticked.

Still I think I am missing some config in SUS because of which XML is not getting generated.

Can you please give me some pointers?

Regards