I'd recommend using Data Services or another ETL tool to get a clean hierarchy table (i.e. parent-child or level hierarchy) that you can leverage for your reporting (i.e. either natively via hierarchies in Attribute/Calculation Views, or via navigation paths defined in your universe for relational sources).
In theory - you could write some SQL against PRHI (and probably PRPS) and use it to define your own custom hierarchy column view in SQL, but I'd recommend against this for many reasons - you won't (easily) know how "clean" your source hierarchy data (and hierarchies are very sensitive to "badly structured" data) and custom hierarchy column views aren't available as repository objects - making their maintenance and reusability quite complex and limited, respectively.