I settled on tagging both entities and accounts with UserDefined fields set to differentiate "discretionary" and "mandatory." Since nearly all the discretionary/mandatory lines use the same accounts, I placed a calculated account on each one to reverse out the line's balance for the opposite case. So the mandatory account will zero out it's line when looking at a discretionary entity. The rule that will handle this turns out to be fairly simple. I was trying to avoid custom metadata for every line that would require tons of VB to maintain.
05 February 2010
I spent today working at Market Street Coffee in Purcellville to avoid getting stuck at the office with the oncoming snow. It turned into an extremely productive day. With colleagues and clients in hibernation, I was free to focus on figuring out how to best handle the new SF133 requirements from Treasury in Hyperion Financial Management (HFM). I can see how Treasury is able to generate the SF133 directly off FACTS II submissions since all the data elements are either on the bulk file or already in Treasury's records. It's a little trickier to perform the same report in a consolidation system, where you can see the same numbers, but from multiple angles.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment