How to check in Cube for Non cumulative calculation?

Hi All/surendra (Inventory Specialist)
  I am now supporting the Inventory cube. I never worked in inventory. I have read all the documents like
a. How to Inventory
b. Surendra's Inventory with 3parts
c. Non cumulative..
But none of the above docs gave me solution how to go ahead to find or compare with R3 for the first time consultants who is handling Inventory..
Can you pls help me resolve the following issues?
1. May I know how actually the NON CUMULATIVE calculation is done for filelds 0VALSTCKVAL and 0VALSTCKQTY  and also other KF's like ISSUE and RECEIPT qty, blocked qty, scrap, stck transit etc as I dont see any mapping done in transformation, if it is not done for Inventory, how it is fetched.??
2.Also I wanted to know what are the fields used cumulated for the above fields as I dont see any transformation mapping done for Key Figure and understood all Inventory docs that the KF are not visible as they are NON CUMULATIVE KF's.
3. How to compare the Inventory stock with R3 Material Stocks as when I compare with transaction MC.9, I see the values are totally different?? how and which transactions or tables supposed to be compared? Also we are not 2lis_03_BX in our Inventory. so I am not sure how they loaded the Inventory. Looks I need to redesign, can you tell steps to check and apply if I have initialize to make sure that my data will come correctly??
Thanks a lot for all you help and efforts in advance.

The source field for quantities is the field CPQUABU, and for values it is the field CPPVLC.
Explanation for the routine :-  
IF ( COMM_STRUCTURE-processkey EQ '000' "Other Receipts
OR COMM_STRUCTURE-processkey EQ '001' "Goods Receipt / Vendor
OR COMM_STRUCTURE-processkey EQ '004' "Material Transfer / Receipt
OR COMM_STRUCTURE-processkey EQ '005' "Stock Adjustment InvD +
OR COMM_STRUCTURE-processkey EQ '006' "Stock Adjustment Other +
OR COMM_STRUCTURE-processkey EQ '010' ) "Receipt from Stock Transfer
AND COMM_STRUCTURE-bwapplnm EQ 'MM'
only stock in transit is considered
AND COMM_STRUCTURE-stocktype CA 'FH'
only movements which are relevant for stock control
AND COMM_STRUCTURE-stockrelev EQ '1'
AND COMM_STRUCTURE-cpquabu 0. *
The above part is used for the KF : 0ISSTRANSST - Issue Quantity: Stock in Transit
IF ( COMM_STRUCTURE-processkey EQ '100' "Other Issues
OR COMM_STRUCTURE-processkey EQ '101' "Returns / Vendor
OR COMM_STRUCTURE-processkey EQ '104' "Material Transfer
OR COMM_STRUCTURE-processkey EQ '105' "Stock Adjustment InvD
OR COMM_STRUCTURE-processkey EQ '106' "Stock Adjustment Other
OR COMM_STRUCTURE-processkey EQ '110' ) "Issues from Stock Transfers
AND COMM_STRUCTURE-bwapplnm EQ 'MM'
only movements which are relevant for stock control
AND COMM_STRUCTURE-stockrelev EQ '1'
AND COMM_STRUCTURE-cppvlc 0
see OSS note 630254
AND ( COMM_STRUCTURE-stockcat IS INITIAL OR
( COMM_STRUCTURE-stockcat CA 'EQ' AND
COMM_STRUCTURE-indspecstk CA 'AM' ) ).
result value of the routine
RESULT = COMM_STRUCTURE-cppvlc. *
This part is used for : 0ISSTOTSTCK - Issue Quantity Total Stock
Hope this hepls,
Reg,
Rahul

Similar Messages

  • Workbook Displays Data Not Present in the Cube for Non-Cumulative KF

    Hi All,
    I have a user that is reporting using noncumulative info object 0TOTALSTCK. If I look in the cube, the data starts in October and goes from there. When viewing the data, there are figures that display for the months prior to October even though there is no data in the cube.
    The interesting thing is that when viewed in excel using the analyser, these figures display using square brackets. This is then throwing out the total values of the prior months as they are being added in.
    Does anyone have an idea why this value would display even though there is no data in the cube for it?
    Thanks in advance for any help supplied.

    Just thought I would share the solution to this.
    It looks like the validity date for the cube was not set up properly. I fixed it using transaction RSDV.
    Details on how to proceed can be found here:
    http://help.sap.com/saphelp_nw70/helpdata/EN/02/9a6a1f244411d5b2e30050da4c74dc/frameset.htm

  • How to remove negative values for non-cumulative amount

    Hello
    I have a requirement from the user, wherein he needs to see the balance amount from credit and debit without calendar day being a factor. Hence, they do not need a bank passbook kind of scenario.
    I kept the balance amount aggregation as sum+last value. It works fine when I keep calendar day in rows. However, removing it shows negative value in the balance amount in case of just debit.
    They wish to see 30,000 on 07.12.2014 and 25,000 on 04.02.2015 in Non-cumulative key figure column. This works if I drag 0calday, but doesnt work in this scenario.
    Is it possible?

    Hi Yasemin
    Credit & Debit are inflow and outflow amount key figures. The user want the data somewhat like this:-
    GL Account No.
    Credit
    Debit
    Non Cumulative Balance
    1
    1000
    1000
    1
    500
    500
    1
    100
    400
    However, as of now, I get this data only when I keep 0calday in rows. If I remove it the data turns into this:-
    GL Account No.
    Credit
    Debit
    Non Cumulative Balance
    1
    1000
    1000
    1
    500
    -500
    1
    100
    -100
    I also tried suppressing result rows, yet it didnt work. This scenario is sort of like an account passbook debit and credit amount balance report, but they want that amount coming in without the 0calday row.

  • How to archive info cube with non-cumulatives values ??

    Dear All,
    Would you like kindly help me please .. ??
    It's regarding archiving, but right now archiving in Info Cube with cumulative values like Info cube movement.
    Because it's rather different than other cube due it has marker ..
    I've already read from article discussing about archiving, it said i must archive the data before the marker (it's if i'm not having incorrect understanding). But right now, i don't know where the marker is ??
    My questions are:
    1. Could somebody help me please giving me explanation regarding it ??
    2. If don't mind, would you like to explain me step-by-step how to archive it ??
    3. Is my comprehension above correct that we have to archive data before the marker ?? If yes, how can i know where the marker is (What date does the marker point to ?? ) ??
    Best regards,,
    Niel.

    Hi
    May be helpful to you
    Step by step https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0974515-7225-2b10-14a1-f5abba35b19f
    Data Archiving Part 1 – A Tour d’Horizon
    http://www.sap-press.com/product.cfm?account=&product=H956
    Technical Setting for Data Archiving
    Hope it helps

  • "initial non-cumulative for non-cumulative values"  is not available in DTP (0AFMM_C02)

    Hi Experts,
    We are working for BI implementation for AFS Industry,
    when we are working on AFS specific inventory cube 0AFMM_C02 , we are facing stock mismatch problem
    for AFS Stock initialization we are using the data source 2LIS_AF_STOCK_INITALIZATION instead of 2LIS_03_BX, this data source is specificly designed for AFS
    when we are extracting the data using 2LIS_AF_STOCK_INITALIZATION for stock initialization and
    2LIS_03_BF data source to load the Moments.
    we compressed cube with Marker update for 2LIS_AF_STOCK_INITALIZATION data load(by deselecting the No marker update check box)
    we compressed cube with No Marker update for 2LIS_03_BF historical data load(by selecting the No marker update check box)
    we compressed cube with Marker update for 2LIS_03_BF Delta data load(by deselecting the No marker update check box)
    Now we are facing stock mistach problem, we found reason for this
    "initial non-cumulative for non-cumulative values" option is not available in DTP only Delta & Full options are available
    and infopackage of  2LIS_AF_STOCK_INITALIZATION data source also has "Full update" instead of "Generate Intial Status"
    Please let us know how can we get the "initial non-cumulative for non-cumulative values" option in the DTP level.
    Regards,
    Chandra

    Hi Chandrakumar,
    We are facing the same problem, how do you solve it?
    Regards,

  • Archive Stock Cube with non-cumulative nature

    Hi All,
    I have been trying to archive the Inventory (Stock) Infocube as we have more than couple of hundread million records in the cube and it is taking long time to execute query.
    I know how to acrive the regular cubes and DSOs, but I couldn't find any helpful documentation where I can know how to archive the Infocube with non-cumulative nature or containing Marker update.
    Can anyone pleaes post the link of document?
    BTW, we are using BI7.0 SP15
    Thanks,
    Dhaval

    Hi,
    There are two ways of archiving data from a non-cumulative InfoCube - time slot archiving and archiving with selection characteristics.
    Time slot archiving (recommended)
    As an archiving method, you must choose for a non-cumulative InfoCube, time slot archiving for the time reference characteristic. When you recreate an archiving object for a non-cumulative InfoCube, this characteristic is also suggested by the system.
    Only archive non-cumulative changes up to a specific point in the past. This reduces the volume of data in the InfoCube. The marker (= end non-cumulative) remains unchanged.
    In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements Only option.
    You are only able to archive the marker if you also archive all of the non-cumulative changes. Subsequently, the contents of the non-cumulative InfoCube are archived completely. In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements and End Non-cumulative option.
    You must archive the non-cumulative changes (for all times) first, and then archive the marker in a separate archiving run, so that the non-cumulative changes and the marker are stored separately in the archive.
    The advantage of time slot archiving is that archiving runs can be carried out periodically using a single variant with a relative time restriction. The alternative archiving method described below does not have this advantage.
    Archiving with selection characteristics
    In some cases, archiving based only on time slots does not have the required effect of reducing the volume of data in the InfoCube. This is the case, for example, if the non-cumulative bearing objects are subject to high fluctuations, meaning that data is constantly being loaded for new objects and old objects are made obsolete. With time slot archiving, the end non-cumulative remains for all objects until all of the data in the InfoCube is finally archived, even if all the non-cumulative changes for an object have been archived already.
    In this case, you want to archive and delete completely any objects that are no longer active in the InfoCube. This means archiving the marker as well. For other objects that are still active, you only need to archive the non-cumulative changes from the past, which means the marker is retained.
    When you define the archiving properties for a non-cumulative InfoCube, do not therefore choose the time slot archiving method. Instead, select individually the characteristics that are relevant to restricting archiving runs. The time reference characteristic should also be included in this selection whenever possible.
    Using this archiving method, for each archiving run, you need to create selection conditions in a variant. In the variant for the archiving run, in addition to the selection conditions, you can also specify for the selected characteristics whether or not non-cumulative changes and marker data is archived. If you choose to archive marker data, be aware that the time selection contains the maximum value for time.
    Please refer to the below link to archive the data for Stock Cube:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/c219fe9a46194aa66d55254fdab182/frameset.htm
    Hope this helps.
    Regards
    Tanuj

  • Define the Characteristics of the validity table for non-cumulatives

    Hi Friends,
      Here I am designing MultiProvider ( ZCA_M01), based on the Two Business content info cubes (0IC_C03 & 0SD_C03 ) & one customized info cube (ZPUR_C01).
    I done Identification for char & keyfigures also.
    When i trying to activating the Multiprovider, here i am getting the error , error message is : Define the Characteristics of the validity table for non-cumulatives.
    Even here I am attaching the error message help also.
    Message no. R7846
    Diagnosis
    The InfoCube contains non-cumulative values. A validity table is created for these non-cumulative values, in which the time interval is stored, for which the non-cumulative values are valid.
    The validity table automatically contains the "most detailed" of the selected time characteristics (if such a one does not exist, it must be defined by the user, meaning transfered into the InfoCube).
    Besides the most detailed time characteristic, additional characteristics for the InfoCube can be included in the validity table:
    Examples of such characteristics are:
    •     A "plan/actual" indicator, if differing time references exist for plan and actual values (actual values for the current fiscal year, plan values already for the next fiscal year),
    •     the characteristic "plant", if the non-cumulative values are reported per plant, and it can occur that a plant already exists for plant A for a particular time period, but not yet for plant B.
    Procedure
    Define all additional characteristics that should be contained in the validity table by selecting the characteristics.
    In the example above, the characteristics "plan/actual" and  "plant" must be selected.
    The system automatically generates the validity table according to the definition made. This table is automatically updated when data is loaded.
    Please take as a high priority.
    Thanks & Regards,
    Vanarasi Venkat.

    Hi Venkat,
    If you want to include 0IC_C03 cube in your multi provider the you must make sure that the time characterestics ( 0CALDAY, 0CALMONTH ....) are present in all of the other info providers which you are including in the MP. The Time char to choose depends upon the Inventory cube in which you have mentioned during the definition. As you are using the standard cube 0IC_C03 it has the time char as 0CALDAY. Try to include this in all the other info providers and dont include more tha one Non-cumulative in the MP.
    Try this and see if it helps....

  • When do you go for non cumulative key figures?

    hi all,
    Can anyone explain the significance of non cumulative key figures. and when do we go for non cumulative key figures.
    Can anyone explain me with an example.
    thanxs in advance
    hari

    Hi,
    chk these threads:
    non cumulative key figures
    Cumulative and Non-cumulative Key Figures
    also,
    There is also an explanation of advantages and disadvantages of using non-cumulative key figures in "How to handle inventory management scenarios in BW" white paper:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/how%20to%20handle%20inventory%20management%20scenarios.pdf
    Assign points if this helps!!
    Regards,
    Dhanya.

  • Intregarted Planning Design for Non-Cumulative Key Figures

    Hi,
    I have a requirement where i have to design a planning layout for a Invenotry Scenario (Using Non cumulative Key Figures).
    What should be the factors i should consider in my design specifically for non cumulative ke figures and how it is different from design for a regular (cumulative) key figure
    Thanks
    Rashmi.

    Thanks for your response. My requirement is to design a retail inventory planning application in which one of the KPI's planned is stock price which is a non cumulative key figure and i am trying to figure out how than can be planned if non-cumulative key figures are not allowed in planning
    Thanks
    Rashmi.

  • How to check with table for cursor..?

    How to check with table for cursor..?
    Here I have Table temp_final_plan
    Here i want to update if already exit...below is the procedure....
    CREATE OR REPLACE PROCEDURE spu_final_profit_plan
    AS
    -- Constant declarations
      ln_errnum number := 0;
    -- Variable declarations
       ls_errmsg app_errors.err_msg%TYPE;
       ls_appmsg app_errors.app_msg%TYPE;
       ls_appid  app_errors.app_id%TYPE;
    -- Cursor declaration for final_update_el
    CURSOR cur_final_update_el IS
        select '910' ent,
               '9127316' center,
               post_acct,
               sum(avg_mtd_01) sum_avg_mtd_01,
               sum(avg_mtd_02) sum_avg_mtd_02,
               sum(avg_ytd_01) sum_avg_ytd_01,
               sum(avg_ytd_02) sum_avg_ytd_02
          from mon_act_cypy
         where rec_type = 'A'
           and sum_flag = 'D'
           and yr = '2008'
           and substr(ctr_or_hier, 1, 2) = 'el'
           and ent || sub_ent in
               (select ent || sub_ent
                  from ent_ref
                 where roll_ent || roll_sub_ent = '999100')
         group by post_acct
        having sum(avg_mtd_01) <> 0
            or sum(avg_mtd_02) <> 0
            or sum(avg_ytd_01) <> 0
            or sum(avg_ytd_02) <> 0;
    -- Cursor declaration for final_update
    CURSOR cur_final_update IS
        select b.plan_ent b_plan_ent,
               b.plan_ctr b_plan_ctr,
               a.post_acct a_post_acct,
               sum(a.avg_mtd_01) sum_avg_mtd_01,
               sum(a.avg_mtd_02) sum_avg_mtd_02,
               sum(a.avg_ytd_01) sum_ytd_mtd_01,
               sum(a.avg_ytd_02) sum_ytd_mtd_02
          from mon_act_cypy a,
               plan_unit_tbl b
         where a.ent || a.ctr_or_hier = b.ent || b.ctr_or_hier
           and a.rec_type = 'A'
           and a.sum_flag = 'D'
           and a.yr = '2008'
           and b.hier_tbl_num = '001'
           and a.ent || a.sub_ent in
               (select ent || sub_ent
                  from ent_ref
                 where roll_ent || roll_sub_ent = '999100')
         group by b.plan_ent, b.plan_ctr, a.post_acct
        having sum(a.avg_mtd_01) <> 0
            or sum(a.avg_mtd_02) <> 0
            or sum(a.avg_ytd_01) <> 0
            or sum(a.avg_ytd_02) <> 0;
    -- Begin the procedure body
       BEGIN
    -- Insert / Update final profit plan for final_update query using cursor
       FOR rec_final_update_el IN cur_final_update_el
       LOOP
       EXIT WHEN rec_final_update_el%NOTFOUND;
       IF rec_final_update_el. THEN
          UPDATE temp_final_plan
             SET sum_avg_mtd_01 = rec_final_update_el.sum_avg_mtd_01,
                 sum_avg_mtd_02 = rec_final_update_el.sum_avg_mtd_02,       
                 sum_avg_ytd_01 = rec_final_update_el.sum_avg_ytd_01,       
                 sum_avg_ytd_02 = rec_final_update_el.sum_avg_ytd_02,       
           WHERE ent = rec_final_update_el.ent
             AND center = rec_final_update_el.center
             AND post_acct = rec_final_update_el.post_acct;
       ELSE
          INSERT INTO temp_final_plan VALUES(rec_final_update_el.ent,
                                             rec_final_update_el.center,
                                             rec_final_update_el.post_acct,
                                             rec_final_update_el.sum_avg_mtd_01,
                                             rec_final_update_el.sum_avg_mtd_02,
                                             rec_final_update_el.sum_avg_ytd_01,
                                             rec_final_update_el.sum_avg_ytd_02);
       END IF;
       END LOOP;
    -- Insert / Update final profit plan for final_update query using cursor
       FOR rec_final_update IN cur_final_update
       LOOP
       EXIT WHEN rec_final_update%NOTFOUND;
       IF rec_final_update. THEN
          UPDATE temp_final_plan
             SET sum_avg_mtd_01 = rec_final_update.sum_avg_mtd_01,
                 sum_avg_mtd_02 = rec_final_update.sum_avg_mtd_02,       
                 sum_avg_ytd_01 = rec_final_update.sum_avg_ytd_01,       
                 sum_avg_ytd_02 = rec_final_update.sum_avg_ytd_02,       
           WHERE ent = rec_final_update.b_plan_ent
             AND center = rec_final_update.b_plan_ctr
             AND post_acct = rec_final_update.a_post_acct;
       ELSE
          INSERT INTO temp_final_plan VALUES(rec_final_update.b_plan_ent,
                                             rec_final_update.b_plan_ctr,
                                             rec_final_update.a_post_acct,
                                             rec_final_update.sum_avg_mtd_01,
                                             rec_final_update.sum_avg_mtd_02,
                                             rec_final_update.sum_avg_ytd_01,
                                             rec_final_update.sum_avg_ytd_02);
       END IF;
       END LOOP;
    -- EXCEPTION handling section
       EXCEPTION
    -- Fire OTHERS Exception case by default
       WHEN OTHERS THEN
    -- ROLL BACK Transaction, if any failure
       ROLLBACK;
       ln_errnum := SQLCODE;
       ls_errmsg := SUBSTR(SQLERRM, 1, 100);
    -- Log the ERRORS into APP_ERRORS table using SPU_LOG_ERRORS procedure
       spu_log_errors(ln_errnum, ls_errmsg, ls_appid, ls_appmsg);
    -- End of the stored procedure
    END spu_final_profit_plan;
    [\pre]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    I'm not sure what you mean by, 'How to check with table for cursor..?' but I'll offer a comment on your Code Snippet. I think you want to know how to check if a record exists so you know if you need to perform an INSERT or an UPDATE.
    Here is a snippet of your code. I'll put my comments in "Comment" style in your code.
    -- Insert / Update final profit plan for final_update query using cursor
       FOR rec_final_update_el IN cur_final_update_el
       LOOP
    /* There is no need to test for %NOTFOUND since you are using Cursor FOR Loop! 
    ** This construct automatically exits when the last record is processed. */
       EXIT WHEN rec_final_update_el%NOTFOUND;
    /* Is this where you would like to know how to Check if the record already exist??
    ** I asked this because, 'rec_final_update_el.' is not valid syntax.  Are you looking for
    ** an Cursor Attribute or Method you can check here? 
    ** I would suggest a Primary Key or Unique Index on ENT, CENTER, and POST_ACCT
    ** on the TEMP_FINAL_PLAN table. Then simply perform an INSERT and code an
    ** Exception to UPDATE when you get a DUP_VAL_ON_INDEX exception.  Otherwise,
    ** you will need to simply run an Implicit or Explicit Cursor to test if the row exists and
    ** use this return value to determine if you should INSERT or UPDATE.  */
       IF rec_final_update_el. THEN
          UPDATE temp_final_plan
             SET sum_avg_mtd_01 = rec_final_update_el.sum_avg_mtd_01,
                 sum_avg_mtd_02 = rec_final_update_el.sum_avg_mtd_02,       
                 sum_avg_ytd_01 = rec_final_update_el.sum_avg_ytd_01,       
                 sum_avg_ytd_02 = rec_final_update_el.sum_avg_ytd_02,       
           WHERE ent = rec_final_update_el.ent
             AND center = rec_final_update_el.center
             AND post_acct = rec_final_update_el.post_acct;
       ELSE
          INSERT INTO temp_final_plan VALUES(rec_final_update_el.ent,
                                             rec_final_update_el.center,
                                             rec_final_update_el.post_acct,
                                             rec_final_update_el.sum_avg_mtd_01,
                                             rec_final_update_el.sum_avg_mtd_02,
                                             rec_final_update_el.sum_avg_ytd_01,
                                             rec_final_update_el.sum_avg_ytd_02);
       END IF;
       END LOOP;I hope I've answered your question, but if I haven't please provide more details so we can better understand your request.
    Craig...

  • Is there a solution for iphone 4 too like iphone5, It doesnt have tab Cellular. How to check call duration for total dialled calls (after resting) on a particular day?

    How to check call duration for total dialled calls (after resting) on a particular day in iphone 4?
    Is there a solution like iphone 5, i.e.Settings > Cellular.

    if the device is unlocked cellular is called mobile

  • Validity slice is not correct for non-cumulative cube

    Hello Expert,
    There are two non-cumulative cube, say cube1 and cube2. Cube2 has only one more dimension of PLANT than Cube1.
    Cube2 is copied from cube1 and change the char of validity.
    Cube1 & cube2 use the same fill data source. That is, first load with opening balance and second with delta.
    char of validity for cube1: calendar day & material
    char of validity for cube2: calendar day & plant.
    The query based on cube1 works well. To say cube2, the validity slice(in TXN RSDV or TBL /BIC/TCUBE2) is not correct. There is only one record which contains BLANK plant.
    There are plants in F table.
    I tried the following steps to recovery the validity slice, however, it made no sense.
    1) PGM RSDG_CUBE_VALT_MODIFY to rebuild the validity slice structure
    2) FM RSDV_VALID_RECREATE with I_REBUILD_FROM_FACT = 'X' to create validity slice from fact table.
    Would you please suggest?
    Thanks
    XY

    Hi XY,
    For sure, running the RSDV_VALID_RECREATE function module in SE37 will recreate the validity table. And you can use the parameter "X"  in the parameter I_REBUILD_FROM_FACT if the entire fact table should be  read.
    Also, to change the validity slice manually in tcode RSDV you should:
    - overwrite the column 'To mode' with a 'F', which mean Fixed
    - & then the 'Fixed to time' with your new value.
    There is a program which allows you to modify it: Program   > RSDG_CUBE_VALT_MODIFY
    At
    Nadja Xavier

  • How to load init for non cumulative values?

    Hi folks,
    anyone here, who can tell me how to load initial amounts from DSO to non cumulative values in InfoCubes?
    I found only poor documentation about this.
    Thanks!

    hi Timo
    you load initial of load as you do in the normal case only thing you have to keep in mind that before loading opening balance you have to UNCLICK  NO MARKER UPDATE from the infocube and compress the request ASAP as it will greatly effect your query performance.
    sanjeev

  • Archiving and reload possible for non-cumulative infocube 0IC_C03 ?

    Hello,
        Can the cube 0IC_C03 be archived and reloaded into another cube so that the data can be accessed via a multiprovider ? I read in help (http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm) that 'You cannot use the InfoCube together with another InfoCube with non-cumulative key figures in a MultiProvider'..
        While archiving seems doable, I have doubts on the reload. How do we report the data once it is archived from this cube.. Any ideas ?
    Thanks

    hi
    please check the below link.
    http://help.sap.com/saphelp_nw04s/helpdata/en/42/ead8d7b55e1bd2e10000000a11466f/frameset.htm
    Regards,
    madhu

  • Activate cube with non-cumulative error

    Hello Expert,
    There are two cumulative key figures and one non-cumulative key figure in one cube.
    To active the cube with the two cumulative key figure, it is OK.
    To include the non-cumulative key figure and activate the cube, there are errors.
    "/BIC/LCUBE (specify a primary key), When defining table fields, you omitted to specify a primary key."
    The non-cumulative key figure uses the other key figure as inflow and outflow.
    Do you know what has happened?
    Thanks
    XY

    hi,xy chen
    before active the Cube,you should goto menu "Extra" and click on 'Maintain non-cumulative values',here you can choose fields for the Validity table or you do not choose(it's optional,for instance you can find search How to Handle Inventory Management Scenarios in BW.pdf in google).Then you can active the Cube.
    holp it helps!
    best regards.

Maybe you are looking for

  • Hyperlink problem when exporting to PDF

    We are using Crystal Reports XI R2 and having a problem when exporting a report to PDF that contains a Hyperlink to "A File".  The hyperlink works correctly when previewed inside Crystal but when it is exported to a PDF the text does not appear to sh

  • "Invalid Currency" in JE

    Dear All, When posting a JE in foreign currency  (USD)for a BP, the client is getting an error "Invalid Currency" even though the account currency is set to "USD" in the Chart of Accounts. The corresponding contra account is set to 'Multi Currency".

  • War application in weblogic6.0

    i have a war application with the following directory structure.(for jsp tag libraries) .jsp file WEB-INF/.jsp file, .tld file, web.xml. WEB-INF/classes/tagclass. i am able to deploy this file in weblogic 6.0, but what extra settings are required to

  • IDE: automatic start of workflow for switch document

    Hello guys, Please, can someone tell me how do you automatically start the distributor workflow (WS20500195) without using SWUD transaction? I created the switch document ( switch view: distributor, switch type: end of supply), but the workflow won't

  • Won't start from Start up Disk- Dead iMac - help!!

    Hi, My iMac at work died today, first it crashed and then the hard disk began to spin and then the fan cut in and it sounded like a jumbo taking off. I used the power switch to turn off, waited a minute turned it back on and it then hung at the blue