More discussions in Business Intelligence Old Forum 1 (Read Only Archive)Where is place located?
    1 Reply Latest reply: Oct 11, 2011 12:23 PM by Durgesh Gandewar RSS

    0COORDER Hierarchy as a Flat structure

    Srivatsa Nori
    Srivatsa Nori Mar 1, 2012 12:08 PM
    Currently Being Moderated

    Hi,

     

    I load the hierarchy for internal order from ERP into BI in 0COORDER InfoObject.

     

    But the requirement I have is to show the Hierarchy as a flat structure and not as a drill down.

     

    For e.g.: the hierarchy is: Company ¬ Business Unit ¬ Area ¬ Region ¬ Sector ¬ Internal Order.

     

    When I use the hierarchy display in the query for 0COORDER, it will obviously display it as a drilldown. But I need it to display as a normal flat structure.

     

    One solution that I can think of is to create a DSO to maintain this hierarchy which will feed of 0COORDER. But is this possible? How can I extract the Hierarchy data (from table: /BI0/HCOORDER) to load into a DSO?

     

    Thanks,

    Sri.

     

    • 230 Views
    • Re: 0COORDER Hierarchy as a Flat structure
      Durgesh Gandewar
      Durgesh Gandewar Oct 11, 2011 12:23 PM (in response to Srivatsa Nori)
      Currently Being Moderated

      Hi,

       

      Create a generic extractor in BW using transaction RSO2 directly based on table /BI0/HCOORDER. After that you can extract data into DSO.

       

      Regards,

      Durgesh.

      • Re: 0COORDER Hierarchy as a Flat structure
        Srivatsa Nori
        Srivatsa Nori Dec 8, 2011 12:05 PM (in response to Durgesh Gandewar)
        Currently Being Moderated

        Hi,

         

        I've created a Generic DataSource on the H table where the Hierarchy is stored in BI. I then wrote an Expert Transformation routine from the DataSource to the DSO which will convert the Hierarchy data into flat structure.

         

        There was an issue with this approach though. The expert routine will only act on the data in each data package. If the higher level hierachy details are in a different package then the hierarchy structure will not be built correctly. To overcome this, there should be a temporary table in the expert routine which again reads the HIERNODE from the H table.

         

        A slightly better approach would've been to write a Function Module on the H table which converts the data into flat structure and then create a Generic DataSource on this Function Module. The transformation will then be a simple one-to-one mapping.

         

        Thanks,

        Sri.

    Actions