How to: from time independent hierarchy to time dependent hierarchy in BW

Question

Hello goeroes outthere,
I am facing the following problem and was wondering if some of you have faced the same issue.
In ECC we have a time independent hierarchy on Profit Center. Our customer wants to perform time DEPENDENT reporting in BW.
As the standard datasource does not support to be loaded via PSA in the datasource definition (only IDOC) we cannot enhance the datasource with fields such as DATEFROM and DATETO. I've tried doing so but this results in the following error message when loading : Selected number does not agree with transferred number of records.
So I have cancelled out this as being an option.
I am analyzing the following two options :
1. Making the hierarchy time dependent. (globally). The idea would be to create a custom ABAP program that would copy the loaded hierarchy to a hierarchy in which we define the datefrom as the actual system date and the dateto as 31.12.9999.
Prior to doing so the abap program should change the already loaded hierarchy by modifying the dateTO as actual system date -1 in the header of the hierarchy.
In theory this seems to be a good option, but I am afraid of the complexity of the ABAP program to be created by looking in debug how the copying process is handled in SAP. 
2. Making the hierarchy structure TIme dependant. THis has as a consequence that the table  /BI0/HPROFIT_CTR is adjusted to include DATETO and DATEFROM fields. A custom program could read the entries and perform the same activities as described above. So meaning finding and modifying the existing entries with DATETO fields with as an entry 31.12.9999 to adjust to sysdatum -1 and modfying all entries that don't have dateto and datefrom entries by putting datefrom (=sysdate) and the dateto (=31.12.9999).
The issue here is that first we need to find the link between the hierarchy ID and the Hierarchy loaded and that I am not sure how SAP will deal with this SID wise.
Option 1 seems feasable as the hierarchy does'nt change every single day and doesn't require to be loaded every single day. But before going in this direction, I would appreciate some confirmation of my approach.
Thanks in advance for sharing your lights on this topic.
Rgds,
Bvpe

Answer 1

Hi Bart,
I just solved this very problem today in a two step process:
In our implementation, we only want to control when a new version of the hierarchy is created.  If nothing changes, whatever is brought in from the source system will just replace the current version.  We imagine we'll only create versions at month end or major re-organization.
1) I created a Select Options variable in tcode: stvarv called ZPROFCTR_FROMDATE.  I added a value to the low position and set the option to equals.
2) Open the infoPackage that is used to load the hierachy from the source system.  Go to the Hierarchy Selection Tab and click on the button at the bottom of the tabbed frame "Dynamic Hierarchy Selections".
You should see two check boxes, place a check in the second box: "Determine Using Routine"  Click on the create icon and put this in the routine
  p_s_sel_hier = l_s_presel_hier.
  data: tempfrom type tvarv_val.
  select single low
  from tvarvc
  into tempfrom
  where name = 'ZPROFCTR_FROMDATE'.
  move tempfrom to p_s_sel_hier-datefrom.
  p_s_sel_hier-dateto = '99991231'.
  clear p_subrc.
I've include the entire subroutine for context, and so you can see the SAP generated coments in the form that attempt to explain what the form is going to do.
Long story short, the hierarchy you have selected with the radio button on the Hierarchy Selection tab will be the one that is affected by this logic.
form compute_hier
  tables l_t_all_hier structure rshiertrsf
  using l_s_presel_hier like rshiertrsf
        l_infopackage   type rslogdpid
  changing p_s_sel_hier like rshiertrsf
           p_subrc like sy-subrc.
*Insert Source Code to decide which Hierarchy shall be loaded.
*The Hierarchy you select from table l_t_all_hier and fill
*into p_s_sel_hier will be loaded.
*The Structure l_s_presel_hier contains the pre-selection of the
*BW-Scheduler - just to inform you what the BW wll load
*if you change nothing.
*$*$ begin of routine - insert your code only below this line        *-*
  p_s_sel_hier = l_s_presel_hier.
  data: tempfrom type tvarv_val.
  select single low
  from tvarvc
  into tempfrom
  where name = 'ZPROFCTR_FROMDATE'.
  move tempfrom to p_s_sel_hier-datefrom.
  p_s_sel_hier-dateto = '99991231'.
  clear p_subrc.
*$*$ end of routine - insert your code only before this line         *-*
endform.                    "compute_hier
Hope this helps,
Quack