<?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: Nested Segment in Inbound IDoc. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588443#M864024</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are welcome.&lt;/P&gt;&lt;P&gt;However, I was expecting points &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G@urav.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Mar 2008 20:36:34 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-03-19T20:36:34Z</dc:date>
    <item>
      <title>Nested Segment in Inbound IDoc.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588438#M864019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have created all required settings for Inbound Idoc and then I created one function module to process it. When I have simple 2 or 3 segment, I use &lt;/P&gt;&lt;P&gt;case idoc_data-segnam&lt;/P&gt;&lt;P&gt;      when 'segname1'&lt;/P&gt;&lt;P&gt;      when 'segname2'&lt;/P&gt;&lt;P&gt;endcase. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I have nested segment in 'segname1' then how to use the case syntax?. Please write some sample.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 19:34:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588438#M864019</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-19T19:34:09Z</dc:date>
    </item>
    <item>
      <title>Re: Nested Segment in Inbound IDoc.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588439#M864020</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can continue using the same case statement.&lt;/P&gt;&lt;P&gt;case idoc_data-segnam&lt;/P&gt;&lt;P&gt;when 'segname1'&lt;/P&gt;&lt;P&gt;when 'segname2'&lt;/P&gt;&lt;P&gt;endcase. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;idoc_data-segnam will capture the segment name irrespective to the segment hierarchy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G@urav.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 19:58:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588439#M864020</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-19T19:58:19Z</dc:date>
    </item>
    <item>
      <title>Re: Nested Segment in Inbound IDoc.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588440#M864021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gaurav, You mean If first segment has 2 nested segments then these child segments will be considered 2nd and 3rd segments in case statements.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 20:10:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588440#M864021</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-19T20:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: Nested Segment in Inbound IDoc.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588441#M864022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes..&lt;/P&gt;&lt;P&gt;it will take the successive child segments in segment2 and segment3.&lt;/P&gt;&lt;P&gt;Try debugging it.. you will get a better understanding.&lt;/P&gt;&lt;P&gt;G@urav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 20:13:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588441#M864022</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-19T20:13:16Z</dc:date>
    </item>
    <item>
      <title>Re: Nested Segment in Inbound IDoc.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588442#M864023</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok........Thank you very much.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 20:30:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588442#M864023</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-19T20:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: Nested Segment in Inbound IDoc.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588443#M864024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are welcome.&lt;/P&gt;&lt;P&gt;However, I was expecting points &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G@urav.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 20:36:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/nested-segment-in-inbound-idoc/m-p/3588443#M864024</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-19T20:36:34Z</dc:date>
    </item>
  </channel>
</rss>

