Characteristic of selection not part of aggregation level

I am receiving the following message in my log after running a background job for my forecast.  My selection profile has an exclusion so I did not add the Characteristic to the Aggregation Level.  I want to run the forecast at the higher level of aggregation excluding these two criteria (Sales Regions).  If I include it in the Aggregation Level it runs the forecast at the individual Sales Regions.  Can an expert clarify this is ok and I am not running the forecast at the higher level including the two Sales Regions. 
Thanks.

Thanks Guarav, please see my comment below.
Ok, I believe I have resolved the issue.  I am going to summarize my previous process. 
1.Created a Master Profile (forecast) for each Strategy I wanted to test.  I would use the same Master Profile even if I changed the Parameters in the Univariate Profile. 
2.Used the same forecast Activity, changing each time I changed the Strategy.  Planning Job would remain the same.
3.By creating a New Activity & New Planning Job my forecast model appears to be running correctly.  The only items I continue to select in the Planning Job Aggregation Level are SourceSystem and Product.
It Appears the best methodology is to set up a separate Master Profile/Univariate Profile for each Strategy & set of Parameters.  A separate Activity & Planning Job should also be set up for each Strategy & set of Parameters.  This would also have to be done in order to add to an overnight (monthly) Process Chain.

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

  • Planning Job Aggregation Level

    I am running a Background Job (Univariate Forecast Profile).  My Selection Profile excludes 3 single values can I still run the model at this level of aggregation "total" excluding those 3 single values.  Running the model at the Total should be more accurate than running the model for 22 single values and summing the forecast.  For some reason a forecast is no longer being produced?  I do get the warning Characteristic of selection not part of aggregation level.  I didn't notice any problems the last couple months. 
    Thanks, experts!

    Thanks Guarav, please see my comment below.
    Ok, I believe I have resolved the issue.  I am going to summarize my previous process. 
    1.Created a Master Profile (forecast) for each Strategy I wanted to test.  I would use the same Master Profile even if I changed the Parameters in the Univariate Profile. 
    2.Used the same forecast Activity, changing each time I changed the Strategy.  Planning Job would remain the same.
    3.By creating a New Activity & New Planning Job my forecast model appears to be running correctly.  The only items I continue to select in the Planning Job Aggregation Level are SourceSystem and Product.
    It Appears the best methodology is to set up a separate Master Profile/Univariate Profile for each Strategy & set of Parameters.  A separate Activity & Planning Job should also be set up for each Strategy & set of Parameters.  This would also have to be done in order to add to an overnight (monthly) Process Chain.

  • Forecast, selection and aggregation level

    Hi gourous,
    I'm working on APO 4.1.
    Forecast runs in background as following:
    - Aggregation level: Sales organization / distribution channel / division / product size.
    All these four characteristics are part of the characteristic combination.
    - Selection ID is defined on: sales organisation / sales statut / standard - promo indicator / product size
    Sales statut and standard - promo indicator are attributes of the characteristic material (sales view).
    However there is forecasts on promo SKUs even if they aren't  in the selection ID (standard - promo indicator as value egal to standard in the selection ID)
    My question is: how is it possible? is there a conflict between the selection ID and the aggregation level?
    I check the assignment of forecast profiles and there is no profil assigned on the ID selection.
    Thank you for your return.
    Sophie

    Hi Datta,
    Let me go further with my data model first.
    Selection criteria:
    Sales organisation = CZ01
    Sales statut = active
    Standard / promo = standard
    Product size = A, B, C, D, E
    Aggregation level:
    Sales organisation
    Distribution chanel
    Division
    Product size
    What I understand of the 546079 OSS notes:
    Distribution chanel and division are to be out of the aggregation level. Moreover in my case, there is only one value possible.
    What I understand of the 374681 OSS notes:
    The system searches for all the characteristics of the sales organisation * product size (of the aggregation level) that match the selection. At that step, APO should select only active and standard skus for CZ01 sales organisation and A, B, C, D, E product size. Afterwards the system searches for all the characteristics combinations that fit the chosen aggregation level and aggregates its values.
    My question is: does APO disaggregate on the ID selection?
    The characteristic combination I see in the job log are those defined on the aggregated level taking into account the sales organisation and product size restriction defined in the selection ID.
    Thank you for your return.

  • Create entry for characteristic which is not in aggregation layer

    Dear all,
    I have an realtime cube with an aggregation layer on top for a planning application. For some reason I can not include one characterisctic in the aggregation layer.
    Although I need a value for this characteristic, e.g. after each saving within the planning application.
    Is there a way to create entries (constant) for specific characteristic which are not part in the aggregation layer.
    We are running NW 7.1.
    Any help would be great.
    Best regards,
    Stefan from Munich/Germany

    Hi,
       As tilak has mentioned above, you can use characteristic relationships to derive a characteristic data based on another charactereistic value.
    The following are thr things are the things to be kept in mind whn using characteristic relationships,
    1. Load the master data properly for the required characteristics if you are using relationship of type, either attribute or   hierarchy.
    2. If you want to derive rthe data based on your own requirements, use  relationship of type DSO or Exit.
    3. Make sure that the particular characteristic relationship after creation, inorder to use it in your planning application.
    For more details, you can refer to the link, [Re: IP: Characteristic derivation during Transfer values|Re: IP: Characteristic derivation during Transfer values]
    Rergards,
    Balajee.

  • Aggregation level is not getting activated

    Hello Experts,
    I am working for Integrated Planning(BI 7.0). I have created one Aggregation level and i have transported from Dev to Qty.
    After transporting i need to do some changes in Aggregation Level in Dev.
    Problem:
    When i am trying to change aggregation level in Dev, It is showing below errors.
    1) choose an existing request
    2) BEx transport request is not available or not suitable
    3) Aggregation level is locked by the change and Transport organizer.
    Please help me to solve this issue.
    Best Regards,
    Ranganath

    Hi,
    Please check if the respective aggregation level is assigned to
    a transportable development class. If so, there must be a BEx
    request in /nRSA1 created for further processing in this regard either.
    The reported message is raised when aggregation level is not assigned
    to Bex Transport request. In this case, maybe creating a new transport
    request will be helpful.
    Please check the following URLs.
    http://help.sap.com/saphelp_nw70/helpdata/en/43/c6ba9859c4332ee10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/38/5ee7377a98c17fe10000009b38f842/content.htm
    Regards,
    Amit

  • IP - Aggregation Level not showing in Query Designer as infoprovider

    Hi guys
    I just started implementing Integragted Planning at a new client. I created an aggregation level to build my input ready query. However this aggregation level is not available as an inprovider in the Query Designer nor is it available under the infocube in RSA1 on which the aggregation has been defined.
    Any suggestions?
    Thanks for your help.
    Ameya Kulkarni

    Hi Mayank
    Good point. But I could not see the aggregation level whatsoever in RSA1. The aggregation level is consistent and activated but does not show in the query designer.
    I was wondering if there is some configuration that I have to do to get the aggregation level available in the query desginer.
    Please let me know.
    Thanks,
    Ameya Kulkarni

  • 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

  • Cross-Aggregation-Level Selection Evaluation indicator

    Hi,
              Can any one explain me the meaning of the below statements in the two paragraphs. This is for "Cross-Aggregation-Level Selection Evaluation indicator" in alert monitor.
    If the Cross-Aggregation-Level Selection Evaluation indicator has not been set in the SDP alert profile, only planning objects that exactly correspond to the aggregation level defined in the selection are taken into account. This means that the planning objects contain exactly the characteristics of the aggregation level. Planning objects that have additional characteristics are not taken into account.
    If however, the Cross-Aggregation-Level Selection Evaluation indicator is not set in the SDP alert profile, the system takes into account not only planning objects that exactly correspond to the aggregation level of the selection but also those containing additional characteristics.
    Example
    If you use a selection with the aggregation level 'Product' in the SDP alert profile and set the Cross-Aggregation-Level Selection Evaluation indicator, alerts will be issued not only for this product but for the relevant location products.
    Thank you.

    Hi Datta,
    Let me go further with my data model first.
    Selection criteria:
    Sales organisation = CZ01
    Sales statut = active
    Standard / promo = standard
    Product size = A, B, C, D, E
    Aggregation level:
    Sales organisation
    Distribution chanel
    Division
    Product size
    What I understand of the 546079 OSS notes:
    Distribution chanel and division are to be out of the aggregation level. Moreover in my case, there is only one value possible.
    What I understand of the 374681 OSS notes:
    The system searches for all the characteristics of the sales organisation * product size (of the aggregation level) that match the selection. At that step, APO should select only active and standard skus for CZ01 sales organisation and A, B, C, D, E product size. Afterwards the system searches for all the characteristics combinations that fit the chosen aggregation level and aggregates its values.
    My question is: does APO disaggregate on the ID selection?
    The characteristic combination I see in the job log are those defined on the aggregated level taking into account the sales organisation and product size restriction defined in the selection ID.
    Thank you for your return.

  • Can a CR work only for one aggregation level and not other ?

    Hi Experts,
    I have a real time infocube (RTIC) over which there is a multiprovider, on top of which I have built 2 aggregation levels.
    There are sequence of 2 characteristic relationships (CR's based on exit class) defined for the same RTIC.
    Is it possible that the CR's be functional for one aggregation level and not in case of second aggregation level ?
    Thanks and Regards,
    Pankaj

    Additionally let me explain the scenario in more detail:
    The difference between 2 mentioned aggr levels is that of 0CALMONTH which is checked in second aggr level.
    0CALMONTH is assigned as target char in first CR, hence both the CRu2019s work for input ready report built on first aggregation level and do not function with input ready report built over second aggregation level.
    Therefore I wish to skip the complete execution of CRu2019s for I-R reports based on 2nd aggregation level.
    As CR of type with derivation is functional only if the target char selected is not present in the aggregation level.
    Please let me know if any more details are required.
    Thanks,
    Pankaj

  • 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.

  • Aggregation level ZSPLN inconsistent : Infoprovider 0PLANT can not be used

    Hi ,
    I have added a new characteristic in the multi provider . Added the same characteristic in the aggregation level. But when I activated the aggregation level , system is giving aggregation
    level inconsistent message? Has anyone come across this error.  Early reply on this issue will be much
    appreciated.
    Thanks
    JC

    Hi Mayanak,
    I have looked at this post earlier . I have activated planning cube and  multi  provider. But still I a not able to activate the aggregation level. Please let me know if you have any other thoughts.
    Thanks
    Hareesh

  • 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

  • Can you post Notes (Display Note) at a higher level of aggregation than CVC

    I am only able to post Notes with the Display Note at the CVC level.  ALL PRODUCTS ALL CUSTOMERS and I receive the error message "No Notes can be processed in the current selection".  ONE PRODUCT ALL CUSTOMERS OR ALL PRODUCTS ONE CUSTOMER and I get display only no input (greyed out).  I can post notes at the CVC level.  Is this the only level you can post notes.

    HI Kevin ,
    Yes there are restrictions on the levels you put the note and the level you can edit the notes.and hence those will be greyed out at certain levels .
    For more details please refer my earlier post [No notes can be processed in the current selection - Error Msg|Re: No notes can be processed in the current selection - Error Msg.]
    Regards,
    Digambar

  • Aggregation Level & Selection ID in Demand Planing Background job

    Folks
    Whle creating a Demand Planning job in the background, we need to make few selection such as
                1. Choosing a Selection ID(One, Several & Select All) and
                2. Choosing an Aggregation level.
    My question is : Doesn't the selection ID already have the aggregation level defined with in as selection ID is basically something defined or shown as Product by Location and then by Sales Org etc. Isn't this the same as the aggregation level ???
    Why do we need to have Selection Id as well as Aggregation level in Background job ?
    In the interactive planning do we need the aggregation Level ? If so where do we specify the same ?
    TIA

    The aggregation level can make a big difference to the forecast results. If you run the forecast on a high level (for example, at division level), the system aggregates the historical data (for example, the historical data of all products in a division) before it carries out the forecast. However, if you run the forecast on a low level (for example, for just one product), the system creates the forecast based on the historical data at this level, and then aggregates the forecast results in the planning screen at runtime.
    The default level is the most detailed level.Here values will be disaggregated to the lowest detailed level and forecast will be executed in that level for each CVC.
    say
    PRD  LOC     PRD_GRP
    A       A1           PG1
    B       A1           PG1
    C       A1           PG1
    A       B1           PG1
    B       B1           PG1
    C       B1           PG1
    here forecast wil be carried out for 6 CVCs
    However, in real time, as you have many CVCs, we dont follow this.
    Say we specify the aggregation level as PRD_GRP and LOC.. Then system aggregates values at product group and location level..executes forecast and then disaggregates.
    in this case forecst will be carried out for
    PRD  LOC     PRD_GRP
          A1           PG1
          B1           PG1.
    Selection ID on the other hand will be used for specific selections.
    Suppose if u want to execute one profile  for PRDGRP PG1 at LOC A1 , you create a selection ID with this selection like in interactive planning..
    How ever, if your selection is
    PRD         *
    PRDGRP  *
    LOC          *,
    then , here ur aggregation level helps how to disaggregate values before running the forecast

Maybe you are looking for