Aggregation level control?

Hi all,
I am having a bit of an issue trying to use Lumira to analyze the CMS (healthcare procedure Medicare charge data) recently released by the US government. The data has the following structure:
Provider ID
Procedure ID
Average payment for this provider & procedure
Number of this procedure billed by this provider
So, in order to figure out the total paid out by Medicare, I would need to create a custom measure taking "Average payment for this provider & procedure" * "Number of this procedure billed by this provider". This works fine if I use a table view and include Provider ID & Procedure ID in the drill-down. But as soon as I remove Provider ID and aggregation kicks in, it goes haywire. We end up with the aggregated "Average payment for this provider & procedure" across all providers multiplied by the aggregated "Number of this procedure billed by this provider" across all providers. Using SUM aggregation on these measures, that clearly results in very very large (and incorrect) number.
I have tried setting the aggregation type of the 2 measures to "None", but that seems to result in the custom measure not being aggregated either.
I would need to get Lumira to calculate the custom measure before aggregation and then aggregate the result. Is that possible?
Thanks,
Ethan

Update update: I got a Twitter suggestion to try creating a calculated dimension and then create a measure based on that. (Twitter / ccpg04: @esjewett the measures also ...) I *believe* this actually gives the correct result! However, it is extremely slow and results in application errors when I display the tabular view to try to verify the results. In any case, maybe this will be helpful for people with smaller data sets who are looking for this type of functionality in the future.

Similar Messages

Query Designer not working with Aggregation Levels on BW 7.30

Hi,
Every time I try to create a query on top of an Aggregation Level that I created with the new ABAP based RSPLAN transaction.
If somebody can help me out I'd appreciate it.
By the way, we don't have the Java stack, but we are currently using BO4's JVM as we're on ramp up.
This is the error that I get when trying to create the query:
QD Revision 667
ERROR ID: E-ONGUIUNHANDLEDEXCEPTION
And this is the error log:
1:42:13 p.m..319: Info: Query Designer Start. Revision: 667
QDbCommandBase::Execute - Standard View
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - Documents
QDbCommandBase::Execute - Where-Used List
QDbCommandBase::Execute - Properties
QDbCommandBase::Execute - Properties
QDbCommandBase::Execute - Messages
QDbCommandManager::ItemClickedHandler - Bar clicked: NewQuery
QDbCommandBase::Execute - New...
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - Documents
QDbCommandBase::Execute - Where-Used List
QDbCommandBase::Execute - Messages
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Properties
-EXCEPTION-START- 1:42:52 p.m..416: TRACE EXCEPTION ---
Exception Name: TargetInvocationException
Exception Message: Exception has been thrown by the target of an invocation.
Exception    at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.PropertyGet(Object iPropertySource, String iPropertyName)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueGetDefault(Object iPropertySource)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.pValueDefault()
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueDefault()
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueResolved()
   at com.sap.bi.et.QueryDesigner.QDpPropertyMulti.SetFirstProperty(QDpPropertyBase iProperty)
   at com.sap.bi.et.QueryDesigner.QDpPropertyMulti.Add(QDpPropertyBase iProperty)
   at com.sap.bi.et.QueryDesigner.QDuPropPageQuery.ToDialog()
   at com.sap.bi.et.QueryDesigner.QDuPropPageBase.ToDialogCore()
   at com.sap.bi.et.QueryDesigner.QDuPropPageBase.set_CommandContext(QDbCommandContext Value)
   at com.sap.bi.et.QueryDesigner.QDuPropPages.EnablePage()
   at com.sap.bi.et.QueryDesigner.QDuPropPages.ContextChangedHandler(Object iSender, QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.ContextChangedEventHandler.Invoke(Object iSender, QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.OnContextChanged(QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CalculateContext(QDcView iViews, QDeAreaType iAreaType)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CalculateContext(QDbElement iElement)
   at com.sap.bi.et.QueryDesigner.QDbCommandPropertiesQuery.ExecuteCommand()
   at com.sap.bi.et.QueryDesigner.QDbCommandBase.Execute()
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CommandExecute(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.InitialCommandExecute(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.DoExecuteCommandInternal()
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.DoExecuteCommand(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.ItemClickedHandler(Object sender, BarItemClickedEventArgs args)
   at com.sap.bi.et.QueryDesigner.QDdEventDispatcher.MenuItemClickedHandler(Object iSender, BarItemClickedEventArgs iE)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarManager.OnItemClicked(BarItemClickedEventArgs args)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarItem.OnItemClicked(EventArgs args)
   at com.sap.bi.et.QueryDesigner.QDiBarItem.OnItemClicked(EventArgs args)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarItem.PerformClick()
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarRenderer.OnMouseUp(MouseEventArgs e)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarControlInternal.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarControlInternal.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Full Stack:   at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
   at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.OnGuiUnhandledException(Object iSender, ThreadExceptionEventArgs iEventArgs)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDbQueryDesigner.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDStarter.QDStartup.Main()
-EXCEPTION-END----
-CALLING-FROM- 1:42:52 p.m..416: TRACE EXCEPTION ---
   at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
   at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.OnGuiUnhandledException(Object iSender, ThreadExceptionEventArgs iEventArgs)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDbQueryDesigner.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDStarter.QDStartup.Main()

Hi,
it seems that you are already using the most recent query designer version. Is your SAPGUI also the most recent version? If yes, open a OSS ticket. If not reinstall the SAPGUI and the BEx tools. I am also working with this query desinger version and I don't have this kind of problem.
Regards,
Gregor

Error : Reading from Aggregation Level not permitted

Hello Gurus,
Could somebody please give some help or advice regarding this?
I have a multiprovider on a regular cube and an aggregation level, for some reason the multicube gives me the following error message when I try to display data using listcube.
Reading from Aggregation Level is not permitted
Message no. RSPLS801
Also the Query on the multicube does not display data for any of the KF's in the Agg Level but when I create a query on the Agg level itself it is fine.
Any suggestions?
Thanks.
Swaroop.
Edited by: Swaroop Chandra on Dec 10, 2009 7:29 PM

Hi,
transaction LISTCUBE does not support all InfoProviders, e.g. aggregation level are not supported. LISTCUBE is a 'low level' to read data from the BW persistence layer, e.g. InfoCubes. Since aggregation level always read transaction data via the so called planning buffer and the planning buffer technically is a special OLAP query LISTCUBE does not support aggregation level.
Regards,
Gregor

Setting aggregation level in POSDM

Hi experts
I would like to consult from you regarding SAP standard function on aggregation level to be set in POSDM.
The requirement I get is to aggregate sales in the level of day/store/article/promotion ID.
Are there any solution to this in terms of configuration?
Really appreciate your help.
BR
Dominic

Hi,
Aggregation Method plays a key role in terms of One-Step Processing Tasks.For eg.,if you want to Generate WPUTAB Idoc and there is an aggregation Method code which is specifically available to have the aggregation done based on the means of payment.
SImilarly you can have aggregation method based on material,by sales item and qualifier and also with material&Conditions combination.
You can see the difference when you choose 0000 - Code for Aggregation method for Task code 0013 - Generate Idoc WPUTAB and process.Later on change the Code for Aggregation Method to 0005 and you can see if in POS Workbench also.
NOTE : You can also custom specific Aggregation Method - for eg, Aggregation should be done based on transaction type/sales item type etc.
Thanks and Regards,
Ramesh D

Aggregation level

Dear Experts
I have 2 restricted key figures both set with aggregation level Total with reference to a characteristic. both are with reference to different characteristics. KF 1 is a formula containing KF 2 .
So, the referred characteristics are Char 1 for KF 1 and Char 2 for KF 2.
In the rows, if I drill down further by chars other than char 1 and char 2, how will the KF 1 and KF 2 values be affected?
Am i right to say drill down will not affect the aggregation behavior?
What determines which chars to be referred to when setting aggregation level in the KF?
Thanks in advance.
regards
Pascal

Hi Pascal,
Can i ask you to paste your report requirement so that we can visualize in a better way and guide you on the same.
Regards,
AL

When i try to create Filter on aggregation level the system gives me error

Hi BI Guru's,
I am facing a problem BI - IP .
When i try to create Filter on aggregation level the system gives me follwoing error.
"Authorization check of component failed"
"You do not have authorisation for Add or Create".
"Could not create Filter "
Please let me know if have any solution for this
Thanks & Regards,
Nilesh Labde

Here are list of auth objects for BI IP
S_RS_ALVL --> aggregation levels
S_RS_PLSE -->planning functions
S_RS_PLSQ-->planning sequences
S_RS_PLST-->planning function types
S_RS_PLENQ-->maintain and display lock settings
Authorization templates for Integrated planning are
S_RS_PL_ADMIN
S_RS_PL_PLANNER
S_RS_PL_PLANMOD_D----
> Planning modeler(Dev System)
A portal role is required to use the planning modeler.

Aggregation level activation problem

Hello experts.
I have a problem with activation of aggregation level with abap program. When I debug the program i saw error like 'BWTK907074 BEX report is unavailable.' . Its a request code. Now i dont know how to pass this step and activate aggregation level.
Best Regards
Bilal
"If it is Nescessary my code is:
REPORT z_activate_obj.
DATA stat TYPE rsobjstat.
DATA cube TYPE rsinfocube.
TYPE-POOLS rsds.
DATA : rspar_tab TYPE TABLE OF rsparams ,
         rspar_line LIKE LINE OF rspar_tab.
DATA zaglevel LIKE STANDARD TABLE OF rspls_alvl.
DATA wa1 LIKE LINE OF zaglevel .
ZFI_M01
SELECT SINGLE infocube objstat
INTO (cube,stat)
FROM rsdcube
WHERE objvers EQ 'A'.
IF stat NE 'ACT'.
PERFORM act_mpro USING cube.
ENDIF.
SELECT *
INTO TABLE zaglevel
FROM rspls_alvl
WHERE objvers EQ 'A'
AND objstat EQ 'INA'.
LOOP AT zaglevel INTO wa1.
PERFORM act_agglevel USING wa1-aggrlevel.
ENDLOOP.
*&      Form ACT_mpro
FORM act_mpro USING    p_cube.
rspar_line-selname = 'P_AREA'.
rspar_line-kind    = 'P'.
rspar_line-sign    = 'I'.
rspar_line-option = 'EQ'.
rspar_line-low     = 'X'.
APPEND rspar_line TO rspar_tab.
rspar_line-selname = 'SO_MPRO'.
rspar_line-kind    = 'S'.
rspar_line-sign    = 'I'.
rspar_line-option = 'EQ'.
rspar_line-low     = p_cube.
APPEND rspar_line TO rspar_tab.
DATA: number           TYPE tbtcjob-jobcount,
        name             TYPE tbtcjob-jobname ,
        print_parameters TYPE pri_params.
CONCATENATE 'Activate' p_cube INTO name SEPARATED BY space.
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      jobname          = name
    IMPORTING
      jobcount         = number
    EXCEPTIONS
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      OTHERS           = 4.
SUBMIT rsdg_mpro_activate WITH SELECTION-TABLE rspar_tab
                            VIA JOB name NUMBER number
                            AND RETURN.
IF sy-subrc = 0.
    CALL FUNCTION 'JOB_CLOSE'
      EXPORTING
        jobcount             = number
        jobname              = name
        strtimmed            = 'X'
      EXCEPTIONS
        cant_start_immediate = 1
        invalid_startdate    = 2
        jobname_missing      = 3
        job_close_failed     = 4
        job_nosteps          = 5
        job_notex            = 6
        lock_failed          = 7
        OTHERS               = 8.
ENDIF.
ENDFORM.                    " ACT
*&      Form ACT_AGGLEVEL
FORM act_agglevel USING    p_agglevel.
DATA: l_t_return TYPE STANDARD TABLE OF bapiret2,
        l_s_return TYPE bapiret2,
        l_subrc TYPE sysubrc,
l_t_alvl TYPE STANDARD TABLE OF rspls_alvl,
l_s_alvl TYPE rspls_alvl,
l_t_alvl_iobj TYPE STANDARD TABLE OF rspls_s_rfc_alvl_iobj.
data zreturn like LINE OF l_t_return.
CALL FUNCTION 'RSPLS_ALVL_CHANGE'
    EXPORTING
      i_aggrlevel    = p_agglevel
    IMPORTING
      e_subrc        = l_subrc
    TABLES
      i_tk_alvl_iobj = l_t_alvl_iobj
      e_tk_return    = l_t_return.
CHECK l_subrc = 0.
CALL FUNCTION 'RSPLS_ALVL_CHECK'
    EXPORTING
      i_aggrlevel = p_agglevel
      i_objvers   = 'A'
    IMPORTING
      e_subrc     = l_subrc
    TABLES
      e_tk_return = l_t_return.
CHECK l_subrc = 0.
CALL FUNCTION 'RSPLS_ALVL_ACTIVATE'
    EXPORTING
      i_aggrlevel = p_agglevel
    IMPORTING
      e_subrc     = l_subrc
    TABLES
      e_tk_return = l_t_return.
loop at l_t_return into zreturn.
WRITE zreturn-message.
ENDLOOP.
ENDFORM.                    " ACT_AGGLEVEL

Hi,
Check the link and manupulate your code accordingly..
[Activate all the Aggregation level of underlying multi provider;
Thanks
Pratyush

Aggregation level doesnt support non-cumulative kf

hello
IP planer generates an error "Infoobject 0AMOUNT (version A) is not compunded" when I include non-cumulative kf into aggregation level of infoprovider.
KF ZAMOUNT is non-cumulative and depends on 0AMOUNT. Both kf are active.
I need non-cumulative kf just for informative purposes, i dont want to plan with this kf.
Does anyone know is it possible to use non-cumulative kf in aggregation level of multicube?

Hi,
no non-kumulative key figures are not supported in aggregation levels.
But one can use a MultiProvider on the cube with the non-cumulative key figure. Create an aggregation level for the objects you want to plan and use this aggregation level also in the MultiProvider. Then you can integrate the 'plan objects' and the non-cumulative key figure in a query defined on the MultiProvider.
Regards,
Gregor

No zoom level controls on second monitor!

I use a second monitor to display a loupe view of the photo I have selected in the grid view, which is on the first monitor. I have always had the zoom-level controls (Fit, Fill, etc.) at the bottom of the loupe display on the second moitor, until I replaced my first monitor this week. Everything else is still the same, but I no longer have the zoom controls on the second monitor. This means that I cannot change the zoom levels that are availabel to me. I either have Fit or 100% zoom. Without the zoom controls on the second monitor I can't change the settings. Does anyone know how to get the zoom controls back (or why they might have disappeared)?
Thanks for any help.

Never mind. I found the problem (the second monitor was in full-screen mode). Nothing
to see here. Keep moving.

How data update when there is two planning cubes in one aggregation level

If we have two planning cubes and a multi-cube includes these two planning cubes.
then we have the aggregation level defined based on this multi-cube.
if the characteristics and key figures defined in aggregation level all are included in these two planning cubes. When we plan the data with plan query based on this aggregation level, which plan cube will be updated with plan data, or both of them?

HI Wang,
yes as Bindu said you need to restrict the layout based on the infoprovider.
Lets assume that we have a multi provider M1 and it has two planning cubes cube1 and cube1.
in case u develop a layout for updating cube 1 give the restriction in the filter section as infoprovider = cube1.
or the vice versa.
Else ur layout must input values for both the cubes simultaneously, then in that case create two restricted KF with each having a restriction for cube1 and cube 2.
so wen the user enters value for the first restricted KF it will get saved in cube1 and wen he enters value for the second restricted KF it will gets saved in cube2.
This is how it works. Guess this was useful to u.
Regards.
Shafi.

Planning level to be added in aggregation level

Hi,
Currently my aggregation level has the following elements:
1. Plant
2. Sales Group
3. Cutomer
Now I need to change from Plant to Customer Plant. Following are my queries on the same:
1. Can I add customer plant in addition to plant in the aggregation level?
2. Hence forth I would be doing planning on customer plant level, will that be an issue?
3. Will there be any issue with the historical data already planned at plant level?
Kindly help me with the above issue.
Regards,
Bhushan

Hi Bhushan,
1. You can add freely your additional characteristic and your model will technically keep on working ,of course you will need to adjust the filters and functions to the new aggregation level of data
2. Again you will need to adjust your business logic in all components of the aggregation level (filters ,functions)
3.Historical data is apearing currently under Customer Plant = '#' ,you should consider reposting historical data in order to align current with historical data
Regards,
Eitan.

Customer Exit in query on aggregation level

Hi,
I try to have variables filled with a customer exit.
The coding of the customer exit is correct, this have been tested in queries on multiproviders.
Unfortunately it is not working when these variables are used on level of aggregation levels.
What I would like to achieve:
We have some planning queries on aggregation levels. Different users can plan on the same query (and aggregation level), but not for the same set of data. Therefore the query should be restricted to the authorized values. Unfortunately we can not switch to the new authorization concept (analysis authorizations) yet, but we already need this functionality very soon.
The customer exits are the only possible option. Unfortunately it seems that the customer exits are not being executed when the variables are used in queries on aggregation levels.
The variables are not ready for input and should be filled in I_STEP = 2
Is this normal? If so, is there a work around?
Thanks in advance for quick replies!
Kind regards,
Bart

Hi,
You can debug your query by putting the break-point in your exit code and execute the query in RSRT. This way you will be able to find if your customer exit is actually being called or not. If it is being called then there can be some logical problem with your code due to which the variable values are not getting populated.
Regards,
Deepti

Aggregation level includes filter objects...

Hi,
We are using a BO universe on top of a BEX query to create WebI reports.
We now run into the following problem when filtering on a certain characteristic in the BO query.
The result set of rows is limited to the correct values, but not aggregated up to the requested aggregation level. The problem exists whether the key figure is defined as having an aggregation to be database delegated or sum.
In the query results we see the number of rows being pulled back is too high, the results displayed are correct (because aggregated by WebI). In the example below we selected three stores, but not store as a result object.
*** Query Name:Query 1 ***
** Query Properties:
Universe:Retail Sales and Stock
Last Refresh Date:9/2/10 2:29 PM
Last Execution Duration: 33
Number of rows: 4,947
Retrieve Duplicate Row: ON
** Query Definition:
Result Objects: Style Code, NSLS @ PCS
Filters ( Only RMS Billing Documents Infoprovider
AND Given Legacy Division Set
AND Given Currency Conversion Type
AND Store Key In List { 1001; 1002; 1003 }
AND NSLS @ PCS Not Equal 0
We cannot attach a document, but the actual amount of rows should have been 2,856,
the number of different style in these 3 stores.
When we include the store object in the results, we can see the number of rows stays the same (proof that it did indeed return rows on a store level and not aggregated upt to the style code...
*** Query Name:Query 1 ***
** Query Properties:
Universe:Retail Sales and Stock
Last Refresh Date:9/2/10 2:09 PM
Last Execution Duration: 13
Number of rows: 4,947
Retrieve Duplicate Row: ON
** Query Definition:
Result Objects: Style Code, Store Key, NSLS @ PCS
Filters ( Only RMS Billing Documents Infoprovider
AND Given Legacy Division Set
AND Given Currency Conversion Type
AND Store Key In List { 1001; 1002; 1003 }
AND NSLS @ PCS Not Equal 0
Is this behaviour fixed in any fix pack? Or did noone address this problem?
The problem becomes a real problem when the user wants to select everything u/i a certain date.
The number of rows are then pulled back on a style/store/day combination and easily reached 100.000 rows.
Thanks for any insight you can give on this,
Marianne

Hi Rik,
Thanks for at least trying
I didn't try this before, so I just did, despite the fact that the aggregation level only has something to do with the way data aggregates within webi. (I'm that desperate)
No difference, other then the fact that I now get #MULTIVALUE in the cells with multiple underlying rows.
Anyone else?
Marianne

Aggregation Level in not prepared to run on HANA

Hello Experts,
I've the following system configuration:
CPMBPC 810: SP 0001
POASBC 100_731: SP 0005
HANABPC 810: SP 0001
Hence we've PAK and BPC license too for working with PAK.
Now, I've created an Aggregation level: ZTPM_AG01 on top of a Multiprovider which encompasses 2 real time and 1 standard cube. By default all three are HANA Optimized.
Then why I'm getting a red traffic light for both the aggregation level 'ZTPM_AG01' as well as the MultiProvider as shown below:
I've gone through below link:
How to Check whether a Planning Function or a Disaggregation in PAK is executed in Memory
and noted that we were in alignment for the most of the below points except the one in bold:
Is note 1637148 implemented?
Is the system switched to PAK (see note 1637199)?
Is the InfoCube HANA optimized?
Is the InfoCube/DataStore Object entered in the list of HANA optimized InfoCubes?
Is a characteristic relationship type exit or type hierarchy used in the InfoProvider?
Is a data slice type Exit used in the InfoProvider?
Is any virtual object used (virtual InfoCube, master data with own read class etc.)?
Is a key figure type TIMS or DATS used (input enabled)?
Is the user parameter RSPLS_HDB_SUPPORT set to ‘HDB_ON’ (if necessary, see note 1637199)?
Global emergency exit switch is not set using report SAP_RSADMIN_MAINTAIN with parameter object RSPLS_HDB_PROCESSING_OFF with blank or empty value.
I've made user parameters RSPLS_HDB_SUPPORT to HDB_ON.
Can you please let me know, what am I missing here ?
Thanks & regards,
Jomy

Dear DonB evis!
I had exactly the same problem with lightroom as you:
"C:\Program Files\Adobe Photoshop Lightroom\lightroom.exe
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem."
Event log indicates, that "Component identity found in manifest [inside Lightroom - Microsoft.VC80.MFC.MANIFEST] does not match the identity of the component requested".
The theory is that files called manifests tell the system loader that application X (here: lightroom.exe) depend on assembly Y (Microsoft.VC80.MFC). This very CRT assembly is a shared one, and it resides in C:\Windows\WinSxS\.
SO this is a problem of your Windows not Lightroom, which refers to windows shared element which cannot be found (due to .NET installation and policies mess).
Side by side assemblies use publisher configuration files (POLICIES) to globally redirect applications and assemblies from using one version of a side-by-side assembly to another version of the same assembly.
There is a problem on certain machines caused by Windows SP1 to .NET 2.0 which causes problems messing with policies and redirecting applications from using proper shared assemblies.
After installing SP1 (which installs with Windows Update) to .NET 2.0 on those machines it was impossible to reinstall .NET unless you delete the policies inside the C:\Windows\WinSxS\Policies\ folder (I do not know exactly why, but it was my case and several other people too).
In my previous post I described you the process I did two days ago on my system (WinXP Pro with SP2) and after that lightroom start to run.
I am sorry you are experiencing such difficulties, but I would not post my way of solving the problem if I did not test it successfully on my system.
Hope you manage to solve it.
Best regards.

Problems creating aggregation levels over a Multiprovider

Hi experts,
When I create a aggregation level over a multiprovider the system returns an error " Infoprovider XX cannot be used for definition". I have read other threads with the same question and its solutions. I have checked my system and all is correct. The multiprovider has linked five infoproviders, one as real time.
Any Idea?
Please, it is very urgent to solve this.
Thanks a lot in advance.

Hi Mayank and Ravi,
I have checked the identification of chars and kf. The realtime cube has five chars and a kf. All of them are assigned with all cubes witch are linked with the multiprovider.
I have tried by removing the realtime cube and the system shows the same error message. I have also tried by reactivating the cubes and multicube.
Any idea?
Thanks.

Aggregation level control?

Similar Messages

Maybe you are looking for