Acknowledgment for SO

[Former Member]

Hi,

I understand that using File to IDOC scenario, we can post the PO data (ORDERS.ORDERS05) from legacy sys to R/3 backend as IDOC.

My doubt is, do we need to implement IDOC to File scenario again in order to give acknowledgement to the customer (legacy sys). Or, any other way for giving the acknowledgement (confirmation).

Please help me.

Thanks

Prabhu.

[Former Member]

<i>Receiver adapters support system acknowledgments if they are requested by the server.

They are triggered if the message is processed successfully by the adapter.

The receiver adapters do not support any application acknowledgments.

http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm

Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender.

Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed.

Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments.

• Sender adapters of the Adapter Engine do not request any acknowledgments</i>

[Former Member]

Hi,

Are you talking of Technical Acknowledgement in terms of ALEAUD or are you intersted in the Order Confirmation, wherein a SalesOrder has been created in the vendors system in refernce to the PO?

1. For ALEAUD, you can configure a simple communication channel in XI to send back an acknowldegement. Refer to <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb">How to handle Acknowledgement for IDoc</a> for this.

2. For Order Confirmation, you need to design a Legacy-to-IDoc scenario, depending on the legacy system of your vendor. The Confirmation IDoc will be ORDRSP.ORDERS05.

Regards,

Amitabha

[MichalKrawczyk]

hi,

>>>>we can post the PO data (ORDERS.ORDERS05) from legacy sys to R/3 backend as IDOC.

of course ORDERS.ORDERS05 will not create PO in SAP but SO

hope this is what you expect...

for creating PO in SAP there is a completely different idoc

PO - SO idoc exchange as well as confirmations are described in my book:

<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[former_member431549]

If you are doing an asynch scenario to create the order (as you describe with idoc), then you will need another asynch scenario to send an ack back to other business system. So yes, you will ilkely need to configure an ORDRSP idoc out of R/3 and a scenario whereby this idoc is transformed into a file to be delivered to the legacy system.