<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SAP Integration Experts - DataXstream &#187; DELFOR02</title>
	<atom:link href="http://www.dataxstream.com/tag/delfor02/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dataxstream.com</link>
	<description>SAP Certified Consultants</description>
	<lastBuildDate>Tue, 31 Aug 2010 15:53:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>SAP Standard Sale Area Cross Reference For Inbound IDOC Processing</title>
		<link>http://www.dataxstream.com/2009/10/sap-idoc-sales-area-cross-reference/</link>
		<comments>http://www.dataxstream.com/2009/10/sap-idoc-sales-area-cross-reference/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 04:00:15 +0000</pubDate>
		<dc:creator>dkoch</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[SAP EDI Blog]]></category>
		<category><![CDATA[SAP Interface Blog]]></category>
		<category><![CDATA[SAP PI Blog]]></category>
		<category><![CDATA[SAP Technical]]></category>
		<category><![CDATA[Cross Reference]]></category>
		<category><![CDATA[DELFOR02]]></category>
		<category><![CDATA[Dick Koch]]></category>
		<category><![CDATA[EDI]]></category>
		<category><![CDATA[EDSDC]]></category>
		<category><![CDATA[IDOC]]></category>
		<category><![CDATA[Interface]]></category>
		<category><![CDATA[ORDERS05]]></category>
		<category><![CDATA[SAP]]></category>

		<guid isPermaLink="false">http://www.dataxstream.com/?p=2425</guid>
		<description><![CDATA[Cross Reference To SAP Sales Area From External Customer Number &#8211; SAP EDSDC Table If you have ever converted an external file into a SAP Sales Document IDOC (ex: ORDERS05) you may have hard coded the E1EDK14 segments of the IDOC which specify Sales Area and order type for the SAP Sales Document.  However, these segments are [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #ff0000"> </span></p>
<h2>Cross Reference To SAP Sales Area From External Customer Number &#8211; SAP EDSDC Table</h2>
<p>If you have ever converted an external file into a SAP Sales Document IDOC (ex: ORDERS05) you may have hard coded the E1EDK14 segments of the IDOC which specify Sales Area and order type for the SAP Sales Document.  However, these segments are not required if you populate the E1EDKA1-LIFNR segment of the IDOC with the External Customer Number and populate the EDSDC table with the Sales Area and Order Type for the customer.  Your SAP system contains a standard utility that converts the External Customer Number to the Sales Area values and Order Type value contained in this table.</p>
<h2>Sales Area Cross Reference From IDOCs ORDERS05 and DELFOR02</h2>
<p>This utility is available in the standard SAP package to convert External Customer Number to SAP Sales Area when processing inbound IDOCs (ex: ORDERS05, DELFOR02) from non-SAP systems.  It eliminates the need to add E1EDK14 segments to the IDOC as it populates the Sales Organization, Distribution Channel, Division, and Sales Document Type using the entries in the EDSDC table which is populated using transaction VOE2.  In order for this process to work, you must have the Customers External number populated in the E1EDKA1-LIFNR field of the IDOC where E1EDKA1-PARVW is &#8216;AG&#8217; and the EDPAR Customer Conversion table set up to convert the Customer External number to the SAP Customer number.  <strong>See my blog &#8216;SAP EDPAR Table &#8211; External Customer Number cross reference to SAP Customer Number&#8217; for instructions on the External Customer Conversion</strong>.  By properly doing this, the standard SAP function module will use the EDSDC table to convert the External Customer Number to the SAP Sales Area and Document Type.  The following instructions will explain how to populate the inbound IDOC and the EDSDC table.</p>
<p><span id="more-2425"></span>
On the Inbound IDOC do not create any E1EDK14 segments.  The use of the EDSDC table will populate the Sales Area and Document Type of the Sales document and therefore no E1EDK14 segments are required.  Populate the E1EDKA1 segment for the Sold-To party where the PARVW field is &#8216;AG&#8217; and the LIFNR field is the External Customer Number (<em><strong>Note: the EDPAR table must be populated to convert this External Customer Number to the SAP Sold-To number</strong></em>).</p>
<p><img class="alignnone size-full wp-image-2626" src="http://www.dataxstream.com/wp-content/uploads/2021/12/IDOC_LIFNR1.jpg" alt="IDOC_LIFNR" width="643" height="505" /></p>
<p>Use transaction VOE2 to populate the EDSDC table.  Enter the SAP Sold-To Customer number in the Customer field and your Customer&#8217;s External Sold-To number in the Vendor number field.  You will then populate the SOrg, DChl, and Dv fields on VOE2 with the Sales Area information(Sales Organization, Distribution Channel, and Division) related to your SAP Customer number.  Finally, you will enter the Sales Document Type(ex: OR = Standard Order) in the SaTy field.  These values will be used as the Sales Area and Document Type on the SAP Sales Document once the IDOC is processed.</p>
<p><img class="alignnone size-full wp-image-2629" src="http://www.dataxstream.com/wp-content/uploads/2021/12/EDSDC3.jpg" alt="EDSDC" width="779" height="265" /></p>
<p>So eliminate hard coding multiple E1EDK14 segments in the inbound IDOC, just use the Standard SAP Utility designed to populated the Sales Area and Order Type of your Sales Documents.  Populate the EDSDC table using the VOE2 transaction and send the External Customer Number in the E1EDKA1-LIFNR field of the IDOC.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dataxstream.com/2009/10/sap-idoc-sales-area-cross-reference/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SAP Standard Customer Cross Reference For Inbound IDOC Processing</title>
		<link>http://www.dataxstream.com/2009/10/sap-idoc-customer-cross-reference/</link>
		<comments>http://www.dataxstream.com/2009/10/sap-idoc-customer-cross-reference/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 16:00:42 +0000</pubDate>
		<dc:creator>dkoch</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[SAP EDI Blog]]></category>
		<category><![CDATA[SAP Interface Blog]]></category>
		<category><![CDATA[SAP PI Blog]]></category>
		<category><![CDATA[SAP Technical]]></category>
		<category><![CDATA[Cross Reference]]></category>
		<category><![CDATA[DELFOR02]]></category>
		<category><![CDATA[Dick Koch]]></category>
		<category><![CDATA[EDPAR]]></category>
		<category><![CDATA[IDOC]]></category>
		<category><![CDATA[Interface]]></category>
		<category><![CDATA[ORDERS05]]></category>
		<category><![CDATA[SAP]]></category>

		<guid isPermaLink="false">http://www.dataxstream.com/?p=2426</guid>
		<description><![CDATA[Converting External Customer Number To Internal Customer Number &#8211; SAP EDPAR Table Have you ever had a project where you are converting a customer file into an SAP Sales Document IDOC (ex: ORDERS05) and the customer file contains their Internal Customer Number?  So you need to determine what the SAP Customer Number will be on [...]]]></description>
			<content:encoded><![CDATA[<h2>Converting External Customer Number To Internal Customer Number &#8211; SAP EDPAR Table</h2>
<p>Have you ever had a project where you are converting a customer file into an SAP Sales Document IDOC (ex: ORDERS05) and the customer file contains their Internal Customer Number?  So you need to determine what the SAP Customer Number will be on the IDOC.  If you are not familiar with the SAP interface process you may hardcode the SAP Customer Number or create external tables in your third party mapping software to accomplish this conversion process.  However, this involves customer specific logic or updating the tables with your SAP Customer Numbers and having a process to maintain this table as new SAP Customer Numbers are created.  There is a much easier way to perform this conversion with no additional coding as it is a standard SAP utility.</p>
<h2>Customer Conversion For IDOCS ORDERS05 and DELFOR02</h2>
<p>This utility is available in the standard SAP package to convert External Customer Numbers to SAP Customer numbers (Sold-To, Ship-To, etc.) when processing inbound IDOCs (ex: ORDERS05, DELFOR02) from non-SAP systems.  When working with data that will be imported into SAP via IDOC format the data usually  contain your customers external sold-to and ship-to numbers and not the associated SAP customer numbers.    Therefore, you would need to convert this External Customer Number to  your internal SAP Customer Number.  Instead of creating cross-reference tables or conversion routines in your third-party translation software you can populate the E1EDKA1-LIFNR field of the inbound IDOC with the External Customer Number and use transaction VOE4 to populate the EDPAR table.  By properly doing this, the standard SAP function module will use the EDPAR table values to convert the External Customer Number to the SAP Customer number.  The following instructions will explain how to populate the inbound IDOC and the EDPAR table.</p>
<p><span id="more-2426"></span></p>
<h2>Configuration Of IDOC Segment E1EDKA1</h2>
<p>On the inbound IDOC, the only fields you will need to populate on the E1EDKA1 segment is the PARVW(Partner Function) field and the LIFNR(Vendor Number at Customer Location) field.  In most cases you will have an E1EDKA1 segment for the Sold-To party and another E1EDKA1 segment for the Ship-To party.  For the Sold-To party you would enter &#8216;AG&#8217; in the PARVW field and the External Sold-To Number in the LIFNR field.</p>
<p><img class="alignnone size-full wp-image-2631" src="http://www.dataxstream.com/wp-content/uploads/2021/12/IDOC_LIFNR2.jpg" alt="IDOC_LIFNR" width="643" height="505" /></p>
<p>For the Ship-To party you would enter &#8216;WE&#8217; in the PARVW field and the External Ship-To Number in the LIFNR field.</p>
<p><img class="alignnone size-full wp-image-2632" src="http://www.dataxstream.com/wp-content/uploads/2021/12/IDOC_LIFNR_WE2.jpg" alt="IDOC_LIFNR_WE" width="648" height="499" /></p>
<h2>Populating SAP EDPAR Table Via Transaction VOE4</h2>
<p>Prior to processing an inbound IDOC you would use transaction VOE4 to populate the EDPAR table.  The SAP Sold-To number will always be entered in the Customer number field.  The Ext Function field will be populated depending on the External number.  If you are converting the Sold-To number you would enter &#8216;SP&#8217; in the Ext Function field.  If you are converting the Ship-To number you would enter &#8216;SH&#8217; in the Ext Function field.  The External Sold-To/Ship-To number would be entered in the External partner field.    Finally, you would enter the SAP Sold-To number or Ship-To number in the Int no. field.  This value will be used as the Sold-To/Ship-To on the SAP Sales Document once the IDOC is processed.</p>
<p><img class="alignnone size-full wp-image-2633" src="http://www.dataxstream.com/wp-content/uploads/2021/12/EDPAR.jpg" alt="EDPAR" width="691" height="444" /></p>
<p>So if you ever need to convert External Customer Number to SAP Customer Numbers take advantage of the utilities that SAP supplies.  You can even incorporate the EDPAR table entry updates  into the SD Business Configuration processes so when a new customer number is created and it is designated as an EDI Customer, the personnel creating the new customer can also update the EDPAR table entries.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dataxstream.com/2009/10/sap-idoc-customer-cross-reference/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
