<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Creating an IDOC type in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/creating-an-idoc-type/m-p/3774994#M908321</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sagar,&lt;/P&gt;&lt;P&gt;Thanks for the info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue is that I am trying to create a new basic type using the current one as the predecessor. Thsi would be for the SAP in the new release.&lt;/P&gt;&lt;P&gt;Extending it by the customer is not an issue here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Elham&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 May 2008 17:39:09 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-02T17:39:09Z</dc:date>
    <item>
      <title>Creating an IDOC type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/creating-an-idoc-type/m-p/3774992#M908319</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I am trying to create an IDOC type, using an existing one that is already released as the predecessor.&lt;/P&gt;&lt;P&gt;But apparently this cannot be done in the IDOC editor (TA WE30).&lt;/P&gt;&lt;P&gt;Does any one know how this can be done?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, what is the advantage of creating a successor over the other options?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;-Elham&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 May 2008 13:37:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/creating-an-idoc-type/m-p/3774992#M908319</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-02T13:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: Creating an IDOC type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/creating-an-idoc-type/m-p/3774993#M908320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Elham,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extending an IDoc Type &lt;/P&gt;&lt;P&gt;Purpose&lt;/P&gt;&lt;P&gt;In the case of a customer extension, you add additional segments to an IDoc type supplied by SAP (basic type), so that you can transfer more (or simply other) business information. This extension is upward compatible, that is, it will be supported by future releases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Prerequisites&lt;/P&gt;&lt;P&gt;This checklist requires that the basic type to be extended is already included in the processing: This means, in particular, that the processing (inbound and outbound) is defined using process codes in the partner profiles and that the corresponding programs (for example, function modules) which lie behind the process codes are extended in the same way as the basic type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You require development authorizations (authorization object S_IDOCDEFT, for example, in the role SAP_BC_SRV_EDI_DEVELOPER) for the extensions. Development takes place in the customer system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Process flow&lt;/P&gt;&lt;P&gt;The following subsections contain the individual steps. The list can be used as a checklist when creating the extension. More information about the required steps and any alternatives can be found in the process flow diagram.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the help of an example, you can define an actual IDoc type and process the type in a number of different ways. The example is used in each individual step. As a prerequisite, master data for the test customer TESTCUST (partner type KU) and the test vendor TESTVEND (partner type LI) must be present in the system. In addition, the example also assumes that the file port TESTPORT has been created.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Process flow diagram&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Individual steps&lt;/P&gt;&lt;P&gt;General Definitions&lt;/P&gt;&lt;P&gt;·         Combining Segments&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Extending Basic Types&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Assign Message Type Basic Type and Extension&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuring outbound processing (outbound under Message Control)&lt;/P&gt;&lt;P&gt;·         Extending Outbound Function Modules&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Changing Partner Profiles (Outbound)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Testing Outbound Processing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuring inbound processing (direct inbound processing using ALE function module)&lt;/P&gt;&lt;P&gt;·         Extending Inbound Function Modules&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Extending Function Module Assignments (Direct Inbound)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Checking Partner Profiles (Inbound)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Testing Inbound Processing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see this link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;sagar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward me if usefull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 May 2008 16:25:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/creating-an-idoc-type/m-p/3774993#M908320</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-02T16:25:29Z</dc:date>
    </item>
    <item>
      <title>Re: Creating an IDOC type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/creating-an-idoc-type/m-p/3774994#M908321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sagar,&lt;/P&gt;&lt;P&gt;Thanks for the info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue is that I am trying to create a new basic type using the current one as the predecessor. Thsi would be for the SAP in the new release.&lt;/P&gt;&lt;P&gt;Extending it by the customer is not an issue here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Elham&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 May 2008 17:39:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/creating-an-idoc-type/m-p/3774994#M908321</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-02T17:39:09Z</dc:date>
    </item>
  </channel>
</rss>

