BI 7 Inventory Transformations  0IC_C03

Hi,
any body implemented Inventory managment in BI 7 flow.
we are implemenating Inventory managment in BI 7 flow. issue is when installling transformations most of the keyfigures are not mapped, do we have to map/ write rouitnes, content will not give rouitnes for keyfigures.
transformations for 2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM.
can any one please help on this. transformations with routines are much helpful.
Regards
Raj

Raj,
Check note: [Note 1073268 - SAP Best Practices for BI V2.70|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1073268]
BI Scenario Inventory Analysis
Symptom:
You have activated InfoCube 0IC_C03 in dataflow before. The dataflow is available from the InfoCube downwards to the InfoSources in 7.0 technology (transformations). However there is no connection between the InfoSources and the DataSources, because all DataSources have been activated as 3.x DataSources.
Reason:
The Business Content for the InfoCube 0IC_C03 has changed and now uses the 7.0 technology for data flow.
Solution:
1. Migrate the follwing DataSources to 7.0 DataSources:
2LIS_03_BX
2LIS_03_BF
2LIS_03_UM
In transaction RSDS enter the relevant DataSource and the source system. From the menu choose DataSource -> Migration 3.x DataSource -> DataSource.
2. Reactivate the InfoCube 0IC_C03 in dataflow before.
3. Check the transformation TRCS 2LIS_03_BF_TR -> CUBE 0IC_C03. If it is not active, check if there is an error in the start routine. If this is the case, refer to SAPNote 1052648, section "Start Routine" for a solution.
Srini

Similar Messages

  • Inventory Management (0IC_C03) cube

    When I carry out delta loads to the Inventory Management (0IC_C03) InfoCube do I need to compress these delta loads with No Marker Update? Thanks

    hi Nitish,
    1. Compressing the request containing the opening stock that was just uploaded. Make
    sure the "No marker update" indicator is not set. Please consider note very carefully
    643687 before you carry out the compression of requests in stock InfoCubes!
    2. Loading the historical movements into the InfoCube 0IC_C03 via the DataSource /
    InfoSource 2LIS_03_BF. Choose the upload mode "Initializing the delta process"
    here.
    3. After successfully uploading the historical material movements, the associated
    request has to be compressed. You must make sure the "No marker update"
    indicator is set. This is necessary because the historical material movements are
    already contained in the opening stock. We’ll look more closely at markers later on.

  • Selective Deletion on Inventory Cube 0IC_C03 via Calendar Day

    Hello Group
    I am trying to do a selective delete to our inventory cube 0IC_C03 and found there is not an option to select day.
    Does anyone have any thoughts on how do delete using day? Please note that my cube has been compressed and I do not have a request in the cube.
    Thanks
    Frank

    Hi Frank,
    REPORT  ZRSDRD_SEL_DELETION                     .
    DATA:
        l_thx_sel   TYPE rsdrd_thx_sel,
        l_sx_sel    TYPE LINE OF rsdrd_thx_sel,
        l_s_range   LIKE rsdrd_s_range,
        l_t_range   TYPE rsdrd_t_range,
        l_t_msg     TYPE rs_t_msg.
    ******************* 0CALDAY *****************
    l_s_range-sign   = 'I'.
    l_s_range-option = 'EQ'.
    l_s_range-low    = '20030308'.
    *l_s_range-high   = .
    l_s_range-keyfl  = 'X'.
    APPEND l_s_range TO l_t_range.
    l_sx_sel-iobjnm   = '0CALDAY'.
    l_sx_sel-t_range  = l_t_range[].
    INSERT l_sx_sel INTO TABLE l_thx_sel.
    CLEAR l_s_range.
    REFRESH l_t_range.
    ************** 0PLANT **********************
    l_s_range-sign   = 'I'.
    l_s_range-option = 'EQ'.
    l_s_range-low    = 'PLNT'.
    *l_s_range-high   = .
    l_s_range-keyfl  = 'X'.
    APPEND l_s_range TO l_t_range.
    l_sx_sel-iobjnm   = '0PLANT'.
    l_sx_sel-t_range  = l_t_range[].
    INSERT l_sx_sel INTO TABLE l_thx_sel.
    CLEAR l_s_range.
    REFRESH l_t_range.
    ************** 0MATERIAL ****************
    l_s_range-sign   = 'I'.
    l_s_range-option = 'EQ'.
    l_s_range-low    = 'MATERIAL'.
    *l_s_range-high   = .
    l_s_range-keyfl  = 'X'.
    APPEND l_s_range TO l_t_range.
    l_sx_sel-iobjnm   = '0MATERIAL'.
    l_sx_sel-t_range  = l_t_range[].
    INSERT l_sx_sel INTO TABLE l_thx_sel.
    CLEAR l_s_range.
    REFRESH l_t_range.
    CALL FUNCTION 'RSDRD_SEL_DELETION'
         EXPORTING
              I_DATATARGET      = 'ZICRT_C37'
              I_THX_SEL         = L_THX_SEL
              I_AUTHORITY_CHECK = 'X'
              I_THRESHOLD       = '1.0000E-01'
              I_MODE            = 'C'
              I_NO_LOGGING      = ''
              I_PARALLEL_DEGREE = 1
              I_NO_COMMIT       = ''
         CHANGING
              C_T_MSG             = L_T_MSG.

  • Difference between Inventory cube 0IC_C03 and 0CP_IC_C1

    Hi Gurus
    I'd like to ask what's the difference between this 2 cubes in inventory? 0IC_C03 and 0CP_IC_C1 ? Any help will be much appreciated. Thanks in advance
    - Kit

    Hi,
    Well I am not an expert on Inventory but this is what I know:
    0IC_C03 - LO Cockpit cube - Standard Inventory qty and values. This can be used for all purpose on a generic basis. This is not customized for any specific Industry sector. A standard ECC can use this as well as Retail can use this.
    0CP_IC_C1 - This is also an Inventory cube containing value and quantities but this is more specifically designed for CP industry sector (Consumer Products). Here the BW transaction keys are different meaning that events/movement types specific to CP industry transactions will generate these transaction keys which gets updated to BW.
    Also the cube 0CP_IC_C1 KPIs are average figures on the stock quantities and values (Exception Aggregation: Average Over Calendar Days). Whereas in 0IC_C03 the KPIs (NCKFs) are based on last value (Exception Aggregation: Last for Calendar Days)
    Therfore if you are not aiming at Consumer Products Industry specific implementation, I would recommend 0IC_C03 cube.

  • Inventory Management (0IC_C03) - 0TOTALSTCK

    Good Day,
    Inventory cube 0IC_C03 is getting data, but all non-cumulative KFs (for example - 0TOTALSTCK0) are empty in the Report (Stock Overview - 0IC_C03_Q0013). 
    Background info:
    - The document that outlines the steps in R3 and BW was followed to load BX, BF, following the rules around marker updates.
    - This is a new instance of BW.
    - Standard stock overview query 0IC_C03_Q0013 does not have any filters and was not manipulated in any way.
    Thank You very much!  Any insight would be really appreciated...

    Hi,
    Pl check following link step by step it explains you everything in terms of Non cumulative KF as well.
    Check all the definitions are correct as mentioned there.
    Pl check any mapping is missing at Infoprovider level hence data is not coming.
    Check at DSO and cube level whether data is getting populated or not?
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366?quicklink=index&overridelayout=true
    Thanks and regards
    Kiran

  • Business Content Inventory Management (0IC_C03) Cube

    I am thinking of adding a data staging ODS to our Inventory Management model.  However, I wanted to check whether the delivered cube 0IC_C03 is aggregated or whether it is a representation of the R3 extraction.  If the latter is the case I do not see the purpose of an additional ODS layer.  Could anyone pass their thoughts? Thanks

    hi Niten,
    check oss note 581778-ODS capability of extractors from Inventory Management
    Symptom
    Data is not updated into the ODS when you load certain data records of the 2LIS_03_BF extractor.
    Other terms
    ODS, 2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 0STORNO, ROCANCEL, RODMUPDMOD, 0RECORDMODE, Inventory Management, 0IC_C03,
    Application 03, Logistics Extraction Cockpit, LBIW
    Reason and Prerequisites
    The 2LIS_03_BF extractor does not return any "connected" after and before images, as in the SD extraction, for example.
    Originally, the extractor was only designed for updating into an InfoCube. The extraction method was converted from the "D" delta process to "ABR1" with PI 2000.1 patch 4, or PI-A 2000.1 patch 4 so that it could be updated into an ODS object (see notes 322303, 385703 and 323811).
    If documents are canceled in Inventory Management, a new document is generated (new document and item number).
    This type of operation is transferred into BW with the "ROCANCEL" field set to 'X'. This results in the necessary inversion of quantities or value key figures. A new record is generated for this in the ODS (the "preceding document" has another key).
    Example:
    ODS key: Doc.
    Movement data:
    Document   Item    Document year   Movement type     Qty     ROCANCEL
    4711       1       2002             101              +100
    4712       1       2002              102              -100     X
    ODS contents:
    Document   Item.   Document year   Movement type    Quantity
    4711       1       2002             101                 +100
    4712       1       2002                                   -100
    The "Movement type" field was set to "initial" in the data record for document "4712" by the processing during the ODS update.
    Document 4712 is a before image (0RECORDMODE = 'X') for the ODS. Therefore, this data does not arrive in the ODS. Nevertheless, the before image (document 4712) does not have any context with the after image (document 4711) because there are different keys (document/item/document year). The SAP R/3 inventory management controls these activities with new material documents and (reversal) movement types.
    BW technology note no. 747037 provides more information.
    Solution
    You have two options to evaluate cancellations or operations which contain reversal movement types and ROCANCEL = "X" in the ODS:
    1. Implement a start routine
    Insert the following code into the start routine of your update:
    ODS key: Material doc.|Item number|Calendar year
    BEGIN******************************
    LOOP AT DATA_PACKAGE.
      if DATA_PACKAGE-recordmode eq 'X'.
        DATA_PACKAGE-recordmode = ''.
        modify DATA_PACKAGE.
      endif.
    endloop.
    END********************************
    2. Change the transfer rules
    With the transfer rules, do not assign the "ROCANCEL" DataSource field to the "0RECORDMODE" InfoObject in the InfoSource. As a result, only records with "0RECORDMODE" = ' ' are transferred to the ODS. For the ODS, the after images whose characteristics or key figures that are set to overwrite, are not deleted.
    Other special features when updating the extractors of the inventory management into ODS objects:
    1. 2LIS_03_BF and 2LIS_03_UM
    a) ODS capability
    For more information, see notes 322303, 323811 and 385703.
    b) Key creation
    For 2LIS_03_BF, see note 417703.
    The following keys are available for 2LIS_03_UM:
    1. MCMSEG-BUKRS
    2. MCMSEG-BELNR
    3. MCMSEG-GJAHR
    4. MCMSEG-BUZEI
    Field no. 4 is not delivered as standard in the extract structure, but it can be added using the Logistics extract structures Customizing Cockpit.
    Field no. 1 may not be included in the relevant organizational structure.
    2. 2LIS_03_BX (up to and including 3.0B 2LIS_40_S278)
    The dynamic stock calculation from stocks (2LIS_03_BX) and movements (2LIS_03_BF) is only possible with (non-cumulative) InfoCubes.
    Using ODS technology is only useful in this context for:
    - an Enterprise DataWarehouse layer
    - the realization of a snapshot scenario:
    See the How to paper for this topic at:
    -> http://service.sap.com/bw
    -> left navigation area: SAP BW InfoIndex
    -> info index: N ("Non-cumulatives") ->
    "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
    Use note 773823 to update the 2LIS_03_BX InfoSource into an ODS.
    Note also that you cannot update any key figures into an ODS object (see notes 752492 and 782314).

  • Change in Inventory Infocube 0IC_C03

    Hi All,
    We have several reports on Inventory cube 0IC_C03 and we have gone live before one year , so we are having around one year data in production for the cube.
    Now, we have to develop a report on the same cube. But user wants to add one char. "MRP Type" in the report. Now. Standard 0IC_C03 does not have this char.
    I have checked my system and found one Infoobject "0MAT_PLANT" having MRP Type as it's Navigational attribute.
    Now, i want to add this infoobject(0MAT_PLANT) into the current cube. But, i do not want to delete the data of the cube
    Also, one important thing i want to share is , we have done "Roll up" and "compression" for the same cube in production, and that is the reason i do not want to delete data from Inforcube.
    I want to have some solution for my problem as it is a burning issue for the team .
    Please suggest.
    Regards,
    Macwan James.

    hi James,
    Try Virtual Char... for more info go through below link.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e051fda8-71a9-2a10-ac9e-8d17414a8c8c
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/60e34f63-f44c-2c10-488e-c89b04e0ca7c
    ...In case you want your Virtual Char to be user input enabled... please refer
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how%20to%20use%20variable%20time%20references%20in%20currency%20conversion
    You can also refer to. - for below link you'll need SAP Marketplace ID
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700004790632001E
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700009299362001E
    Hope this helps.
    Regards
    Raj

  • Inventory Transformation error

    Hi All
    I have loaded the Inventory data to the infocube 0IC_C03
    No my req is i need to add the infoobject 0VALSPECST in to cube. I done this now i am trying to activate the transformation but it is showing Start routine syntax errror
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    "SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE".
    Can any one help me on this....
    Thanks in advance
    Raju

    Hi
    Remove that infoobject and try again..
    i think that it may be some system error..
    Refer to this thread..
    Re: How to add the field in infocube?
    It may help..
    Regards
    gaurav

  • Extend Inventory Management (0IC_C03) with new field MSEG-INSMK

    Dear Experts, We are using Business Content InfoCube "Material stocks/movements" (0IC_C03) in Area "Inventory Controlling/Inventory Management" in BW. We are using following Business Content DataSources: Stock Initialization for Inventory Management              2LIS_03_BX Goods Movements From Inventory Management        2LIS_03_BF Revaluations                                                            2LIS_03_UM Everything works fine with delta load till now. Now we have a new requirement so that we have to fill additionally the R/3-Field MSEG-INSMK in existing Inventory Management InfoCube (0IC_C03). The Business Content DataSource (2LIS_03_BX/BF/UM) doesn't provide R/3-Field MSEG-INSMK and I don't find any other Datasource for the R/3-Field MSEG-INSMK ("Document Segment: Material" - Stock Type). How can we extend the InfoCube 0IC_C03 with the R/3-Field MSEG-INSMK? Should I define a new Generic Datasource based on the table MSEG to extract the field INSMK. The table MSEG is very large. What would be Delta-Specific Field for Generic Delta? I would load the data from generic DataSource into a new DSO. And I can read the field MSEG-INSMK per Look-Up from the DSO in the transformation to the InfoCube 0IC_C03. Is this the solution? Many Thanks Moha

    2LIS_03_BX cannot be enhanced. There is an SAP note that says enhancing this Datasource is not supported.
    2LIS_03_BF can be enhanced though, and the process is just like enhancing any other LO Datasource.
    So you can include the new field in the cube, enhance BF and load to the cube. With this, you will be able to report the INSMK field on the goods movements. But as INSMK is not present in BX, you will not be able to report the INSMK field on stock position reports.

  • Customization of Inventory Cube - 0IC_C03

    Hi gurus,
    I need to implement the Inventory for my client using the Std cube 0IC_C03.
    Here the client wants me to take the Total stock as the sum of the following stocks in MARD Table
    LABST - Unrestricted
    UMLME - Stock in Transfer
    EINME  - Restricted Use
    SPEME - Blocked
    RETME - Return              
    In the Standard Content we are considering only Stock in transfer & Blocked stock.
    Please help me in suggesting what are the changes needed in Transformations for both 2LIS_03_BX and 2LIS_03_BF.
    Thanks in Advance
    Seshu

    Hi ,
    The fields LABST - Unrestricted
    UMLME - Stock in Transfer
    EINME - Restricted Use
    SPEME - Blocked
    RETME - Return
          The fields other than blocked and Stock in transfer are not present in the datasources  2LIS_03_BX and  2LIS_03_BF .
      If you need these fileds , you can go ahead with a function module datasource based on MARD , MSEG tables from where you can take these fields directly .
    You can also refer to the links below for other options
    Datasource for MARD table
    Re: MARD Table  -  Not giving Stock in Transit Value
    If in case the relevant fields are not seen in the datasource , you can go to transaction LBWE, CLICK ON 03 :Inventory Controlling(your case), click on maintainence tab and just drag the required fields to the left .
    Also you need to delete and fill the setup tables after this step.

  • All fields are not mapped in transformation 0IC_C03 to 2LIS_03_BF_TR

    I have replicated BI7 data sources of 2lis_03_BF,BX & UM from ECC. All the infosources are BI7 infosources.After installing the BI Content for 0IC_C03, infosource 2LIS_03_BF_TR is not active.When I am trying to activate the transformation it is showing a error in START ROUTINE & also all fields are not mapped.
    Please suggest a solution.
    Thanx in advance.
    Edited by: Aritra on Nov 28, 2011 11:37 AM

    Hi,
    i think you have done some modification manually(either added something and deleted something in transformation) thats why code isn't maching with standard sorce package.
    so to resolve this error just remove  changes you manually did. or remove that code and again create start routine and paste the code which u need.
    Thanks & Regards,
    NIKHIL

  • Inventory cube 0IC_C03 ,Stock on particular date

    Hi All,
       We are trying to get the stock on a particular date using cube 0IC_C03 ,but we are unable to get the total stock on a given date.
    1)Ex: I want stock on 01.12.2009 ,but in the query output I am getting  null values.
      I am only getting the total stock quantity on the loaded date for ex:04.01.2010(which is my data loading date in to the cube).
    2)And when we restrict 0calday with <=01.12.2009 ,i have to get the total stock till 01.12.2009
    Thanks&regards,
    Sunitha

    Hi,
    Check
    Treatment of historical full loads with Inventory cube
    Setting up material movement/inventory with limit locking time
    1)Ex: I want stock on 01.12.2009 ,but in the query output I am getting null values.
       I am only getting the total stock quantity on the loaded date for ex:04.01.2010(which is my data loading date in to the cube).
    For 2LIS_03_BX it will give the extracted date only
    2)And when we restrict 0calday with <=01.12.2009 ,i have to get the total stock till 01.12.2009
    try with below options.
    Use :
    0VALSTCKVAL   " for Value
    0VALSTCKQTY   " for Qty
    0CALMONTH        " for Month
    Use the above combinations in New Selections in columns and go it.
    For Qty Opening:
    New Selection bad drag abd drop following things
    0VALSTCKQTY   " for Qty
    0CALMONTH        " for Month and restrict with less then or equalto option variable (single value, user input)  and set the offeset
                                   value = -1 bcoz if user will give 12.2009 , so it will display 11.2009 closing stock, this is opening for 12.2009.
    For Qty Closing:
    New Selection bad drag abd drop following things
    0VALSTCKQTY   " for Qty
    0CALMONTH        " for Month and restrict with less then or equalto option variable (single value, user input) .
    In the same way build for Value and other Keyfigures on 0IC_C03.
    And
    Drag & drop
    0MATERAIL
    0PLANT  " Give some Input Variable.
    See the steps.
    Treatment of historical full loads with Inventory cube
    Setting up material movement/inventory with limit locking time
    If it is BI 7 then for BX in in DTP in Extraction Tab you need to select Extacrion mode = NON-Cumulative option.
    Thanks
    Reddy

  • Inventory Management (0IC_C03) Business Content queries

    I have the following queries which are delivered when I activate 0IC_C03.  The queries below have also been activated as part of the model.
    Is there any additional queries which should/can be activated against this InfoProvider and of the list below are any redundant? Thanks
    Blocked Stock
    Consignment Stock at Customer
    Inventory Turnover
    Quantities of Valuated Project Stock (as of 3.1 Content)
    Quantities of Valuated Sales Order Stock (as of 2.1 Cont.)
    Receipt and Issue Customer Consignment Stock
    Receipt and Issue of Blocked Stock
    Receipt and Issue Quality Inspection Stock
    Receipt and Issue Stock in Transit
    Receipt and Issue Vendor Consignment Stock
    Scrap
    Stock in Quality Inspection
    Stock in Transit
    Stock Overview
    Stock Overview (as of 3.1 Content)
    Stock Range of Coverage
    Valuated Stock
    Valuated Stock (as of 3.1 Content)
    Vendor Consignment Stock

    hi Niten,
    by choosing that 0IC_C03 and using grouping 'in dataflow afterward' in business content activation, you should get all the queries.
    you can cross check in rsa1->metadata repository->local object (business content).
    in sap help
    http://help.sap.com/saphelp_nw2004s/helpdata/en/77/65073c52619459e10000000a114084/frameset.htm
    (expand left node)
    hope this helps.

  • Inventory Management 0IC_C03: Beginning and ending inventory

    Hi Gurus
    My report is based on Inventory Management cube and I have a requirement where in I need to show Begining Inventory and Ending Inventory for Plant per Period.
    There is no KF for Beginning Invin SAP standard model in inventory management cube (0IC_C03 cube), so I thought to restricting total quantity by Fiscal period and Offset by minus one to get begining inventory.
    Here is my report layout:
    I have got : Period , Plant in rows and Beginning and ending inventory in Columns.
    Desired Output:
    Fiscal Period | Plant |  |  Begining Inventory | Ending Inventory.
    03/2009        |  1001 |    100                       |  50
    Actual Report output
    Fiscal Period | Plant |  |  Begining Inventory | Ending Inventory.
    02/2009        |  1001 |                 100          | 
    03/2009        |  1001 |                                |  50
    So basically report is being split on two lines for current and previous (due to restriction in begining period : Offset =-1 on period).
    Question is how to achieve both begining and ending inventory for a period in same line.
    Thanks in avdance for help and time
    SA

    HI Naveen
    Thanks for the reply. Non *** KF are already being used and Standard SAP model is being followed. Problem is not with back end but with frontend. Data coming on the report is fine but problem is how to show them on same line. Remember Beginning inventory for current open is ending inventory for previous month and  in SAP content there is no KF called as begining inventory. Basically data from two consecutive periods (current and previous one) needs to be on same row of report, but they are coming on different rows if we have period in drilldown by period. this makes sense but how to overcome this.
    This, We have all the correct data but facing issue while displaying that on frontend.
    Thanks
    Sorabh
    Edited by: Sorabh on Mar 23, 2009 5:01 PM

  • Inventory Management 0IC_C03 customizations

    Dear Experts,
    I have a task in hand to implement Inventory Management in SAP BW 3.5. Now, this is the first time that we will be implementing anything related to Logistics and I havenu2019t done so earlier in my support projects. I have got 10 hrs of downtime.
    I need to fetch the report for both Trading as of now.
    The fields needed in the report by the customer are:
    Plant
    Plant Description
    S. Loc.
    S.Loc. Description
      Opening Stock Qty,
      Opening Stock Value,
    Receipts against PO Qty,
            Value,
    Receipt against STO  Qty,
            Value,
    Receipt against return SO  Qty,
         Value,
    All Other Receipts  Qty,
          Value,
    RevaluationValue,
    Miro Differences,
    Issue against SO  Qty,
          Value,
    Issue against STO Qty,
            Value,
    All Other Issues Qty,
          Value,
      Closing Stock Qty,
               Value,
    Book Inv Qty,
    Physical Inv Count.
    I am planning to define these as Zkey-figures and write routines in update rules based on processing keys to capture each qty and value separately.
    My questions are:
    1) What are the fields from above that can be pulled from standard BI Content Reports (if possible, please specify which report)? OR fields (or combination of fields) that are already in the cube?
    2) For every above field, customer has given standard movement types.
    For ex: for Receipts against PO = Mov Types 101,105,123,162 (Doc Type IN/IM)
                for Receipt against STO = Mov Types 351, 352 (Doc Type UB)
    But when brought in BI, all routines are based on processing keys (BW Transaction key). Where can I find mapping of each processing key to the corresponding movement type?
    If you know which processing key can be used for above fields, please let me know.
    3) What are the other fields that need to be considered in routines. If possible please specify field wise.
    4) Should I extend the 0IC_C03 with these new custome KFs creating a new zcube or should I add only required fields in zcube.
    If I follow the latter, will there be any impact on standard BF/UM runs as in If I load till PSA and from PSA I follow my customized update rules terminating into my customized cube?
    Thanks friends.

    BJ,
    My questions are:
    1) What are the fields from above that can be pulled from standard BI Content Reports (if possible, please specify which report)? OR fields (or combination of fields) that are already in the cube?
    ~ You will get fields from the Cube only.
    2) For every above field, customer has given standard movement types.
    For ex: for Receipts against PO = Mov Types 101,105,123,162 (Doc Type IN/IM)
    for Receipt against STO = Mov Types 351, 352 (Doc Type UB)
    ~ Check this Table in Source system for BW Keys : TMCLVBW
    But when brought in BI, all routines are based on processing keys (BW Transaction key). Where can I find mapping of each processing key to the corresponding movement type?
    If you know which processing key can be used for above fields, please let me know.
    Check this table
    3) What are the other fields that need to be considered in routines. If possible please specify field wise.
    That depends upon your requirement in the report or Check the standard Dcoument for Inv management in SDN search.
    you will get lot of help.
    4) Should I extend the 0IC_C03 with these new custome KFs creating a new zcube or should I add only required fields in zcube.
    If I follow the latter, will there be any impact on standard BF/UM runs as in If I load till PSA and from PSA I follow my customized update rules terminating into my customized cube?
    ~Best Practice and even SAP Recommends Make a ZCUBE and then enhance or customize to fullfill your rek.
    No impact follow IM steps for BW.
    Make sure you keep these things in Mind:
    There are 3 SAP delivered transactional data sources for stock management.
    2LIS_03_BX : Always needed to carry the initialization of the stocks.
    2LIS_03_BF :  Initialize this in source if you need historical data else an empty init can be done for this to load only future delta records. If the Source system is new then no need to do an initialization. 
    2LIS_03_UM : Only needed if revaluations are carried out in Source. This data source is helpful if adjustment in material prices is done time to time otherwise it wonu2019t extract any data.
    2.  Check list for source system. Needs to be carried out before initialization of the above 3 data sources .
    A.   Table TBE11 : Maintain Entry u2018NDIu2019 with text u2018New Dimension Integrationu2019 and activate the flag(Note 315880)
    B.   Table TPS01 : Entry should be as below(Note 315880)
    PROCS u2013 01010001
    INTERFACE  - SAMPLE_PROCESS_01010001
    TEXT1 u2013 NDI Exits Active
    C.   Table TPS31 : Entry should be as below(Note 315880)
    PROCS u2013 01010001
    APPLK  - NDI
    FUNCT u2013 NDI_SET_EXISTS_ACTIVE
    D.   Tcode u2013   MCB_  
    In most cases you need to set the industry sector as u2018standardu2019. For more info please see Note 353042
    E.    Tcode u2013  BF11
    Set the indicator to active for the Business warehouse application entry. This entry may needs to be transported to the production system. (Note 315880)
    3.  After running the setup data, check the data for the fields BWVORG, BWAPPLNM, MENGE. If no data available in these fields then some setting mentioned in the above checklist are missing in R/3. Correct the issue and rerun the setup data.
    4.  Data staging with DSO for BX extractor is not allowed. Data should directly load from extractor to Cube only once. Choose the extraction mode as u2018Initial Non-cumulative for Non-cumulative valuesu2019 in the DTP.
    5.  DSO is possible for BF. If you are creating a standard DSO then choose the fields MJAHR,BWCOUNTER,MBLNR,ZEILE as key fields. Some of these fields wonu2019t be available in the standard data source but the data source can be enhanced using LO Cockpit (LBWE) to add these fields. In addition to these other fields depending upon the DSO structure is also possible.
    Note  417703 gives more info on this.
    6.  Point-5 is valid for UM also. The Key fields could be a combination of MJAHR,MBLNR,ZEILE,BUKRS  fields. Note 581778 
    7.  Data load to the cube should follow the below process
    A.      Load the BX data. Compress the request with stock marker(uncheck the marker option).
    B.      Load the BF and UM init data. Compress the loads without the stock maker(Check the marker option).
    C.      The future delta loads from BF and UM should be compressed with Stock marker(uncheck the marker option).
    8.  If in future the cube needs to be deleted due to some issues then the load process should also be carried out as above. (only init of BF and UM should be loaded first and then the deltas should be processed)
    9.  To check the data consistency of a Non cumulative cube the standard program SAP_REFPOINT_COMPLETE can be used. To check the compression status of the cube the table RSDCUBE can be refered. Before the compression of BX request, the u2018REFUPDATEu2019 field should be blank and after the compression the value should become u2018Xu2019. Check Note 643687 for more info.
    10. After BX data load to cube the data wonu2019t be visible by LISTCUBE. Only after compression the data can be seen by running a query on the Non cumulative cube.
    ~AK

Maybe you are looking for