<?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: Trouble with PROC OLAP time dimension!! Driving me NUTS!!!!!! in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75105#M7451</link>
    <description>i see you guys aren't solution driven, rather pass the buck...&lt;BR /&gt;
&lt;BR /&gt;
I obviously check the sas.com support site.&lt;BR /&gt;
&lt;BR /&gt;
What do you want me to explain?</description>
    <pubDate>Thu, 08 Oct 2009 17:21:08 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2009-10-08T17:21:08Z</dc:date>
    <item>
      <title>Trouble with PROC OLAP time dimension!! Driving me NUTS!!!!!!</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75102#M7448</link>
      <description>I'm trying to create a Time dimension trough a Proc Olap but I have been having a fustrating experience.&lt;BR /&gt;
&lt;BR /&gt;
The date is stored in my detailed table under the column "Reported_Month".  The dates are stored as "01Jul2009", 01Aug2009", etc...  I've attached my code and the log with errors.&lt;BR /&gt;
&lt;BR /&gt;
Where is my code:&lt;BR /&gt;
&lt;BR /&gt;
dimension Time&lt;BR /&gt;
   hierarchies=(Time)&lt;BR /&gt;
   type=time&lt;BR /&gt;
   ;  &lt;BR /&gt;
   hierarchy Time&lt;BR /&gt;
      levels=(Year Quarter Month Day)&lt;BR /&gt;
      ; &lt;BR /&gt;
   level Year &lt;BR /&gt;
      type=year &lt;BR /&gt;
      column=reported_month&lt;BR /&gt;
      format=year.&lt;BR /&gt;
      ;  &lt;BR /&gt;
   level Quarter&lt;BR /&gt;
      type=quarters&lt;BR /&gt;
      column=reported_month&lt;BR /&gt;
	format=qtr.&lt;BR /&gt;
      ;      &lt;BR /&gt;
   level Month&lt;BR /&gt;
      type=months&lt;BR /&gt;
      column=reported_month&lt;BR /&gt;
      format=monname.&lt;BR /&gt;
      ;  &lt;BR /&gt;
   level Day&lt;BR /&gt;
      type=days&lt;BR /&gt;
      column=reported_month&lt;BR /&gt;
      format=weekdate.&lt;BR /&gt;
      ;&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Here is the LOG with errors!:&lt;BR /&gt;
&lt;BR /&gt;
49         dimension Time&lt;BR /&gt;
50            hierarchies=(Time)&lt;BR /&gt;
51            type=time&lt;BR /&gt;
52            ;&lt;BR /&gt;
53            hierarchy Time&lt;BR /&gt;
54               levels=(Year Quarter Month Day)&lt;BR /&gt;
55               ;&lt;BR /&gt;
56            level Year&lt;BR /&gt;
57               type=year&lt;BR /&gt;
58               column=reported_month&lt;BR /&gt;
                 ______&lt;BR /&gt;
                 22&lt;BR /&gt;
                 76&lt;BR /&gt;
ERROR 22-322: Syntax error, expecting one of the following: ;, CAPTION, DESC, EMPTY, IGNORE_EMPTY, SORT_ORDER, TYPE.  &lt;BR /&gt;
&lt;BR /&gt;
ERROR 76-322: Syntax error, statement will be ignored.&lt;BR /&gt;
&lt;BR /&gt;
59               format=year.&lt;BR /&gt;
60               ;&lt;BR /&gt;
61            level Quarter&lt;BR /&gt;
62               type=quarters&lt;BR /&gt;
63               column=reported_month&lt;BR /&gt;
                 ______&lt;BR /&gt;
                 22&lt;BR /&gt;
                 76&lt;BR /&gt;
ERROR 22-322: Syntax error, expecting one of the following: ;, CAPTION, DESC, EMPTY, IGNORE_EMPTY, SORT_ORDER, TYPE.  &lt;BR /&gt;
&lt;BR /&gt;
ERROR 76-322: Syntax error, statement will be ignored.&lt;BR /&gt;
&lt;BR /&gt;
64         	format=qtr.&lt;BR /&gt;
65               ;&lt;BR /&gt;
66            level Month&lt;BR /&gt;
67               type=months&lt;BR /&gt;
68               column=reported_month&lt;BR /&gt;
                 ______&lt;BR /&gt;
                 22&lt;BR /&gt;
                 76&lt;BR /&gt;
ERROR 22-322: Syntax error, expecting one of the following: ;, CAPTION, DESC, EMPTY, IGNORE_EMPTY, SORT_ORDER, TYPE.  &lt;BR /&gt;
&lt;BR /&gt;
ERROR 76-322: Syntax error, statement will be ignored.&lt;BR /&gt;
&lt;BR /&gt;
69               format=monname.&lt;BR /&gt;
70               ;&lt;BR /&gt;
71            level Day&lt;BR /&gt;
72               type=days&lt;BR /&gt;
73               column=reported_month&lt;BR /&gt;
                 ______&lt;BR /&gt;
                 22&lt;BR /&gt;
3                                                          The SAS System                           09:38 Wednesday, October 7, 2009&lt;BR /&gt;
&lt;BR /&gt;
                 76&lt;BR /&gt;
ERROR 22-322: Syntax error, expecting one of the following: ;, CAPTION, DESC, EMPTY, IGNORE_EMPTY, SORT_ORDER, TYPE.  &lt;BR /&gt;
ERROR 76-322: Syntax error, statement will be ignored.&lt;BR /&gt;
74               format=weekdate.&lt;BR /&gt;
75               ;&lt;BR /&gt;
76</description>
      <pubDate>Thu, 08 Oct 2009 15:41:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75102#M7448</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-10-08T15:41:37Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with PROC OLAP time dimension!! Driving me NUTS!!!!!!</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75103#M7449</link>
      <description>Hi:&lt;BR /&gt;
  Since you've posted this question in 2 different forums, you might consider contacting Tech Support, instead. They should be your resource of choice for urgent questions where you need a definitive response. To open a track with Tech Support, use the following link:&lt;BR /&gt;
&lt;A href="http://support.sas.com/ctx/supportform/createForm" target="_blank"&gt;http://support.sas.com/ctx/supportform/createForm&lt;/A&gt;&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Thu, 08 Oct 2009 16:34:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75103#M7449</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2009-10-08T16:34:35Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with PROC OLAP time dimension!! Driving me NUTS!!!!!!</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75104#M7450</link>
      <description>Humbly, I disagree and would suggest some fundamental desk-checking while also at least make a reasonable attempt to exhaust available resources that are accessible to SAS users, starting with the SAS.COM support site.  As I commented in the other duplicate-forum post, maybe start out by explaining what is expected, given the SAS log diagnostics generated thus far.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Thu, 08 Oct 2009 17:08:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75104#M7450</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-10-08T17:08:25Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with PROC OLAP time dimension!! Driving me NUTS!!!!!!</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75105#M7451</link>
      <description>i see you guys aren't solution driven, rather pass the buck...&lt;BR /&gt;
&lt;BR /&gt;
I obviously check the sas.com support site.&lt;BR /&gt;
&lt;BR /&gt;
What do you want me to explain?</description>
      <pubDate>Thu, 08 Oct 2009 17:21:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75105#M7451</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-10-08T17:21:08Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with PROC OLAP time dimension!! Driving me NUTS!!!!!!</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75106#M7452</link>
      <description>Hi:&lt;BR /&gt;
  I'm not sure what you mean by solution-driven. I don't use PROC OLAP that often. When I design cubes, it is with OLAP Cube Studio, so I rarely play with OLAP code. Scott's suggestion to compare your code to the documented examples is a good one to help you debug. You could have a simple syntax error that would be revealed if you compared your code to the documentation.&lt;BR /&gt;
&lt;BR /&gt;
  Urgent questions are not appropriate to the forum. If you have an immediate need your best resource is Tech Support. Since you posted the question twice, I interpreted your question to be of an urgent nature. If you have the time to wait for a response, then by all means, wait and see whether someone with PROC OLAP experience can help you here.&lt;BR /&gt;
 &lt;BR /&gt;
  Since I don't use PROC OLAP, I'm not a good resource.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Thu, 08 Oct 2009 17:32:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75106#M7452</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2009-10-08T17:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with PROC OLAP time dimension!! Driving me NUTS!!!!!!</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75107#M7453</link>
      <description>Depends on how one interprets "solution-driven".  I tend to assist, guide, lead, encourage, and on-occasion, share example code.  Others may be willing to simply crank-out code in response to an individual's post - as is, their own choice.  I find it more effective to offer input/feedback to other posters ideally to help with the SAS learning experience.  &lt;BR /&gt;
&lt;BR /&gt;
No doubt, there will be a time (now or later) where a piece of code will need to be supported, modified, hence starting out by understanding the SAS language and the specific code piece is definitely a plus.  Basic desk-checking techniques and self-initiated DOC review is a good start and offers some enhanced credibility, IMHO.  Also, that sticky CAPS LOCK KEY and exclamation character doesn't help convey the important details.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Fri, 09 Oct 2009 16:04:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Trouble-with-PROC-OLAP-time-dimension-Driving-me-NUTS/m-p/75107#M7453</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-10-09T16:04:12Z</dc:date>
    </item>
  </channel>
</rss>

