Problems with subsequent documents - SRM-SUS

[Former Member]

Hi experts,

We are working with the integration scenario ECC 6.0 with SRM-SUS 7.2 and we have the following problem:

When we migrated a PO of ECC for SUS are not available all subsequent documents such as standards attached.

What may be happening?

Dhan Unmesh

[Former Member · Accepted solution]

Please check the correct confirmation control key in ECC PO.

Shipment notification appears in SUS only when the PO has confirmation control key which entails inbound delivery.

With Regards,

Malay

[Former Member · Accepted solution]

Thank's for attention Malay...

What's "control key in ECC PO"?

We need to understand is whether there is any way to configure the followingdocuments in the SUS, because when we create and confirm a PO is onlyavailable option to generate an invoice, skipping the process of creating an ASN,for example.

Regards,

Dhan

[Former Member · Accepted solution]

You can use confirmation control key "0001" available in standard.

There is no other way to have or skip ASN other than confirmation control key.

Invoice generation has link with goods receipt if the PO line item is GR-based IV. Invoice has no link with ASN.

If there is ASN, GR Can be done against the ASN only.

With Regards,

Malay

[Former Member · Accepted solution]

Hi Dhan,

Followon actions are depend on the indicators in PO, if PO has GR Based IV then Create ASN button will enable, please check the PO once again.

Regards,

Raghu

[Former Member · Accepted solution]

As pointed by Malay, ASN depends on confirmation control key and not G/R based I/V indicator.

Kindly plug 0001 as the confirmation control key in the vendor master information, so that when a PO with this vendor is created in ECC, the vendor in SUS gets the create ASN option.

Regards,

Nikhil

[Former Member · Accepted solution]

Thanks for the answers ... but this parameter in the master vendor was filled (as picture) ...

The problem continues ...

One question: We are working with IDOC (ORDERS) to send the PO to the SUS. This information has to be in the structure of IDOC?

Other:

We had an up grade version of 6.0 to 4.6C (ECC) ... may have been some change in the system that prevented proper operation?

Regards,

Dhan

[Former Member · Accepted solution]

Have you set up the partner profile/Distribution model accordingly to send out the IDOC?

Nikhil

[Former Member · Accepted solution]

Although you have maintained the master data, please check in PO also. If not it has to be maintained manually in PO.

In PO, Confirmation control comes from info record (1st priority).

With Regards,

Malay