0% found this document useful (0 votes)
102 views48 pages

Approvals

The document outlines a Financials Cloud Technical Implementation Workshop scheduled for February and March 2024, targeting Techno-Functional Consultants and Technical Consultants. It includes a detailed agenda covering topics such as approvals, reports, integrations, and extensibility, with a focus on use case-driven, implementation-focused learning. Participants are expected to have basic functional knowledge of Financials Cloud and will engage in presentations, demonstrations, and hands-on labs during the sessions.

Uploaded by

anshulmishra96
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
102 views48 pages

Approvals

The document outlines a Financials Cloud Technical Implementation Workshop scheduled for February and March 2024, targeting Techno-Functional Consultants and Technical Consultants. It includes a detailed agenda covering topics such as approvals, reports, integrations, and extensibility, with a focus on use case-driven, implementation-focused learning. Participants are expected to have basic functional knowledge of Financials Cloud and will engage in presentations, demonstrations, and hands-on labs during the sessions.

Uploaded by

anshulmishra96
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Financials Cloud - Technical

Implementation Workshop

Sreeni Devireddy Vinit Poddar Harsh Tulsyan


Product Management Director Product Management Director Principal Product Manager
Oracle Development Oracle Development Oracle Development
[ 05 Feb - 09 Feb ]

[ 19 Feb - 23 Feb ]

CANCELLED

[ 04 Mar - 07 Mar ]

2 Copyright © 2021, Oracle and/or its affiliates | Confidential: Restricted


Logistics

• Focus Area: Financials Cloud “native” technical capabilities

• Target audience: Techno-Functional Consultants, Technical Consultants & Architects

• Pre-requisite: basic functional knowledge of Financials Cloud

• Approach: Use case driven, Implementation focused

• Content & Environment

• SecureSites access e-mail from Oracle Content and Experience (no-reply@[Link])


• For environment details, e-mail oracle-development_ww@[Link]

• 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

3 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Financials Cloud – Technical | Workshop Agenda

Day 1 Day 2 & 3 Day 3 Day 4


Approvals Reports Integrations Extensibility

✓ 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

✓ Configurable Notifications ✓ REST & SOAP API ✓ User Interface Text

✓ Transactions Console ✓ API Authentication ✓ Messages, Lookup & Data


Security
✓ Business Events
✓ Personalizations
✓ B2B Messaging
✓ Flexfields

4 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Oracle Financials Cloud
Approvals

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.

6 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Agenda

• Configure using Spreadsheet


• Sample Use Cases
• Advanced Mode
• Best Practices
• Migration, Archive & Purge
• Configurable Notifications
• Transactions Console
Architecture | SOA | BPM | Human Workflow | AMX

AMX Approval Management extensions


extend human workflow services with
complex approval patterns. It serves as a
sophisticated "Assignment Manager" for
human workflow.

AMX provides the following additional


features:

• Attributes derived from ADF view object in


transactional applications
• The ability to retrieve various job, position,
and supervisory hierarchies from HR
systems using hierarchy provider plug-ins.
• The ability to define rules for controlling
approval lists and hierarchy configurations

BPM Technical References


BPM: Using Approval Management
BPM: Using Human Workflow

8 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Financials | Supported Approvals
Product Transaction Setup task for enabling approval (if any)
Payables Invoice Manage Invoice Options
Payment Process Request Manage Disbursement System Options Refer Appendix A

Invoice Account Coding Manage Invoice Options Replay

Hold Resolution Manage Invoice Holds and Releases


Incomplete Invoice
General Ledger Journal Specify Ledger Options; Manage Journal Sources; Manage Journal Categories
Expenses Expense Report
Cash Advance
Spend Authorization
Receivables Dispute / Credit Memo Refer Appendix B

Intercompany Intercompany Transaction Manage Intercompany Transaction Types


Receiver Distribution
Budgetary Control Override Request
Cash Management Bank Account Transfer
Advanced Collections Bankruptcy

To Search BPM Workflow Task

9 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Approval Routing (or) List Builders

Anita Kennedy Anita Kennedy • Approval Group


Director
(Director) (Director; Job Level = 3)
• Serial Mode
• Parallel Mode
Casey Brown Casey Brown o Group in Parallel (all should approve)
Senior Manager
(Senior Manager) (Senior Manager; Job Level = 2) o First Responder (any one to approve)
• Role
Pat Stock Pat Stock • Named User
Manager
(Manager) (Manager; Job Level = 2)

Mary Walton Mary Walton


Consultant
(Consultant) (Consultant; Job Level = 1)

Supervisory Job Level Position Hierarchy

• ‘Job Level’ field in Job • Position Tree must be defined


• ‘Line Manager’ field on Definition in HCM
employee definition
• All approvers / Final approver • All approvers / Final approver
only / manager and final only / manager and final ✓ Parallel Approval
approver / include all approver / include all
managers at last level managers at last level ✓ List Builders - Documentation
• Job levels can be a range • Position levels can be a range

10 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Use Case | Discussion & Demo
Purchase Order Matched or Unmatched

• 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.

Business Requirement Approval rules in spreadsheet


Routing Type Rule details
Unmatched invoices with requester require Supervisory Hierarchy Invoice is not matched to a PO. Requester details are available.
supervisory approval. Any unmatched invoice [1 Level]
without approval should be rejected. Matched
Auto Reject Invoice is not matched to a PO. Requester details are not available.
invoices do not require this type of approval.
Skip Invoice is matched to a PO.
Invoices with invoice amount greater than USD Group in Serial Invoice amount is more than USD 5000
5000 require approval from Finance approval [For US1 BU & CC 200 -> GRP1]
group. Any invoice with amount less than USD [For US1 BU & CC 300 -> GRP2]
5000 should be automatically approved.
Auto Approve Invoice amount is less than USD 5000

11 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Simplified Workflow Rules in Spreadsheet Enforcement [23B]

• 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

12 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


✓ Rule Block Configuration
Workflow Rules in Spreadsheet | Demo

13 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Routing & Operators

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’

• To negate any condition add ‘not’ as prefix


• Operators are not case sensitive
• Create Workflow Rules Using Spreadsheet

14 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Evaluation
Invoice 1 Evaluation

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

15 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Start Approver | Use Dataset & Add Custom Value

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].

16 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


FYI Option for Supervisory & Job Level Hierarchy

• 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

17 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Agenda

• Configure using Spreadsheet


• Sample Use Cases
• Advanced Mode
• Best Practices
• Migration, Archive & Purge
• Configurable Notifications
• Transaction Console
Use Case One | Discussion & Demo

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

Source and Supplier Type

• 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

19 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Use Case Two | Discussion & Demo

Distribution Account Segment

• 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

Pay Group and Invoice Amount

• 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

20 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Use Case Three | Discussion & Demo

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

Cost Center and Asset Purchases

• 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

21 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Agenda

• Configure using Spreadsheet


• Sample Use Cases
• Advanced Mode
• Best Practices
• Migration, Archive & Purge
• Configurable Notifications
• Transaction Console
Basic Vs Advanced Mode

• Financial transactional models consist of an object hierarchy where Each


one parent object can have one or more child objects and each of Evaluates each line or distribution to check if there is match with the rule
these child objects can have one or more grandchild objects. conditions.

• 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.

23 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Basic Vs Advanced Mode

Basic Mode

Rules engine will evaluate all the child lines if rule configured on a child level attribute.

Use Cases:

• Route invoice for approvals based on invoice header information only


• Route invoice for approvals if all invoice lines match with the rule condition
• Route invoice for approvals if all invoice distribution lines match with the rule condition
• Route invoice using invoice line or distribution attributes like requester from Invoice lines or project manager from invoice distributions.

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

Options are: At least one / Each / None / Aggregate

24 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Basic Vs Advanced Mode | Discussion & Demo

Use Case: Send for approval if any of the invoice lines are NOT matched to PO

Basic Mode:

Invoice [Link] Header ID is null

Result: All invoice lines are evaluated

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.

25 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Basic Vs Advanced Mode | Discussion & Demo

Use Case: Any Invoice distributions having project details AND payment method code on the any Invoice installment equal to ‘Check’ or
‘Wire’.

Basic Mode:

Invoice [Link] Number = ‘12201’ and


Invoice [Link] Method Code in (’CHECK’, ‘WIRE’)

Result: All invoice distributions and all installments are evaluated.

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.

26 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Use Case | Discussion & Demo

✓ Condition: If there is at least one cash


Surround
Surround
expense that is charged to non-default cost
center
simple test Pattern
✓ Advanced Mode

Surround

simple test

27 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Pattern

Use Case | Discussion & Demo

✓ Condition: If the total expense charged to


default cost center is more than 500

✓ Advanced Mode

simple test Surround

simple test
✓ Advanced Mode of Rule Creation for Approvals
✓ White Paper on Advanced Mode in Journal Approval
Rules (Doc ID 2233374.1)

28 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Agenda

• Configure using Spreadsheet


• Sample Use Cases
• Advanced Mode
• Best Practices
• Migration, Archive & Purge
• Configurable Notifications
• Transaction Console
Best Practices

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

30 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Best Practices

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

✓ ERP – Workflow Rules Configuration Best Practices - Replay


✓ ERP – Recent Enhancements And Best Practices For Workflow Rules Configuration - Replay

31 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Best Practices

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

32 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Agenda

• Configure using Spreadsheet


• Sample Use Cases
• Advanced Mode
• Best Practices
• Migration, Archive & Purge
• Configurable Notifications
• Transaction Console
Migration, Archive & Purge
• Tasks are automatically archived once a day without you having to set
anything up. You can't change or stop this automatic archive, which
includes all eligible tasks that aren't archived yet. These scheduled
processes run in this order to get the daily archive done:
Updating the file
• Extract Workflow Tasks for Archive
• With the new releases / updates, workflow rules spreadsheet may
change • Process Translations for Workflow Tasks Archive
• Upload Workflow Task Attachments for Archive
• On the new file, choose ‘Update Spreadsheet’ option > select your
existing file > to load the rules from your existing spreadsheet
• Archived tasks that were last updated over 30 days ago are purged without
you doing any setup. The purge runs daily at midnight. You can't change
Importing the rules from BPM or stop this automatic purge.
• Download BPM rules into a file; Manage Workflow Rules in Spreadsheet • After a task is purged, users can no longer find it in BPM Worklist or the
> Download BPM Rules Worklist: Notifications and Approvals work area. The task's approval history
• This downloads the rules into a JSON file won't be available either. But, the tasks are still in the archive tables and
available in analytics or anything else that reflects the archived data
• From spreadsheet > Import Rules into Spreadsheet > Choose JSON file
• For workflow data, you can use the tables that start with FND_BPM in the
• If you choose to, can restore the rules back to BPM; Manage Workflow
Oracle Applications Cloud Tables and Views for Common Features guide,
Rules in Spreadsheet > Restore Rules
and the Manage Tasks API in the REST API for Common Features in Oracle
Applications Cloud guide. Don't query other tables or use other APIs that
Roles required for defining rules aren't documented.

• 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

• Configure using Spreadsheet


• Sample Use Cases
• Advanced Mode
• Best Practices
• Migration, Archive & Purge
• Configurable Notifications
• Transaction Console
Configurable Notifications | Controls

Administration > Application Preferences Notifications tab


• Turn-off Notifications • When: Assign; Complete; Error; Expire; Alerted; Update; Outcome;
• From Display Name Update etc.,
• Who: Assignees; Initiator; Approvers; Owners; Reviewers; Email from
• Test E-mail Address
Payload
• Max no. of email attachments
• Reminders [Prefix in Subject]
• Max size of email attachments • Display Name
Automatic Dismissal or Withdrawal • Actionable email notifications; hide URL
• ‘FYI Notifications Expiration Period’ profile option (7 days Configuration tab
default)
• Prohibit Self-Approval [at participant level also]
• Open Tasks Withdrawn After Number of Days (180 days
default) • Mandate Comments
Vacation Rules / Delegations [Limit Whom to Reassign or Delegate Workflow Tasks To]
• Preferences > Vacation Period
Deadlines tab: Due Date & Expiration Settings
• Preferences > My Rules
• Preferences > Other Rules
Access tab
People
• Content: Payload; Attachments; Assignees; Comments; Dates;
Flexfields; History; Reviewers • Task Owner; Reviewers; Error Assignees

• Actions: Escalate; Delegate; Reassign; Adhoc Route etc.,


• Who: Admin; Approvers; Assignees; Creator; Owner;
Reviewers

36 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Configurable Notifications | Content and Look & Feel
/Shared Folders/Custom/Common Content
Provides common components, such as a
branding logo and buttons, that can be
reused in multiple reports.

Customize subtemplate to insert branding


logo or any common text / instructions etc

/Shared Folders/Custom/Financials/Workflow Notifications


Determines final content & appearance

Customize layout template to include additional


fields (from data model) into the output and/or
to include changes from subtemplate

Determines which attributes


from data sources are available
to be included in the notification
and how that data is retrieved.

Customize data model if you


want to add more fields into the
extract
/Shared Folders/Custom/Common Content
/Shared
Provides styles such as the type of lines and
Folders/Custom/Financials/
fonts to use in tables, or the font type, size,
Workflow Notifications
and color to use for headings

37 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Task
Configuration

Before & After

Subtemplate

Layout Template

38 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Subtemplate Layout Template

Inserted from
data model xml

FinFunWorkflowNotificationSub InvoiceApprovalNotificationReport
/Shared Folders/Custom/Common Content /Shared Folders/Custom/Financials/Workflow Notifications

39 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Subject Line

✓ How to Customize the Subject Line of


Email/Worklist Notification [Doc ID 2530445.1]

40 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Configurable Notifications | References

• Configurable Approval Notifications

• Invoice Approval Notification Configuration Example

• Expense Report Approval Notification Configuration Example

• Add Logo and Shared content in notifications

• Set Up Content to Appear in Only Email or In-App Workflow


Notifications

• Configurable Workflow Notifications: Implementation


Considerations [Doc ID 2215570.1]

• FAQ - BIP Workflow Notifications [Doc ID 2709827.1]

• Best Practices for Layouts in Workflow Notifications

41 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Agenda

• Configure using Spreadsheet


• Sample Use Cases
• Advanced Mode
• Best Practices
• Migration, Archive & Purge
• Configurable Notifications
• Transaction Console
Transactions Console | Discussion & Demo

• One Stop place for workflow administrators to review and


manage all workflow tasks
• Recover
• Terminate
• Reassign
• Withdraw
• Download
• Resend Email Notification (23A)
• Roles
• Financial Application Administrator – Job Role
• Financial Transaction Approval Reviewing – Duty Role
• Review Approval Transactions - Privilege

• Enabled for
• Payables Invoice Approvals
• Expense Report Approvals
• Journal Approvals
• Invoice Hold Release (21B)

• To limit to Financials tasks only


• Manage Enterprise HCM Information > Enable Transaction
Security
Customer Connect: Transaction Console Replay
Payment Approval Workflow Added in 23A
Account Coding Workflow Added in 23C
43 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted
Notes & References

• 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

44 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Recent New Features
• Custom Values for Start Approver [21D]
• Employee Vacation and Delegation Rules Report [21C]
• Workflow Transactions Reassignments and delegation report [22D]
• Additional attributes for rule configuration for Payables Workflow[22D]
• Import rules from BPM into spreadsheet
• All transaction attributes are added to spreadsheet
• Optimization of workflow rules evaluation
• Rule priority and additional sample rules
• Approval Rules Navigation for Financial Workflows in Workflow Transaction Console
• Workflow rules report (validates against recommended best practices)
• Transaction console security by product or workflow
• Dataset available for Start Approver
• Resend Email Notifications[23A]
• Simplified Workflow Rules configuration Enforcement for Journal and Invoice Approval Workflows[23B]
• List Feature in Workflow Spreadsheet[23C]

✓ 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

45 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Appendix A | PPR Approval | First Approver

• When Payment approval is enabled, all payment process requests go


through the payment approval process. When a payment process
request is submitted, payment approval is automatically triggered
after it reaches the Review Proposed Payments stage. The status of
the payment process request is then set to Payments Approval
Initiated. Payment approvers then receive payment approval e-mail
notifications, as well as payment approval BPM Worklist notifications.

• How payment approval is processed

• Oracle Fusion Payments: Payment Approvals in R13 (Doc ID


2360085.1) • If customer requirement is to get PPR approval from first approver
details entered in PPR selection criteria, then while configuring a rule in
BPM, Select List Builder type as “Resource” and in user field, enter
“[Link] Approver”

• If customer requirement is to start the PPR approval process using the


first approver hierarchy, then select “first approver” in PPR selection
Automatic Resumption of PPR after Approval[23B] criteria. When rule is configured in THEN Part, select “Supervisor or Job
Level ” and in Starting Partcipant field enter the details as
“[Link]([Link]
Approver,-1,"","")

46 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Appendix B | Dispute / Credit Memo Approval

• BPM Task: FinArTrxnsCreditMemosApproval


o Approval for disputes

• BPM Task: FinArTrxnsCreditMemosAutomaticManual


o Upon dispute approval, should the credit memo be automatically created or made available for manual review
o If AutoAction is set to HtOutcmeCreateAutomaticCreditMemo; credit memo is created automatically
o If AutoAction is set to HtOutcmeCreateManualCreditMemo; credit memo information to be reviewed and created manually. Task
FinArTrxnsCreditMemosCreationPostProcessing to be configured for the manual review & creation of credit memo

• Approvals are not available for On-Account Credit Memos (ER 21285074, 27950656)

• Reference

Credit Memo to be Task: FinArTrxnsCreditMemosAutomaticManual


automatically created AutoAction = HtOutcomeCreateAutomaticCreditMemo

Dispute
Approval Task: FinArTrxnsCreditMemosAutomaticManual
AutoAction = HtOutcomeCreateManualCreditMemo
FinArTrxnsCreditMemosApproval Credit Memo to be created
for Review Configure Task
FinArTrxnsCreditMemosCreationPostProcessing
to notify reviewers

47 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted


Thank You

48 Copyright © 2024, Oracle and/or its affiliates | Confidential: Restricted

You might also like