Run FDM Report on Multiple Location

Question

Hello,
We are on FDM 11.1.2.1. What I'm trying to do is design/change one of the can reports out of FDM so that it will run on multiple locations. I can get the report to run on the current location, a location selected by the user or can get it to run on all locations (takes way too long). What I would like to be able to do is set it up to run the report for all of the children under a control review location. Has anyone ever attempted this or do you have any insight into how to accomplish this? Any suggestions would be appreciated.
Thank you,
Jason

Answer 1

Some food for thought.
The easiest way to do this would be to have a stored procedure / SQL query that the report is going to hit that will give it exactly what it needs.
- If you are OK with hard coding values into locations, I agree that the Group Tag idea is good. You could retrieve all of the locations with a query like :
select * from tPOVPartition where PartNotes = 'GroupNameHere'or assuming it is going to be used in there where clause :
Select blah blah blah
from blah blah blah
where blah blah blah and (PartitionKey in (select PartitionKey from tPOVPartition where PartNotes = 'GroupNameHere'))
- If you are NOT OK with hard coding Group Tags and want to just let the natural hierarchy work, there is hope.
By using the tStructParitionLinks table, you can traverse the hierachy and get your list.
Assuming You have nothing deeper than 1 level, the follow SQL will work:
(NOTE: Start Location would be the parent and Endlocation would be the child)
SELECT     a.StartLocationID, a.EndLocationID, b.PartName
FROM         tStructPartitionLinks AS a INNER JOIN
                      tPOVPartition AS b ON a.EndLocationID = b.PartitionKey
where a.StartLocationID = <starting parent ID>The problem here is that if you have multiple nested levels, this query is not going to return all of the base items. If you need something to do that, than what you want to do is create a nested stored procedure. I'm not going to supply one as it would take me a bit to write it up.
The basic premise is :
- The stored procedure takes an input parameter, ParentID
- The stored procedure uses a temp table to hold results
- The stored procedure keeps track of it's recursive level and starts at one. (SQL Server handles this built in, assume oracle does as well)
- When you call the routine, it takes the ParentID, scans the Partition Link table and pulls all children that are tied directly to it.
- For each of the children, it adds an entry to the temp database table.
- Then it checks to see if that child record is also a parent in the table.
- If it is a parent, it calls another instance of itself (stored procedure) this time passing the child ID as the parent ID
- Eventually after you've exhausted all of the children/parents, you end up at the end of the initial call and at this point, you return the contents of the temp table.
- A third option, would be to use FDM script to accomplish this. In theory you could kick something off in a script, have it pull the list of children, and have it pass that info to the report and run it..... The following script will give you a listing of children for a parent :
Sub ShowChildren()
'Hyperion FDM CUSTOM Script:
'Created By:       cbeyer
'Date Created:       2012-02-22-10:43:06
'Purpose:
'Declare variables
Dim lngLocID
Dim lngParentID
Dim strParentName
Dim strChildren
'Get current ID by current POV
'NOTE: You could easily change this around to accept a parameter, etc, by using GetName/GetID calls shown below.
lngLocID = STRUCTMGR.fGetLocationIDFromName(API.POVMgr.PPOVLocation)
'Get parent ID
lngParentID = STRUCTMGR.fGetLocationParent("Controls", lngLocID)
'Get Name of parent
strParentName = STRUCTMGR.fGetLocationName("Controls", lngParentID)
'Create recordset and Enumerate children
With STRUCTMGR.frsChildrenAll("Controls", lngLocID)
   If Not .BOF And Not .EOF Then
       Do While Not .EOF
          strChildren = strChildren & .Fields("PartName").Value & vbCrLf
          .MoveNext
       Loop
   Else
       'No children
       strChildren = "Location has no children"
   End If
   'Close recordset
   .Close
End With
'Display the children information
If LCase(API.DataWindow.Connection.PstrClientType) = "workbench" Then
     MsgBox "List of Children for " & strParentName & " : " & strChildren
Else
     'Web Client (Set API action properties)
     RES.PlngActionType = 2                    
     RES.PstrActionValue = "List of Children for " & strParentName & " : " & strChildren
End If
End Sub