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.

Similar Messages

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

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.

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

Aggregation level disactivation.

Hi All.
In our solution we use multiProvider and several aggregation levels based on it. When we are updating something in multiProvider all aggregation levels become inactive.
It is very boring to activate each aggregation level by hand.
Does anybody know how to do it automatically or by ABAP code?
Best Regards,
Andrey.

Hi,
the following report reads all aggregation level using g_iprov as InfoProvider and activates the aggregation levels:
*& Report ZGD_TEST_ACTIVATE_ALVL
REPORT zgd_test_activate_alvl.
TYPE-POOLS: rs.
PARAMETER: g_iprov TYPE rsinfoprov,
           g_objv TYPE rsobjvers DEFAULT 'M'.
PERFORM run.
*&      Form run
      text
FORM run.
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.
SELECT * FROM rspls_alvl INTO TABLE l_t_alvl
                           WHERE infoprov = g_iprov
                           AND   objvers = g_objv.
CHECK l_t_alvl IS NOT INITIAL.
LOOP AT l_t_alvl INTO l_s_alvl.
    CALL FUNCTION 'RSPLS_ALVL_CHANGE'
      EXPORTING
        i_aggrlevel    = l_s_alvl-aggrlevel
      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 = l_s_alvl-aggrlevel
        i_objvers   = rs_c_objvers-active
      IMPORTING
        e_subrc     = l_subrc
      TABLES
        e_tk_return = l_t_return.
    CHECK l_subrc = 0.
    CALL FUNCTION 'RSPLS_ALVL_ACTIVATE'
      EXPORTING
        i_aggrlevel = l_s_alvl-aggrlevel
      IMPORTING
        e_subrc     = l_subrc
      TABLES
        e_tk_return = l_t_return.
ENDLOOP.
ENDFORM.                    "run
Regards,
Gregor

Aggregation level query "value help" = Only Values in InfoProv doesn't work

Hi,
I have a problem with Selection Variable for a BEx Query :
- I'm working with SAP BI 7.0 support package 15
- My query is an input ready query built for an "aggregation level" based on "real time infocube" (Planning);
- Characteristic, I want to filter with variable, has query property Advanced->Query Execution for Filter Value Selection = Only Values in InfoProvider
- Characteristic (info-object) has set the property: Business Explorer tab--> Query Def. Filter Value Selection as Only Values in the info-provider...
My problem is:
when I execute a query,
the Select Values for Variables screen appears
I push on the Select from List button
and Select Values For MyCharacteristic appears...
but it shows me all values in master data table of my characteristic instead of only values in the infoprovider!!!
If I build a query for the Real Time Cube it works correctly, but if the query is built for the aggregation level it doesn't work!
Could someone explain me why it doesn't work correctly?
Thanks in advanced
Fede

Thanks to Mariana Lazar
30.03.2009 - 12:30:36 CET - Risposta by SAP
Dear Fede,
Regarding the query built on aggregation level please note the following
the aggregation level is always a Virtual Provider built other
InfoProvider and hence it does not have the dimension table and hence
the F4 mode D is not supported.
Therefore when aggregation level is used in a query, F4 does not supportD-mode: 'Only Values in InfoProvider' and all master data values are
displayed in the value list.
Reference from the note
984229 F4 modes for input help as of SAP NetWeaver 2004s BI
4. Since other InfoProviders do not have a dimension table, the system
displays only posted values if you select "Only Posted Values for
Navigation". Otherwise, it displays the values from the master data
table.
Hope this should clarify your doubts. Please let me know if you have
questions else please confirm the message at your earliest convenience.
Thank you for your cooperation and kind regards,
@KR@ Mariana Lazar
Senior Support Consultant
SAP Active Global Support
Netweaver Business Warehouse

Non-Cummulative KeyFigures Usage at Aggregation Level in IP

Dear Team,
I am getting following error while selecting Non-Cummulative Keyfigure at Aggregation Level in IP
InfoObject 0CFMF0902 (version A) is not compounded
Aggregation level ZCFMAG1 is inconsistent.
I have selected the Key Figure which is using by this Key Figure and also selected the Unit Loc Currency , eventhough I am getting the above error.
If anybody aware of this problem or if there is any alternative way to use Non-Cummulative Key Figure , kindly reply to this.
Best Regards,
SG.

SAP Note 1323302
We cannot use Non-Cummulative Key Figure at Aggregation Level in IP.
I have to get opening balance in each month without using Non-Cummulative Key Figure and I have to use that for futher calculation in FOX. Can anybody give me idea how can i get it.
Best Regards,
SG
Edited by: SG on Dec 29, 2009 2:55 PM
Edited by: SG on Dec 29, 2009 2:57 PM

Question on aggregation level "%" (percent) in aggregate definition

Hello,
I would like to find out all the aggregates that have at least one navigation attribute of a specific characteristic (let's say 0CUSTOMER) in their definition. The idea behind that is to find out which aggregates are potentially affected in a change run by a master data change for the 0CUSTOMER characteristic.
Well, I looked in table RSDDAGGRCOMP for entries that met the selection criteria {OBJVERS = 'A'; IOBJNM = '0CUSTOMER_*'}
For all navigation attributes of 0CUSTOMER - except for those that can actually be seen in the aggregate definition screen (launched via "Maintain Aggregates") - there are records that have as aggregation level (field AGGRST) '%'. What does this aggregation level mean and why is it in that table? That field description ("SAP-internal use only (technical:facts)") doesn't really bring me forward.
An aggregate, that only contains '%' as aggregation level in RSDDAGGRCOMP for navigation attributes of char 0CUSTOMER is not affected by a change run regarding the master data change of 0CUSTOMER attributes, is that right?
Thanks to any replies in advance.
Regards,
Philipp

aggregation against cubes require the following approach-
http://epmandbitech.blogspot.com/2010/12/obiee-11g-and-multidimensional-data.html
http://epmandbitech.blogspot.com/2010/12/obiee-11g-integration-with-microsoft.html
Thanks.

Pivot Aggregation Level

Hi.
My criteria result set is a sort of
CUSTOMER ... QTY .......... LABEL
=======================================================
1 ................ 100 .......... "QTY_LOWER_THAN_1000"
2 ................ 3000 ........ "QTY_BIGGER_THAN_1000"
3 ................ 2000 ........ "QTY_BIGGER_THAN_1000"
where LABEL is calculated with a formula containing the measure QTY and a CASE WHEN.
When I try to create a pivot to get a result set like
...................... "QTY_LOWER_THAN_1000" ........ "QTY_BIGGER_THAN_1000"
=======================================================
TOTAL_QTY ...... 100 .......................................... 5000
the total are obiously correct, but all the QTY is put under the label QTY_BIGGER_THAN_1000 because obi aggregate further and the formula is not evaluated at the level of criteria result set as expected.
How can achive my goal ?
I tried to use the "Treat as an Attribute Column" option but I get a maximum record exceeded if I put the LABEL in row or column (while if put the LABEL in the measure area I don't get the error but it still persistent the wrong aggregation).
The result set table contains 200000 records and the configured buffer size for pivot table are bigger.
Thanks,
Andrea
Edited by: aromani on 9-ago-2012 3.47
Edited by: aromani on 9-ago-2012 3.47
Edited by: aromani on 9-ago-2012 3.48
Edited by: aromani on 9-ago-2012 3.48
Edited by: aromani on 9-ago-2012 3.49
Edited by: aromani on 9-ago-2012 3.49

I wonder that not exists a simple way to achive this simple and basic pivot behaviour ...Please don't flog the product if you can't make it work. I'm not entering any discussion on "Excel can do this, why can't OBI"...simply because Excel is Excel and OBI is OBI. One is cell calculation in any way you want, the other based on the principles of dimensional modelling.
Anyways, here's a very, very simple example doing exactly what you want. You can paste the XML into a SampleApp (Oracle has one here: http://aosdemeamt07.oracle.com:7779/analytics) and it will show you precisely what you want:
<saw:report xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlVersion="201201160" xmlns:sawx="com.siebel.analytics.web/expression/v1.1">
   <saw:criteria xsi:type="saw:simpleCriteria" subjectArea=""A - Sample Sales"" withinHierarchy="true">
      <saw:columns>
         <saw:column xsi:type="saw:regularColumn" columnID="cbc4e4291fc1a381e">
            <saw:columnFormula>
               <sawx:expr xsi:type="sawx:sqlExpression">"Customers"."C1 Customer Name"</sawx:expr></saw:columnFormula></saw:column>
         <saw:column xsi:type="saw:regularColumn" columnID="c94363662e33f987b">
            <saw:columnFormula>
               <sawx:expr xsi:type="sawx:sqlExpression">"Base Facts"."2- Billed Quantity"</sawx:expr></saw:columnFormula></saw:column>
         <saw:column xsi:type="saw:regularColumn" columnID="c4400acdbec215548" forceGroupBy="true">
            <saw:columnFormula>
               <sawx:expr xsi:type="sawx:sqlExpression">case when "Base Facts"."2- Billed Quantity" > 10000 then 'Above 10k' else 'Below 10k' end</sawx:expr></saw:columnFormula></saw:column></saw:columns></saw:criteria>
   <saw:views currentView="0">
      <saw:view xsi:type="saw:compoundView" name="compoundView!1">
         <saw:cvTable>
            <saw:cvRow>
               <saw:cvCell viewName="titleView!1">
                  <saw:displayFormat>
                     <saw:formatSpec/></saw:displayFormat></saw:cvCell></saw:cvRow>
            <saw:cvRow>
               <saw:cvCell viewName="pivotTableView!1">
                  <saw:displayFormat>
                     <saw:formatSpec/></saw:displayFormat></saw:cvCell></saw:cvRow></saw:cvTable></saw:view>
      <saw:view xsi:type="saw:titleView" name="titleView!1"/>
      <saw:view xsi:type="saw:tableView" name="tableView!1">
         <saw:edges>
            <saw:edge axis="page" showColumnHeader="true"/>
            <saw:edge axis="section"/>
            <saw:edge axis="row" showColumnHeader="true">
               <saw:edgeLayers>
                  <saw:edgeLayer type="column" columnID="cbc4e4291fc1a381e"/>
                  <saw:edgeLayer type="column" columnID="c94363662e33f987b"/>
                  <saw:edgeLayer type="column" columnID="c4400acdbec215548"/></saw:edgeLayers></saw:edge>
            <saw:edge axis="column"/></saw:edges></saw:view>
      <saw:view xsi:type="saw:pivotTableView" name="pivotTableView!1">
         <saw:edges>
            <saw:edge axis="page" showColumnHeader="true"/>
            <saw:edge axis="section"/>
            <saw:edge axis="row" showColumnHeader="true">
               <saw:edgeLayers>
                  <saw:edgeLayer type="measure"/></saw:edgeLayers></saw:edge>
            <saw:edge axis="column">
               <saw:edgeLayers>
                  <saw:edgeLayer type="column" columnID="c4400acdbec215548"/></saw:edgeLayers></saw:edge></saw:edges>
         <saw:measuresList>
            <saw:measure columnID="c94363662e33f987b"/></saw:measuresList></saw:view></saw:views></saw:report>UPDATE: if you know the password, here's the direct link BTW: http://aosdemeamt07.oracle.com:7779/analytics/saw.dll?Answers&path=%2Fusers%2Fipad_user1%2FPivot Aggregation Level Example
Edited by: Christian Berg on Aug 21, 2012 10:52 AM

Aggregation level transportation from dev to quality

Hi,
I have 2 aggregation levels in my mutiprovider. How can I transport these 2 aggregation levels from dev to Quality systems?

Hi,
you can collect the aggregation levels in transport connection (transaction rsa1 --> transport connection). There is a folder "Planning" and a type "Aggregation Level" (technical name: ALVL). Just select your aggregation levels and add them to a request. Please be aware that depending objects such as the multiprovider have to be transported to your quality system at same time if they are not already existing over there.
Brgds,
Marcel

Input Ready query based on aggregation level

I have an input ready query that reads data from an aggregation level, based on a multiprovider that contains a cube for planning and a cube with real data.
There are two columns of data, two of them for read-only and another for input.
I´m selecting different fiscal year/periods for each column.
The problem is that, when I select fiscal year/periods and the real data cube doesn´t contain any data for this filter, it doesn´t show me a line to input data anyway..
how do I configure the query so that it understands that eventhough I don´t have data for the selected period, I still want to be able to perform the planning?
Thanks,
Cris.

Hi Christina,
Even though there is no Data in the Real time Cube the Query must allow you to Input values. I guess the Query you have designed is not enabled for input yet.
Kindly check the following Points before proceeding.
1. In the Query properties under Planning tab, make sure the Start Query in change mode is turned On.
2. Make sure you have used all of the characteristic in the aggregation level in the Query and is restricted to single value.
3. make sure the columns are Input ready under the Planning tab in its properties
Hope this Helps.
Regards.
Shafi.

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

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

Cross-Aggregation-Level Selection Evaluation indicator

Similar Messages

Maybe you are looking for