Approvals
Approvals
Implementation Workshop
[ 19 Feb - 23 Feb ]
CANCELLED
[ 04 Mar - 07 Mar ]
• Zoom session is approximately for about 4.5 hours and covers presentations, use-cases & product demonstrations
• Audio lines are placed on mute for the entire session. Please submit your questions at any time during the Zoom session via Q&A
Panel
• If any questions remain unanswered, please post them on Q&A chat on SecureSites. Post Zoom, you will perform the activities/labs
offline and use forum incase of any questions or issues
✓ Configure using Spreadsheet ✓ Financial Reporting Studio ✓ File Based Data Import ✓ Sandbox
✓ Sample Use Cases ✓ SmartView ✓ Financial Extracts ✓ Appearance
✓ Migration, Archive & Purge ✓ OTBI ✓ BIP Report Extract ✓ Structure
✓ Advanced Mode ✓ Sunburst ✓ BI Cloud Extracts ✓ Page Composer
✓ Best Practices ✓ BI Publisher ✓ File Encryption & Decryption ✓ Page Integration
Harsh Tulsyan
Principal Product Manager
Oracle Development
Safe harbor statement
The following is intended to outline our general product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing decisions. The development, release,
timing, and pricing of any features or functionality described for Oracle’s products may change and remains
at the sole discretion of Oracle Corporation.
Statements in this presentation relating to Oracle’s future plans, expectations, beliefs, intentions and
prospects are “forward-looking statements” and are subject to material risks and uncertainties. A detailed
discussion of these factors and other risks that affect our business is contained in Oracle’s Securities and
Exchange Commission (SEC) filings, including our most recent reports on Form 10-K and Form 10-Q
under the heading “Risk Factors.” These filings are available on the SEC’s website or on Oracle’s website
at [Link] All information in this presentation is current as of September 2019 and
Oracle undertakes no duty to update any statement in light of new information or future events.
• All invoices not matched to a Purchase order must be approved by 1 level of Supervisory hierarchy. Each such unmatched invoice must have a requester available on it, and the
approval process must start from the manager of the Invoice requester. Invoices that are matched to a Purchase order do not require this type of approval.
• Any invoice not matched to a Purchase order, and which does not have a requester available on it, must be automatically rejected in the approval process.
Invoice Amount
• Further, any invoice with an invoice amount of more than USD 5000 requires approval by the Finance approval groups. The organization’s business is such that supplier invoices
are created in several different invoice currencies and for the purpose of approval, they must all be evaluated in their USD equivalent amount. The approval group that needs to
approve any invoice depends on the Business Unit (US1) of the invoice and the Cost center (200 & 300) on the Invoice distributions. All members of the group must approve the
invoice.
• Any invoice which has an invoice amount less than USD 5000 should be automatically approved.
• From 23B, mandatorily create workflow rules using spreadsheet for Payables Invoice Approval and GL Journal Approval.
• This feature is applicable for new customers and no change for existing customers.
• Existing customers who use either of the workflows in the TEST/DEV POD, but did not migrate changes to the Production POD, no
longer have access to the Assignees tab. Use either of these options to configure rules in the Production POD:
• Migrate approval rules from TEST/DEV PODs to the SRC spreadsheet and use the Manage Workflow Rules using
Spreadsheet task to configure rules.
• Raise a service request to enable BPM. ✓ Simplified Rules Configuration
Text Operators
• start with; ends with; contains; matches; equals ignore
case; in
• example for ‘matches’ operator:
• 4th segment ranging from 2000-2999
• Matches (.*)-(.*)-(.*)-2[0-9][0-9][0-9]-(.*)
Number Operators
• >; <; >=; <=; in; between
Date Operators
• between; before; after; on or before; on or after
• format must be ‘dd/mm/yyyy’
Header Participant 1
• Amount = 6000 USD • Supervisor [S]
Block A (Participant Type = Serial [other options: Parallel (all), Parallel (single), FYI] • Purchase Order = NULL
• Requestor = Casey Participant 2
IF [unmatched & no requester] THEN Reject; Lines • Line 1: A1, A2
• Line 1: 102-00-5005-200-000 • Line 2: B1, B2
IF [unmatched & requestor] THEN requestor’s supervisor; • Line 2: 102-00-5005-300-000
• Line 3: 102-00-5005-000-000 Final approver list:
IF [matched] THEN skip approval;
S -> A1 -> A2 -> B1 -> B2
Invoice 2 Evaluation
Block B (Participant Type = Serial [other options: Parallel (all), Parallel (single), FYI] Header Participant 1
• Amount = 6000 USD • Supervisor [S]
• Purchase Order = NULL Participant 2
IF [amount >= 5000 USD & Cost Center = 200] THEN Approval Group A • Requestor = Casey • None of the conditions
Lines satisfy;
IF [amount >= 5000 USD & Cost Center = 300] THEN Approval Group B
• Line 1: 102-00-5005-500-000 • Validate BPM rules for
IF [amount < 5000 USD] THEN Auto Approve; • Line 2: 102-00-5005-000-000 Block2 and ensure it
returns a valid
approval hierarchy
21D Reference
Administrators can now use the 'Add Custom Value' option to define rules using start approvers
other than those available in the list of values. You can specify either transaction attributes that
indicate a user (for example, Invoice [Link] Manager Name) or specify the user
name of a specific user (for example, [Link]). You can also specify the manager of
transaction attribute users or specific users. For example, Manager of Invoice
[Link] Manager or Manager of [Link].
• Use the FYI option in the Approval Routing column to define rules to send information-only notifications that do not
require user action to approvers. Administrators can use this option to define rules to send FYI notifications to members of
a Supervisory Hierarchy or Job Level Hierarchy.
• Reference
PO Match
• All invoices which are not matched to a purchase order require supervisory approval
• Any unmatched invoice which does not have requester details should be automatically rejected.
• Invoices that are matched to a purchase order do not require approval under this rule
Invoice Amount
• All invoices with an invoice amount greater than or equal to USD 5000 require approval by the Finance approval group.
• The Finance approval group which needs to approve the invoice varies based on the invoice distribution cost center and the business unit on the invoice.
• Any invoice with an invoice amount less than USD 5000 should be automatically approved
• Invoices imported with a specific source and for specific supplier types require approval from an approval group where any one member needs to approve
the invoice.
• Any invoice from sources and supplier types other than these specific types do not require this type of approval
Sample Spreadsheet: Manage Workflow Rules in Spreadsheet > Invoice Approval > Download > Invoice Approval Sample Template 1
• All invoices for a business unit and with specific distribution account segment values requires approval from a job based hierarchy.
• The range of job levels that need to approve the invoice vary based on the invoice amount.
• Any invoice which does not have the specified distribution account segment values should be automatically approved.
Project Related
• All invoices which have project information on them require approval by the project manager.
• Any invoice which does not refer to a project should be auto approved
• All invoices with a pay group starting with 'Stand' and for which any freight or miscellaneous line has an amount more than 20 percent of the total invoice
amount, must be approved by an approver having the Accounts Payables Supervisor Role. Such freight and miscellaneous lines must have details
entered in segment 1 of the line level descriptive flexfield.
• If the invoice line descriptive flexfield segment1 does not have a value for such lines, then the invoice must be automatically rejected.
• Invoices which have freight and miscellaneous lines with amount less than 20 percent of the invoice amount should be automatically approved.
Sample Spreadsheet: Manage Workflow Rules in Spreadsheet > Invoice Approval > Download > Invoice Approval Sample Template 2
Invoice Source
• All invoices for specific invoice sources require approval by a supervisory hierarchy.
• The paygroup and invoice amount determine the required number of levels of supervisory approval.
• Invoices from certain invoice sources require approval by a specific approval group
• All invoices for asset purchases for specific cost centers with invoice amount more than a specific amount, require approval by the cost center manager.
• Invoices for the same specific cost centers for asset purchases less than the specific amount require auto-approval.
• Invoices for asset purchases by any cost center other than the specified cost centers require auto-rejection
Legal Entity
• All invoices for specific legal entities require approval by a supervisory hierarchy.
• The invoice distribution balancing segment value determines the starting approver for such supervisory hierarchy approval.
• An FYI notification should also be sent to the requester for such invoices
• Invoices for other legal entities require auto-approval
.
Sample Spreadsheet: Manage Workflow Rules in Spreadsheet > Invoice Approval > Download > Invoice Approval Sample Template 3
• For example, the object hierarchy for Payables invoices consists of At least one
invoice header, lines, and distributions. If an attribute from a non- Evaluates the lines or distributions against the rule conditions until at least
header level is used to configure rules, then the application evaluates one match is found. Once a match is found, no further lines or
each line or distribution object. distributions will be evaluated for the rule.
• This works well if the business requirement is to evaluate the approval None
rule conditions for each line or distribution. However, if the business Evaluates the lines and distributions to check that none of them match
requirement is to evaluate if the rule condition holds true for any one with the rule conditions.
line or distribution, then rules should be defined in advanced mode.
Aggregate
• Advanced mode offers additional pattern-matching options. These Allows use of a combination of operations, such as Sum, Count,
options can optimize rule execution even when rule conditions include Maximum and so on.
attributes from different object at different levels of object hierarchy.
Basic Mode
Rules engine will evaluate all the child lines if rule configured on a child level attribute.
Use Cases:
Advanced Mode
Rules engine will stop processing further child lines once it identifies the first child line which satisfied the rule condition
Use Cases:
• Route invoice for approvals if any of the invoice line match with the rule condition
• Route invoice for approvals if any of the distribution line match with the rule condition
Use Case: Send for approval if any of the invoice lines are NOT matched to PO
Basic Mode:
Advanced Mode:
At least one {
Invoice [Link] Header ID is null
}
Result: Evaluation will stop as soon as the first record is found matching the conditions.
Use Case: Any Invoice distributions having project details AND payment method code on the any Invoice installment equal to ‘Check’ or
‘Wire’.
Basic Mode:
Advanced Mode:
At least one {
Invoice [Link] Number = ‘12201’
} and
At least one {
Invoice [Link] Method Code in (’CHECK’, ‘WIRE’)
}
Result: Evaluation will stop as soon as the first record is found matching the conditions.
Surround
simple test
✓ Advanced Mode
simple test
✓ Advanced Mode of Rule Creation for Approvals
✓ White Paper on Advanced Mode in Journal Approval
Rules (Doc ID 2233374.1)
Use Case: Invoice amount more than 1,000 and invoice type is Standard and if any of the invoice line is not matched to PO then route invoice for approvals
using supervisory hierarchy of the workflow submitter.
Best Practice: Don’t use Basic. Use Advanced (‘at least one’ option)
Use Case: Invoice amount more than 5,000, Business Unit is Vision Operations and if any of the invoice distribution line having account “1560” which related
to capital expenditure then route invoice to the approval group “Capital Budgeting Department”
Best Practice: Don’t use Basic. Use Advanced (‘at least one’ option)
Use Case: Invoice header amount more than 1,000, invoice line matched to PO and invoice distributions having project details then route invoice to the
project manager.
Scenario: If business intent is to identify the lines that are matched to a PO and then check whether the distributions for such lines have project
number information on them. In this case, the invoice needs approval from Project managers for only those projects which appear on
distributions for which the line is PO matched i.e. both line and distribution conditions are satisfied.
Best Practice: Use condition Invoice [Link] Number = Invoice [Link] Line Number (to avoid cartesian product)
Scenario: If the business intent is to check whether there are any lines that are matched to a PO and evaluate all distributions (for all lines,
matched to PO or not) and check whether they have project information. In this case, project managers for projects on all the distributions will
need to approve the invoice.
Best Practice: Line condition in advanced (use: at least one) mode and Distribution condition in basic mode
Use Case: If invoice amount more than 1,000 and invoice description (non mandatory field on the transaction UI) starts with “ Airfare” then route invoice for
approvals.
Best Practice: Use Invoice [Link] isn’t null (otherwise null pointer exception)
Use Case: Any Invoice distributions having project details and payment method code on the Any Invoice installment equal to Check or Wire.
Best Practice: Use Advanced Mode ‘at least one’ on invoice distribution and ‘at least one’ on invoice instalment
o Do not use [Link] attributes; instead use direct attributes like Invoice [Link] Amount
o When defining auto approval, DO NOT use [Link]; instead use [Link]
o For Journals approvals, instead of using something like [Link] use [Link] Combination matches
*(.*).(.*).(8724).(.*).(.*).(.*)*
o Skip Approval cannot be the final outcome i.e., outcome of the last block
o Make sure ‘Line Manager’ is populated for employees
o Use pre-defined functions like Duration, Calendar etc to achieve desired outcome.
o Days lapsed between expense date and report submission date: [Link] between(Expense [Link] Report Date,[Link]())
o Days between date and period end date: [Link]
between([Link](),[Link]())
o Submitted transaction must satisfy one or more of the conditions within a block (participant); so make the conditions inclusive of possible data variants
o Run “Reassign Pending Approvals for Terminations and Correct Invalid Supervisor Assignments Process” at least once a day
o DO NOT define conflicting approval routings (participant types) in the same block. For example, Group in Serial & Group in Parallel. During the rule import
system does validate and return error(s).
o Workflow rules report and More financial workflows covered in 23A
o Optimization of workflow rule evaluation
• BPM Workflow All Domains Administrator Role (for all product families) • Invoice Approval and notification history REST API
• BPM Workflow Financials Administrator (for financials) • Approval Rules can be migrated using SOA Composer
• PR and PO Approval Rules Migration
• Audit the changes made to workflow configurations [New 22A]
34 Copyright © 2021,
2024, Oracle and/or its affiliates | Confidential: Restricted
Agenda
Subtemplate
Layout Template
Inserted from
data model xml
FinFunWorkflowNotificationSub InvoiceApprovalNotificationReport
/Shared Folders/Custom/Common Content /Shared Folders/Custom/Financials/Workflow Notifications
• Enabled for
• Payables Invoice Approvals
• Expense Report Approvals
• Journal Approvals
• Invoice Hold Release (21B)
• Documentation: Define Approval Management • Why You Assign Security Profiles to Roles
• Customer Connect: Common Use Cases & Best Practices • Configure Employee List of Values
• Documentation: Best Practices for Approval Management • Simplified Rule Configuration (SRC) Spreadsheet (Doc ID 2948013.1)
• Customer Connect: Recent Enhancements And Best Practices For Workflow Rules • Advanced Mode of Rule Creation for Approvals (Doc ID 2768204.1)
Configuration • A-Team Blog: Extend Oracle application cloud approvals on Oracle Cloud
• Customer Connect: Configuring Workflow Rules Using a Spreadsheet Infrastructure
• Customer Connect: Common Approval Issues encountered by Customers
• Oracle Fusion Payables Approvals Overview
• Payables Invoice Approval Process: Business Use Cases
• How To Setup A Vacation Rule For Journal Approval Process In Fusion Financials
• Overview of Journal Approval in Fusion General Ledger
• How to bypass Approval for Payables Invoices having a specific Source
• Advanced Mode of Rule Creation for Approvals
• Workflow Transaction Console
• Seeded Reports: Workflow Rules Report, Approval Groups Report & Workflow
Transactions Listing
• Migrating Workflow Rules from Oracle BPM and Maintaining Rules Using Spreadsheets
• Diagnostics Data Collection
✓ For a complete list of update-wise new features, visit Oracle Cloud Readiness
✓ Feature Opt-In Matrix
✓ Enable Offerings for Oracle Applications Cloud Release 13 Upgrade (Doc ID 2317112.1)
✓ Cloud Applications Roadmap
• Approvals are not available for On-Account Credit Memos (ER 21285074, 27950656)
• Reference
Dispute
Approval Task: FinArTrxnsCreditMemosAutomaticManual
AutoAction = HtOutcomeCreateManualCreditMemo
FinArTrxnsCreditMemosApproval Credit Memo to be created
for Review Configure Task
FinArTrxnsCreditMemosCreationPostProcessing
to notify reviewers