MM-SUS procurement cycle without ASN possible?

[Former Member]

In MM-SUS

We are able to map, PO(ECC) > PO Display (SUS)> PO Response(SUS) > ASN(SUS) > IBD (ECC) > GR with Reference to IBD (ECC) > GR Display(SUS).

In some cases we also need,

We are able to map, PO(ECC) > PO Display (SUS)> PO Response(SUS) u2026u2026. GR with reference to PO (ECC) > GR Display(SUS).

Will it be possible? If so, what should be the message type in ALE (WE20)? What should be the message type for Inventory Management Document (i.e. GR).

Ganapathi

[Former Member · Accepted solution]

Hi Ganapathy,

For vendors with whom you need to carry out the procurement cycle without ASN, just remove the 'Confirmation Control Key' indicator in the vendor master. (001)

Thus these vendors will not have to create an ASN and you can create a GR with reference to PO.

Regards,

Nikhil

Edited by: Nikhil RGupta on Feb 10, 2011 6:58 PM

[Former Member · Accepted solution]

Dear Stephane Bailleul and Nikhil R Gupta,

Thanks for the response.

This is fine. But the questions are,

1. In ECC, when we do the GR with reference to PO what is the message type and IDOC?

2. What is the output type to define in TCode NACE, to trigger IDOC when we do the GR with reference to PO?

Ganapathi

[Former Member · Accepted solution]

Hi Ganapathy,

Do you want your GR confirmation to flow to your supplier? Try with Message type STPPOD.

Regards,

Nikhil

[Former Member · Accepted solution]

Dear Nikhil,

We have not yet tried STPPOD for the case, if we do the GR with reference to PO.

We are under the impression that, STPPOD will work only if we do GR with reference to Inbound Deliveryu2026

Did you mean STPPOD will work for both cases?

Ganapathi

[Former Member · Accepted solution]

Hi Ganapathi,

Create a GR in your ECC system. This GR info will flow into your SUS system if you define STPPOD in your outbound messages on the ECC side.

Then based on this, create an invoice from SUS.

Regards,

Nikhil

[Former Member · Accepted solution]

Hi,

Unfortunately STPPOD also did not work.

We were getting error as

Update was terminated

Error Info... Processing log for program RSNASTED routine EDI_PROCESSING.

Finally got resolved developing custom idoc message type

Closing the thread now.

Ganapathi

[Former Member]

In the MM SUS scenario you are not obliged to have an ASN

I doesn't change your setting on WE20,the asn depends on your agreement with the vendor, on SUS some will have to do the ASN whereas someothers don't need to do it .

So the interface between ECC and SUS don't need to be change because of the vendor.

Whereas the role of your vendor on SUS can include or not the ASN possibilities;

I hope it helps you

Cheers

Stephane