<?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: in cross apps what is basic type,idoc type , message type in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080714#M730618</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Basic Type:&lt;/P&gt;&lt;P&gt;&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;Segments:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps in creating Segments:&lt;/P&gt;&lt;P&gt;    T.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 and Go back.&lt;/P&gt;&lt;P&gt;    Go to Edit -&amp;gt; Set Release.&lt;/P&gt;&lt;P&gt;    Repeat the steps to create more segments.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC TYPE:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Business data is exchanged with an external system using the IDoc Interface.&lt;/P&gt;&lt;P&gt;IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments).  The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.&lt;/P&gt;&lt;P&gt;Steps in creating IDoc Type:&lt;/P&gt;&lt;P&gt;    T.Code WE30 to create IDoc Type.&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;&lt;/P&gt;&lt;P&gt;Message Type:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps in Creating Message Type:&lt;/P&gt;&lt;P&gt;    T.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 "The table is cross client (See help for further info)". 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;    T.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 "The table is cross client (See help for further info)". 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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rewards if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Nov 2007 04:12:22 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-11-29T04:12:22Z</dc:date>
    <item>
      <title>in cross apps what is basic type,idoc type , message type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080713#M730617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;in cross apps what is basic type,idoc type , message type  explain to me breflley how to work on realtime plz help me i am learning&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 03:50:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080713#M730617</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-29T03:50:13Z</dc:date>
    </item>
    <item>
      <title>Re: in cross apps what is basic type,idoc type , message type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080714#M730618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Basic Type:&lt;/P&gt;&lt;P&gt;&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;Segments:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps in creating Segments:&lt;/P&gt;&lt;P&gt;    T.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 and Go back.&lt;/P&gt;&lt;P&gt;    Go to Edit -&amp;gt; Set Release.&lt;/P&gt;&lt;P&gt;    Repeat the steps to create more segments.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC TYPE:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Business data is exchanged with an external system using the IDoc Interface.&lt;/P&gt;&lt;P&gt;IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments).  The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.&lt;/P&gt;&lt;P&gt;Steps in creating IDoc Type:&lt;/P&gt;&lt;P&gt;    T.Code WE30 to create IDoc Type.&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;&lt;/P&gt;&lt;P&gt;Message Type:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps in Creating Message Type:&lt;/P&gt;&lt;P&gt;    T.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 "The table is cross client (See help for further info)". 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;    T.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 "The table is cross client (See help for further info)". 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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rewards if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 04:12:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080714#M730618</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-29T04:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: in cross apps what is basic type,idoc type , message type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080715#M730619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&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;&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;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 04:15:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080715#M730619</guid>
      <dc:creator>p291102</dc:creator>
      <dc:date>2007-11-29T04:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: in cross apps what is basic type,idoc type , message type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080716#M730620</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hai sri vasu,&lt;/P&gt;&lt;P&gt;u want to learn cross aplications  purchase the book &amp;lt;b&amp;gt;ALE EDI IDOC&amp;lt;/b&amp;gt; witten by Arvind Nagpal.&lt;/P&gt;&lt;P&gt;This is a excellent book for beginners i am sure.&lt;/P&gt;&lt;P&gt;it covers all things....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;kishore ale&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 04:15:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080716#M730620</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-29T04:15:46Z</dc:date>
    </item>
    <item>
      <title>Re: in cross apps what is basic type,idoc type , message type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080717#M730621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sri,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC : Intermediate Document..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC can be used for the ALE(Application Link Enabling) for different buissness fucntions spread accross an enterprise.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP -System &amp;lt;--&lt;DEL&gt;-&amp;gt;IDOC&amp;lt;&lt;/DEL&gt;---&amp;gt; Non-SAP -Syst(may be a legacy system)or a client interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic type : we30&lt;/P&gt;&lt;P&gt;Segment :we31&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC is an instance of IDOC type.&lt;/P&gt;&lt;P&gt;Each IDOC has 3 parts&lt;/P&gt;&lt;P&gt;1. Control Record&lt;/P&gt;&lt;P&gt;2. Data Record&lt;/P&gt;&lt;P&gt;3. Status Record&lt;/P&gt;&lt;P&gt;We02 or We05 is used to display an idoc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At run time the following events occur&lt;/P&gt;&lt;P&gt;A unique IDOC no. is allocated by SAP&lt;/P&gt;&lt;P&gt;One control record is attached to the IDOC&lt;/P&gt;&lt;P&gt;Segments translate into data records&lt;/P&gt;&lt;P&gt;Status records are attached&lt;/P&gt;&lt;P&gt;Syntax rules are checked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE 30 Basic IDOC Type defines the structure and format of the business document that is to be exchanged.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE31: Segment type &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC Type has a &lt;/P&gt;&lt;P&gt; 1.specific name&lt;/P&gt;&lt;P&gt;2. list of permitted segments&lt;/P&gt;&lt;P&gt;3. hierarchy of segments&lt;/P&gt;&lt;P&gt;4. mandatory/optional segments&lt;/P&gt;&lt;P&gt;5. minimum/maximum range of each segment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parter profile:we20 A partner is defined as a business partner with whom you conduct business and exchange documents&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Port :we21&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then after attaching the mesager type through the we81 and assigning thorugh we82 we go for the process code we42 for inbound IDOC and we41 for outbound.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC trigger.&lt;/P&gt;&lt;P&gt;Can be done through &lt;/P&gt;&lt;P&gt;FM or Report &lt;/P&gt;&lt;P&gt;Or through message control.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We 19 :Test the IDOC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reference:http://idocs.de&lt;/P&gt;&lt;P&gt;rewards if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mohinder Singh Chauhan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 04:25:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/in-cross-apps-what-is-basic-type-idoc-type-message-type/m-p/3080717#M730621</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-29T04:25:59Z</dc:date>
    </item>
  </channel>
</rss>

