cancel
Showing results for 
Search instead for 
Did you mean: 

EDI Mapping/VoE2 and VoE4 settings for Sales Order creation via IDoc

0 Kudos

Dear Experts,

I have a scenario where my Customer and its partner systems both are in SAP S4HANA. Here my Customer (assume ABC) is creating a Purchase Order for Partner (assume DEF) and send the PO as an IDoc to partner system to create a Sales Order. I understand in the receiving system (DEF) we need to maintain VOE2/4 settings to determine the external partner and map it to an internal partner. Please see the screens below.

Please see the PO to DEF

Outbound ORDERS IDoc

E1EDK01

E1EDKA1 AG

E1EDKA1 LF

E1EDKA1 LS

E1EDKA1 WE

VOE2/VOE4 Settings in the Partner System

When the IDoc is trying to create the Sales Order, it is not able determine the Sales Data for this external partner. Now I am not able to understand where the configurations are going wrong. Do I need to tweak the Orders IDoc in partner information before sending?

If yes, please suggest how as per above screen shots. I mean what values to ensure correct partner/sales data determination.

Some quick help will be highly appreciated. Please let me know if you need more information.

Thanks in advance!

Cheers!

Amitabh

0 Kudos
Can someone help in this please!

Regards

Amitabh

Accepted Solutions (0)

Answers (2)

Answers (2)

VeselinaPeykova
Active Contributor
0 Kudos

The concept of setting up VOE2 and VOE4 is the same in ECC and S/4HANA, so if you know how to configure the process in ECC you should be able to do so in S/4.

From your screenshots it seems that this is the first time you work with VOE2 and VOE4. This is why I suggest that you start by reading a bit more on the subject here.

If after reading the documentation and changing your setup you are still unable to figure out why the inbound IDOC ends in error status it may be a good idea to resort to debugging (at least this is what I did some time ago in a highly customized system with no functional and development documentation.

Lakshmipathi
Active Contributor
0 Kudos

Have a look at OSS note 1158386