<?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: Material master IDOC Issue when transfering between two systems in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-idoc-issue-when-transfering-between-two-systems/m-p/10539362#M1855994</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sukumar, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's a catch 22 situation. I think you can implement a BADI which gets triggered post processing of IDOCs &amp;amp; write a code to delete unprocessed (just created) change pointers in that BADI. This Thread might be helpful for you.&lt;/P&gt;&lt;P&gt;&lt;A __default_attr="1825147" __jive_macro_name="thread" class="jive_macro_thread jive_macro" data-orig-content="fm about reset change pointer" href="https://community.sap.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Aug 2014 17:56:06 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-08-19T17:56:06Z</dc:date>
    <item>
      <title>Material master IDOC Issue when transfering between two systems</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-idoc-issue-when-transfering-between-two-systems/m-p/10539361#M1855993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are facing one issue, Like we are transferring material master data between two SAP systems by change pointers RBDMIDOC.&lt;/P&gt;&lt;P&gt;Problem is when we create a material in system 1, then it is transfered to system 2 and material is created there, the change pointers table are being updated in target system 2.&lt;/P&gt;&lt;P&gt;Because of this when RBDMIDOC is run in target system 2, Again the material created is creating a new outbound IDOC is system 2 target for us and it is being transfered to system 1 source.&lt;/P&gt;&lt;P&gt;This process is being repeated and idocs are going on creating for same material.&lt;/P&gt;&lt;P&gt;Please help in how to avoid this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sukumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Aug 2014 11:57:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-idoc-issue-when-transfering-between-two-systems/m-p/10539361#M1855993</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-08-14T11:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: Material master IDOC Issue when transfering between two systems</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-idoc-issue-when-transfering-between-two-systems/m-p/10539362#M1855994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sukumar, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's a catch 22 situation. I think you can implement a BADI which gets triggered post processing of IDOCs &amp;amp; write a code to delete unprocessed (just created) change pointers in that BADI. This Thread might be helpful for you.&lt;/P&gt;&lt;P&gt;&lt;A __default_attr="1825147" __jive_macro_name="thread" class="jive_macro_thread jive_macro" data-orig-content="fm about reset change pointer" href="https://community.sap.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2014 17:56:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-idoc-issue-when-transfering-between-two-systems/m-p/10539362#M1855994</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-08-19T17:56:06Z</dc:date>
    </item>
  </channel>
</rss>

