Marquette University implemented iExpense in May 2016. A brief summary of the iExpense functionality /features implemented at MU will be shared, followed by a more in depth discussion of the approval and review process. During the process definition phase the project team learned that business requirements for the approval function varied more than expected by department/college. The approval workflow needed to be static (not ad hoc) yet flexible enough to address each unit's business practice without customizing critical EBS functions.Using MS Visio, the team mapped out the iExpense submission and approval process, which helped identify gaps to be closed and decisions to be made during development and testing. The technical team wrote code that is executed by AME, leveraging existing data and some new Descriptive Flexfields in the HRMS module, to route iExpense transactions differently than the delivered supervisor hierarchy, as needed. These exceptions are easily maintained by the functional team.In addition, the project team used MS SQL Server Reporting Services to develop reports that enable team members to view current system configurations by organization and employee. These reports are used for troubleshooting and monitoring approval rules.
International / Regional
Finance | HCM | Student Systems | CRM | Technical | Careers
Alliance / International / Regional / E-Academy
User Membership / Corporate Membership