<?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: outbound interfaces in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/outbound-interfaces/m-p/2491168#M562262</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;&lt;/P&gt;&lt;P&gt;There are basically two types of IDOCs.&lt;/P&gt;&lt;P&gt;Basic IDOCs&lt;/P&gt;&lt;P&gt;Extended 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;Extension Idoc:Extending the functionality by adding more segments to existing Basic IDOCs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A basic IDOC type has the following characteristics: &lt;/P&gt;&lt;P&gt;Name : A basic Idoc type can be assigned upto a thirty character name. &lt;/P&gt;&lt;P&gt;List of permitted segments: The segments make up the IDOC structure. &lt;/P&gt;&lt;P&gt;Hierarchy of segments : The hierarchy of segments specifies the physical sequence and &lt;/P&gt;&lt;P&gt;any parent - child relationship in the segments.&lt;/P&gt;&lt;P&gt;Mandatory Vs Optional Segments : When used in the IDOC type, each segment has &lt;/P&gt;&lt;P&gt;an attribute that defines whether the segment is option or mandatory. &lt;/P&gt;&lt;P&gt;Minimum/Maximum range for each segment: It defines the maximum and minimum &lt;/P&gt;&lt;P&gt;number of timesa data record corresponding to a segment cn exist in an IDOC.&lt;/P&gt;&lt;P&gt;- Segments : A segment defines the format and structure of a data record. &lt;/P&gt;&lt;P&gt;Segments are reusable componets. A segment consists of various fields that represent data&lt;/P&gt;&lt;P&gt;in data record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;IDOC Run time components:&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------------------" /&gt;&lt;P&gt;- A unique IDOC number 16 digits is allocated. &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;- Sytax rules are checked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Priyanka.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 13 Jul 2007 05:36:08 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-13T05:36:08Z</dc:date>
    <item>
      <title>outbound interfaces</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/outbound-interfaces/m-p/2491167#M562261</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,, can any one explain abt the types of outbound  for idocs in hr...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;suggestions will be rewarded withpoints..&lt;/P&gt;&lt;P&gt;thanks in  advance..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jul 2007 05:33:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/outbound-interfaces/m-p/2491167#M562261</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-13T05:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: outbound interfaces</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/outbound-interfaces/m-p/2491168#M562262</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;&lt;/P&gt;&lt;P&gt;There are basically two types of IDOCs.&lt;/P&gt;&lt;P&gt;Basic IDOCs&lt;/P&gt;&lt;P&gt;Extended 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;Extension Idoc:Extending the functionality by adding more segments to existing Basic IDOCs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A basic IDOC type has the following characteristics: &lt;/P&gt;&lt;P&gt;Name : A basic Idoc type can be assigned upto a thirty character name. &lt;/P&gt;&lt;P&gt;List of permitted segments: The segments make up the IDOC structure. &lt;/P&gt;&lt;P&gt;Hierarchy of segments : The hierarchy of segments specifies the physical sequence and &lt;/P&gt;&lt;P&gt;any parent - child relationship in the segments.&lt;/P&gt;&lt;P&gt;Mandatory Vs Optional Segments : When used in the IDOC type, each segment has &lt;/P&gt;&lt;P&gt;an attribute that defines whether the segment is option or mandatory. &lt;/P&gt;&lt;P&gt;Minimum/Maximum range for each segment: It defines the maximum and minimum &lt;/P&gt;&lt;P&gt;number of timesa data record corresponding to a segment cn exist in an IDOC.&lt;/P&gt;&lt;P&gt;- Segments : A segment defines the format and structure of a data record. &lt;/P&gt;&lt;P&gt;Segments are reusable componets. A segment consists of various fields that represent data&lt;/P&gt;&lt;P&gt;in data record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;IDOC Run time components:&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------------------" /&gt;&lt;P&gt;- A unique IDOC number 16 digits is allocated. &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;- Sytax rules are checked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Priyanka.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jul 2007 05:36:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/outbound-interfaces/m-p/2491168#M562262</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-13T05:36:08Z</dc:date>
    </item>
  </channel>
</rss>

