<?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>Question Re: Multiple UNH Segment in EDIFACT message in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702794#M190959</link>
    <description>&lt;P&gt;Hi Manoj,&lt;/P&gt;&lt;P&gt;we currently don't have this feature installed. I saw it when I was searching for another problem. But it says you have to update the metadata of EDI separator channel  as described in note 2534770.&lt;BR /&gt;Regards&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;</description>
    <pubDate>Thu, 04 Oct 2018 06:02:47 GMT</pubDate>
    <dc:creator>peter_karg</dc:creator>
    <dc:date>2018-10-04T06:02:47Z</dc:date>
    <item>
      <title>Multiple UNH Segment in EDIFACT message</title>
      <link>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaq-p/702789</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;I have a EDIFACT to flat file Scenario where i am getting multiple UNH segments in the EDIFACT file. EDISeparator is spliting the UNH segments into multiple EDIFACT messages and sending to sender EDIseparator. For my requirement, i have to merge all the UNH files into single EDIFACT file.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Is there any option to merge multiple UNH segments into single edifact file&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Regards,&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Manoj Kumar&lt;/P&gt;</description>
      <pubDate>Mon, 01 Oct 2018 13:05:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaq-p/702789</guid>
      <dc:creator>former_member312853</dc:creator>
      <dc:date>2018-10-01T13:05:03Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple UNH Segment in EDIFACT message</title>
      <link>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702790#M190955</link>
      <description>&lt;P&gt;Hi Manoj,&lt;/P&gt;&lt;P&gt;can you please check note 2548098. With B2B Add-On SP05 you should have the possibility to split messages only on UNB level.&lt;BR /&gt;Regards&lt;BR /&gt;Peter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Oct 2018 07:01:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702790#M190955</guid>
      <dc:creator>peter_karg</dc:creator>
      <dc:date>2018-10-02T07:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple UNH Segment in EDIFACT message</title>
      <link>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702791#M190956</link>
      <description>&lt;P&gt;Manoj ,&lt;/P&gt;&lt;P&gt;Just trying the purpose of your requirement. multiple UNH segments mean the partner is sending multiple orders in one file whereas per order one idoc would be generated in your backed ECC system. What is the reason to combine them?&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Manoj&lt;/P&gt;</description>
      <pubDate>Tue, 02 Oct 2018 12:03:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702791#M190956</guid>
      <dc:creator>manoj_khavatkopp</dc:creator>
      <dc:date>2018-10-02T12:03:32Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple UNH Segment in EDIFACT message</title>
      <link>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702792#M190957</link>
      <description>&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;We are on latest version of B2B add-on, but the option for "Receive Split UNB" was not available in Sender EDI separator channel.&lt;/P&gt;&lt;P&gt;Do we need to update our Adapter metadata structure !!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Manoj &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Oct 2018 15:27:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702792#M190957</guid>
      <dc:creator>former_member312853</dc:creator>
      <dc:date>2018-10-02T15:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple UNH Segment in EDIFACT message</title>
      <link>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702793#M190958</link>
      <description>&lt;P&gt;Hi Manoj,&lt;/P&gt;&lt;P&gt;Our requirement is EDIFACT to Flat file scenario, where all the order of a partner will generate in a single EDIFACT file and PI has to generate the single Flat file. Target system is SFTP folder&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Oct 2018 15:43:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702793#M190958</guid>
      <dc:creator>former_member312853</dc:creator>
      <dc:date>2018-10-02T15:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple UNH Segment in EDIFACT message</title>
      <link>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702794#M190959</link>
      <description>&lt;P&gt;Hi Manoj,&lt;/P&gt;&lt;P&gt;we currently don't have this feature installed. I saw it when I was searching for another problem. But it says you have to update the metadata of EDI separator channel  as described in note 2534770.&lt;BR /&gt;Regards&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2018 06:02:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/multiple-unh-segment-in-edifact-message/qaa-p/702794#M190959</guid>
      <dc:creator>peter_karg</dc:creator>
      <dc:date>2018-10-04T06:02:47Z</dc:date>
    </item>
  </channel>
</rss>

