Problem while drill down

Hi
I have a query which is based on the sales and which has the following characteristics i.e drill down is based on Region,Area,Territory, customer and material wise sales..
Intially we have to show up to customer where as material would be a free characteristics and the sales value for this should be shown.
when i look at the region wise/area wise/territory wise result it is not equal to the sum of the all the customer values but it is showing some thing which is entirely differant. so as i keep removing the drill downs the value is getting changed.
i used the option USE STANDARD AGGREGATION - TOTAL - WITH RESPECT TO MATERIAL AND CALCUALTE RESULT AS - TOTAL... to get even the customer level value rite or otherwise even that shows a differant value.

Hi,
In query how the sales value is getting calculated. Is it just a direct key figure or some calculation. There is a possibility that you are doing some calculations. For example if you find the value by dividing two key figures, then adding after dividing will give you a different result and divding after addition. To be clear,
When you drill down the result(KF3) will be the addition of divided values which is 13.
KF1 KF2 KF3(KF1/KF2)
10   2     5
15   5     3
20   4     5
But when you drill up the result(KF3) will be different.
KF1 KF2 KF3(KF1/KF2)
45   11   4.09
I think this should be your case. check this.

Similar Messages

Problem with drill down in time dimension - OBIEE 11G

Hello There,
I have a problem with drill down in time dimension. The hierarchy for time dimension is " Fiscal Year---> Fiscal Quarter---> Month(Name)--->Date". When I select a Time dimension and click results its getting opened in a Pivot table view. The problem here is, when I click the "Total" its getting drilled down to Year ---> Quarter but when I click on "+ sign next to quarter" it should drill down to month for that particular quarter for that particular year but its drilling down to month for that particular quarter for all years.
Any suggestions are much appreciated.
Thanks,
Harry.

1.) Congrats for resurrecting a year-old thread.
2.) Your answer is here: "Check the level key of the quarter level...it should include both quarter and year columns. Since a specific quarter occurs every year, quarter column alone can't be used as the level key."

Error while drilling down the data from reports

Hi friends,
I have created dimension hierarchies in rpd for drilling down the data.. While i drill down its showing no results at some level when i am clicking on the data.. but when i am clicking on the same levels column header its drilling down properly and i can view the next level for the data item which has shown no results while clicked on it.. Please help me and helps will be appreciated..

Hi,
>when i click on 2000 results displaying is no results
but when i click on the header year its showing the results with 3 for 2000.
So you are able to drill when you click on header..Go to column properties and make heading interaction to no interaction under column format,put value interaction to default and try to drill clicking on value.
in RPD i have some derived columns like month .I created month as derived column from date using logical formula and i used this derived columns as the key.. Is it a problem?No I dont think its a problem
Regards,
Srikanth

While drill down a char system going into dump

Hi,
We have changed 0COUNTRY as a navigation attr to the 0COMPANY and added to the Muti provider.
In query level initially for 0COMPANY data is paulating while trying to drill down 0COUNTRY with 0COMPANY then system is going into dump.
Thes system message;
The current application triggered a termination with a short dump.
An error occurred while communicating with the BI server.
As a result of this error, the system has been disconnected from the BI server.
Detailed description
can any one let me know the reason.
Regards,
Sharma.

Hi,
The problem is resolved in my self.
Regards,
Sharma

Problem displaying drill down STANDARD ALV for a particular record after pressing back button

I have a simple interactive ALV grid report. NOT 'OO'. It display correctly on initial execution. AT the moment, 6 records. I want it to work such that if i click record '1', a drill-down version of that ALV with only that one record clicked is displayed. This currently occurs correctly. The problem arises when i click the back button and want to click on a new record, say in the 2nd row..this new 2nd row record is not displayed. The first one is displayed again. I tried clearing and fiddling around but then the last record is displayed. I have used the 'ID' field as a 'hotspot' getting picked up by sy-tabindex. Maybe it could be that i shouldn't loop and use a work area e.g in my select statement. i'm not so sure i've looked around, and tried a few things. I can't get it right yet. My code is below:
*& Report ZALV
REPORT ZALV.
TABLES: ZCONTACT.
TYPE-POOLS: slis. "slis contains all of the ALV data types.
TYPES: BEGIN OF ty_zcontact.
         INCLUDE STRUCTURE zcontact.
TYPES: icon TYPE char4, "field holding traffic light value- adding a column to internal table to hold the traffic light
         END OF ty_zcontact.
DATA: "fieldcatALOG TYPE slis_t_fieldcat_alv WITH HEADER LINE,
       it_zcontact TYPE TABLE OF ty_zcontact,"declares an internal table of type ZCONTACT
       wa_zcontact TYPE ty_zcontact,
       gd_layout TYPE slis_layout_alv,
       gd_repid LIKE sy-repid,
       g_variant TYPE disvariant,
       gx_variant TYPE disvariant,
       g_save TYPE c VALUE 'X',
       it_fieldcat TYPE slis_t_fieldcat_alv,"declares field catalog table of line type alv
       wa_fieldcat TYPE slis_fieldcat_alv, "declares the work area of the field catalog
       it_list_top_of_page TYPE slis_t_listheader.
DATA: it_fieldcat1 TYPE slis_t_fieldcat_alv,
       wa_fieldcat1 TYPE slis_fieldcat_alv.
DATA: V_FIELD(30) TYPE C,
V_VALUE(10) TYPE C.
       "izontact TYPE TABLE OF zcontact.
        "i_logo TYPE OT.
       "ls_layout TYPE slis_layout_alv.
**Selection Screen details
*SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME.
*PARAMETERS: variant like disvariant-variant.
*SELECTION-SCREEN END OF BLOCK B1.
SELECT-OPTIONS:
age FOR wa_zcontact-age,
lastnme FOR wa_zcontact-lastname.
**Getting default variant
* AT SELECTION-SCREEN ON age.
*    SELECT SINGLE age FROM zcontact INTO wa_zcontact-age WHERE age = age.
* IF sy-subrc NE 0.
*    MESSAGE:'That age does not exist mate, Please enter another age' TYPE 'E'.
*    ENDIF.
INITIALIZATION.
*gx_variant-report = sy-repid.
*CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
*EXPORTING
* I_SAVE = G_SAVE
* CHANGING
*    CS_VARIANT = GX_VARIANT
* EXCEPTIONS
*    NOT_FOUND = 2.
*IF SY-SUBRC = 0.
* VARIANT = GX_VARIANT-VARIANT.
* ENDIF.
START-OF-SELECTION.
PERFORM DATA_RETRIEVAL.
PERFORM BUILD_FIELDCATALOG.
PERFORM DISPLAY_ALV_REPORT.
PERFORM top_of_page.
"g_repid = sy-repid.
*Fetch data from the database
FORM DATA_RETRIEVAL.
SELECT * FROM zcontact INTO TABLE it_zcontact WHERE age IN age AND lastname IN lastnme.
"assigning traffic light colour to each row based on a condition
* IF wa_zcontact-age GE 65.
*   wa_zcontact-icon = 1. "Red Traffic Light
*   ELSEIF wa_zcontact-age BETWEEN 40 AND 64.
*     wa_zcontact-icon = 2. "Yellow traffic light
*     ELSE.
*       wa_zcontact-icon = 3." Green traffic light
*       ENDIF.
*       MODIFY it_zcontact FROM wa_zcontact TRANSPORTING icon.
*       CLEAR wa_zcontact.
ENDFORM.
FORM BUILD_FIELDCATALOG.
*Build field catalog
wa_fieldcat-fieldname = 'ID'.
"wa_fieldcat-seltext_m = 'The Contact ID'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'LASTNAME'.
"wa_fieldcat-seltext_m = 'Contact Lastname'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'FIRSTNAME'.
"wa_fieldcat-seltext_m = 'Contact Firstname'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'DOB'.
"wa_fieldcat-seltext_m = 'Date Of Birth'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'TEL'.
"wa_fieldcat-seltext_m = 'Telephone Number'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'ADDRESS'.
"wa_fieldcat-seltext_m = 'The Address'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'OCCUPATION'.
"wa_fieldcat-seltext_m = 'The Occupation'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'WEIGHT'.
"wa_fieldcat-seltext_m = 'WEIGHT'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'AGE'.
"wa_fieldcat-seltext_m = 'AGE OF THE CONTACT'.
wa_fieldcat-do_sum   = 'X'.        "Display column total
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'SALARY'.
"wa_fieldcat-seltext_m = 'SALARY'.
wa_fieldcat-do_sum   = 'X'.
APPEND wa_fieldcat TO it_fieldcat.
gd_layout-lights_fieldname = 'ICON'.
ENDFORM.
FORM DISPLAY_ALV_REPORT.
gd_repid = sy-repid.
*Pass data and field catalog to ALV function module to display ALV list
   CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
     EXPORTING
       it_fieldcat            = it_fieldcat
       i_callback_program     = gd_repid
       i_callback_top_of_page = 'TOP_OF_PAGE'
       i_callback_user_command = 'USER_COMMAND'
       i_structure_name       = 'ZCONTACT'
       i_save                 = 'X'
       is_variant             = g_variant
       is_layout     = gd_layout
TABLES
       t_outtab      = it_zcontact
EXCEPTIONS
       program_error = 1
       OTHERS        = 2.
ENDFORM.
FORM top_of_page.
*ALV Header declarations
   DATA: it_listheader TYPE slis_t_listheader,
         wa_listheader TYPE slis_listheader,
         t_line like wa_listheader-info,
         ld_lines TYPE I,
         ld_linesc(10) TYPE C.
wa_listheader-typ = 'H'.
wa_listheader-info = 'Contact Details'.
APPEND wa_listheader TO it_listheader.
CLEAR wa_listheader.
wa_listheader-typ = 'S'.
wa_listheader-info = sy-repid.
wa_listheader-key = 'Program Name:'.
APPEND wa_listheader TO it_listheader.
CLEAR wa_listheader.
wa_listheader-typ = 'S'.
wa_listheader-info = sy-uname.
wa_listheader-key = 'User Name:'.
APPEND wa_listheader TO it_listheader.
CLEAR wa_listheader.
wa_listheader-typ = 'S'.
wa_listheader-key = 'Run Date :'.
CONCATENATE sy-datum+6(2)
             sy-datum+4(2)
             sy-datum(4)
             INTO wa_listheader-info
             SEPARATED BY '/'.
APPEND wa_listheader TO it_listheader.
CLEAR wa_listheader.
wa_listheader-typ = 'S'.
wa_listheader-key = 'Time :'.
CONCATENATE sy-uzeit(2)
             sy-uzeit+2(2)
             sy-uzeit+4(2)
             INTO wa_listheader-info
             SEPARATED BY ':'.
APPEND wa_listheader TO it_listheader.
CLEAR wa_listheader.
   CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
     EXPORTING
       it_list_commentary = it_listheader
       i_logo = 'KLOGO'.
ENDFORM. "top_of_page
*& Form sub_user_command
FORM USER_COMMAND USING P_UCOMM TYPE SY-UCOMM
P_SELTAB TYPE SLIS_SELFIELD.
CASE P_UCOMM.
   WHEN '&IC1'.
CASE p_seltab-fieldname.
   WHEN 'ID'.
   READ TABLE it_zcontact INTO wa_zcontact INDEX p_seltab-tabindex.
   PERFORM DATA_RETRIEVAL1.
   PERFORM BUILD_FIELDCATALOG1.
   PERFORM SECOND_GRID.
   ENDCASE.
   ENDCASE.
ENDFORM. "
FORM DATA_RETRIEVAL1.
SELECT * FROM zcontact INTO TABLE it_zcontact WHERE id EQ wa_zcontact-id.
ENDFORM.
FORM BUILD_FIELDCATALOG1.
*Build field catalog
CLEAR: wa_fieldcat, it_fieldcat.
wa_fieldcat-fieldname = 'ID'.
"wa_fieldcat-seltext_m = 'The Contact ID'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'LASTNAME'.
"wa_fieldcat-seltext_m = 'Contact Lastname'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname = 'FIRSTNAME'.
"wa_fieldcat-seltext_m = 'Contact Firstname'.
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
ENDFORM.
FORM SECOND_GRID.
   CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
     I_CALLBACK_PROGRAM = SY-REPID
     IT_FIELDCAT = IT_FIELDCAT
     i_structure_name       = 'ZCONTACT'
     i_callback_user_command = 'USER_COMMAND'
     TABLES
       T_OUTTAB = IT_ZCONTACT.
   ENDFORM.

Hi Ten Mariga,
                 I wonder why the second select Query is needed at all instead you can use
---> Not Needed
FORM DATA_RETRIEVAL1.
SELECT * FROM zcontact INTO TABLE it_zcontact WHERE id EQ wa_zcontact-id.
ENDFORM.
----> Instead you can do
   READ TABLE it_zcontact INTO wa_zcontact INDEX p_seltab-tabindex.
Append wa_zcontact to Second_table.
And you can use the Second_table to display the second ALV. The second Select Query will affect the performance too.
Cheers,
Krishnakumar B.

Javascript Problem for Drill Down Action in SSRS Report when integrated to PPS 2010

Hi all,
I have a SSRS report which is integrated to PPS 2010(Performance Point Services) and it is having a drill down action through Go to URL action(I wrote javascript:void(window.open('xxxxx')) to open drill down report in new window).
This report has 5 parameters and all are multiple valued. Drill down report is opening very well when I open the report form Report Manager for any number of parameters values selected. But when I integrate the same report is PPS and deployed to SharePoint
then it is working only for 23 parameter values selected in PPS filters. If I select more the 23 values in PPS filters then the drilldown report is not opening.
But it is working well in Chrome, I verified in IE and Mozilla, both browsers are having problem.
When I look at Error Console of Mozilla, it is showing a javascript error as "Error: uncaught exception: ReferenceError: window is not defined" but the same report is working well if I select less than 24 filter values.
Please provide me the solution
Thanks in advance

Hi Vasu,
The issue might occur due to the Microsoft security update MS11-100 which limits the maximum number of form keys, files, and JSON members to 1000 in an HTTP request. Here, I suggest that you modify the Web.config file of the SharePoint site as follows:
<appSettings>
<add key="aspnet:MaxHttpCollectionKeys" value="10000" />
</appSettings>
If the SharePoint site uses the port 80, the web.config file of the SharePoint site is located in the C:\inetpub\wwwroot\wss\VirtualDirectories\80 folder.
Reference:
An ASP.NET request that has lots of form keys, files, or JSON payload members fails with an exception
If the issue persist, please check whether there are any related errors in the Reporting Services log file which is located in <Drive>:\Program Files\Microsoft SQL Server\MSRSXX.<Instance Name>\Reporting Services\LogFiles.
Regards,
Mike Yin
TechNet Community Support

Problem with drill down on hierarchy with data on diffrent levels

Hello,
Im working on a project using oracle bi 10.1.3.4.1, and im kinda stuck with some problems.
I have a transaction table in which i have data about products, something like :
prod_id
amount1
amount2
and a product hierarchy which is something like:
prod_id
prod_name
parent_id
since bi doesnt support hierarchies, i had to faltten the hier table to somehing like this:
prod_id
lvl1_prod_id
lvl2_prod_id
lvl3_prod_id
lvl4_prod_id
and use this as my hierarchy in oracle bi. thus when i drill to lvl3, it will find all the products which are decendents of lvl3 value and group them.
the problem is, that the hier tree is not even, one product data (in transaction table) can be for lvl4 and another for lvl2. so for a lvl2 product id's in level 3 and 4 will be null.
when i try to drill to lvl 4, it takes all the rows which have the selected value in column lvl4 and group them, and if lvl 4 is null, it would sum up all the rows that have no parent at lvl4...
i hope you understand... cause it is a bit complicated..
anyway i would eventually like to add a filter of != null to the column being drilled down.
but how do i know which column is it?
i cant add a != null filter to all the columns since most if not all of them will have null in some lvl (lvl 10 or so).
one suggested solution was to make a report for each lvl with the !=null filter on the report lvl, and use navigate instead of drilldown... but that would mean i have to make 10 reports for each "real" report... a big problem to maintain.
hope i was clear enough, any suggestions?
thanks a lot!

Hi Ingo,
Thanks for your reply. If I combine two objects in one objects then I cannot use that object for drill down in my report.
I want to drill down for both Key and Text.

Changing the table name while drill down at the dashboard query

I have a DAY fact table that has about 1B rows.
The purpose of this table is to store on hand quantity for each item per day.
On the presentation layer I have a dashboard that will display average on hand qty per year and then user can drill down to quarter/month/week and then by day level to see the actual value at evey level.
Its hard to run aggregation on fly as all my 3 TEMP tablespace 32gb each filled and then I get error can not extent TEMP file.
So I thought I will do the aggregation at the database level and store the aggregated data in another table. So at first dashborad will read this new aggregated table to display qty at yearly. As soon as user drill down to quarter the dashbord should query the actual DAY fact table by filtering for specific year and quarter.
IS it possible? Can I change the table name while I drill down to lower level?
Thanks in advance.

Hi use,
Yes. This is possible in OBIEE. You need to use Action Links to have navigation between reports. The main idea is to have 2 analysis. One with your aggregated data by year (using your aggregated table), and another one with the rest of the hierarchy and data (using normal fact table)
You add an action link on this report, that can navigate to the second report. showing "the details" (in your case would be the rest of the time dimension).
Please refer to http://www.rittmanmead.com/2010/07/obiee-11gr1-action-framework-and-conditions/ for actions links.
Another way is to create 2 analysis, then go to the 2nd analysis, and filter the column year as "Is based on results of other analysis" and you select there the first analysis. In this case when you click on the year in the first analysis, this value will be passed to the second analysis so you can filter the rest of the hierarchy based on the year you clicked on the first analysis.
If helpful, assign points.
J.

Layout problem for Drill down ALV Report

Hello Everyone,
                       I have developed a ALV drill down report using the method G_GRID->SET_TABLE_FOR_FIRST_DISPLAY. The problem is what ever layout i save for the primary list 'Screen 100' is effecting my secondary list 'Screen 200'. User need to save both Screen 100 and Screen 200 layouts independently without affecting each other.
I am calling screen 100 as below,
Call metthod g_grid_100->set_table_for_first_display
Exporting
   i_Save                                     = 'A'
   is_layout                                 = ls_layout
   is_Variant                                =   ls_Variant
Changing
   it_outtab                                  = ct_poitems
   it_fieldcatalog                           = lt_fieldcat
Exceptions
   Invalid_parameter_combimation   = 1
   Program_error                            = 2
   too_many_lines                         = 3
   others                                       = 4.
Could any body suggest me a way to do this..
Thanks in advance.
Regards,
Shyam.

Hi,
Use multiple Layout structure (each alv have its own structure) .
Note the use of disvariant-log_group .
DATA: gs_disvariant_1 TYPE disvariant ,
           gs_disvariant_2 TYPE disvariant .
* Layout-Logical groups
CONSTANTS: gc_log_group_1 TYPE disvariant-log_group VALUE 'ALV1' ,
                        gc_log_group_2 TYPE disvariant-log_group VALUE 'ALV2' .
INITIALIZATION.
PERFORM at_initialization .
FORM at_initialization .
DATA: vari TYPE disvariant-variant .
PERFORM alv_variant_get_default USING gc_log_group_1 CHANGING gs_disvariant_1 vari .
PERFORM alv_variant_get_default USING gc_log_group_2 CHANGING gs_disvariant_2 vari .
ENDFORM.
FORM alv_variant_get_default
USING
    log_group TYPE disvariant-log_group
CHANGING
    disvariant TYPE disvariant
    variant    TYPE slis_vari .
DATA: ls_disvariant TYPE disvariant.
ls_disvariant-report = sy-repid .
ls_disvariant-log_group = log_group .
disvariant = ls_disvariant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      i_save     = 'A'
    CHANGING
      cs_variant = ls_disvariant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 0.
    disvariant = ls_disvariant.
    variant    = ls_disvariant-variant .
ENDIF.
ENDFORM.                    "alv_variant_get_default
Later....
   CALL METHOD gui_alv_grid_1->set_table_for_first_display
      EXPORTING
        is_layout       = wa_layout
        is_print        = wa_print
        i_save          = 'A'
        is_variant      = gs_disvariant_1
      CHANGING
        it_sort         = it_sort
        it_fieldcatalog = it_fieldcatalog
        it_outtab       = it_alv_grid_1.
CALL METHOD gui_alv_grid_2->set_table_for_first_display
      EXPORTING
        is_layout       = wa_layout
        is_print        = wa_print
        i_save          = 'A'
        is_variant      = gs_disvariant_2
      CHANGING
        it_sort         = it_sort
        it_fieldcatalog = it_fieldcatalog
        it_outtab       = it_alv_grid_2.
Regards.

Problem creating Drill-Down report

Hi,
I have problem in creating a drill-down report,got confused how to do it. this is my requirement.
The main portion that will be first displayed contains a group on match_code and has its own detail section. now when the user selects one of these match_code it should drill down to give more information about this match_code, so the Drill down should also have its own detail section that will be hide and drilldown ok.
If this the proper way to do it. I will be creating a drill down report for the first time.
Thanks,
Reena

Hello Reena,
If I understand your situation correctly you have a group on match_code and a details and b section. You want the Group Header and Details a sections to appear on the first "page" or drilldowngrouplevel 0. When the user drills down you want the Details b section to appear.
You can do that using the drilldowngrouplevel function.
Set the details b section to suppress when drilldowngrouplevel = 0, this section will only appear after drilldown.
I am not sure if you still want the details a or group sections to appear after drilldown, if you do then there is no need for conditional suppression. If you don't then use a conditional suppression formula for those sections of drilldowngrouplevel <> 0

Problem in Drill down the PPT produced by Xcelsius

I usually prepare the PPT using Xcelsius s/w. That PPT can be drilled down in my office system but it could not drillled down in my client system. This problem is for this month. In the past i didnt face this issue.
When i try to drill down its giving an error message as " Some controls cant be activated in ur system"
Can anyone please help ?

I've had a similar problem going back and forth between systems with Office 2003 and Office 2007 loaded on them. If the file is viewed from an Office 2003 machine the next time it's opened on a 2007 machine it crashes. I have reinsert the chart each time. I'd love to stop doing this!

Error while Drilling down across sheets

Hi ,
I am using the new BI 7.0 Bex Analyzer as forntend to my BI 7.0.
While navigating in BI Bex Analyzer, when I select the the drill down accross sheet from the context menu of any characteristics, i get an error message as follows.
"*A Critical program error occurred. The program has to be clos. Please refer the trace for furhter inforamtion*."
My SAP GUI version is 7.10 and the patch level 5.0
Can any body suggest some solution on this.
Thanks in advance.
Nilesh Labde

I know it is too late to reply back on this error.
However, the query which you have already saved, You save it with a different technical name & then execute it, it works.
It worked for me.
Thanks,
Pradip.

Transaction Variant related problem in Drill Down working

Dear Sir,
We had a business requirement that in CO02 transaction users should now be allowed to change the Material Component quantity . To address this requirement we had created a Transaction Variant YCO02 and it is working in normal course .
However we face problem in certain Drill-Down working . E.g in Tcode COOIS , when users double click a Production Order it goes to CO02 and user has no authorization for CO02 . Insteat of CO02 , user has authorization for YCO02 .
Pl guide us as how can we resolve this problem.
With Thanks and Rgds
Sonia Agarwal

Dear Mr KrishnamurthyDSS
Thanks for reply .
Pl clarify that can we make Transaction Variant with the same name i.e CO02 .
If Transaction Variant and Original Transaction have the same name (i.e CO02) then how to control the authorization , because we want to give authorization only for Transaction Variant one and not for base transaction .
Kindly help me pl .
Rgds
Sonia Agarwal

Problem with Drill down using Pie chart

Hi all,
I have a dashboard which displays sales according to product category in which I'm using combo box for category.
Based upon the selection the corresponding products are displayed in the Pie chart and when I click a particular
product its total sales value should be displayed in a Guage.
The problem is if for one category there are 10 products the pie chart is showing only 5 labels if drill down option is checked
and if its not then its showing all the products......
What could it be ??
Thanks
John

Hi John
Is this fixed now?
Regards
[Charles|http://www.reportex.co.uk/xc_dataload.html]

Problem on Drill Down

Hi Guru,
In the Opportunity summary report, I have where condition which is Created Date is GREATER THAN 04/09/2008 and when I click data in column 'Report to' to drill down,It'll show Opportunity Detail report.My problem is when it show Opportunity Detail report,It get all the reocrds from the system which include Created Date is LESS THAN 04/09/2008.I already added where condition Created Date is greater than 04/09/2008 in both Opportunit Summary and Opportunity Detail report
Any Idea?Please advice.
Pitiporn

Finally I sovled it by changing the criteria of Created Date from "Create Date >= ... " and "Created Date <= ..." to "Created Date between ... and ..."

Problem while drill down

Similar Messages

Maybe you are looking for