Disco+ 10g - Financial Year Total Problem (ye old ORA-00979)

Hi, I'm pretty much a newbie to Disco+.
I have created a crosstab report for the Jul06-Jun07 financial year. The report is to display a monthly count of the number of times (days) each month an employee participates in a specified meeting type (query condition), with sub-total (column) at each QTR and Total (column) for financial year.
- Row item is "Emp.EmpName"
- Column items (calculated in EUL) are "Meeting.MeetYear", "Meeting.MeetQtr",
"Meeting.MeetMonth".
- Data points are calculation "CountMeets" being:
NVL(COUNT_DISTINCT(EmpMeetDateID),0), where EmpMeetDateID is a concatenation
of Emp.EmpName & Meeting.MeetDate & Meeting.MeetType.
The report produces correct monthly and quarterly totals, but when I try to add in the grand total at right (financial year total), Disco+ generates ORA-00979 not a GROUP BY expression.
Here'e hoping someone can give greatly appreciated guidance.
Thanks
Rick

Well actually your response is helpful,
but would you care to clarify where in the IDE you should adjust what?
Thanks so much!

Similar Messages

  • Partition By Function creating problem in Disco 10g

    We have used "Partition By" analytical function in some of our reports. We were running it in Disco 4i without any problem. But when we tried to run those reports in disco 10g, all the calculation columns where "Partition By" function is used, showing empty. When I remove "partition by" clause it retrieves the data. Anybody knows why it is happening?
    Update: When I tried to add following existing calculation in the report gives me a error "column ambiguously defined"
    ROW_NUMBER() OVER(PARTITION BY Invoice Number,Invoice Line Number ORDER BY Invoice Line Number )
    Thanks
    Message was edited by:
    DiscoverDiscoverer

    Hi
    You don't type the double quotes but if Discoverer puts them in leave them there.
    My gut feeling is that the problem is caused by the names of the items in the folder, or at least inside the report. As you know, whenever Discoverer begins parsing a name it stops whenever the name can be satisfied or tied to an object. Look again at your code:
    ROW_NUMBER() OVER(PARTITION BY Invoice Number,Invoice Line Number ORDER BY Invoice Line Number )
    You have an item called Invoice Number right? You also have an item called Invoice Line Number. As Discoverer is parsing these do you happen to have another item in your system called Invoice? If so, Discoverer will think you are asking it to PARTITION BY that item. Does this make sense?
    Let's try an experiment.
    Create 2 calculations, one called INV_NUM and one called INV_LINE, pointing INV_NUM directly at INVOICE NUMBER and INV_LINE at INVOICE_LINE_NUMBER.
    Having got these 2 calculations in use, remove the original items from the report
    Now try adding this code:
    ROW_NUMBER() OVER(PARTITION BY INV_NUM,INV_LINE ORDER BY INV_LINE)
    Did this help at all?
    May I finally give you a workd of warning and that is to take care when naming items in folders. While Discoverer will let you do it, try to avoid using Oracle reserved words in item names. The name Number is a reserved word.
    Having these as item names can lead to terrible problems when using analytic functions. Imagine if you will that you have a column called INVOICE and another called INVOICE DESC, short for DESCRIPTION and you use this:
    ROW_NUMBER() OVER(PARTITION BY INVOICE AMOUNT ORDER BY INVOICE DESC )
    Discoverer will think you want the INVOICE sorted in descending order which is not what you want at all. In this case you won't get an error. You'll just get the wrong answer.
    Michael

  • Problems archiving old messages at the end of the year?

    At the end of 2007 I'd like to create new mailboxes for messages sent and received in the year, date them, and move the messages across into them; leaving the Inbox and Sent box empty and ready to handle messages for 2008. Is this a reasonably straightforward thing to do? Are there potential pitfalls I should be aware of?

    Yes, it’s reasonable and straightforward, and is also what I do, except I don’t wait till the end of the year to archive my messages. Instead, I create a (white) folder for each year, including the current one, and organize my mail by topic into (blue) sub-mailboxes there as I read them. My Inbox only contains messages (if any) that are waiting for me to do something with them.
    Are there potential pitfalls I should be aware of?
    The main pitfall you should be aware of would be not doing that and leaving all your mail in the account mailboxes indefinitely. Using Inbox and Sent for archiving purposes (which a lot of people do) is a bad idea.
    Another thing to be aware of is that you shouldn’t use the same folder as both a mailbox (i.e. to store messages of its own) and as a parent folder for other folders. Mail allows that duality, but doesn’t handle it very well, and it’s better to not try to “take advantage” of it.
    You may also want to read this:
    Blue and white Mail folders explained
    BTW, the title of your post is “problems archiving old messages at the end of the year?

  • Problem transferring old iPhone 3GS to new phone 5S using computer.  The iMac which I've been using to back up 3GS for years does not seem to recognize the 5S.  No setup assist is coming on screen so I can't begin the transfer.  Any ideas for this?

    Problem tranferring old iPhone 3GS (ios 6.1.6) to new iPhone 5S (ios 8.1.2) through iTunes on my iMac computer  (OSX 10.5.8) . I have backed up the 3GS this way since purchase of 3GS.  The computer does not seem to recognize the 5S is there -- no setup assist is appearing on screen. Any ideas welcome.

    this may not be your problem my according to the tech specs on apple.com the 5s requires:
    Syncing with iTunes on a Mac or PC requires:
    Mac: OS X v10.6.8 or later
    PC: Windows 8; Windows 7; Windows Vista; or Windows XP Home or Professional with Service Pack 3 or later
    iTunes 11.1 or later (free download

  • Query for getting data for every quarter for financial year

    Hi,
    My problem is I need to get the data for every quarter for financial year and also I need data for every week for financial year.
    For example for financial year 2012-13, Apr2012 to Jun2012 would be Q1, Jul2012 to Sep2012 would be Q2 and so on. Total 8quarters should come upto Apr2013.
    In the same way  1st apr 2012 to 7th apr 2012 would be week1, 8th apr to 15th apr would be week2 and son on. How to write a query for this scenario in oracle. Can anybody help me on this. very urgent..
    Thanks in advance.

    lakmesri wrote:
    Hi,
    My problem is I need to get the data for every quarter for financial year and also I need data for every week for financial year.
    For example for financial year 2012-13, Apr2012 to Jun2012 would be Q1, Jul2012 to Sep2012 would be Q2 and so on. Total 8quarters should come upto Apr2013.
    In the same way  1st apr 2012 to 7th apr 2012 would be week1, 8th apr to 15th apr would be week2 and son on. How to write a query for this scenario in oracle. Can anybody help me on this. very urgent..
    Thanks in advance.
    How can you get 8 quarters within a year ? I'b be concerned here.
    lakmesri wrote:
    Hi,
    In the same way  1st apr 2012 to 7th apr 2012 would be week1, 8th apr to 15th apr would be week2 and son on. How to write a query for this scenario in oracle. Can anybody help me on this. very urgent..
    Thanks in advance.
    First, that question is really not clearly asked. Second how could it be urgent ? You even did not tell us your Oracle version, did not show any tables descr, output sample nor any effort on your side to work on.
    Nicolas.

  • Alternate Financial year(AFY) in Indian Payroll

    Hi All,
    I am facing a strange problem in my payroll configuration. I activated business function for AFY and now Income tax should get calculated from March to Feb. I have necessary config for AFY including payroll period & control record. Now in my system period 1 of 2013 is equal to 01.03.2013 to 31.03.2013 & period 12 is 01.02.2014 to 28.02.2014.
    I hired an employee on 01.03.2013 & trying to run payroll for whole financial year i.e. march 2013 to Feb 2014.
    I noticed a discrepancy while calculating gross salary & professional tax while it calculates IT.
    In March 2013 (012013) payslip monthly gross & Ptax are getting multiplied by 12
    In April 2013 (022013) payslip monthly gross & Ptax are getting multiplied by 12. In March & April there is no issue.
    But after that from May 2013 (032013) onward monthly gross & Ptax are getting multiplied by 11 for calculating IT which is very strange & I am not able to find the issue.
    I also checked projection factor and /401 is giving accurate value only.
    Pls help me with this as this highly important for my project.
    Thanks & regards,
    Arka

    Hi Arka,
    I think you are saying wrong.
    In the March/2013---/401 will be hold the value 11
    in the April/2013----/401 will be hold the value 10
    in the May/2013----/401 will be hold the value 9.
    Check and tell me.
    Regards,
    Sankarsan

  • Open PO's after new financial year ??

    hii
    If we have some open PO's after year end .(New financial year got opened )
    In this case , we ahve to open new MM period using MMPV.
    What are the impacts will be there in SAP system, how to proceed further.
    Thanks

    hii
    Can u tel me , the steps has to be carried out in MMPV and OMSY.
    Once the new Period got opened in MMPV , how to proceed furthere with ur solution.
    Anthony said , there is no problem .
    can soem bosy explain me the step in MMPV and OMSY??
    Thanks

  • Date Range according to Financial year-end

    Hi
    I'm building this Discoverer report and one of my parameters is a LoV date field, which gives me a date range from Jan to Dec each year. Now my problem is, I want my date range to be as per our Financial Year End, which is from 01-Oct-03 to 30-Sep-04.
    You'd find "<All>" amongst the range. This "All" currently indicates date between Jan 2003 - Dec 2003. Now I need to write a query/trigger that will put my date range to be between 01-Oct-02 to 30-Sep-03 recurring automatically after each Financial year-end.
    Thanks

    Hi,
    Although I haven't tried it, you should be able to use a combination of hierarchies and alternative sorts to accomplish this.
    How have you created your list of values? If your LOV is a list of months and years e.g. JAN-2003, FEB-2003 etc, you can create a alternative sort which will make OCTOBER the first month of the year - i.e. with value 1, and NOVEMBER = 2 and so on...
    Sorry this is a bit vague. I will try and test tomorrow and see if it works, but this should be enough to give you an idea of how to progress.

  • Financial Year-End date range

    Hi
    I'm building this Discoverer report and one of my parameters is a LoV date field, which gives me a date range from Jan to Dec each year. Now my problem is, I want my date range to be as per our Financial Year End, which is from 01-Oct-03 to 30-Sep-04.
    You'd find "<All>" amongst the range. This "All" currently indicates date between Jan 2003 - Dec 2003. Now I need to write a query/trigger that will put my date range to be between 01-Oct-02 to 30-Sep-03 recurring automatically after each Financial year-end.
    Thanks

    Hi,
    You might want to post the Q on Discoverer Forum also
    Discoverer
    Navneet.

  • Customer Exit Variable Period 000 is not valid in financial year variant Z2

    Hi all,
    I am trying to get the week number from a particular posting period. But I get this error when I execute the Query:
    Error Group
    RFC_ERROR_SYSTEM_FAILURE
    Message
    SYST: Period 000 is not valid in financial year variant Z2
    I checked in "FIRST_DAY_IN_PERIOD_GET" FM and it is not accpting period 000 for PERIV Z2. It works fine for all other periods.
    Does anyone have an idea on this?
    Thanks.

    Simon,
    So do you think that there is a problem in my Query restrictions? You ask me to restrict from 0 - 12, but this period is calculated based on the SY_DATUM in a cust. exit variable. And this period is being used to pull week number. So, do I need to change the code?
    But I already have another query which is similar to this, only ready for input options are missing in the new one. The older one is working fine but the I have problem with this.
    Any more ideas?
    Thanks!!

  • Create asset-error"E003 SYST: Period 000 is not valid in financial year var

    Error during Asset Creation: E003
    AS01: Create asset was executed. During saving the asset got an error
    E003 SYST: Period 000 is not valid in financial year variant
    Following are the Depr keys assigned;
    LINA is being used for Book Depreciation
    MSTL Depreciation key is being used for ACRES, ALT MIN, ACE, E&P.
    Asset Class is Buildings

    Hello!
    I had the same problem a few month ago. There is a SAP note about this. Run the Asset Year end technical proces in ARJW. Try again your asset creation.
    Greetings,
    Stéphane

  • FGV003 - SYST: Period 000 is not valid in financial year variant K4

    Hello,
    I am getting the error below when trying to bring Period 000/2008 from our BCS cube into a basic cube.  I've run the "Transfer Global Settings" for our R/3 system but am still getting this error.  The BCS does have Period 000 Yr 2008 with FYV K4 and is showing in the master data for fiscal period.  Any ideas??
    SYST: Period 000 is not valid in financial year variant K4
    Thanks,
    Senthil

    Dear colleagues:
    The same problem is appearing to me. I am trying to run a job in background but the following error appears to me>
    SYST: Period 000 is not valid in financial year variant 36
    Do you know what I have to do to suprime the error?
    The job I am trying to run is for creating an evaluation in order to run the report S ALR 87012167
    Your Sincerely
    Leonardo López
    FI Consultant

  • SYST Period 012 is not valid in financial year variant R2 Msg no;FGV003

    Hi SAP Gurus,
    I have encountered with an error as following :
    SYST: Period 012 is not valid in financial year variant R2
    Message no. FGV003
    Our client following calendar year till December 2009.  They want to change to April to March , from April 2010 . So we need to define a shortened fiscal year for January to March 2010 for 3 months.
    One important thing is Depreciation should be calculated only for 3 months ie., from January 2010 to March 2010 for year 2010. For year 2011 u2013 April 2010 to March 2011 be calculated.
    I have done the following settings :
    Current fiscal year variant = K4, i.e. the standard variant with 12 periods (calendar year)
    -the current fiscal year must be closed on 31.12.2009
    -this change have to be done in the next month, i.e. on 01.01.2010
    -on 1.1..2010 starts the new fiscal year 2010
    -the fiscal year 2010 ends on 31.03.2010 and have 3 posting periods
    1) Create a new Fiscal Year Variant for the shortened fiscal year u2013 e.g. "R2" (OB29).
    2) R2 to be made Year Dependent. Current Period Configuration
    Month Days Period Year Shift
    1 31 1 0      
    2 28 2 0
    3 31 3 0
    4 30 4 0
    5 31 5 0
    6 30 6 0
    7 31 7 0
    8 31 8 0
    9 30 9 0
    10 31 1 +1
    11 30 2 +1
    12 31 3 +1
    3) Company Code assignment (OB37): K4 to be replaced with R2 .
    4) Controlling Area (OKKP): K4 to be replaced with R2.
    5) Fiscal Year to be shortened for Depreciation Areas in Asset Accounting customization (OAYP).
    6) Table T093C to be viewed to check whether the field XRUMPF (Shortened Fiscal Year) has been activated with u201CXu201D..(SE 11 Check Table) Done manually
    Other Problem : 1. The system calculates deprecation for period 3 ( Full year deprecation) as seen from AW01n for one asset.
    2. When I run AFAB for 2010 period 1 the error is displayed
    SYST: Period 012 is not valid in financial year variant R2
    Message no. FGV003
    Please anybody help me in this issue .
    Subbu

    Have you maintained the Year Shift Properly in OB29
    For e.g if Financial Year is from July to June, year shift will be as follows:
    Month      Days        Period       Year Shift
    1     31     7     0
    2     29     8     0
    3     31     9     0
    4     30     10     0
    5     31     11     0
    6     30     12     0
    7     31     1     +1
    8     31     2     +1
    9     30     3     +1
    10     31     4     +1
    11     30     5     +1
    12     31     6     +1
    Check also FI period and aseet periods are open through OB52 and AJAB

  • SYST: Period 012 is not valid in financial year variant V3 Message no. FGV0

    Hi!
    While I am going to create Asset it is giving me following error :
    SYST: Period 012 is not valid in financial year variant V3
    Message no. FGV003
    I checked in OB29, I have maintained 12 period,
    can you please tell me what will be the problem.
    Rakesh

    Have you maintained the Year Shift Properly in OB29
    For e.g if Financial Year is from July to June, year shift will be as follows:
    Month      Days        Period       Year Shift
    1     31     7     0
    2     29     8     0
    3     31     9     0
    4     30     10     0
    5     31     11     0
    6     30     12     0
    7     31     1     +1
    8     31     2     +1
    9     30     3     +1
    10     31     4     +1
    11     30     5     +1
    12     31     6     +1
    Check also FI period and aseet periods are open through OB52 and AJAB

  • Gaps in financial year variant periods IW

    Hi All,
    how to fill the Gaps in financial year variant periods IW. i am not able to finish these!!!
    we have 52 weeks, when i am posted i am facing the above error.
    thanks and regards
    Prathap

    Hi..
    When you go to in T.code OB29, you will find 'number of posting period' based on your posting period you change the number of posting period and maintain the numbers.
    And  your problem could be solved by going into OB29, select the Fiscal Year Variant, then click on Shortened Fiscal Year and enter the year where you get the error message. Then click on New Entries and enter 52, if for the year in question you only have 52 periods, which can absoluteley be fine, depending how the weekdays fall in a calendar year. Save and record on transport. Check if the error message you were getting still appears in your period definition screen.
    And also Please check the SAP Note 849016 - OB29: FGV556 (period gaps) incorrect.
    Hpoe it will helps
    Thanks.

Maybe you are looking for