12/18/25 Update on iLab issues
The reported issue with internal iLab corrections/refunds is ongoing. Our team is actively working with our Agilent partners to resolve it, but unfortunately, a code fix before winter recess is not expected. As mentioned in previous alerts, please do not submit any new internal refunds or corrections, and cancel any that have been created, but not sent out. Events that have already posted incorrectly in SAP will be reversed. Our team will be in touch with the originating business office with additional information.
As a workaround for time-sensitive corrections only, core admins and their business office support should do the following:
AR corrections can be processed as normal (create the correcting event in iLab, email ilabhelp@purdue.edu to lock, and follow the AR SAP side correction process).
Questions and other support needs can be sent to ilabhelp@purdue.edu.
12/12/25 update:
The issue with iLab Corrections/Refunds reported on 12/4 by the iLab@Purdue team is still ongoing. Our team is actively working with our Agilent partners to resolve it.
Until the issue is fixed, please do not submit any new refunds or corrections and cancel any that have already been created. We will notify users as soon as the functionality is restored.
A potential cause has been identified, and our partners are currently developing a fix. We will provide another update once the issue is fully resolved. If you have questions, please contact ilabhelp@purdue.edu.
12/4/25 update:
The iLab@Purdue team and Managerial Accounting have discovered some additional post-upgrade issues with corrections, and ask that departments do not create or process correction events in iLab until these issues are resolved. We will send an additional update when the issues are resolved, any questions can be directed to ilabhelp@purdue.edu.
12/2/25 update: The upgrade process and post-upgrade fixes have been implemented, and users should have access to all funds uploaded prior to November 21st. Additional funds added through SAP or SPS since then will be uploaded beginning December 4th. Billing events may be created (as of Dec 1st), and will begin sending to SAP on December 4th as well (along with new Principal Investigator lab additions).
If you encounter any additional issues related to the upgrade, or need assistance with iLab usage, please contact ilabhelp@purdue.edu.
11/26/25 update: Additional fixes have been implemented, and there are now less than a dozen funds with formating errors. In some cases, funds will need to be "toggled" on for users, but otherwise can be used as normal. Additional messaging regarding the remaining funds and resumption of billing processes will be send out after the holiday break.
11/25/25 update: Fixes have been implemented that have resolved many of the display issues, but there is still a small number of IO and WBSEs in labs that do not appear correctly. Additional work is being done to resolve, and we expect to have these corrected before the holiday break.
The Purdue iLab implementation is experiencing issues post refactor, particularly with the display of some IOs and WBSE account strings. Users may be unable to select the proper fund due to a lack of unique identifiers of full account string numbers. The ilab@Purdue team is working with our partners to resolve, and will update this notificatio (as well as sending notifications through other campus communications). We thank you for your patience, and ask you send any immediate issues to ilabhelp@purdue.edu.
iLab@Purdue and Purdue IT, in conjunction with our partners are Agilent will be deploying iLab system changes on November 21st to allow for intercompany billing between Purdue and the Purdue Applied Research Institute. After this deployment, fund strings (IO and WBSE) will include a company code in front of them (PUR for Purdue, ARI for PARI) in all display fields.
iLab@Purdue staff will be making neessary edits to research/recharge core settings post upgrade and will notify each core when the work is complete, after which normal billing may resume.
Additional updates and status changes durung the upgrade process will be posted here.
Need help, but prefer to talk to a person? iLab support provides daily drop in remote sessions.
These are Q&A focused sessions, and not intended as a formalized training (if you need formalized training, please email ilabhelp@purdue.edu to schedule)
To access, click on the below links during the session time and you will be placed into a Teams call with our support team:
Drop in sessions are temporarily suspended until the iLab upgrade conclude on November 21st. New dates and links will be posted after that.
iLab Support has deployed new training materials for Principal Investigators (PIs), Lab Members, and Business Support Staff/Financial Admins (with upcoming revised materials for Core Admins and Staff). To access these, select Training at the top of the page.
In conjunction with Business Administration, Managerial Accounting and Sponsored Program Services, iLab Support has deployed a new and modified FY 25 Recharge Calendar. with extended Core Review and Department Account Review periods (each now seven days instead of the previous five). This change extended the billing period by four days, so business and account staff should not deactivate any used accounts until the 22nd of each month, and verify those accounts are not in active billings. The changes went into effect on July 1st, 2024.
For more information about iLab at Purdue, please contact ilabhelp@purdue.edu.
