Previous  Next          Contents  Index  Navigation  Glossary  Library

The Predefined Expense Reporting Workflow Definition

AP Standard Expense Report Process (Parent)

Server Side Validation Process

Attention: The Server Side Validation process also calls the DoCustomValidation function. You may want to customize this process to include any custom validation in your Expense Reporting workflow. For example, if you do not want to use AP Approval, then in the AP_EXPENSE_REPORT_LINES table, set both the JUSTIFICATION_REQUIRED_FLAG and the RECEIPT_REQUIRED_FLAG to N for all lines. Or, if you want AP Approval to be required for expense reports above a certain amount, then set both the JUSTIFICATION_REQUIRED_FLAG and the RECEIPT_REQUIRED_FLAG to N on expense reports below the amount.

Attention: If you use the DoCustomValidation function to perform custom processing for your expense reports, place any custom code in a directory protected from an upgrade prior to the upgrade. After the upgrade, if appropriate, reapply any custom code.

Warning: If you customize the predefined Workflow definition, do not modify the Payables Validation activity of the Server Side Validation process. This activity populates all missing required columns in AP_EXPENSE_REPORT_HEADERS and AP_EXPENSE_REPORT_LINES. If this activity does not complete successfully, you may encounter data corruption errors.

Manager (Spending) Approval Process

Attention: The Manager (Spending) Approval Process checks the SUPERVISOR_ID column in HR_EMPLOYEES_CURRENT_V and the AP_WEB_SIGNING_LIMITS table to obtain the approver(s) for an expense report, and to verify the spending authority of an approver(s). If you want to store spending authority in other (custom) tables, you need to customize the Find Approver activity and the Verify Authority activity of this process.

Request Approval Process

Third Party Expense Report Process

Rejection Process

No Manager Response Process

AP Approval Process

Attention: Once management approves an expense report during the Manager (Spending) Approval Process, the Workflow process determines if accounting review is required, and, if so, it checks if accounting review has occurred. If accounting review is required, and it has not been completed, the Workflow process sets itself in deferred status and waits for accounting review to be performed. You can perform accounting review in the Payables Expense Reports window. Once accounting review has been performed, you must run the Workflow Background Process to restart the Workflow process from deferred status. If the Workflow Background Process determines that accounting review has been performed, the Workflow process can continue towards completion. If the Workflow process for an expense report does not complete, the expense report cannot be imported using Payables Invoice Import.

Suggestion: You should set the Workflow Background Process to run periodically to check for accounting review. See: Setting Up Background Workflow Engines.

Suggestion: If you do not require accounting review, you can use the DoCustomValidation function in the Server Side Validation process to set the RECEIPT_REQUIRED_FLAG column value to N and the JUSTIFICATION_REQUIRED_FLAG column value to N for an expense report. You can set these flags to N for all expense reports, or for only those expense reports below a certain amount threshold.

Attention: If you use the DoCustomValidation function to perform custom processing for your expense reports, place any custom code in a directory protected from upgrade prior to the upgrade. After the upgrade, if appropriate, reapply any custom code.

Shortpay Unverified Receipt Items Process

Policy Violation Shortpay Process

Missing Receipts Shortpay Process

See Also

Oracle Workflow Guide


         Previous  Next          Contents  Index  Navigation  Glossary  Library