Activate an Aggregation Level in Production

Hi,
Can anyone please assist me in activating an aggregation level in Production?
Some of our aggregation levels are inactive and we can't transport them at the moment as we are busy with an upgrade in development.
Your help would really be appreciated, as this is quite high priority at the moment.
Thank you!
Regards,
Tanya

Hi Shafi,
We did do the investigation. The MultiProvider on which the Aggregation Level was built, was still active in the morning. We ran two queries from the MultiProvider, and the second one (for some reason) de-activated the one InfoCube in the MultiProvider.
We did version comparisons to see what might have changed in the InfoCube or MultiProvider, but there was nothing. We re-activated both the InfoCube and MultiProvider with programs that are available in SE38 (RSDG_CUBE_ACTIVATE and RSDG_MPRO_ACTIVATE), but could not find a program to re-activate the aggregation levels (and the function module did not work).
Thank you!
Regards,
Tanya

Similar Messages

Activate aggregation level

Hi,
I had a planning infocube and an aggregation level on top it.recently we send a transport to that changed the structure of the Planning infocube....as a result aggregation level on top of it got deactivated.
Can you please update me on how can i activate it (aggregation level)
Thanks

Hi,
Check the blog to activate the aggregation levels,
[http://wiki.sdn.sap.com/wiki/display/Snippets/CodetoActivateallyourAggregationLevelsinBI-IntegratedPlanninginoneGo]
Regards,
Durgesh.

Aggregation level is locked by the Change and Transport Organizer

Dear All,
I have created aggregation level in the planning cube and transported to Production from dev, Once i transported to production i am not able to change the aggregation level in Dev, and also aggregation level is Inactive. Aggregation level YPNC2 is locked by the Change and Transport Organizer. Please suggest how to activate the aggregation level in Dev.
Thanks
Christopher

Hi,
Kindly check the following,
1. Is your aggregation level transported properly to the production system ?
2. Was your aggregation level active while you were including it in the transport request ?
3. Did you properly include the aggregation level in the request?
If you find that the answers of all the above questions is "YES", then there should not be any problem in your aggregation level.
Hope this solves your issue, if not kindly get back to me.
Regards,
Balajee

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

Mass activation of Aggregation level

Dear all..
How to do the mass activation of all Aggregation level in Modeler at one instance. while collection tp we have to activate the individual aggregation level, its more time consuming.
I have lot of aggregation levels to activate, any solutions.
Regards
Perasel

Hi there,
Create this program (it was referenced by a SAP note) in se38 transaction:
*& Report Z_ACTIVATE_ALVL
REPORT Z_ACTIVATE_ALVL.
TYPE-POOLS: rs.
PARAMETER: g_iprov TYPE rsinfoprov.
PERFORM run.
*&      Form run
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 = 'A'.
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.
    READ TABLE l_t_return INDEX 1 INTO l_s_return.
    CHECK l_subrc <> 0 OR ( sy-subrc = 0 AND l_s_return-type = 'S' ).
    CLEAR l_t_return.
    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
This will mas activate your aggregation levels built on InfoProvider.
Diogo.

Activate more than one Aggregation Level

Hello experts,
We use the Integrated Planning and we have more than 80 Aggregation Levels. When the MultiProvider is deactived because of adding a new InfoObject, all our Aggregation Levels are deactivated.
Is there a possibility to activate more than one Aggregation Level at once? Maybe a special report?
Thank you.

Hi,
please check:
[Re: Activate all the Aggregation level of underlying multi provider]
Gregor wrote a small program and posted it to the forum. Please note: There is no support for this tool.
Bye Matthias

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 save

Guys,
I got an aggregation level which is moved for testing. Now we got make some changes in development environment. After I am done with my changes and click on save/activate, its not giving popup screen to save the aggregate level in my request. How do I save te aggr levels in my request?
Thanks.

Here is the process I followed to save the aggregation levels in my own request.
My Aggregation levels were inactive. Before activating them, I collected them (inactive aggr levels) into my own request in the Transport connection and then I activated them. So my aggr levels got saved in my own request.

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

Aggregation level in only bps ?

hi friends,
can we need aggregation level in reporting for only bps module or for normal cubes also. so what is the if we use for normal cube alos.,
Tu
suneel.

Lets say you have fiscal period, fiscla year, GL account, amount, qty, product in the cube. But you wish to plan for GL account, fiscal period, fiscal year. Then you create an aggregation level for this and plan on GL account.
Similarly, you wish to plan for product, fiscal period, fiscal year and amout, then you create another aggregation level and plan for product.
Under this level, you further have filters, in which you restrict the values for the characteristics that you wish to plan.
Ravi Thothadri

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.

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 deletion issue

Hi ,
I have a requirement to delete few aggregation levels from the system , i deleted them in development system and put them in a request but on transporting to Production these are not getting deleted. Any pointers .
Is there any other way to delete them directly in production system . There are few tables like RPLS_ALVL and RPLS_ALVLT .can deleting entries from these tables can resolve the issue ?
thanks.

Check whether these objects are attached in any transport in production.
You can re-import the transport by checking 'overwrite originals' and 'overwrite objects in unconfirmed repairs' options.

Aggregation level not getting deleted.

Hi All ,
We have deleted the aggregation levels from our development system and captured them in one change request.
On transporting this request to quality (the transport is going successful) ,the objects are not getting deleted and getting displayed in transport connection and metadata repository.
Any pointers to delete directly the aggregation levels from quality and production system or to resolve this issue.
Thanks and Regards
Rashmi Nair.

Hi Rashmi,
Have you deleted all the objects using the aggregation level.
e.g query, planning function etc.
-Vikram

Activate an Aggregation Level in Production

Similar Messages

Maybe you are looking for