Page tree
Skip to end of metadata
Go to start of metadata


In a typical order to cash scenario in between a Customer and the vendor, sometimes, the vendor need to send an Order confirmation back to the customer. The order confirmation essentially tells the customer, whether the order has been accepted or rejected by the vendor.
In EDI Parlance, a purchase order is represented by the Transaction set 850. And the Order Confirmation is represented by the set 855.
Typically a 850 is mapped to the ORDERS IDOC on sap side (Inbound) and the order response idoc ORDRSP is mapped to 855.
In case the order gets successfully created by the ORDERS Idoc, then an Order Response Idoc can be triggered automatically by doing the necessary backend configuration.
The problem of sending an 855 will arise in the case of an Order NOT being created due to some reason. We will try to address this issue in the web log.

The Problem 

Consider the following scenario.

You are a Vendor using SAP ERP and your customer sends the Orders via EDI (Electronic Data Interchange). The requirement is that you have to send an EDI Order confirmation whenever you receive an order from the customer.

To rephrase the requirement in slightly technical terms, the customers sends an EDI 850 document(Purchase Order) and you need to send a EDI 855 document(Order Confirmation).The EDI 855 can be a positive confirmation , saying that the order has been accepted or a negative confirmation, saying that the order has been rejected due to some reason.

Typically, if you have Netweaver XI/PI in your landscape, the solution for this requirement would be to map the EDI 850 document to ORDERS Idoc and map the Order response Idoc (ORDRSP) to the EDI 855 document.

This solution would work so long as the order gets successfully created in the backend and the outbound Order response idoc gets triggered in the backend. The problem arises, when the ORDERS idoc fails to create a Sales Order in our system. In which case, there would be no Order response idoc being triggered at all.

The Solution 

In such cases, we can adopt the following approach to solve this problem.

Create a client proxy for the inbound asynchronous interface for Order Response (855) that is created in XI integration repository, using SPROXY transaction. Refer the following link:

Identify a USER EXIT in the inbound idoc processing function module (IDOC_INPUT_ORDERS) .In this case, it is EXIT_SAPLVEDA_004. Populate the proxy class's interface tables and call the outbound proxy using the methods of the proxy class that is generated. Refer the following to see how to send a message using a client proxy:

This proxy class will cater the information to the outbound EDI 855 document, which is sent to the customer as a negative confirmation.