Creating Hierarchy Report..

Hi I am new to the ABAP Development and I am facing a problem. I want to create a hierarchy between tables ZSICM2 and Infostructure S961E. I have not Idea how to create a report of this. Could someone please help me in creating a report of creating hierarchy. This is the documentation provided to me by the client.
<b>For each new record of ZSICM2, we must ensure hierarchies exist in S961E.
1- Creation of hierarchy:
Select * from ZSICM2 where ZNEW = ‘X’.
     Submit report RMCA961H (This program should automatically be created when creating infostructure) with all necessary parameters.
Endselect.</b>
Also The report RMCA961H, I have no idea where this report will come from because I am not finding it in Library and also It is not being created automatically while creating infostructure.
Please help me in creating this report.
Thanks and regards,
Ravi

Hi,
This is the sample report for HIERARIHIAL SEQUENTIAL LIST   report.
REPORT  YMS_HIERSEQLISTDISPLAY                      .
Program with FM REUSE_ALV_HIERSEQ_LIST_DISPLAY                      *
Author : Michel PIOUD                                               *
Email : [email protected]  HomePage : http://www.geocities.com/mpioud *
TYPE-POOLS: slis.                    " ALV Global types
CONSTANTS :
  c_x VALUE 'X',
  c_gt_vbap TYPE SLIS_TABNAME VALUE 'GT_VBAP',
  c_gt_vbak TYPE SLIS_TABNAME VALUE 'GT_VBAK'.
SELECTION-SCREEN :
  SKIP, BEGIN OF LINE,COMMENT 5(27) v_1 FOR FIELD p_max.    "#EC NEEDED
PARAMETERS p_max(02) TYPE n DEFAULT '10' OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN :
  SKIP, BEGIN OF LINE,COMMENT 5(27) v_2 FOR FIELD p_expand. "#EC NEEDED
PARAMETERS p_expand AS CHECKBOX DEFAULT c_x.
SELECTION-SCREEN END OF LINE.
TYPES :
1st Table
  BEGIN OF ty_vbak,
    vbeln TYPE vbak-vbeln,             " Sales document
    kunnr TYPE vbak-kunnr,             " Sold-to party
    netwr TYPE vbak-netwr,             " Net Value of the Sales Order
    erdat TYPE vbak-erdat,             " Creation date
    waerk TYPE vbak-waerk,             " SD document currency
    expand TYPE xfeld,
  END OF ty_vbak,
2nd Table
  BEGIN OF ty_vbap,
    vbeln TYPE vbap-vbeln,             " Sales document
    posnr TYPE vbap-posnr,             " Sales document
    matnr TYPE vbap-matnr,             " Material number
    netwr TYPE vbap-netwr,             " Net Value of the Sales Order
    waerk TYPE vbap-waerk,             " SD document currency
  END OF ty_vbap.
DATA :
1st Table
  gt_vbak TYPE TABLE OF ty_vbak,
2nd Table
  gt_vbap TYPE TABLE OF ty_vbap.
INITIALIZATION.
  v_1 = 'Maximum of records to read'.
  v_2 = 'With ''EXPAND'' field'.
START-OF-SELECTION.
Read Sales Document: Header Data
  SELECT vbeln kunnr netwr waerk erdat
    FROM vbak
      UP TO p_max ROWS
    INTO CORRESPONDING FIELDS OF TABLE gt_vbak.
  IF NOT gt_vbak[] IS INITIAL.
  Read Sales Document: Item Data
    SELECT vbeln posnr matnr netwr waerk
      FROM vbap
      INTO CORRESPONDING FIELDS OF TABLE gt_vbap
       FOR ALL ENTRIES IN gt_vbak
     WHERE vbeln = gt_vbak-vbeln.
  ENDIF.
  PERFORM f_display.
      Form  F_DISPLAY
FORM f_display.
Macro definition
  DEFINE m_fieldcat.
    ls_fieldcat-tabname = &1.
    ls_fieldcat-fieldname = &2.
    ls_fieldcat-ref_tabname = &3.
    ls_fieldcat-cfieldname = &4.       " Field with currency unit
    append ls_fieldcat to lt_fieldcat.
  END-OF-DEFINITION.
  DEFINE m_sort.
    ls_sort-tabname = &1.
    ls_sort-fieldname = &2.
    ls_sort-up        = c_x.
    append ls_sort to lt_sort.
  END-OF-DEFINITION.
  DATA:
    ls_layout   TYPE slis_layout_alv,
    ls_keyinfo  TYPE slis_keyinfo_alv,
    ls_sort     TYPE slis_sortinfo_alv,
    lt_sort     TYPE slis_t_sortinfo_alv," Sort table
    ls_fieldcat TYPE slis_fieldcat_alv,
    lt_fieldcat TYPE slis_t_fieldcat_alv." Field catalog
  ls_layout-group_change_edit = c_x.
  ls_layout-colwidth_optimize = c_x.
  ls_layout-zebra             = c_x.
  ls_layout-detail_popup      = c_x.
  ls_layout-get_selinfos      = c_x.
  IF p_expand = c_x.
    ls_layout-expand_fieldname  = 'EXPAND'.
  ENDIF.
Build field catalog and sort table
  m_fieldcat c_gt_vbak 'VBELN' 'VBAK' ''.
  m_fieldcat c_gt_vbak 'KUNNR' 'VBAK' ''.
  m_fieldcat c_gt_vbak 'NETWR' 'VBAK' 'WAERK'.
  m_fieldcat c_gt_vbak 'WAERK' 'VBAK' ''.
  m_fieldcat c_gt_vbak 'ERDAT' 'VBAK' ''.
  m_fieldcat c_gt_vbap 'POSNR' 'VBAP' ''.
  m_fieldcat c_gt_vbap 'MATNR' 'VBAP' ''.
  m_fieldcat c_gt_vbap 'NETWR' 'VBAP' 'WAERK'.
  m_fieldcat c_gt_vbap 'WAERK' 'VBAP' ''.
  m_sort c_gt_vbak 'KUNNR'.
  m_sort c_gt_vbap 'NETWR'.
  ls_keyinfo-header01 = 'VBELN'.
  ls_keyinfo-item01 = 'VBELN'.
  ls_keyinfo-item02 = 'POSNR'.
Dipslay Hierarchical list
  CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
    EXPORTING
      i_callback_program      = sy-cprog
      i_callback_user_command = 'USER_COMMAND'
      is_layout               = ls_layout
      it_fieldcat             = lt_fieldcat
      it_sort                 = lt_sort
      i_tabname_header        = c_gt_vbak
      i_tabname_item          = c_gt_vbap
      is_keyinfo              = ls_keyinfo
    TABLES
      t_outtab_header         = gt_vbak
      t_outtab_item           = gt_vbap
    EXCEPTIONS
      program_error           = 1
      OTHERS                  = 2.
  IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
          WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.
ENDFORM.                               " F_LIST_DISPLAY
      Form USER_COMMAND                                             *
FORM user_command USING i_ucomm     TYPE sy-ucomm
                        is_selfield TYPE slis_selfield.     "#EC CALLED
  DATA ls_vbak TYPE ty_vbak.
  CASE i_ucomm.
    WHEN '&IC1'.                       " Pick
      CASE is_selfield-tabname.
        WHEN c_gt_vbap.
        WHEN c_gt_vbak.
          READ TABLE gt_vbak INDEX is_selfield-tabindex INTO ls_vbak.
          IF sy-subrc EQ 0.
          Sales order number
            SET PARAMETER ID 'AUN' FIELD ls_vbak-vbeln.
          Display Sales Order
            CALL TRANSACTION 'VA03' AND SKIP FIRST SCREEN.
          ENDIF.
      ENDCASE.
  ENDCASE.
ENDFORM.                               " USER_COMMAND
END OF PROGRAM Z_ALV_HIERSEQ_LIST ******************
Thanks,
Sankar M

Similar Messages

  • Abt Hierarchy Reporting

    Hi ALL,
                We have uploaded data from Flat file to hierarchy using IDOC transfer method , data transfered successfully to hierarchy.
    The hierarchy contains following structure ,
    SALES REGION----->> SALES OFFFICE -
    >>SALES REP ID .
    While Creating Hierarchy Report , in query designer we drag the SALES REP ID to rows and right click the
    SALES REP ID -
    >>Properties -
    >> Hierarchy -
    >>Expand Level=10---->ok ... Given
    Note: Hierarchy is active...
    But Still Query  doesnt contain any data in output .
    What is the Reason ??
    Thanks n Advance

    Hi,
             Thanks for the Answers...
           1). The Sales Rep ID is available at infoprovider level ..
           2). We have removed the hierarchy in the query properties , and use Sales rep id alone  in rows and reported but the report doesnt fetch any data ...
            3). In RSH1 we have seen Our Hierarchy Structure presented ...
    need further answers ......
    thanks ....

  • Create Hierarchy in REport

    Hello SAP Guru,
    Please any one can giv me procedure to create hierarchy in BPC Report using Report & Analysis.
    Thanks.
    With regards,
    Anand KUmar

    Hi Anand,
    I believe, you want a structure like this:
    Acc1
       Acc2
          Acc3
       Acc4
       Acc5
          Acc6
    Acc7
    If this is the case, then you need to setup a hierarchy in the dimension sheet first. You need to use the property ParentH1, etc. I hope you are aware of this. If this has been setup in the member sheet, then the system will automatically create a property called HLEVEL and then you can use the formula which I had specified earlier. It will definitely work. For the above example, you need to specify the formula only for Acc1, and then expand. You will get the display like above.
    Hope this helps.

  • How to Create COPA report by using Product Hierarchy?

    HI,
    I have to create COPA report using Product Hierarchy. Here i need to Bring Variant configuration characterstics to COPA through Product hierarchy.
    Kindly give me some points on how to start doint this process. Please provide me the steps to create Product Hierarchy which can be bring into COPA report. It would be a great help if any one can provide some inputs.
    Thanks
    Kishore

    Hi,
    Check transaction OVSV to define a Production hierarchy in logistics module.
    Refer this link on how to configure...
    http://www.sap-basis-abap.com/sd/how-to-configure-product-hierarchy.htm
    http://help.sap.com/saphelp_46c/helpdata/en/77/1a39516e36d1118b3f0060b03ca329/content.htm
    Hope this helps.

  • How to create a report which will show us the hierarchical stucture

    Hi all,
    I am using financial reporting studio for reports.
    I have a planning appliaction. And i used Zones as the Entity Dimension.
    Now I am trying to create a report for users to see my entity dimension hierarchy.
    Something like Zones
    East
    West
    North
    South
    I am able to generate the report but the hierarchy of the Zones does not show up..
    Can anybody advice if there is a option in Financial Reporting to make the hierarchy structure more visible by adding proper indentation between the parent and the child?..
    And yes i have used a prompt for the Entity in the report....
    Thanks

    Hi Venuramani,
    Thanks for ur reply........
    Let me explain you properly what I want......
    I am getting the hierachical structure , but I am getting the child first,then parent and then
    grant parent level members.But I want it in a different way first grant parent, then parent and then
    child .Is there any way to do this?Pls advise me.........
    Thanks

  • Problem creating hierarchy based on 2 physical dimension tables

    I'm having a problem creating 1 logical dimension with a drill-down hierarchy, based on two separate physical dimension tables. The errors I receive when navigating the drill-down hierarchy is:
    "Cannot find logical table source coverage for logical columns" &
    "Missing join between logical tables".
    I'm using OBIEE 10.1.3.4
    Here are the details of what I have setup sofar:
    Physical layer:
    Dimension table DIM_ORG with columns:
    -dimension_key
    -org_total_code
    -org_total_description
    -org_detail_code
    -org_detail_description
    Dimension table DIM_DEPT with columns:
    -dimension_key
    -dept_total_code
    -dept_total_description
    -dept_detail_code
    -dept_detail_description
    Fact table FACT_SALES with columns:
    -fk_org
    -fk_dept
    -sum_sales
    Physical Joins:
    FACT_SALES.fk_org = DIM_ORG_dimension_key
    FACT_SALES.fl_dept = DIM_DEPT.dimension_key
    Business Model & Mapping layer:
    I created a logical dimension ORG_DEPT. It contains two logical table sources (DIM_ORG & DIM_DEPT) and the following logical columns:
    - All Departments (mapped to dept_total_code)
    - Organisation (mapped to org_detail_description)
    - Organisation Number (mapped to org_detail_code)
    - Department (mapped to dept_detail_description)
    - Department Code (mapped to dept_detail_code)
    The business logical key is based on the combination of Organisation Number & Department Code
    The hierarchy I need is: All Departments -> Organisation -> Department so I created the following hierarchy for ORG_DEPT:
    - Total Level containing: All Departments
    - Organisation Level containing: Organisation Number (defined as the Logical level key) & Organisation (defined als the Drill level key)
    - Detail Department Level containing: Department Code (defined as Logical level key) and Department (defined as Drill level key).
    In the LTS of the dimension ORG_DEPT I've set the Content levels for the sources:
    DIM_ORG : Organisation Level
    DIM_DEPT: Detail Department Level
    In the LTS no -inner- joins have been added against related physical tables.
    I created a logical fact table SALES (based on the physical fact table) and joined it against the logical dimension table ORG_DEPT.
    In the LTS the Content level for ORG_DEPT is set against the Detail Department Level. No - inner- joins have been aded against related physical tables.
    When I create a report in Answers to test the hierachy and select only 'All Departments' I get the correct dimension value returned. When I try to drill to the next level I get the following ODBC error:
    "Cannot find logical table source coverage for logical columns: [All Departments]. Please check more detailed level keys are mapped correctly".
    When I create a report in Answers and select both 'All Departments' and 'Sales' I get the correct result. When I try to drill to the next level I get a different ODBC error:
    "Missing join between logical tables DIM_DEPT and DIM_DEPT: There must be at least one physical join link between the underlying physical tables".
    Any suggestions are welcome!
    Thanks!

    Hello Robert,
    Your suggestions were known to me but I still wanted to combine the two physical dimension tables in one logical dimension. So I've played around a bit more and found the solution: In my original setup I had two seperate logical table sources (one for each physical dimension table). The solution was to combine the two logical table sources in one logical table source. I achieved that by logical joining the DIM_DEPT table to the FACT_SALES table and subsequently to the DIM_ORG within the 1 LTS and using inner joins.
    Then I created the logical table key (a combination of org_detail_code & dept_detail_code). After that I could create the hierarchy with no problem.
    Edited by: The_Dutchman on Nov 4, 2011 9:43 PM

  • Need Help in creating BPC Report

    Hi,
    I want to develop a BPC report as shown below .
    .........................2010.TOTAL... 2011.TOTAL......2011.Q1..... 2011.Q2......2011.Q3.......2011.Q4
    ............................ ACTUAL  ........PLAN..............PLAN....... .PLAN..........PLAN............PLAN
              REVENUE
                COGS
    (.......) have been used for only formatting the report in above format.           
    I am not very much trained in BPC . I have loaded the actual data for 2010 with the proper hierarchy and i am able to see it on the report but i am facing difficulty in below two things.
    1] I am not able to create a report where i can see the Actual of 2010 and i can enter the forecast for 2011.
    2] My 2010.TOTAL is not getting rolled up , I have used proper hierarchy in Time dimension and i have selected YTD as measure.
    Please help.

    Hi,
    I stumbled across SAP note 1506275 today which dieals with the issue, but unfortunately is not helpful at all. What SAP are saying is: replace the pipe with a comma. Well, this quite obviously gives a different result than the one you were aiming at with the pipe in the first place, but that's the official answer.
    Now, I'm wondering, has anyone successfully used the pipe, and in which service pack of BPC? MS or NW? I'm on 7.5 NW SP7 and the pipe casuses the error message mentioned in this post.
    Cheers
    Matthias

  • How to create hierarchy across more than one dimesion

    Hi experts,
     How to create hierarchy on more than one dimension in SSAS.please guide me.
    Thanks

    Hi ,
    This is not Possible without making changes in the cube design .i.e;
    Using Join for have to create one dimension with all attributes that you require in dimension .
    Lets say you have
    Dim1
     att1
     att2
     att3
    Dim2
      F1
      F2
    You need Hierarchy as below;
    Hier
     att1
     att3
     F2
    1. Add one Table in DSV using Join between both the tables.
    2.Create Dimension using this newly added table.
    3. Create hierarchy
    https://www.simple-talk.com/sql/reporting-services/implementing-user-defined-hierarchies-in-sql-server-analysis-services/
    Thanks
    Please Mark This As Answer or vote for Helpful Post if this helps you to solve your question/problem. http://techequation.com

  • Creating a report using unrelated facts

    We the following Scenario where we have 2 date dimensions, Transaction Created Date Dimension and Application Created Date Dimension. Both these tables are aliases created in the OBIEE Physical Layer of RPD from the same source table - Date Dimension which is created in the database.
    We have 2 facts -
    1. Transaction fact which is joined to Transaction created Date Dimension.
    2. Application Fact which is joined to Application created Date Dimension.
    We need to create a report which shows 4 columns,
    1. Application created date
    2. number of applications
    3. Transaction Created Date
    4. total Transaction amount
    When we try to create this report it throws us an error,
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026]
    Is there anyway we can resolve this?
    Please suggest.
    Thanks.

    Hi All,
    I have a similar problem with the related facts. Here is the scenario,
    I have two facts ( Fact - HR- Event Information and Fact - HR - Salary Event Information), both of them have same physical table as source but conditions in the business layer in the content tab is different(second fact has got some additional conditions). These two facts have no join between them in the business layer.
    I have a dimension table 'Dim - Employee' which is joined to both of these facts in the business layer. I have also set the dimension hierarchy of this table in the facts (set the logical level to employee detail in both the facts)
    I then moved these two facts to the presentation layer. When i select columns from the dimension table and any of fact i'm able to see the results, but when i select columns from both the fact tables i'm getting this error,
    [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: Fact - HR - Salary Event Information.Salary Change Reason. Please fix the metadata consistency warnings
    Can any one help me on this.
    Thank You,

  • How to create  hierarchy on bi7 by using dtp

    how to create  hierarchy on bi7 by using dtp

    Hi Deba,
    Procedure to create Hierarchies:
    1.      In the Data Warehousing Workbench under Modeling, choose the InfoObject tree.
    2.      If you have assigned the hierarchy basic characteristic to an InfoObject catalog, select the corresponding InfoObject catalog for an InfoArea.
    If the hierarchy basic characteristic does not belong to an InfoObject catalog, choose the InfoArea Non-Assigned Nodes and the InfoObject Catalog Non-Assigned Characteristics.
    3.      Select the characteristic for which you want to create a hierarchy and choose Create Hierarchy from the context menu. The Create Hierarchy dialog box appears. The InfoObject name appears by default.
    4.      Enter a hierarchy name and description (short, medium, long). Other fields may be displayed, depending on which hierarchy properties were selected for the hierarchy basic characteristics
    Fields used to enter the Validity (valid to, valid from) for the hierarchy property Total Hierarchy Time-Dependent
    Fields used to specify the Hierarchy Version for the hierarchy property Hierarchies Version-Dependent.
    5.      Confirm your entries. The Maintain Hierarchy screen appears. You can define the structure of a hierarchy here.
    6.      To create a hierarchy node, you first need to choose an insertion mode:  Insert as First Child or   Insert As Next Neighbor (see Hierarchy Editing Functions).
    7.      Choose the type of node you want to create: Text Node, Characteristic Node, <Hierarchy Basic Characteristic Node> or Interval (see Hierarchy Nodes)
    8.      Repeat this procedure until the hierarchy structure has been set. For more information, see Modeling Nodes and Leaves.
    A hierarchy can contain 50,000-100,000 leaves at most. If your hierarchy is larger, you should insert a level that is used as a navigation attribute or preferably as a separate characteristic in the dimension table.
    9.      You can use Level Maintenance and Hierarchy Attributes to set how the hierarchy is to be displayed and processed in reporting (see Level Maintenance and Hierarchy Attributes).
    10.      Save the hierarchy.
    11.      Activate the hierarchy. See Editing Hierarchies.
    For more info
    [http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a6736e07211d2acb80000e829fbfe/content.htm]
    [http://help.sap.com/saphelp_nw70/helpdata/EN/e6/951d102a6c11d5b2e40050da4c74dc/content.htm]
    Regards,
    Rajkandula

  • Create a report showing a tree with unlimited number of levels

    Hi,
    Our reporting requirement is to be able to show a tree structure of tasks and task groups plus other data specific to a task. Task is the lowest level but there can be many levels of task groups above it. We do not have a maximum number of levels. So the tree can go many levels deep. Since it is impossible to predict the number of levels, is there a way to apply grouping here? Is it even possible to create a report displaying unknown number of hierarchies? Here is a sample skeletal outline of how the report is supposed to be laid out:
    TG1
    ----TG1.1
    --------TG1.1.1
    ------------Task1
    --------TG1.1.2
    ------------Task2
    ----TG1.2
    --------Task3
    --------Task4
    TG2
    ----TG2.1
    --------TG2.1.1
    -------------TG2.1.1.1
    ------------------TG2.1.1.1.1
    --------------------------Task1
    ----TG2.2
    ---------Task2
    Thanks!
    Sarah

    Hi Tim,
    Here is the sample xml output. In our application, to display the hierarchy, our developers implement some looping/code mechanism. The XML output shows the flat data used to create the hierarchy although i have included a GROUP BY clause in my SQL to show the distinct data. Using the PARENT_TEMPLATE_GUID column, they will trace back the ancestors of the given task group or task in the tree. So after you get the PARENT_TEMPLATE_GUID of a task or task group (record), you will compare its value to the TASK_GROUP_GUID of other records to identify its parent. Once found, you will again take that record's PARENT_TEMPLATE_GUID and compare against the other TASK_GROUP_GUID to search for its parent/ancestor. Once you encountered a record with a null PARENT_TEMPLATE_GUID, then you have reached the top most level of the tree and establish the hierarchy for a given task group or task. We have no way of knowing how many levels deep a tree is as it is variable.
    <?xml version='1.0' encoding='UTF-8' ?>
    <results>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB03ECFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB03DCFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[LCM_ORA00001_ORA00004]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task 121]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[1]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB03DCFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB03BCFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[TG_ORA00001_ORA00003]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task Group 12]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[2]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB03BCFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[TG_ORA00001_ORA00001]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task Group 1]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[1]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB046CFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB042CFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[LCM_ORA00001_ORA00012]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task 222]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[2]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB03FCFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB03DCFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[LCM_ORA00001_ORA00005]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task 122]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[2]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB044CFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB041CFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[LCM_ORA00001_ORA00010]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task 212]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[2]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB041CFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB040CFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[TG_ORA00001_ORA00007]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task Group 21]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[1]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB040CFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[TG_ORA00001_ORA00006]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task Group 2]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[2]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB043CFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB041CFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[LCM_ORA00001_ORA00009]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task 211]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[1]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB045CFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB042CFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[LCM_ORA00001_ORA00011]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task 221]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[1]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB042CFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB040CFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[TG_ORA00001_ORA00008]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task Group 22]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[2]]></ORDER_BY>
         </row>
         <row>
              <RAWTOHEX(A.TASK_GROUP_GUID)><![CDATA[446A0F0BB03CCFF3E040578CAF0B1C16]]></RAWTOHEX(A.TASK_GROUP_GUID)>
              <RAWTOHEX(A.PARENT_GROUP_GUID)><![CDATA[446A0F0BB03BCFF3E040578CAF0B1C16]]></RAWTOHEX(A.PARENT_GROUP_GUID)>
              <TASK_GROUP_IDENTIFIER><![CDATA[LCM_ORA00001_ORA00002]]></TASK_GROUP_IDENTIFIER>
              <NAME><![CDATA[Task 11]]></NAME>
              <STATUS><![CDATA[NR]]></STATUS>
              <MIN_DOWN_TIME><![CDATA[Y]]></MIN_DOWN_TIME>
              <ORDER_BY><![CDATA[1]]></ORDER_BY>
         </row>
    </results>

  • ALV HIERARCHIAL REPORT

    Dear Experts,
    Can anyone tell me how to create a ALV Hierarchial report with one HEADER table and multiple ITEM(child) tables.
    thanks & regards,
    gautam

    Hi you can tray review this code for a example i found in the web and help me:
    REPORT Z_TEST_HIESEQ_REPORT.
    TABLES: ekko,ekpo.
    * selection option
    SELECT-OPTIONS s_ebeln FOR ekko-ebeln.
    TYPE-POOLS:slis.
        * define header table and item table
    DATA: BEGIN OF headertab OCCURS 0,
              ebeln LIKE ekko-ebeln,
              bstyp LIKE ekko-bstyp,
             bsart LIKE ekko-bsart,
             statu LIKE ekko-statu,
             END OF headertab.
        DATA: BEGIN OF itemtab OCCURS 0,
        ebeln LIKE ekpo-ebeln,
        ebelp LIKE ekpo-ebelp,
        matnr LIKE ekpo-matnr,
        werks LIKE ekpo-werks,
        menge LIKE ekpo-menge,
        netpr LIKE ekpo-netpr,
        peinh LIKE ekpo-peinh,
        netwr LIKE ekpo-netwr,
        END OF itemtab.
        DATA: i_fieldcat TYPE slis_t_fieldcat_alv.
        DATA: v_repid LIKE sy-repid.u201Ccurrent program name
        DATA: g_tabname_header TYPE slis_tabname,
        g_tabname_item TYPE slis_tabname.
        * data connect header table and item table
        * we can set 5 field as foreign key at same time
        DATA: gs_keyinfo TYPE slis_keyinfo_alv.
        INITIALIZATION.
        v_repid = sy-repid.
        START-OF-SELECTION.
        PERFORM get_data.
        END-OF-SELECTION.
        * get field catalog of header table
        CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
        EXPORTING
        i_program_name = v_repid
        i_internal_tabname = 'HEADERTAB'
        i_inclname = v_repid
        i_bypassing_buffer = 'X'
        i_buffer_active = "
        CHANGING
        ct_fieldcat = i_fieldcat
        EXCEPTIONS
        inconsistent_interface = 1
        program_error = 2
        OTHERS = 3.
        IF sy-subrc <;>; 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1
        sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        * get field catalog of item table
        CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
        EXPORTING
        i_program_name = sy-repid
        i_internal_tabname = 'ITEMTAB'
        i_inclname = v_repid
        i_bypassing_buffer = 'X'
        i_buffer_active = "
        CHANGING
        ct_fieldcat = i_fieldcat
        EXCEPTIONS
        inconsistent_interface = 1
        program_error = 2
        OTHERS = 3.
        IF sy-subrc <;>; 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1
        sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        * set the header and item table are connected by pur doc number
        gs_keyinfo-header01 = 'EBELN'.
        gs_keyinfo-item01 = 'EBELN'.
        g_tabname_header = 'HEADERTAB'.
        g_tabname_item = 'ITEMTAB'.
        CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
        EXPORTING
        i_callback_program = v_repid
        it_fieldcat = i_fieldcat
        i_save = 'A'
        i_tabname_header = g_tabname_header
        i_tabname_item = g_tabname_item
        is_keyinfo = gs_keyinfo
        i_bypassing_buffer = 'X'
        i_buffer_active = ' '
        TABLES
        t_outtab_header = headertab
        t_outtab_item = itemtab
        EXCEPTIONS
        program_error = 1
        OTHERS = 2.
        IF sy-subrc <;>; 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
        WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        FORM get_data.
        SELECT ebeln bstyp bsart statu
        INTO TABLE headertab
        FROM ekko
        UP TO 100 ROWS
        WHERE ebeln IN s_ebeln.
        IF NOT headertab[] IS INITIAL.
        SELECT ebeln ebelp matnr werks menge netpr peinh netwr
        INTO TABLE itemtab
        FROM ekpo
        FOR ALL ENTRIES IN headertab
        WHERE ebeln = headertab-ebeln.
        ENDIF.
        ENDFORM. "get_data
    Edited by: Juan Manuel Garcia on Aug 17, 2010 11:29 PM
    Edited by: Juan Manuel Garcia on Aug 17, 2010 11:36 PM

  • Restrict User to Create Custom Reports

    Hi
    Can we restrict a user from creating custom reports in SPM, If yes how? We want that user can does not see the Create New Report Option
    Regards
    Neel

    HI,
    If the dashboars and reports for users are already so well defined, wouldn't offline Briefing Books give them the same information?
    Also, if ad-hoc reporting and business user empowerment is not what you are looking for, it would also be easy to use SAP BusinessObjects BI tools, such as Xcelsius, on top of SPM data to provide those centrally defined dashboards and reports.
    Finally, BW authorizations are very flexible and comprehensive. You can limit a user to a few dimensions on which he can drill down, to certain Key-Figures, to specific levels of the hierarchy. If you don't have such authorizations in place and want to control instead the selections the user can do, then using Xcelsius on top of SPM could give you that possibility.
    Regards!
    Ricardo Vieira

  • BI Security: Hierarchy reporting authorizations

    Hi Guys,
      I have created hierarchy authorization object in RSECADMIN. Included this object in role and assigned
      this role to user. I have four reports in FI. In this four reports this heirarchy authorization is working for
      three reports as per the requirement but the one report is not working. It is showing the message
      " Need authorization". This report also has to show the required hierarchy node.
        Today  I have included one DSO in the same multi provider. Now all reports are not working for the
    authorized users. It is showing the message "No authorization". Till now I haven't generated the
    authorizations in RSECADMIN. Is this the problem? I tried to generate the authorizations in
    RSECADMIN it is showing below error messages.
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTUSERNM
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTAUTH
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTADTO
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTIOBJNM
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTHIENM
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTHIEVERS
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTHIEDATE
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTNIOBJNM
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTNODE
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTATYPE
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTACOMPM
    InfoProvider ZM_FIAM01 does not contain the required characteristic 0TCTTLEVEL
    Please suggest me if I messed any thing.
    Thanks
    Prasad

    Hi Zaheer,
    Hi Aduri,
    Thanks for your response.
    I tried to execute the user with logs in RSECADMIN. Here it is showing the error
    message "Authorizations missing for aggregation (":")".
    I have included 0TCAACTVT, 0TCAIPROV, 0TCAVALID, 0PROFIT_CTR, 0CO_AREA and
    0ASSET__0PROFIT_CTR in authorization object.
    I checked the relevent SAP not " Note 1140831 - Colon authorization during query execution ". In is
    saying to Restrict the characteristic in the query to a certain selection (single value, interval, hierarchy
    node, and so on) and authorize this selection explicitly.
    Thanks
    Prasad

  • Error while creating a report in BI publisher

    Hi all ,
    I am getting an error while creating a new report in BI publisher .
    the error shown in console is --
    java.lang.SecurityException: /
    In the front end - i am getting
    Operation failed: d:/OracleBI/xmlp/XMLP/Users/~administrator/annapurna/test/test.xdo
    please suggest if anyone knows.

    Hi,
    I am newly using BI publisher . I am using 10.1.3.4.0 . I am just trying to create a report in test name. that is the first step to create a report where i am getting error. I am using default RPD paint , where all the user and Groups are defined .

Maybe you are looking for