VOE4 and VOE2 entries explanation

[Former Member]

Hi,

Can somebody explain about this two Tcodes, i have maintained some entries for EDI processing for Idoc generation, and i have the basic idea of these 2 Tcodes.

I am looking for the documentation on this, pls provide.points can be rewarded!

Regards

syed

[Former Member]

Hello Syed,

Just to get the idea of EDSDC and EDPAR am giving this so that you can get some more knowledge in the two transaction codes.

Firstly, both EDSDC and EDPAR are used for inbound sales processing only. They are not considered by the purchasing module of SAP.

What you can do with EDPAR (the transaction used is VOE4) is map the customers external partner numbers (their plants/ship to addresses) to your own internal customer numbers in KNA1. Thus if the customer calls its delivery address ABC, and you have a customer record for this ship to address of 123, then you can put the mapping in EDPAR. This will be translated by the IDOC_INPUT_ORDERS FM when the idoc enters your system. This prevents you having to "hard code" customer number mappings in your EDI translation software.

With EDSDC, however, you are simply automatically allocating a sales area (sales org, distr. chan., division) to an incoming sales order from a customer. You enter the internal SAP customer number, and the vendor number (the number by which the customer identifies your company) and then specify the sales area and the document type against which the sales order will be created. Again, this is processed in the FM IDOC_INPUT_ORDERS.

Now coming to the T-code: the simple definition is given as:

VOE4 Table view EDPAR. Link external partner number with our internal number

And

VOE2 Table EDSC view. Customer link to sales area detail

**Please reward if this helps***

Regards

AK

[Former Member]

Hi Syed - VOE4 is the transaction to maintain EDPAR table entries. EDPAR entries are basically done to let SAP know on what customer (with the associated partner function) to use for the provided external partner data on the IDOC. General example would be an inbound IDOC from customer to create a sales order in your system. The external system which is creating the IDOC in your SAP system may not know which sold to party to use for a specific purchase order from the customer. So it may decide on using a arbitary combination of say customer ID (EDI ID or self generated) along with some identifier (say store #). This combination can be brought into the IDOC as external parter with partner function sold to party (sent on IDOC on segment E1EDKA1, qual AG). If the entry is maintained in EDPAR to convert the external partner combination to the required sold to party #, your IDOC would post the sales order on the retrieved sold to party.

VOE2 - Is for maintaining a link between you as a vendor and the customer. Say, you have multiple vendor #s for a company, based on the sales agreements. A typical scenario would be that you cater to the needs of customer's department A with a specific sales order and department B with some other. Now here in this table you can maintain the association of a customer with your vendor number for department A with a particual sales organization and sales document type in your system. So when department A in the customer side orders you using a vendor # it has for your company, this table would let the system know as to what sales org an sales doc it has to use. For department B, customer # again may be the same, but your vendor # for department B will change, hence you can assign a different sales org and sales doc type.

Both EDPAR and EDSDC are used for inbound sales order processing.

Thanks

Nikhil