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.

Similar Messages

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

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

  • Standard Business Content Queries not found

    Hi all
    As i was installing the business content queries for the CRM Analytics, I have found all the Queires except two queries. When checked in the SAP Help portal i can see these two queries as newly added to the list. But they are not available in the Business Content queries list.
    I am working on BW 3.5 and queries which i didnt find are
    0MKTG_C01_Q7001 and 0CSAL_C12_Q002
    Any help is greatly appreciated.
    regards
    vijaykumar

    hello vijay,
    for each patch level of each BW version I believe a supporting OSS note is released.Please search in OSS notes stating as 'BW 3.5 patch level XY' or raise an OSS message witb this query.
    In the help page for the new BC queries,does it state any detail about the required version/patch of BW?
    Usually systems are kept 1-2 patch levels behind the latest SAP released patch level.
    My system is at 3.5 patch 17.
    I would suggest u bring system atleast to 16 or 17 as 10 is quite old patch level.
    cheers,
    Vishvesh

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

  • 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

  • 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 InfoCube Partitioning (Recommendations)

    Hello Everyone,
    I have gone through most of the postings available on SDN and other white papers related to Inventory management implementation.
    I did not get enough information and most of the information has given me both yes and no answers for partioning of the InfoCube.
    I am looking for,
    Can you please recommend what is the best practice for Physical and logical partitioning of 0IC_C03 InfoCube.
    We have Calendar Day, Calendar Month, Calendar year in time characteristics and plant as the validity characteristic.
    I have gone through couple of white papers which recommend avoid using the time characteristics for partitioning and rather use plant or territory grouping as applicable.
    But some forum postings I have gone through mention that the partitioning has been done on time characteristics.
    What is the impact of marker update and the paritioning being done on the time characteristics.
    So, can you please let me know what the best practice would be and the reason for partitioning in the way whichever you recommend.
    I really appreciate your input.
    Thanks
    Dharma.

    Hello Naveen,
    Thanks for the prompt response.
    I understand that the partitioning by time characteristics is not useful because of how the data is accessed.
    When I mentioned that the partitioning is considered on Plant or Territory.
    I mean to use the logical partitioning where I am thinking of loading in my data based on the territory field which would then be grouped into regions.
    In this case it can be Region 1, Region 2 and Region 3
    Where
    Region 1 --> Data from Territories 1,2,3
    Region 2 --> Data from Territories 4,5,6
    Region 3 --> Data from Territories 7,8,9
    Once this has been done, I am planning of implementing the entries in RRKMULTIPROVHINT table to accordingly split the queries from Multiprovider.
    The reason being most of the reporting is done at the territory level which in turn would help re-route the queries to appropriate part provider.
    I am more worried about the physical partitioning for an InfoCube in order to have good database breakdown.
    Thanks
    Dharma.

  • 3.x Update rules does not appear in std 0IC_C03 business content

    Hi,
    We are using BI 7.0.
    When trying to install business content update rules for the cube 0IC_C03 (DATA FLOW BEFORE), the three update rules are not appearing in the screen for installation.
    Instead , I'm getting three Transformations !! But I need 3.x Update rules only.
    Note : The data source used are of type 3.x ONLY.

    Hi,
           When you Create the update rules  manually by default Keyfigures will be  set to no-update. You have to propose the rules as you want and it depends on the requirement. And for 0IC_C03 Inventory Cube, almost all the Kfigs are updated based on Routines.
    So it is better to Install from BI Content.
    Replicate your Datasources. Then Install Transfer rules,and then Install update rules.
    Hope this Helps,
    Regards
    Karthik

  • Inventory management: Validy dates in queries???

    Hi experts,
    We have BW 7.0.
    I have loaded data on 04.03.2010 with BF- and UM-datasources and compressed it correctly.
    When I now look into the validy table for plant 0001 there is a validy range from 03.07.1997 to 08.02.2010.
    But when I start a query for 09.02.2010 system says "no data found".
    The document "How To Handle Inventory Management Scenarios in BW" says that I should show the result in parenthesis!
    What is up here?
    But I don't want to update this validy table!!!
    Pls help!
    KR,
    Raimund
    Text in  document:
    ...For example, if data with document data was loaded into the
    InfoCube with values from 01.01.2002 to 15.02.2002 (assigned to the respective time
    characteristic), the validity interval is also determined by these two date values. You can
    extend the intervals by maintaining the table (transaction RSDV). Stock balances are
    displayed for requests that relate to this period. If you start a query that requests the
    stock balance for 16.02.2002 or later, the result is displayed in parenthesis (a blank
    value is displayed in BW 2.0B and 2.1C), since it lies outside the validity area (providing
    that the validity table was not manually extended using transaction RSDV)....

    Hi,
    Hi,
    Use 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM to 0IC_C03 Cube and design the report.
    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.
    See this thread related to Inventory.
    Re: Inventory Mangement steps - questions
    Thanks
    Reddy
    Thanks
    Reddy

  • Business Content -- Queries

    Hi everyone,
    I am looking for a easy way to look for Business Content since I am not yet connected to a BW system (I need to do this through the SAP site)
    I have found a great deal of content except the following:
    ERP-MM-SRV
    SRM-EBP
    SRM-CCM
    Could someone give me pointers in where to search on the site...?
    Thanks a lot!!
    Cheers,
    Andrew

    Andrew
    SRM
    http://help.sap.com/saphelp_nw04/helpdata/en/36/7aeb3cad744026e10000000a11405a/content.htm
    SCM-MM/Procurement/Inventory
    http://help.sap.com/saphelp_nw04/helpdata/en/9d/ea86206cf2e445a5b10ee1bf098c96/content.htm
    SRM-EBP
    http://help.sap.com/saphelp_nw04/helpdata/en/76/68073c52619459e10000000a114084/content.htm
    Hope this helps
    Thnaks
    sat

  • 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

  • Inventory management 0IC_C03

    hi gurus....
    we are working with the standard infocube 0IC_C03, but we are having some problems with the transformations and with the standard queries.... when we are creating the transformation the only time characteristic that we can see is the 0calday  at the target we are missing the 0calmonth, 0calyear and the 0calweek that the standard infocube has it self..... if we run the standard queries a message error appears about the time characteristics (there are no matching rule at the transformation because the only time characteristic we have at the target is de 0calday (note: the infocube has them all but when we create the transformation the only time characteristic we have to match is the 0calday).
    if we create a manual query just as a copy of the standard one the information appears....
    any comments about this issue? any note? any experience?
    Thanks and best regards.

    hi ravi,
      I am unable to match infoobjects in the update rules,do i have write routines in that?
    Can you give u r mail id i can send the screen shots.
    Please let me know.

  • Queries from business content

    Hi,
    When we install the out of the box business content queries from business content where are we able to see those queries. ( Like when we install infocube and dataflow before and we will be able to see it all in modeling area, same way where can we see the queries).
    Also when we install the queries will the objects like structures,variables, restricted key figures and calculated figures will also get installed.?
    Thanks for all the help in advance.

    Well the queries will always be attached to an InfoProvider, so you can easily see a list of queries under each InfoProvider. You can see this in the Open Dialog in Bex, or in the BW system you can do this in RSRT. Just F4 on the query text box and lookup up the queries by InfoArea. You can get a whole list of the queries, but then that would mean going to tables and deciphering the query GUIDS.
    Another way is to go to the Metadata Repository and looked at queries within the Local Objects (Activated objects).
    Hope this helps...

  • Problem while installing a query from Business Content

    Hi all of you,
    I am trying to install this particular query Inventory Turnover from the cube 0IC_C03 (Material/Stock Movements) from Business Content. Now in the third pane in Business Content under Active version available column across the name of this cube there is a calendar symbol.
    a.     So does it mean that the cube 0IC_C03 (Material/Stock Movements) is installed along with all the objects that are dependent on the cube and all those objects on which the cube is dependent. (NOTE: I had selected the grouping option as “In data flow afterwars”)
    b.     When I collapse Query Element I find that some of the queries are not installed. So I expanded Inventory Turnover query, right clicked on it and selected Install All Below.
    c.     I am getting this error, “Abort system error in program SAPLRRI2 and form LI_SETZEN-01-“ when I execute the query Inventory Turnover. However in Business Content when I installed the report Inventory Turnover under the cube Material Stock/Movement I didn’t get any error anywhere. Everything was activated successfully without any errors.
    Please tell me how do I install this Inventory Turnover from business content and how do I execute this report from BEx.
    Thank you.
    TR.

    Hi Arun,
    Thank you for that quick reply. I want to activate only the query and not the cube. I did as you advise me but still I am getting the same error when I run the Inventory turnover report from BEx.
    I am able to run other reports from the cube IC_C03. But not this report Inventory turnover. I have also checked the cube and there is data in the cube.
    Kindly adivse what to do.
    Thank you.
    TR.

Maybe you are looking for