BAPI for all levels of all hierarchies of all dimensions of a cube

Hi Experts,
Is there are way to get all properties of all levels of all hierarchies of all dimensions of a cube (InfoCube, ODSObject, QueryCube, InfoSet)  in one BAPI call?
Any useful answer will be rewarded with suitable points.
Thanks,
Rohan

Hi
Check the following Cube related BAPIS
BAPI_CUBE_ACTIVATE
BAPI_CUBE_CHANGE
BAPI_CUBE_CREATE
BAPI_CUBE_GETDETAIL
BAPI_CUBE_GETLIST
BAPI_INFOCUBE_READ_REMOTE_DATA
BAPI_MDPROVIDER_GET_CUBES
BAPI_MDPROVIDER_GET_STREAMCUBE
UMK_BW_BAPI_CUBE_GETDETAIL
Reward points for useful Answers
Regards
Anji

Similar Messages

  • Query selected levels of multiple hierarchies of one dimension

    Hi to all.
    I have created through AWM 11 a customer dimension with two hierarchies as follows.
    SLM_HIER: All Customers -> Salesman -> Customer
    GEO_HIER: All Customers -> State -> City -> Customer
    I have also created a SALES_CUBE (measures: QUANTITY, VALUE, aggregation: SUM) that is dimensioned with Customer dim.
    I'm using OBIEE to query the OLAP engine (through the relational views that AWM created automatically). I have followed the OTN OBE tutorials.
    I would like to have the following query on the cube:
    Give me QUANTITY where SALESMAN=S1 and CITY in ('Athens','Rome').
    Is it possible to have such a query? As far as I understand there are no ready aggregated data for selected levels of both hierarchies.
    Thank you very much.
    Chris

    I think OBIEE would also give you your answer from OLAP.
    This query has filters defined from both the hierarchies and hence OBIEE would (should) automatically service this query from the highest common level b/w the hierarchies (in this case: base/leaf level - Customer). As a result of this, if CUST is your Customer dimension, OBIEE (at least, the older style of obiee modeling with olap) would introduce the security filter CUST_LEVEL = 'Customer'. Granularity of the resultset returned would be per individual Customer. 1 record per Customer satisfying the criteria SALESMAN='S1' and CITY in ('Athens','Rome').
    Ideally you should include the Cust Id, Quantity columns in your obiee answers report and use an internal answers object/view like a Pivot View to hide Customer details column and get a localized aggregation performed over the resultset returned from OLAP to get the consolidated Quantity. Answers table has data at Customer level, Answers Pivot can show the required result.
    Note1: The Cube cannot have this result pre-calculated since its a contradictory combination of filters across hierarchies. Level specific aggregate values calculated (or pre-calculated) in the cube for Salesman level (h1) would contain Customers from all cities (h2) and similarly City level (h2) Aggregates would contain Customers of all Salesmen (h1).
    Note2: I believe OBIEE modeling with OLAP suffers from some issues relating to multiple hierarchies (e.g: if you have filter from non-default hierarchy CITY in ('Athens','Rome') alone, i think it would still fetch the results from lowest common level Customer instead of from City level directly).
    HTH
    Shankar

  • To calculate average of a measure for particular level of calendar hierarchy across all years

    Hi All,
    Let say Data is available for 10 years: from 2005 to 20015
    Calendar Hierarchy: Year -> Quarter -> Month -> Week -> Day
    Let say Measure Name is : SalesAmt
    Now, I want to create a calculated measure for calculating: Average of SalesAmt for Calendar Hierarchy at particular level (for all the 10 years). Means, if somebody selects, Jan, 2014 it should show Average of all the January’s data (coming from all the 10
    years like average of Jan -2000, Jan-2001, Jan-2002......Jan-2015), similarly if somebody selects 1st Quarter, 2012 it should show Average of all the 1st Quarter of all the 10 years (average of 1st quarter 2000, 1st Quarter 2002....1st Quarter 2015). 
    Kindly suggest.
    Thanks in advance.

    You should use ParallelPeriod. Ex:
    SELECT ParallelPeriod ([Date].[Calendar].[Calendar Quarter]
       , 3
       , [Date].[Calendar].[Month].[October 2003])
       ON 0
       FROM [Adventure Works

  • Bapi for sales dispatch

    Hi all
      I have sale order number and item number, I want to do the sales dispatch automatically ,is any way to do this or have bapi for it?
    Please help me
    Kanishka

    Hi all
      I have sale order number and item number, I want to do the sales dispatch automatically ,is any way to do this or have bapi for it?
    Please help me
    Kanishka

  • ShoppingCart ProcessControlledWorkflow SRM 7.0 -BC set for N-level approval

    Hi experts,
    Which BC set I should activate for Shopping cart N-level approval Work Flow.?
    How to deactivate existing Active BC set in the system?
    Thanks

    Hello,
    Activation of BC set is to facilitate the faster & easier configuration. You have two options :
    1. Activation of new BC set will make the necessary changes. e.g if you have activated SC auto approval, run the BC set for 1 level approval, system will make all the changes required.
    2. Manually change the configuration based on your requirement. SRM - SRM Server - Cross Application Basic Setting - Business Workflow.
    BC sets are generic & might not fulfill all of your requirements. If your requirement is n -level approval, better to build your own expressions & process schema & levels. Take the reference of SAP delivered process levels.
    Hope this helps.
    Thanks
    Ashutosh

  • BAPI for properties of all levels of all hierarchies of all dimensions cube

    Hi Experts,
    Is there are way to get all properties of all levels of all hierarchies of all dimensions of a cube (InfoCube, ODSObject, QueryCube, InfoSet) in one BAPI call?
    Any useful answer will be awarded with suitable points.
    Thanks,
    Rohan

    I have one material BOM like  PA0100P3DR000 --- finish material
                                                PA0100P3GR000 --- Go blank
                                                BA0100P3GR000 --  Hard blank
                                                AA0100P3GR000 --- Soft blank
                                                RSTR0010000000 -- Raw material
    This is for one material display level i.e. for PA0100P3DR000 finish code.
    How i will get for all materials in a single display .
    Pl' tell the step by step procedure.........
    I have little knowledge of BAPI.
    Thanks.

  • BAPI to get  all levels of all hierarchies of all dimensions of a cube

    Hi Experts,
    Is there are way to get all properties of all levels of all hierarchies of all dimensions of a cube (InfoCube, ODSObject, QueryCube, InfoSet) in one BAPI call?
    Any useful answer will be rewarded with suitable points.
    Thanks,
    Rohan

    Hi
    Check the following Cube related BAPIS
    BAPI_CUBE_ACTIVATE
    BAPI_CUBE_CHANGE
    BAPI_CUBE_CREATE
    BAPI_CUBE_GETDETAIL
    BAPI_CUBE_GETLIST
    BAPI_INFOCUBE_READ_REMOTE_DATA
    BAPI_MDPROVIDER_GET_CUBES
    BAPI_MDPROVIDER_GET_STREAMCUBE
    UMK_BW_BAPI_CUBE_GETDETAIL
    Reward points for useful Answers
    Regards
    Anji

  • BAPI  to get all properties of all levels of all hierarchies of a cube

    Hi Experts,
    Is there are way to get all properties of all levels of all hierarchies of all dimensions of a cube (InfoCube, ODSObject, QueryCube, InfoSet)  in one BAPI call?
    I use BAPI_MDPROVIDER_GET_PROPERTIES, and only set input parameters: CAT_NAM, CUBE_NAM. But it only returns all Level1's properties.
    Any useful answer will be awarded with suitable points.
    Thanks,
    Rohan

    Hi,
    Thanks for giving reply.
    Recommended Function module is not a RFC, so it is not working.
    Thanks,
    Rohan

  • The Cube should refers to all leaf levels of hierarchies of the Dimension

    Dear All,
    I'm trying to link a fact table to the month level of a time dimension and i got the following error
    VLD-0398: The Cube TIME_TEST_CUBE does not refer to leaf/lowest level DAY of the dimension SINGLE_HIR_TIME.
    The Cube should refers to all leaf levels of hierarchies of the Dimension.
    would you please help me to solve this problem
    Regards,
    Shaimaa

    I realized that this feature is allowed only for MOLAP dimensions but not for ROLAP
    which exactly the opposite of what is mensioned in
    Oracle® Warehouse Builder
    User's Guide
    10g Release 2 (10.2.0.2)
    B28223-03
    in page 116
    " For a cube that uses a relational implementation, you can refer to intermediate
    levels in a dimension. However, for cubes that use a multidimensional
    implementation, you can only reference the lowest level in the dimension. "

  • Can we load data for all levels in ASO?

    Hi All,
    Im creating cube in ASO
    can i load data for all levels in ASO
    we can load data for all Levels In BSO but in ASO i need confirmation????
    and one more
    wat is the consider all levels option in ASO is used for ? wat is the purpose?
    Can any one help ,it would be appriciate.
    Thanks

    In an ASO cube you can only load to level zero
    The consider all levels if used for aggregation hints. It allows you to tell the aggregation optimizer to look at all levels when deciding if aggregation needs to be done on the dimension

  • Can we load data for all levels in ASO cube

    Hi All,
    Can we load data for all levels of members in ASO cube in 9.3.1.
    Regards

    Yes you can load data for all levels in an ASO cube in any version HOWEVER, none of the upper level data in any cube will be there when you look for it. You will get a warning message in the load because ASO cubes don't store data at upper levels. It is the same as loading data into dynamic calc members in BSO cube. It will do the load without compalints, but there will be no data there (At least you get the warning in ASO)

  • PR release date capturing for all levels

    Hi,
    I have activated PR release strategy at Header level.  There are about 4 levels of release are there.  In custom PR print program, I want to capture the details of all levels corresponding release dates.  Can you help me how I can go about it.
    Munna.

    Hi
    PR release date is not relevant to Release strategy.
    Purchase Requisition Release Date
    Specifies the date on which the purchase order should be initiated on the basis of the purchase requisition.
    The release date is based on:
    The purchasing department processing time defined for the plant
    The planned delivery time from the material master record or purchasing info record
    The delivery date
    The goods receipt processing time from the material master record
    Note
    The planned delivery time from the purchasing info record and the GR processing time are only taken into account if the purchase requisition was generated via materials planning.
    Example
        Processing time   Planned del.   GR processing
           Purchasing         time           time
    Release       PO                    Delivery    Date
    date         date                   date    required
    Date required:                     10.01.96
    GR processing time:                 2 days (working days)
    Planned delivery time:             10 days (calendar days)
    Purchasing dept processing time:    2 days (working days)
    For the material to be available on the date it is needed, the purchase requisition must be released on 09.11.96 (requirement date less GR processing time, planned delivery time, and purchasing department processing time).
    Hope it helps
    Thanks/karthik

  • MPS run, planned orders were created for all levels ?

    Hello PP members
    I ran a small scenario
    material    MRP Type     Low Level    SG           M/T Type
    A      M0         000             40              FERT
    B               PD              001              40             HALB
    c               PD              002               10             ROH
    Maintained PIRs(MD61) for material A, and ran MD41( Single Item Multi level Planning)
    As material A is an MPS item, I was expecting that it should create planned orders only for material A, but in this MPS run it created planned orders for material B & C. (Looked into MD04, where I see planned orders were created
    for all the levels)
    As per the MPS run, it will plan only for one level of BOM (in this scenario for material A)
    Any suggestions, why planned orders were created for material B & C
    please clarify

    Just check
    System must have created a dependent requirement planned order and not the planned order for requirement you put in demand management for B and C
    i.e. if you enter a demand in MD61 for B and C, run the transaction, system will not consider this requirement during MPS run. MPS run will consider the requirement if the requirement for the child is comming from parement where parent is MPS item.
    Hence you need to run MRPm for B amd C if teh requirement(not dependdent requirement from A) is to be considered.
    I hope you are clear
    Edited by: Rajesha Vittal on Jan 28, 2008 8:06 AM

  • MDX missing out 'All' level results for attribute joined to leaf level of a hierarchy

    I have an MDX query with a cross-join of a hierarchy and a simple attribute on rows.  The leaf level of the hierarchy maps one-to-one with the simple hierarchy, while the other levels map onto multiple values of the simple attribute.  In the results,
    an 'All' level row of the simple hierarchy is produced for all values of the hierarchy.  However:
    1. if the rows are numbered using Rank, the row number that the 'All' rows of the root level values of the hierarchy should have is skipped, and the rows that should have it have a repeat of the single child's row number.
    2. in SSRS no 'All' level of the simple attribute is found for the root level of the hierarchy.
    My reading of this is that the All level is not being produced for the one-to-one root level relationship, and the query is reading the first non-empty value.
    Any thoughts on (1) how to force the production of the missing 'All' level values; and (2) how to use Scope or some other means to place values in the positions where they are missing.
    Ken

    It would be helpful to see your MDX query and a screenshot illustrating the results!
    Thanks! Josh

  • Getting error msg even I entered all mandatories to BAPI for sales order.

    Hi Experts,
    I am trying to create sales order using standard BAPI
    "BAPI_SALESORDER_CREATEFROMDAT2". But, even I had entered all mandatory fields, I am unable to create sales order sucessfully.
    I had gone through the documentaion of this BAPI and entered these fields.
    These are the mandatory fields that which I had tried to create,
    ORDER_HEADER_IN :
                       DOC_TYPE     Sales document type
                       SALES_ORG    Sales organization
                       DISTR_CHAN   Distribution channel
                       DIVISION     Division
    ORDER_PARTNERS..:
                       PARTN_ROLE   Partner role, SP sold-to party
                       PARTN_NUMB   Customer number
    ORDER_ITEMS_IN..:
                       MATERIAL     Material number
         Do we have anymore fields to give as inputs? I am getting this error message as below :
    Msg: Personal number 00007176 does not exit.
    But, I am not giving any personal number manually. This personal number was having connection with partner role field,
    I had reffered this from the VBPA (Sales Document: Partner Table). Now, please suggest me how to solve this?
      Can anyone tell me how to solve this problem and create sales order sucessfully.
      Thanks in advance,
      Surender Batlanki.

    hi,
    try out this sample code.. it is working fine in creating sales order through BAPI.
    REPORT z_bapi_salesorder_create.
    Parameters
    Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    Start-of-selection.
    START-OF-SELECTION.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
    regards,
    pavan reddy

Maybe you are looking for