<?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: ALE /  IDOC in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580725#M590103</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the following is the code for populating the custom idoc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CONSTANTS:   C_DOCTYP TYPE EDIDC-IDOCTP VALUE 'ZUSRDET01', idoctype&lt;/P&gt;&lt;P&gt;             C_SEGNAM TYPE EDIDD-SEGNAM VALUE 'Z1USRDET01', segment&lt;/P&gt;&lt;P&gt;             C_MESTYP TYPE EDIDC-MESTYP VALUE 'ZUSRDET'. message type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  DATA:      IT_ZUSR02 TYPE USR02 OCCURS 10,&lt;/P&gt;&lt;P&gt;             IT_EDIDC TYPE EDIDC OCCURS 0,&lt;/P&gt;&lt;P&gt;             IT_EDIDD TYPE EDIDD OCCURS 0,&lt;/P&gt;&lt;P&gt;             WA_ZUSR02 TYPE USR02,&lt;/P&gt;&lt;P&gt;             WA_EDIDC TYPE EDIDC,&lt;/P&gt;&lt;P&gt;             WA_EDIDD TYPE EDIDD,&lt;/P&gt;&lt;P&gt;             WA_Z1USRDET01 TYPE Z1USRDET01,&lt;/P&gt;&lt;P&gt;             V_OCCMAX TYPE IDOCSYN-OCCMAX,&lt;/P&gt;&lt;P&gt;             V_NBSEG TYPE I.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            CLEAR WA_ZUSR02.&lt;/P&gt;&lt;P&gt;            CLEAR WA_EDIDC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            Save the message type and the basic IDoc type in the control segment.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            MOVE C_MESTYP TO WA_EDIDC-MESTYP.&lt;/P&gt;&lt;P&gt;            MOVE C_DOCTYP TO WA_EDIDC-IDOCTP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            Retrieve the maximum number of segments in the basic IDoc type.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            SELECT MIN( OCCMAX )  FROM IDOCSYN  INTO V_OCCMAX  WHERE IDOCTYP EQ C_DOCTYP AND SEGTYP EQ C_SEGNAM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            Save the whole USR02 table content in the IT_ZUSR02 internal table.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            SELECT * FROM USR02 INTO CORRESPONDING FIELDS OF TABLE IT_ZUSR02.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            Create a data segment for each line of IT_ZUSR02.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            LOOP AT IT_ZUSR02 INTO WA_ZUSR02 .&lt;/P&gt;&lt;P&gt;              MOVE-CORRESPONDING WA_ZUSR02  TO WA_Z1USRDET01.&lt;/P&gt;&lt;P&gt;              CLEAR WA_EDIDD.&lt;/P&gt;&lt;P&gt;              MOVE C_SEGNAM TO WA_EDIDD-SEGNAM.&lt;/P&gt;&lt;P&gt;              MOVE WA_Z1USRDET01 TO WA_EDIDD-SDATA.&lt;/P&gt;&lt;P&gt;              APPEND WA_EDIDD TO IT_EDIDD.&lt;/P&gt;&lt;P&gt;              CLEAR WA_ZUSR02.&lt;/P&gt;&lt;P&gt;             CLEAR WA_Z1USRDET01.&lt;/P&gt;&lt;P&gt;            ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;           Count the number of data segments.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              DESCRIBE TABLE IT_EDIDD LINES V_NBSEG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;           If the number of data segments exceeds the maximum allowed number,then display an error message.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              IF V_NBSEG GT V_OCCMAX.&lt;/P&gt;&lt;P&gt;              WRITE:/ 'ERROR'.&lt;/P&gt;&lt;P&gt;              ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'&lt;/P&gt;&lt;P&gt;                EXPORTING&lt;/P&gt;&lt;P&gt;                  master_idoc_control                  = WA_EDIDC&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;                OBJ_TYPE                             = ''&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;                CHNUM                                = ''&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;                tables&lt;/P&gt;&lt;P&gt;                  communication_idoc_control           = IT_EDIDC&lt;/P&gt;&lt;P&gt;                  master_idoc_data                     = IT_EDIDD&lt;/P&gt;&lt;P&gt;               EXCEPTIONS&lt;/P&gt;&lt;P&gt;                 ERROR_IN_IDOC_CONTROL                = 1&lt;/P&gt;&lt;P&gt;                 ERROR_WRITING_IDOC_STATUS            = 2&lt;/P&gt;&lt;P&gt;                 ERROR_IN_IDOC_DATA                   = 3&lt;/P&gt;&lt;P&gt;                 SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4&lt;/P&gt;&lt;P&gt;                 OTHERS                               = 5&lt;/P&gt;&lt;P&gt;                        .&lt;/P&gt;&lt;P&gt;              IF sy-subrc &amp;lt;&amp;gt; 0.&lt;/P&gt;&lt;P&gt; MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO&lt;/P&gt;&lt;P&gt;         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;reward points for useful ans&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;vivek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 Aug 2007 05:18:46 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-08-01T05:18:46Z</dc:date>
    <item>
      <title>ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580722#M590100</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have created my own z.. table&lt;/P&gt;&lt;P&gt;I have created segments&lt;/P&gt;&lt;P&gt;and created basic idoc type&lt;/P&gt;&lt;P&gt;and released it&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and want to how to extend the basic idoc type which i have created &lt;/P&gt;&lt;P&gt;and what is the purpose of extending the basic idoc type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and how to populate the custom idoc via abap programme&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 16:23:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580722#M590100</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T16:23:52Z</dc:date>
    </item>
    <item>
      <title>Re: ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580723#M590101</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Instead of creating a IDOC type with all segments from the scracth we use the existing related IDOC type and we extend it just by creating a single segment with few fields and add to the extended Idoc type&lt;/P&gt;&lt;P&gt;and populate the segment fields from the user exit of that std Basic idoc type or from the fun module program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points for useful Answers&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 17:04:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580723#M590101</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T17:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580724#M590102</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Extending Basic Idoc type&lt;/P&gt;&lt;BR /&gt;Extending a Basic Type Locate the document in its SAP Library structure&lt;BR /&gt;Prerequisites&lt;BR /&gt;&lt;BR /&gt;You must have completed the required steps in &lt;B&gt;&lt;P&gt;Extending Idoc type&lt;/P&gt;&lt;/B&gt;  .&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It can occur that you want to fill table fields which already have an equivalent in the basic type but which are not supplied in the standard system. You therefore do not need to extend the basic type, but rather only the function module that supplies the application fields. In this case, skip the procedure.&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       1.      Choose SAP menu ® Tools ® IDoc Interface/ALE ® Development ® IDoc ® Generate ALE Interface ® IDoc Types (WE30). The IDoc type editor is displayed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       2.      If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select Request ® Create and reply to the questions which appear on screen. By selecting This graphic is explained in the accompanying text you can return to the IDoc type editor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       3.      Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose This graphic is explained in the accompanying text.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Caution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       4.      Choose one of the following options:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create New: Create the extension without a reference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Create copy,which you can then change if necessary&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Create as successor: Note that only one successor is allowed per release for each extension.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       5.      Select the basic type which is to be combined with your extension. Confirm your entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The basic type is displayed as a tree structure. See the color legend (Utilities ® Color legend).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       6.      Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose This graphic is explained in the accompanying text. You must now assign attributes for these child segments:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Mandatory segment (indicator): Must data be written to this segment in the IDoc?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Maximum and minimum frequency of use: How often may/must a segment occur in the IDoc?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       7.      You can add further children or &amp;#147;grandchildren&amp;#148; to this or any other reference segment in the basic type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       8.      When the new extension is complete, you can save your entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Caution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should keep the following factors in mind when dealing with extensions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Segments must not explicitly occur more than once in the IDoc type - this means that the extension cannot have any segments which already exist in the basic type. This also means that a successor must not have any segments which already exist in the predecessor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Parent segments of predecessors must remain parent segments in the case of successors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the example call your extension Z1ORDERS. Append Z1TEST1 child segment to E1EDP19reference segment in ORDERS01 basic type. The child segment can be used only once.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to know regarding &lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm"&gt;Extending Idoc type &lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;*&lt;STRONG&gt;reward for useful answers&lt;/STRONG&gt;*&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jul 2007 17:16:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580724#M590102</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-31T17:16:22Z</dc:date>
    </item>
    <item>
      <title>Re: ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580725#M590103</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the following is the code for populating the custom idoc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CONSTANTS:   C_DOCTYP TYPE EDIDC-IDOCTP VALUE 'ZUSRDET01', idoctype&lt;/P&gt;&lt;P&gt;             C_SEGNAM TYPE EDIDD-SEGNAM VALUE 'Z1USRDET01', segment&lt;/P&gt;&lt;P&gt;             C_MESTYP TYPE EDIDC-MESTYP VALUE 'ZUSRDET'. message type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  DATA:      IT_ZUSR02 TYPE USR02 OCCURS 10,&lt;/P&gt;&lt;P&gt;             IT_EDIDC TYPE EDIDC OCCURS 0,&lt;/P&gt;&lt;P&gt;             IT_EDIDD TYPE EDIDD OCCURS 0,&lt;/P&gt;&lt;P&gt;             WA_ZUSR02 TYPE USR02,&lt;/P&gt;&lt;P&gt;             WA_EDIDC TYPE EDIDC,&lt;/P&gt;&lt;P&gt;             WA_EDIDD TYPE EDIDD,&lt;/P&gt;&lt;P&gt;             WA_Z1USRDET01 TYPE Z1USRDET01,&lt;/P&gt;&lt;P&gt;             V_OCCMAX TYPE IDOCSYN-OCCMAX,&lt;/P&gt;&lt;P&gt;             V_NBSEG TYPE I.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            CLEAR WA_ZUSR02.&lt;/P&gt;&lt;P&gt;            CLEAR WA_EDIDC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            Save the message type and the basic IDoc type in the control segment.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            MOVE C_MESTYP TO WA_EDIDC-MESTYP.&lt;/P&gt;&lt;P&gt;            MOVE C_DOCTYP TO WA_EDIDC-IDOCTP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            Retrieve the maximum number of segments in the basic IDoc type.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            SELECT MIN( OCCMAX )  FROM IDOCSYN  INTO V_OCCMAX  WHERE IDOCTYP EQ C_DOCTYP AND SEGTYP EQ C_SEGNAM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            Save the whole USR02 table content in the IT_ZUSR02 internal table.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            SELECT * FROM USR02 INTO CORRESPONDING FIELDS OF TABLE IT_ZUSR02.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            Create a data segment for each line of IT_ZUSR02.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            LOOP AT IT_ZUSR02 INTO WA_ZUSR02 .&lt;/P&gt;&lt;P&gt;              MOVE-CORRESPONDING WA_ZUSR02  TO WA_Z1USRDET01.&lt;/P&gt;&lt;P&gt;              CLEAR WA_EDIDD.&lt;/P&gt;&lt;P&gt;              MOVE C_SEGNAM TO WA_EDIDD-SEGNAM.&lt;/P&gt;&lt;P&gt;              MOVE WA_Z1USRDET01 TO WA_EDIDD-SDATA.&lt;/P&gt;&lt;P&gt;              APPEND WA_EDIDD TO IT_EDIDD.&lt;/P&gt;&lt;P&gt;              CLEAR WA_ZUSR02.&lt;/P&gt;&lt;P&gt;             CLEAR WA_Z1USRDET01.&lt;/P&gt;&lt;P&gt;            ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;           Count the number of data segments.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              DESCRIBE TABLE IT_EDIDD LINES V_NBSEG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;           If the number of data segments exceeds the maximum allowed number,then display an error message.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              IF V_NBSEG GT V_OCCMAX.&lt;/P&gt;&lt;P&gt;              WRITE:/ 'ERROR'.&lt;/P&gt;&lt;P&gt;              ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'&lt;/P&gt;&lt;P&gt;                EXPORTING&lt;/P&gt;&lt;P&gt;                  master_idoc_control                  = WA_EDIDC&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;                OBJ_TYPE                             = ''&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;                CHNUM                                = ''&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;                tables&lt;/P&gt;&lt;P&gt;                  communication_idoc_control           = IT_EDIDC&lt;/P&gt;&lt;P&gt;                  master_idoc_data                     = IT_EDIDD&lt;/P&gt;&lt;P&gt;               EXCEPTIONS&lt;/P&gt;&lt;P&gt;                 ERROR_IN_IDOC_CONTROL                = 1&lt;/P&gt;&lt;P&gt;                 ERROR_WRITING_IDOC_STATUS            = 2&lt;/P&gt;&lt;P&gt;                 ERROR_IN_IDOC_DATA                   = 3&lt;/P&gt;&lt;P&gt;                 SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4&lt;/P&gt;&lt;P&gt;                 OTHERS                               = 5&lt;/P&gt;&lt;P&gt;                        .&lt;/P&gt;&lt;P&gt;              IF sy-subrc &amp;lt;&amp;gt; 0.&lt;/P&gt;&lt;P&gt; MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO&lt;/P&gt;&lt;P&gt;         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;reward points for useful ans&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;vivek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Aug 2007 05:18:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580725#M590103</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-01T05:18:46Z</dc:date>
    </item>
    <item>
      <title>Re: ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580726#M590104</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Take the correct Idoc type and Message Type and process code from EDBAS and EDMSG tables and use&lt;/P&gt;&lt;P&gt;see the doc&lt;/P&gt;&lt;P&gt;Data Creation in Idoc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an &lt;/P&gt;&lt;P&gt;asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDoc is a intermediate document to exchange data between two SAP Systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*IDocs are structured ASCII files (or a virtual equivalent). &lt;/P&gt;&lt;P&gt;*Electronic Interchange Document&lt;/P&gt;&lt;P&gt;*They are the file format used by SAP R/3 to exchange data with foreign systems.&lt;/P&gt;&lt;P&gt;*Data Is transmitted in ASCII format, i.e. human readable form&lt;/P&gt;&lt;P&gt;*IDocs exchange messages&lt;/P&gt;&lt;P&gt;*IDocs are used like classical interface files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC types are templates for specific message types depending on what is the business document, you want to exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to create idoc?&lt;/P&gt;&lt;P&gt;*WE30 - you can create a IDOC type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information in details on the same along with the examples can be viewed on:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/presentation.html" target="test_blank"&gt;http://www.sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_search.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_search.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.erpgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.erpgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To Create Idoc we need to follow these steps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Segment ( WE31)&lt;/P&gt;&lt;P&gt;Create Idoc Type ( WE30 )&lt;/P&gt;&lt;P&gt;Create Message Type ( WE81 )&lt;/P&gt;&lt;P&gt;Assign Idoc Type to Message Type ( WE82 )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating a Segment&lt;/P&gt;&lt;P&gt;Go to transaction code WE31&lt;/P&gt;&lt;P&gt;Enter the name for your segment type and click on the Create icon&lt;/P&gt;&lt;P&gt;Type the short text&lt;/P&gt;&lt;P&gt;Enter the variable names and data elements&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;Go to Edit -&amp;gt; Set Release&lt;/P&gt;&lt;P&gt;Follow steps to create more number of segments&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create IDOC Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE30&lt;/P&gt;&lt;P&gt;Enter the Object Name, select Basic type and click Create icon&lt;/P&gt;&lt;P&gt;Select the create new option and enter a description for your basic IDOC type and press enter&lt;/P&gt;&lt;P&gt;Select the IDOC Name and click Create icon&lt;/P&gt;&lt;P&gt;The system prompts us to enter a segment type and its attributes&lt;/P&gt;&lt;P&gt;Choose the appropriate values and press Enter&lt;/P&gt;&lt;P&gt;The system transfers the name of the segment type to the IDOC editor.&lt;/P&gt;&lt;P&gt;Follow these steps to add more number of segments to Parent or as Parent-child relation&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;Go to Edit -&amp;gt; Set release&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Message Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE81&lt;/P&gt;&lt;P&gt;Change the details from Display mode to Change mode&lt;/P&gt;&lt;P&gt;After selection, the system will give this message &amp;#147;The table is cross-client (see Help for further info)&amp;#148;. Press Enter&lt;/P&gt;&lt;P&gt;Click New Entries to create new Message Type&lt;/P&gt;&lt;P&gt;Fill details&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assign Message Type to IDoc Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE82&lt;/P&gt;&lt;P&gt;Change the details from Display mode to Change mode&lt;/P&gt;&lt;P&gt;After selection, the system will give this message &amp;#147;The table is cross-client (see Help for further info)&amp;#148;. Press Enter.&lt;/P&gt;&lt;P&gt;Click New Entries to create new Message Type.&lt;/P&gt;&lt;P&gt;Fill details&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check these out..&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2402859"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check below link. It will give the step by step procedure for IDOC creation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.supinfo-projects.com/cn/2005/idocs_en/2/" target="test_blank"&gt;http://www.supinfo-projects.com/cn/2005/idocs_en/2/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALE/ IDOC&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;go trough these links.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.IDOCs are independent of the sending and receiving systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.IDOCs are independent of the direction of data exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The two available process for IDOCs are&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outbound Process&lt;/P&gt;&lt;P&gt;Inbound Process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AND There are basically two types of IDOCs.&lt;/P&gt;&lt;P&gt;Basic IDOCs&lt;/P&gt;&lt;P&gt;Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extended IDOCs&lt;/P&gt;&lt;P&gt;Extending the functionality by adding more segments to existing Basic IDOCs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To Create Idoc we need to follow these steps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Segment ( WE31)&lt;/P&gt;&lt;P&gt;Create Idoc Type ( WE30)&lt;/P&gt;&lt;P&gt;Create Message Type ( WE81)&lt;/P&gt;&lt;P&gt;Assign Idoc Type to Message Type ( WE82)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;imp links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.sap.com/www.sappoint.com" target="test_blank"&gt;www.sappoint.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;--here u can find the ppts and basic seetings for ALE&lt;/P&gt;&lt;P&gt;&lt;A href="http://sappoint.com/presentation.html" target="test_blank"&gt;http://sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.sap.com/www.sapgenie.com" target="test_blank"&gt;www.sapgenie.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/ale/index.htm" target="test_blank"&gt;http://www.sapgenie.com/ale/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;Try this..Hope this will help.&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; SAP ALE &amp;amp; IDOC&amp;lt;&amp;lt;&amp;lt;&amp;lt; &lt;/P&gt;&lt;P&gt;Steps to configuration(Basis) &amp;gt;&amp;gt; &lt;/P&gt;&lt;P&gt;1. Create Logical System (LS) for each applicable ALE-enabled client &lt;/P&gt;&lt;P&gt;2. Link client to Logical System on the respective servers &lt;/P&gt;&lt;P&gt;3. Create background user, to be used by ALE(with authorizaton for ALE postings) &lt;/P&gt;&lt;P&gt;4. Create RFC Destinations(SM59) &lt;/P&gt;&lt;P&gt;5. Ports in Idoc processing(WE21) &lt;/P&gt;&lt;P&gt;6. Generate partner profiles for sending system &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The functional configuration(Tcode: SALE) &lt;/P&gt;&lt;P&gt;&amp;#149; Create a Customer Distribution Model (CDM); &lt;/P&gt;&lt;P&gt;&amp;#149; Add appropriate message types and filters to the CDM; &lt;/P&gt;&lt;P&gt;&amp;#149; Generate outbound partner profiles; &lt;/P&gt;&lt;P&gt;&amp;#149; Distribute the CDM to the receiving systems; and &lt;/P&gt;&lt;P&gt;&amp;#149; Generate inbound partner profiles on each of the clients. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps to customize a new IDoc &amp;gt;&amp;gt;&amp;gt; &lt;/P&gt;&lt;P&gt;1. Define IDoc Segment (WE31) &lt;/P&gt;&lt;P&gt;2. Convert Segments into an IDoc type (WE30) &lt;/P&gt;&lt;P&gt;3. Create a Message Type (WE81) &lt;/P&gt;&lt;P&gt;4. Create valid Combination of Message &amp;amp; IDoc type(WE82) &lt;/P&gt;&lt;P&gt;5. Define Processing Code(WE41 for OUT / WE42 for IN) &lt;/P&gt;&lt;P&gt;6. Define Partner Profile(WE20) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Important Transaction Codes: &lt;/P&gt;&lt;P&gt;SALE - IMG ALE Configuration root &lt;/P&gt;&lt;P&gt;WE20 - Manually maintain partner profiles &lt;/P&gt;&lt;P&gt;BD64 - Maintain customer distribution model &lt;/P&gt;&lt;P&gt;BD71 - Distribute customer distribution model &lt;/P&gt;&lt;P&gt;SM59 - Create RFC Destinations &lt;/P&gt;&lt;P&gt;BDM5 - Consistency check (Transaction scenarios) &lt;/P&gt;&lt;P&gt;BD82 - Generate Partner Profiles &lt;/P&gt;&lt;P&gt;BD61 - Activate Change Pointers - Globally &lt;/P&gt;&lt;P&gt;BD50 - Activate Change Pointer for Msg Type &lt;/P&gt;&lt;P&gt;BD52 - Activate change pointer per change.doc object &lt;/P&gt;&lt;P&gt;BD59 - Allocation object type -&amp;gt; IDOC type &lt;/P&gt;&lt;P&gt;BD56 - Maintain IDOC Segment Filters &lt;/P&gt;&lt;P&gt;BD53 - Reduction of Message Types &lt;/P&gt;&lt;P&gt;BD21 - Select Change Pointer &lt;/P&gt;&lt;P&gt;BD87 - Status Monitor for ALE Messages &lt;/P&gt;&lt;P&gt;BDM5 - Consistency check (Transaction scenarios) &lt;/P&gt;&lt;P&gt;BD62 - Define rules &lt;/P&gt;&lt;P&gt;BD79 - Maintain rules &lt;/P&gt;&lt;P&gt;BD55 - Defining settings for IDoc conversion &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WEDI - ALE IDoc Administration &lt;/P&gt;&lt;P&gt;WE21 - Ports in Idoc processing &lt;/P&gt;&lt;P&gt;WE60 - IDoc documentation &lt;/P&gt;&lt;P&gt;SARA - IDoc archiving (Object type IDOC) &lt;/P&gt;&lt;P&gt;WE47 - IDoc status maintenance &lt;/P&gt;&lt;P&gt;WE07 - IDoc statistics &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BALE - ALE Distribution Administration &lt;/P&gt;&lt;P&gt;WE05 - IDoc overview &lt;/P&gt;&lt;P&gt;BD87 - Inbound IDoc reprocessing &lt;/P&gt;&lt;P&gt;BD88 - Outbound IDoc reprocessing &lt;/P&gt;&lt;P&gt;BDM2 - IDoc Trace &lt;/P&gt;&lt;P&gt;BDM7 - IDoc Audit Analysis &lt;/P&gt;&lt;P&gt;BD21 - Create IDocs from change pointers &lt;/P&gt;&lt;P&gt;SM58 - Schedule RFC Failures &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic config for Distributed data: &lt;/P&gt;&lt;P&gt;BD64: Maintain a Distributed Model &lt;/P&gt;&lt;P&gt;BD82: Generate Partner Profile &lt;/P&gt;&lt;P&gt;BD64: Distribute the distribution Model &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Programs &lt;/P&gt;&lt;P&gt;RBDMIDOC &amp;#150; Creating IDoc Type from Change Pointers &lt;/P&gt;&lt;P&gt;RSEOUT00 &amp;#150; Process all selected IDocs (EDI) &lt;/P&gt;&lt;P&gt;RBDAPP01 - Inbound Processing of IDocs Ready for Transfer &lt;/P&gt;&lt;P&gt;RSARFCEX - Execute Calls Not Yet Executed &lt;/P&gt;&lt;P&gt;RBDMOIND - Status Conversion with Successful tRFC Execution &lt;/P&gt;&lt;P&gt;RBDMANIN - Start error handling for non-posted IDocs &lt;/P&gt;&lt;P&gt;RBDSTATE - Send Audit Confirmations &lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points for useful Answers&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Karthikeyan Pan...   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Posts: 545 &lt;/P&gt;&lt;P&gt;Questions: 0 &lt;/P&gt;&lt;P&gt;Registered: 7/26/07 &lt;/P&gt;&lt;P&gt;Forum points: 212  &lt;/P&gt;&lt;P&gt;   &lt;/P&gt;&lt;P&gt;  Re: STEPS for creating IDOC .   &lt;/P&gt;&lt;P&gt;Posted: Jul 30, 2007 2:15 PM    in response to: Amitava joarder       Reply  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALE/ IDOC&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check these step-by-step links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e" target="test_blank"&gt;https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for Smartforms material&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/message/3815745#3815745 &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Aug 2007 09:30:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580726#M590104</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-01T09:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580727#M590105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how to extend the idoc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;basavaraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Aug 2007 13:27:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580727#M590105</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-03T13:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580728#M590106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where we have to write this code&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ragards&lt;/P&gt;&lt;P&gt;basavarj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Aug 2007 13:39:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580728#M590106</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-03T13:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580729#M590107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Basavraj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To populate the extended segment values u need to write the code in the patricular &amp;lt;b&amp;gt;User Exit&amp;lt;/b&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Look for the &amp;lt;b&amp;gt;CUSTOMER-FUNCTION&amp;lt;/b&amp;gt; and  find the right user exit and write the code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Chandra.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;null&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Aug 2007 13:47:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580729#M590107</guid>
      <dc:creator>former_member187255</dc:creator>
      <dc:date>2007-08-03T13:47:09Z</dc:date>
    </item>
    <item>
      <title>Re: ALE /  IDOC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580730#M590108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have created own z table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have creadted basic idoc type and segmants successfully&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how to extend the basic idoc type and send the data to the other client&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Awaiting Mail&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basavaraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Aug 2007 14:44:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ale-idoc/m-p/2580730#M590108</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-03T14:44:59Z</dc:date>
    </item>
  </channel>
</rss>

