ISFP Install Notes

  • When upgrading to the merged release of ISFP, I had to recreate the df_signon view in son_db.
  • You also have to remember to grant execution priveleges for ISFP database as well as df_signon.

Some times the SQL transaction log can get quite large. To reduce the size, issue this command in query analyzer:

USE df_isfp
DBCC SHRINKFILE (df_isfp_Log, 10)

ISFP Drilldowns

Main Functionality

A record is created in df_fp_budselect_dtls every time the expand icon is clicked, and the report rerun.
The record includes :

  • the current "session ID" (in the form of a budselectid),
  • the budselectnode wich appears to be an Identity field,
  • segnum (the ref to how far down the drilldown path you've come),
  • glnumstart (the beginning up the glnum up to the point of the node)

When collapsed, the record in the budselect_dtls table is merely deleted.


  • How does the data break down? Should I do it by year first?

How this would look if you broke it down

For Data: 2003 Acc DEC and 2003 Acc NOV.

40 + Fee Receipts 50,668,301.86 56,348,065.93
42 - Other Revenue 26,017.89 99,941.49
4011 Interest Income 24,141.71 68,906.99
4013 Honoraria 22,084.36
4014 Miscellaneous Inc 1,876.18 8,950.14
4019 Markup
6902 Recovery-Deposit

Order of processing for Expand Detail

  • onClick for Expand icon
  • Create a dataset from middle tier, passing username, "FunVal" (ID of the clicked value), and a ViewState value that links what user/session is making the request to the detail lines in the database.
  • Middle-Tier calls Data Layer method to create detail lines for clicked object. The dataset is then returned and nothing really done with it.
  • RunReport decides how to output the additional data lines

Initial SQL For P&L Drill Down