Feb 01

SAP EDI EDPAR Table Walkthrough – How to Cross Reference External Customer Number to SAP Customer Number (Part 2)

Let’s say you are receiving EDI ANSI X12 850 Sales Orders from you customers that need to be uploaded into your SAP System using the ORDERS05 IDOC.  Most customers will have their own internal customer numbers that they send in their EDI transmissions to represent the Sold-To and Ship-To partners.

How do you convert these external customer numbers into your internal SAP customer numbers?

Some may hard code these conversions into their EDI maps.  This approach can be very high maintenance as customers can add new ship-to locations or reorganize their internal numbers which would require changes to your maps.

Others may set up a cross reference table within their EDI translation table to perform the conversion.  This works well at times, but then you are at the mercy of your EDI group to update the table with any new additions or changes to existing entries.

I find the best way to perform this conversion is within your SAP system.  Mainly because SAP has given you a standard utility to perform the conversion.  All you need to do is populate a few fields of the incoming IDOC and populate the EDPAR table using transaction VOE4 with the internal and external customer numbers.  The Function Module used to process the IDOC takes care of the rest.  SAP uses the Sender Partner Number of the IDOC Control record along with the PARVW and LIFNR elements from the E1EDKA1 segment to look up the correct entry in the EDPAR table.  In your EDI maps you would populate the PARVW element with the partner function code for the external customer number (AG = Sold-To, WE = Ship-To) and populate the LIFNR field with the external customer number received in the EDI file from that partner.  All other fields would remain blank in the E1EDKA1 segment.

Sender Information Partner Number from the Control Record:

E1EDKA1 Segment for the Sold-To Partner (AG):

E1EDKA1 Segment for the Ship-To Partner (WE):

Use transaction VOE4 to populate the EDPAR table.  You enter the value from the Sender Partner Number in the IDOC control record in the Customer field, the function code for the partner in the Ext. Function field.  Note: The Ext. Function field will not be the same as the Partner Function (PARVW) element of the IDOC.  (AG in IDOC = SP on VOE4, WE = SH).  The External Partner is the number received in the EDI data from the customer which is also the number in the LIFNR element of the IDOC.  Int. no is the SAP customer number associated with the External number.

VOE4 transaction with required entries for the Sold-To and Ship-To for IDOC information above:

Using the EDPAR table for customer conversion allows this function to remain in control of those responsible for customer accounts.  Users can be trained to use the VOE4 transaction to update the EDPAR table so when new ship-to or sold-to numbers need to be added they can be done in a timely matter and not rely on other departments.  It also takes this responsibility away from the EDI group so they don’t have to maintain maps or tables for this function.

This function can be used for other incoming IDOCs as well.  You will need to check the Function Modules used to process incoming IDOCs to determine if EDPAR can be used for customer number conversion and on which IDOC segment you would send the external number.

Outbound IDOCs can use either the EDPAR table or the PUMA table to cross reference external customer numbers.  Again, it depends on the IDOC type.  I will cover this topic in a separate blog.

About The Author

9 Comments

  1. Avatar
    Karen Norton
    March 8, 2012 at 3:11 pm · Reply

    Can you please provide a transaction code for updating PUMA? similar to VOE4 for EDPAR or VOE2 for EDSDC. Thanks.

  2. Avatar
    Rina Zorn
    January 4, 2013 at 4:26 pm · Reply

    RE: Outbound IDOCs can use either the EDPAR table or the PUMA table to cross reference external customer numbers. Again, it depends on the IDOC type. I will cover this topic in a separate blog.

    Hello, I am working on doing our first outbound PO’s using ORDERS05 Idoc type. I need to convert the plant # to a Duns # for the LIFNR. I would prefer to do in SAP verses in our EDI software. Where can I see your other blog regarding outbound? Or if you could send me what needs to entered into PUMA or Edpar for the WE ship to on outbound orders. Thanks much, Rina

  3. Avatar
    Marius
    February 13, 2013 at 7:27 am · Reply

    Hi,
    what’s the usage of Int.No. field ?
    Thanks,
    M

  4. Avatar
    Nimrod Gisis
    July 12, 2015 at 6:05 am · Reply

    If you have a SAP XI/PI/PO installed in your organization it is part of its standard B2B configuration.
    Using Seeburger engine or the B2B addon you can implement the Sender and reciever partners of the IDoc control record inside SAP PI.

    it is a good idea to have the PI implemented in your organziation especially if your IT road map is for more then 3-5 interfaces or EDI messages.
    Will save you valuable time in interafce development and buisness process changes.

  5. Avatar
    sri
    May 10, 2017 at 12:39 pm · Reply

    Hi,
    I am completely new to SAP. Please don’t mind my naive questions. Can you let me know which product of SAP contains EDPAR Tables in order to modify/create idocs?

  6. Dick Koch
    December 20, 2017 at 9:53 am · Reply

    The EDPAR table is in the SAP ECC environment.

  7. Avatar
    Eric V
    July 2, 2018 at 7:43 pm · Reply

    Can we use the EDPAR table to map individual Sold-To locations that have the same External Partner ID but different store numbers? (i.e. Partner 07227171USSO has store 1003 and store 4056 that link to different customers)

  8. Dick Koch
    August 21, 2018 at 11:20 am · Reply

    Eric, you can use the EDPAR table, but would have to combine the External Partner ID and Store number to use as the external Partner ID (ex: 07227171USSO1003 or 07227171USSO-1003). Keep in mind that the External ID field (LIFNR) is 17 characters in length so if you combine two fields they must not exceed that length. In the case above you could remove a portion of the sold-to number as long as it remains a unique number (ex: remove first 3 characters to get 27171USSO1003).

  9. Avatar
    Morten
    March 14, 2019 at 8:30 am · Reply

    As far as I can tell, EDPAR requires use of Partner Type KU as Sender Partner Number. Is there any way we can use Partner Type LS in stead?

Leave a reply

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

This site uses Akismet to reduce spam. Learn how your comment data is processed.