Page Comparison

Status Updates: 

• Ninth Integration Test: January 20th - March 10th

  
  
  • Parking (Completed)
  • Housing/OSCAR (Completed)
  • CTES (Completed)
  • Library (Completed)
  • Payroll (Completed, Black Box file)
  • Student Financial Systems
    
    • ARC (Completed, Black Box)
    • SBS (Completed)
    • CBSO (Completed)
    • CCCS (Completed
    • OPAL (Completed)
    • SLC (Incomplete, Black Box)
    • Fin Aid (Completed)
    • Grad Div (Completed)
  • Telecomm/COMPCO (Completed, Black Box)
  • C&G Billing (Complete)
  • IRB (Complete)
  • ULAR (Complete)
  • Facilities (Completed)
  • Medical Center (Incomplete)
  • UCOP (Incomplete)
  • Bio Sci (Will use Service Billing instead)
  • Phy Sci (Complete)
  • UNEX/Summer Session (Complete)
    
    

...

...

• PI Report

  
  
  • 70% complete, is not able to test because lack of data, the month end balances for awards, and income and expense balances from C&G.  Waiting for balance from DataWarehouse, being worked on.

• C&G Billing

  
  
  • 100% complete. Testing in progress.

• HR

  
  

  •  Implementation is completed including translation of FS data to KFS counterparts, validation, GUI, ledger posting, invoice, BLISS reports as well as first time database alter script.  One time data migration will utilize the web service client. All FAUs will be translated per function user's request. This means even closed FAUs need to have a match in KFS.

  • Outstanding items: There is no 2013 chart of account data in KFS test server, so "2012" is hard-coded for object code translation and validation. Ledger posting is hard-coded to post to fiscal year 2012. Once the 2013 data is loaded in KFS, hard-coding needs to be removed.  There is no object code mapping for 7217 and 3900 under MC chart. Alerted KFS team of this issue. This means full testing will be delayed until these object codes are added.  Default CTES account/fund is translated to different values every time in KFS. However the default CTES account info is hard-coded. Once the translation is finalized, the default CTES chart/account/object will needs to be set.   Implementation to generate GL collector file is complete. However there is no KFS test server to upload the collector file from Unix. Currently must go through the Kuali Portal to manually upload the file.

    • Medical Center

      • No	Task	Spec/Mapping	Coding/Deployment	Assigned To	Status
        1	Cache DB Upgrade on Test Server	n/a		AMS/UCIMC	Waiting for approval by MC purchasing
        2	Chart of Accounts Conversion Strategy	Completed	In testing	AMS/UCIMC	Changed the strategy to just map their code to KFS instead of conversion, using the web services; testing in progress
        3	KFS to AMS Vendor Feed	Completed	Completed	KFS Tech Team	Code installed in AMS Test Server, ready to be tested in ITC4
        4	KFS to AMS Check Number Feed	Completed	In Testing	KFS Tech Team	In Testing
        5	AMS Payment Upload	Completed	In progress	AMS	Coding in process
        6	AMS AP Accrual Feed (Collector Flat)	Completed	In progress	AMS	Targeted completion date unknown
        7	AMS to KFS Secure FTP	NA	In Testing	Modesto/Artie Butler	In testing with AMS Test Server.
        8	KFS to SMS FTP	NA	In progress	Modesto/Phil Obregon	Files are being sent, however, no feedback has been provided. MC is still to set up XFER connection

• Facilities

  
  
  • Figuring out process outside of feeding.  Feeding process is complete.

• Housing

  
  
  • OSCAR-KFS Integration Project

• Biological Sciences

  
  
  • Restarted their efforts to convert to KFS after being put on hold.

• Telecommunications

  
  

  RMS:  Feed generation and upload was successful, after stripping legacy project codes from feed.

  Currently unable to test fields: sub-account, sub-object, project - test/sample data still not available to test with?

  Testing and fixing web form, but that's not directly related to the KFS upload process.

  Compco:  Relying on blackbox conversion.  Some charges are being rejected because "closed" accounts are still being used.  A meeting is scheduled for the Business Office to meet with FS to figure out what happens to the charges, what the Business Office needs to do, and how we'll be notified in order to remove these "closed" accounts from our Compco billing system.

  Modesto will regularly provide updated "aftable" and "dptable" data files on xfer.adcom.uci.edu for Compco to update from.

  Other than that, Compco KFS upload is pretty much done.

•  OIT Helpdesk

  • Regarding KFS conversions for Help desk related systems, I am having difficulty getting answers to my questions so I can proceed with conversion. Neither Nancy nor KFS@uci.edu has responded to the most critical questions.  Below is a copy of email I sent earlier this month, with a few answered questions removed.

    I also need to ensure the terminology is used (or not) in the same way.  For example, yesterday I heard an unconfirmed rumor that the KFS sub-account field is roughly equivalent to the current GL “sub” field, and is of little consequence.

    Should the current data flow of transactions from Help Desk → paper! → Business Office → RMS à (GL soon KFS) be continued? (Nancy or Marie must decide)  

    Will we utilize Control Accounts? (KFS question)

    Is the meaning of Principal Investigator unchanged?  Or is this now a Fiscal Officer or Account Supervisor? (KFS question)

    Is the role of bookkeeper/Account Controller now termed the Account Manager? Will “Account Controller” exist? (KFS question)

    Who can approve the specs / change request as complete and correct? (Nancy, Marie, or KFS)

    Who is responsible for defining the scope of work and approving planned changes? (Nancy, Marie, or KFS)

    Below is my current understanding of the data we will have to collect for a KFS “recharge”.  Is it correct?

     

    Field Name	Required	Type	Description/comment
    Chart	Yes	Char(2)	Location UC - UCOP SW - Systemwide IR - Irvine campus MC - UCIMC PL - Plant   We expect mostly IR & MC
    Account	Yes	Char(7) the values are all numeric/integer	replaces FS account-fund
    sub - Account	No	Char(5) alphanumeric	defined by dept
    Object	Yes	Char(4) alphanumeric	Is this similar to current object code? What will the new code structure be?
    sub - Object	??	Char(4) alphanumeric	Will OIT utilize this field to track software type?
    Project	No	Char(10) ?	Is this at a given department’s discretion?
    Reference ID	No	Char (8) ?	Do we prompt for this, or is it auto-generated by KFS? (another rumor I head yesterday)

     

    Bob Hudack
    rjhudack@uci.edu
    Help Desk
    Office of Information Technolog

...

Should the current data flow of transactions from Help Desk → paper! → Business Office → RMS à (GL soon KFS) be continued? (Nancy or Marie must decide) 

...

Below is my current understanding of the data we will have to collect for a KFS “recharge”.  Is it correct?

Bob Hudack
rjhudack@uci.edu
Help Desk
Office of Information Technology