Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date

Attendees

 

Goals

  • Discuss the outstanding items for the Balance Conversion
    • Transactions?
    • Balances
      • Balance Sheet Accounts (Liability/Asset/Income)
      • Fund Balance
      • Expense

    • SRECNP hierarchy?

Notes

  • (FS) Expenditure accounts (4xxxxx) will be created based on the UC expenditure account and UC fund link combination. 
  • (FS) Income accounts will be converted to Income object codes that will be grouped by a control account.  Each of the control accounts will represent a UC fund. 
  • (FS) Balance sheet accounts will be converted to object codes and will also be grouped by a control account.
  • (FS) Fund Balance and Trans Code
    • Trans Code will be Object Codes type IN/EX

    • Anytime a transcode is used on any KFS account on a transaction, KFS will derive the UC Fund Balance Account based on the Sub Fund group code of that KFS Account

       

       

References

Jira
https://jira.oit.uci.edu/browse/KFSDW-639

TM1 CUBE
https://wiki.oit.uci.edu/display/public/BO+Cube+Design+-+Hierarchies

Discussion items

TimeItemWhoNotes
    

Action items

  • Durendal Huynh will locate the missing KFS entries (Account/Org....)
    • Options:
      • Create new KFS entries
      • Ignore old FS transactions for inactive Org/Accounts
      • Map the missing entities to existing KFS entities
      • Will provide time line of available items by  
  • Maria Gorginova will discuss with Valerie where to place this data
    • Options
      • In a separate fact table that will need to be pulled in separately from the report
      • In the same fact table, but ETL will have to be aware of the historical data when truncate/load
      • If new KFS entities, make sure ETL will pull these in.

 

 

 

 

  • No labels