<?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 Material Master Change Pointers/Distribution Model - any suggestions? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-change-pointers-distribution-model-any-suggestions/m-p/8441156#M1648555</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope everyone is doing good.. I have been trying to come up with a solution for the below issue, but didn't get any further. Your help is highly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Initial Design:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Couple of years before we had a plant 123 and plant 456 where we need to send the materials. So we had specified these plants in Distribution Model and things worked fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;First Problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During testing what we have found out was, if some one changes MARA level, IDOC is being created but it's not being sent out of SAP system because the IDOC doesn't have 123 and 456 plants which the distribution model filtered it out and no data got sent to SAP PI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Solution implemented:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;After doing lot of analysis and research we have implemented solution as per the blog &lt;A class="jive_macro jive_macro_blogpost" href="https://community.sap.com/" __jive_macro_name="blogpost" modifiedtitle="true" __default_attr="49907"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Today's problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;There are couple of more plants we were supposed to send the data 789 and 678. The problem is if some one did a mass change on plant 456, the above solution implemented takes all the data(not the deltas) and pushing it out. Even though the change is only on 456 plant, we were unnecessarily sending the data to 789, 678 which is causing lot of problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now we realize we shouldn't have gone with the solution mentioned above, because it's not applicable in my scenario.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone handled this kind of scenarios in the past, if so can you please shed some lights?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Raj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Dec 2011 18:00:38 GMT</pubDate>
    <dc:creator>justin_santhanam</dc:creator>
    <dc:date>2011-12-20T18:00:38Z</dc:date>
    <item>
      <title>Material Master Change Pointers/Distribution Model - any suggestions?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-change-pointers-distribution-model-any-suggestions/m-p/8441156#M1648555</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope everyone is doing good.. I have been trying to come up with a solution for the below issue, but didn't get any further. Your help is highly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Initial Design:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Couple of years before we had a plant 123 and plant 456 where we need to send the materials. So we had specified these plants in Distribution Model and things worked fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;First Problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During testing what we have found out was, if some one changes MARA level, IDOC is being created but it's not being sent out of SAP system because the IDOC doesn't have 123 and 456 plants which the distribution model filtered it out and no data got sent to SAP PI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Solution implemented:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;After doing lot of analysis and research we have implemented solution as per the blog &lt;A class="jive_macro jive_macro_blogpost" href="https://community.sap.com/" __jive_macro_name="blogpost" modifiedtitle="true" __default_attr="49907"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Today's problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;There are couple of more plants we were supposed to send the data 789 and 678. The problem is if some one did a mass change on plant 456, the above solution implemented takes all the data(not the deltas) and pushing it out. Even though the change is only on 456 plant, we were unnecessarily sending the data to 789, 678 which is causing lot of problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now we realize we shouldn't have gone with the solution mentioned above, because it's not applicable in my scenario.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone handled this kind of scenarios in the past, if so can you please shed some lights?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Raj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 18:00:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-change-pointers-distribution-model-any-suggestions/m-p/8441156#M1648555</guid>
      <dc:creator>justin_santhanam</dc:creator>
      <dc:date>2011-12-20T18:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: Material Master Change Pointers/Distribution Model - any suggestions?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-change-pointers-distribution-model-any-suggestions/m-p/8441157#M1648556</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  As per my experience what you had already implemented, that is absolutely correct. I don't think there is any alternative to send the data as a whole (I understood if you are not sending the Plant data, how the middle ware filter them).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Now your requirement is if you make some mass changes in the materials which are extended different plants other than 456 plant, we have to restrict them. To restrict the outbound Idocs for MATMAS. you can use the Filter option in BD64 (Distribution Model). Here after creating the Filter Group, you can edit LOV for Plants. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Once your mass changes transmission is over, you can remove this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Hope this will work, at least you can give a try...............&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Dec 2011 14:06:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/material-master-change-pointers-distribution-model-any-suggestions/m-p/8441157#M1648556</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-12-21T14:06:54Z</dc:date>
    </item>
  </channel>
</rss>

