Documente Academic
Documente Profesional
Documente Cultură
Agenda
Agenda
• Participants in this process receive messages in the Employee Work Center (P012503) or via email.
• Information passes from one participant to another based on a set of procedural rules.
• These rules define the conditions that must be met before the workflow sends the expense
information to the next participant.
• As of EnterpriseOne release 9.0, the Expense Management solution provides the following
functionality:
• Distribution lists
• Approval hierarchies
• Escalations
• Automatic approval adjustments when organizational changes occur
Agenda
1. Routing Rules
2. Workflow Queues for Expense Management
3. Determine Next Activity
4. Parent/Child Structure
5. Workflow Distribution List
6. Workflow Communication Preferences
7. Employee Profile Setup
8. Update Manager ID
9. Update Employee Profile Structure Types
• Workflow Queues are defined in UDC table 02/MB (Electronic Mail Boxes). The
following values are used in Expense Management:
• The “Determine Next Activity Processing Option” (P09E0007) program can be accessed
via IV (Interactive Versions) and only contains one processing option:
• Workflow message to manager when approval is not required:
• Valid values are:
• Blank: Do not send
• 1: Send
• Messages can sent to the Approver, Employee or Auditor; either via the Work Center (P012503)
or E-mail.
• The Employee’s Address Book (P01111) setup determines the communication method.
• Every employee, manager or approver who uses the Expense Management system must have
an Employee Profile.
• The Employee Profile defines how an employee’s expense report is processed, approved, and
reimbursed.
• Each employee record has an associated manager.
• The Employee Profile contains a user defined structure type which represents the
distribution list the employee belongs to for expense report approval.
• The Update Employee Profile Structure Types report updates the structure type for one or more
employee profiles.
• In PROOF mode, this UBE can be used as an integrity report to validate employee profile
structure types.
Additional
Auditor
approval No Audit required? Yes
approval?
required?
No
Process Expense
Yes
Report
Reimbursement
vouchers created
and message sent
Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | to employee
Expense Management Workflow Process – Expense Entry
1. Expense Report Entry
Agenda
• Use data selection to select the correct records: Process ID equal to “EXPROUTING”
(PROCNAME), Status equal to “Processing Error” (PROCSTS) and User originator address
number equal to “Instance Originator” (ISTORG)
• Note: Run the UBE to purge any demo data delivered with the install.
1. Make sure that the Routing Rules contain the 12 default statuses; even if not used.
2. The Next Status must end in 00.
5. Multiple Authority
• The individual with multiple authority may enter expense reports on behalf of the
employee.
• However, the individual with multiple authority is not allowed to submit expense reports on
behalf of an employee because it is considered an audit risk. Employees must submit their
own expense reports.
• This functionality is activated by adding a flag in the employee profile revision (P20103) and
setting up the Address parent/child revision (P0150) using the structure type ERS (UDC 01/TS).
6. Resending Workflow
• A possible work-around for this issue is to use a generic administrator address book/sign-
on that is included in the distribution list at the employee level when resending
messages.
8. Approval Process
• Ensure that the Expense Report Approval program (P09E113) does not time out when
approving or rejecting expense reports. This may corrupt the workflow for that expense
report.
• Do not cancel out of the Expense Report Approval program (P09E113); this will cause
the workflow to go into an error status.
• Make sure that the manager belongs to the Business Unit for which expense reports
were entered. If not, the manager is unable to view the expense report (for approval or
reject).
Agenda
Agenda
JDE-GetProactive_us@oracle.com
Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |
Learn More
Available References and Resources to Get Proactive