<?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 -Issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-issue/m-p/4906554#M1145616</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;My suggestion is to add matnr1 matnr2 separately, since you will have advantage to do validations on each sub-materials on material master and other transactional tables using the key field matnr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also there will be performance issues if you combine all materials into one and try to use where condition on SAP standard materials where you need to calculate substring of the material you are searching.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know what is your opinion on this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Krishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Dec 2008 15:44:47 GMT</pubDate>
    <dc:creator>nkr1shna</dc:creator>
    <dc:date>2008-12-12T15:44:47Z</dc:date>
    <item>
      <title>Material -Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-issue/m-p/4906552#M1145614</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;I have z table in which i have main material and this is key field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For this material there are sub material for which i need to perform  certain calculations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since in z table material is key field .Will it better to put give &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;main matnr                                  matnr1        matnr 2  matnr3 -      all separately in columns      &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; or &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;main matnr                        matnr1,matnr2, matnr3 -                       all in one text field  separated by ,.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any other suggestion are welcome.We are not prefering to change material master table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ivneet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Dec 2008 15:29:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/material-issue/m-p/4906552#M1145614</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-12T15:29:56Z</dc:date>
    </item>
    <item>
      <title>Re: Material -Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-issue/m-p/4906553#M1145615</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ivneet,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another solution is make a ztable with you main matnr and index number as key and add one column for the submaterial.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First submaterial will have index 1, next index 2 and so on.&lt;/P&gt;&lt;P&gt;In this case is doesn't matter how many subitem it is connected to the main item.&lt;/P&gt;&lt;P&gt;And the table record is a small one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Åsa Thenstedt&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Dec 2008 15:42:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/material-issue/m-p/4906553#M1145615</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-12T15:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: Material -Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/material-issue/m-p/4906554#M1145616</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;My suggestion is to add matnr1 matnr2 separately, since you will have advantage to do validations on each sub-materials on material master and other transactional tables using the key field matnr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also there will be performance issues if you combine all materials into one and try to use where condition on SAP standard materials where you need to calculate substring of the material you are searching.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know what is your opinion on this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Krishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Dec 2008 15:44:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/material-issue/m-p/4906554#M1145616</guid>
      <dc:creator>nkr1shna</dc:creator>
      <dc:date>2008-12-12T15:44:47Z</dc:date>
    </item>
  </channel>
</rss>

