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

Similar Messages

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

  • Error when selecting system during scheduling of background job in RAR

    Hi,
    I am getting an error when I attempt to schedule a background in RAR. It happens when I go to the multiple system selection option. I select a system and click copy. An error example below appears in the logs even when I dont go ahead and schedule the job. The job still runs and returns results when scheduled. However these errors in the logs concern me. Anybody else experience this?
    Aug 4, 2010 4:12:32 PM com.virsa.cc.common.util.ExceptionUtil logError
    SEVERE: NodeElement(.BatchRiskAnalysisSelection.RoleAnalysisInput.RoleAnalysisSystems): unknown attribute Sign
    com.sap.tc.webdynpro.progmodel.context.ContextException: NodeElement(.BatchRiskAnalysisSelection.RoleAnalysisInput.RoleAnalysisSystems): unknown attribute Sign
         at com.sap.tc.webdynpro.progmodel.context.NodeElement.wdGetAttributeInfo(NodeElement.java:374)
         at com.sap.tc.webdynpro.progmodel.context.NodeElement.setAttributeValue(NodeElement.java:877)
         at com.virsa.cc.common.GUIElement.copyAttributes(GUIElement.java:696)
         at com.virsa.cc.common.GUIElement.copyNodeTree(GUIElement.java:792)
         at com.virsa.cc.common.GUIElement.copyNodeTree(GUIElement.java:777)
         at com.virsa.cc.common.ui.MultipleSelectionView.onActionCopy(MultipleSelectionView.java:187)
         at com.virsa.cc.common.ui.wdp.InternalMultipleSelectionView.wdInvokeEventHandler(InternalMultipleSelectionView.java:259)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    Regards,
    Niamh

    Hi
    Did you check the connector whether the background system is connecting or not.
    Goto RAR-Configuration>connectors> select the connector of the background system and then press on test connection.
    Regards
    Hari

  • Can't Delete Aggregation Level

    Hello Experts,
    I can't delete a aggregation Level wich based on a Realtime InfoCube. How
    can I delete This aggregation Level.
    No Filter,
    No Planing Sequenz,
    No Planing Function,
    THANKS....

    Hi,
    i have the same issue. I cannot delete an aggregationlevel. It has no dependent objects. I tried to use the Function module as described but i also get the same message RSPLS112 cannot delete aggregation level.
    Was the issue soved? How was the issue solved?
    Thanks,
    Murat

  • How to select server in which background job should run

    Hi,
    I want to run my program as background job. I want the user to select the server, in which background job should be run, in the selection screen of my program. When it is sheduled in background the job should run in the selected server.
    How to do this?
    Regards,
    Sriram

    Hi,
    please write the code like as below.
    DATA : D_GROUP like TBTCJOB-JOBGROUP.
    use the function moulde JOB_OPEN.
      D_JOBNAME = SY-REPID.
      D_GROUP- BTCSYSREAX =  " pass the target server name Here
         CALL FUNCTION 'JOB_OPEN'
            EXPORTING
                 JOBNAME          = D_JOBNAME
                 JOBGROUP       =  D_GROUP
            IMPORTING
                 JOBCOUNT         = D_JOBNO
            EXCEPTIONS
                 CANT_CREATE_JOB  = 1
                 INVALID_JOB_DATA = 2
                 JOBNAME_MISSING  = 3
                 OTHERS           = 4.
    submit   <Program name>
                  USER SY-UNAME VIA JOB D_JOBNAME NUMBER D_JOBNO
                  USING SELECTION-SET '  var1 '   " Give varient name
                  AND RETURN.
    CALL FUNCTION 'JOB_CLOSE'
               EXPORTING
                    JOBCOUNT             = D_JOBNO
                    JOBNAME              = D_JOBNAME
                    STRTIMMED            = 'X'
               IMPORTING
                   JOB_WAS_RELEASED     = D_REL
               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.
    Hope this will helps you
    Regards
    Kiran

  • Execution of Macro in Background job

    We have created a macro in APO DP that uses 4 characteristics and a key figure. As part of the macro we are executing a Z-function that we have created. The problem occurs when executing the macro in a background job. When the background job is executed the macro processes correctly (performs the correct calculations) for the first CVC that is processes, but it is not able to process the rest of the CVCs.
    <b>ERROR: "There are no plannable characteristic combinations",</b>
    The function copies data from the CVC that is being processed (source CVC) to another CVC (target CVC). The values for the target CVC to which the data has to be copied for a particular key figure are determined from the paramaters that are given to the function in the macro.
    The steps followed in the function are the following:
    1- Determine the relation between source and target CVC, ie, from the source CVC that is being processes in the macro, the function determines the target CVC to which the data has to be copied.
    2- Call BAPI "BAPI_PBSRVAPS_GETDETAIL2" to retrieve the valuesthat are in the Planning Book for the source CVC.
    3- Perform the addition of data (value retrieved from the source CVC is added to the target CVC).
    4- Write value to the target CVC using BAPI "BAPI_PBSRVAPS_CHANGEKEYFIGVAL2".
    When using the BAPIs the aggregation level used is the same aggregation as the one specified in the Background job used for the execution of the macro.
    This macro is executed in a background job, and the copy/calculation is performed correctly for the first CVC (first CVC contained in the data selection used in the background job) processed, but then it does not do anything else for the rest of CVC's. The error message given by the log of the background job is <b>"There are no plannable characteristic combinations",</b> when in fact, the characteristic combinations do exist in the Planning Object Structure.

    Hi Ian
    There are not any other macros in the planning book.
    In addition, if we execute the macro in interactive mode we have another error at the end of the execution (after doing all the combinations):
    <b>Invalid data status</b>.
    and we don't know why.
    Regards

  • DP background job error

    Hi,
    The Demand Planning background job step which is used to Delete the  planning area is not working properly.
    The error message "Process DP Background Processing, variant DELETE VP SALES VALUE_ANNUAL has status Ended with errors (instance D96Y8ITPW9HBSLX8CCXHKV    displayed on the log.
    What could be the possible reasons.
    Thanks and regards
    Murugesan

    Issue resolved by assigning authorization to the background job user.

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

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

  • DP Disaggregation and Aggregation levels

    Hi all,
    I have a question regarding disaggregation and aggregation levels.
    KFu2019s and disaggregation setup:
    KF001:
    Calculation type: I (not relevant)
    Disag. Key Fig.: KF000 (not relevant)
    Time-Based Disaggregation: K (not relevant)
    Time-Based Disag. Key Figure: (not relevant)
    KF002:
    Calculation type: I
    Disag. Key Fig.: Keyfigure001
    Time-Based Disaggregation: P
    We are now interested on the KF002. KF002u2019s disaggregation is based on KF001. I am trying to copy KF001 values to KF002 with a macro that is attached to a background job. Macro doesnu2019t do anything else than copy values from KF001 to KF002.
    Background job setup:
    Selection:
    Sales organization: 2000AB
    Location: 1000EF
    Product: 1 to 2000 (consists 2000 products, including products that do not belong to above location)
    Excluded values:
    Customer group 1: 2500AB
    Aggregation level:
    Sales organization
    Location
    Product
    Customer group 1
    What I try to accomplish (through background job - mass processing):
    I am trying to copy values with above setup so that the most detailed level which is Customer group 2 would have values through disaggregation. I have successfully copied values to product level, location level, sales organization level but the customer group 2 level values are not as KF001u2019s. Values are right in the SUM level, but not disaggregated right to customer group 2 level.
    I get right results when I choose Customer group 2 to the aggregation level but this is not something we can do as it causes way too long runtimes. What I am also interested in is that how come the disaggregation does not work properly or does it? How can I get the disaggregation work so that I only have to select the aggregation levels which are defined in the selection and get proper results through disaggregation to customer group 2 level?
    Thanks in advance,
    Juha

    Hello Juha,
    You do not need another macro, just make the above change to your original one, and the macro should work.
    Your aggregation level in the job should also be OK.
    Since you mentioned that the values at detailed level are not the same as key figure 1, it sounds to me that the system did a pro rata disaggregation. Do you have the key figure 2 totally cleared out before copy? Since you're using disaggregation type 'I', it only disaggregates based on another key figure when the key figure value is initial.
    So my suggestion is, you can try to change the key figure's disaggregation tyep to 'P' and check if the macro works.
    Or if you have to use type 'I', you should add a step in the macro before the copy step, to initialize key figure 2 first.
    To initialize a key figure, just put the row in the step, and for the 'Change Mode', select 'Initialization'.
    Best Regards,
    Ada

  • Running Macros on 9AMALORE aggregation level

    Hi,
    I'm trying to run simple macro in SNP (5.0)
    I use DP Activities and Background jobs for this.
    When I create a Background job, with selection "Select All"  from Aggregation level I can choose what I want - "9AMALORE".
    When I create a selection in the shuffler ( I have to restrict the selection to one plant only) and use it as Background job selection, I cannot manage to run the macro on 9AMALORE level.
    In this case only one selection is available based on the shuffler selection grouping criteria, and unfortunately I can do it only by 9ARE (Resource only) or 9AMALO (Material Location).
    Do you know what trick I can use to achieve this?
    Regards!

    Hi,
    I am trying to understand your requirement. Not sure if I have understood this correctly,
    When I create a Background job, with selection "Select All" from Aggregation level I can choose what I want - "9AMALORE".
    Question - You mean in the /sapapo/mc8d txn you are able to select 9AMALORE as your agg level? What is ur selection id in this case?
    When I create a selection in the shuffler ( I have to restrict the selection to one plant only) and use it as Background job selection, I cannot manage to run the macro on 9AMALORE level.
    In this case only one selection is available based on the shuffler selection grouping criteria, and unfortunately I can do it only by 9ARE (Resource only) or 9AMALO (Material Location).
    Question - Again in the interactive planning, you use shuffler to create a selection id. So here, What is your "Selection characteristics" and what is your "Show Characteristics" (the one at the top). Are you using this selection id in the background job and not able to aggregate by 9AMALORE or are you trying to running the macro in interactive.
    Either ways, we shud be able to achieve what you are looking for.
    Sorry I am a little confused with your requirement, but I am confident that I can help you, if you can clarify what you are looking for.
    Thanks
    Mani

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

  • Background job not automatically poopulating Dependant Demand

    Hi Users,
    We've recently set up a POS & PA using the DP-BOM selection and characteristics, manually created PPM's and generated CVC's using the BOMS. All of this is set up fine in our SCM 7.0.
    The background job has created the forecasts for the ouptput products but NOT the input product.
    Now if I call up the parent material, and then choose to show the input products the dependant demand is generated. If I now return to the material with the dependant demand, it now shows the demand from the parent.
    Or, if the forecast is genereated interactively, then the dependant demand is poopulated.
    Is there an automated method to populate the dependant demand when using background jobs? I would like to think that we don't have to query every sales BOM parent in DP and drill into the input products to load the dependant demand?
    Please let me know if there is an easier way to do this as part of the background processing.
    Thanks
    Edited by: Paul_111 on Mar 31, 2011 4:20 PM

    Hi Andand,
    Thanks for your reply and sorry if my post is confusing.
    As far as the PPM with imputs A & B, output C - I have this relationship working and calcuclating demand in DP no problems.
    If I now add a new PPM combination inpput X, Y and output Z. Create the BOM CVC and TSO so its all set to go. Add to selection profiles and background jobs.
    Now, if I run the background job to create the forecast and this runs successfully. Now I check my products.
    Z has the forecast generated, X & Z have no dependant demand showing.
    The only way I've found that pushes the demand to X & Z is:
    - open product Z in demand planning and then choose the option to show input products from the header
    OR - from demand planning, select the univariate forecast to run interactively.
    My issue:
    The background job (if run alone) does not push the forecast on Z to X & Y.
    And if I show the input products or create forecast (as bove) the dependat demand is shown on X & Y.
    This is going to be a slow process if we have to do this everytime we run the backgound job.
    What am I missing when running the background job?

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

Maybe you are looking for