<?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: Numbering 3rd dimension of proc tabulate individually in ODS and Base Reporting</title>
    <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546519#M22578</link>
    <description>Hi:&lt;BR /&gt;  It looks like you're using a custom denominator with TABULATE. &lt;BR /&gt;&lt;BR /&gt;By group processing might change the percent calculates, since each BY group is treated as a whole entity rather than as a fraction of the whole data set. I also notice that your VAR1, VAR2 and VAR3 are analysis variables which means they are numeric, so BY group processing may not produce what you want, depending on the values for those variables (discrete or continuous). &lt;BR /&gt;&lt;BR /&gt;Three TABLE statements might be the best way to do this. &lt;BR /&gt;&lt;BR /&gt;Since you can't post data here and only post dummy code, you may want to open a track with Tech Support and send them the real data and the real code. If 3 TABLE statements gives you what you want in ODS Document, that seems the best way to go.&lt;BR /&gt;&lt;BR /&gt;Cynthia</description>
    <pubDate>Wed, 27 Mar 2019 14:56:13 GMT</pubDate>
    <dc:creator>Cynthia_sas</dc:creator>
    <dc:date>2019-03-27T14:56:13Z</dc:date>
    <item>
      <title>Numbering 3rd dimension of proc tabulate individually</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546434#M22575</link>
      <description>&lt;P&gt;Dear community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have used proc tabulate to generate a three-dimensional report. Is there a way to give each table a separate number? I tried writing to ods document but proc document list lists all 3 component tables as one table. Thank you for suggestions in advance.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 10:33:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546434#M22575</guid>
      <dc:creator>js5</dc:creator>
      <dc:date>2019-03-27T10:33:17Z</dc:date>
    </item>
    <item>
      <title>Re: Numbering 3rd dimension of proc tabulate individually</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546497#M22576</link>
      <description>Hi:&lt;BR /&gt;  You need to post code and some sample data or use SASHELP datasets to mock up an example of what you're describing. You might try BY group processing with PROC TABULATE to get separate objects for each group. That would mean NOT using the PAGE dimension in your table, as shown below:&lt;BR /&gt;&lt;BR /&gt;Cynthia</description>
      <pubDate>Wed, 27 Mar 2019 14:00:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546497#M22576</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2019-03-27T14:00:32Z</dc:date>
    </item>
    <item>
      <title>Re: Numbering 3rd dimension of proc tabulate individually</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546501#M22577</link>
      <description>&lt;P&gt;Hi &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13549"&gt;@Cynthia_sas&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you for responding! Please see the code in question with variable names replaced with placeholders below:&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;proc tabulate data=foo order=formatted;
	var var1 var2 var3 var4;
	class var5 var6;

	table var1 var2 var3, var5, var6 * (sum colpctsum&amp;lt;var4&amp;gt;) /style=[just=left];
		format var5 $var5fmt. var6 $var6fmt.;
quit;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;While typing it here I realised that I could probably use 3 separate table statements with var1, var2 and var3 only each and get 3 objects at the cost of code triplication. Is there a cleaner solution?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 14:09:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546501#M22577</guid>
      <dc:creator>js5</dc:creator>
      <dc:date>2019-03-27T14:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: Numbering 3rd dimension of proc tabulate individually</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546519#M22578</link>
      <description>Hi:&lt;BR /&gt;  It looks like you're using a custom denominator with TABULATE. &lt;BR /&gt;&lt;BR /&gt;By group processing might change the percent calculates, since each BY group is treated as a whole entity rather than as a fraction of the whole data set. I also notice that your VAR1, VAR2 and VAR3 are analysis variables which means they are numeric, so BY group processing may not produce what you want, depending on the values for those variables (discrete or continuous). &lt;BR /&gt;&lt;BR /&gt;Three TABLE statements might be the best way to do this. &lt;BR /&gt;&lt;BR /&gt;Since you can't post data here and only post dummy code, you may want to open a track with Tech Support and send them the real data and the real code. If 3 TABLE statements gives you what you want in ODS Document, that seems the best way to go.&lt;BR /&gt;&lt;BR /&gt;Cynthia</description>
      <pubDate>Wed, 27 Mar 2019 14:56:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Numbering-3rd-dimension-of-proc-tabulate-individually/m-p/546519#M22578</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2019-03-27T14:56:13Z</dc:date>
    </item>
  </channel>
</rss>

