Release 13 Using The Transaction Console

Using the
Transaction
Console
Release 13 HCM Cloud Common Features
WHITE PAPER / AUGUST 31, 2018

DISCLAIMER
Table of Contents
Transaction console..................................................................................... 3
Role Information .......................................................................................... 3
Overview ...................................................................................................... 3
Transaction Summary.................................................................................. 4
Analytics .................................................................................................... 11
Approval Rules .......................................................................................... 16
Resources ................................................................................................. 25
FAQs ......................................................................................................... 25
How can I secure the Transaction Summary access for HR Specialists, Line Managers, and
Shared Service Approvers? ........................................................................................................25
How do I recover a saved transaction? ......................................................................................25
Where to get more sample BPM approval business use cases for self-learning? ......................25
2 W HITE PAPER / Oracle HCM Cloud Common Features Release 13 Using the Transaction Console
TRANSACTION CONSOLE
Based upon a new SOA fault handling mechanism, the Release 13

Transaction Console is a centralized framework that supports all HCM BPM
transactions. The enhanced fault policy detects:
 Auto recoverable faults due to infrastructure incidents;
 Manual recoverable faults caused by data or routing rule definition
errors.
ROLE INFORMATION
 Use the delivered job role ‘Human Capital Management Application Administrator’
(ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB)
or
 Add the Human Capital Management Approval Rules Management Duty role
(PER_APPROVAL_RULES_MANAGEMENT_DUTY) to grant your customer-defined roles with these
functional privileges:
 Perform HCM Approval Transaction Actions
(PER_PERFORM_APPROVAL_TRANSACTION_ACTIONS_PRIV)
 Review HCM Approval Transactions
(PER_REVIEW_APPROVAL_TRANSACTIONS_PRIV)
 Manage Approval Rules
(PER_MANAGE_APPROVAL_RULES_PRIV)
 Add HCM Transaction Administration Transaction Analysis Duty
(FBI_HCM_TRANSACTION_ADMINISTRATION_TRANSACTION_ANALYSIS_DUTY),
Archived HCM Approval Task Transaction Analysis Duty
(FBI_ARCHIVED_HCM_APPROVAL_TASK_TRANSACTION_ANALYSIS_DUTY) for OTBI analyses
OVERVIEW
(Navigator) Tools > Transaction Console
Transaction Console comprises three work areas:

1. Transaction Summary
2. Analytics
3. Approval Rules
Instead of using the BPM Worklist, administrators can use the Transaction Console to easily configure,
monitor, and troubleshoot HCM approval processes. For example, you can:
 Check the latest status of approval transactions and take necessary actions, such as
Withdraw, Recover, Reassign, Send Back to Initiator, Terminate etc.
 Search on existing transactions based on user-defined criteria, and repeat queries by
creating saved searches.
 Access the simple and straightforward process details page.
 Use the relevant analytics dashboards for tracking and monitoring processes.
 Manage approval rules including Alert Initiator on Error.
TRANSACTION SUMMARY
1. Refresh Transaction Administrator Console Transaction Status. This process updates the
status of a transaction in the Console and can be run on demand by clicking the Last Refresh
icon. It can be scheduled using the Scheduled Processes task. We recommend that this process
is scheduled to run on an hourly basis if the default Alert Initiator on Error is selected, see the
Approval Rules tab.
Console Transaction Status
UI/OTBI 17B UI/OTBI 18B

INTERNAL STATUS STATUS CATEGORY DETAILED STATUS UPDATE MECHANISM
Saved Draft Draft User Action
Initiated/Submitted  Pending Submitted BPEL
In Progress  Pending In Progress BPEL
Completed  Completed Completed BPEL
Stuck  Pending Stuck Scheduled Process
Auto Recovery  Pending Auto Recovery Scheduled Process
Errored  Failed Failed Scheduled Process
Here are some further explanations of transaction statuses:
1.1. SUBMITTED: Submitted is the state right after UI submission of the transaction. After the
Transaction is submitted, the Refresh Transaction Administrator Console Transaction Status
(ESS job) will make sure that the Status of the transaction changes to any one of the
following statuses: IN PROGRESS, ERRORED, STUCK, AUTO RECOVERY.
1.2. IN PROGRESS means the transaction is pending approval.
1.3. STUCK: When a user has created a transaction and due to a SOA server infrastructure
issue, it never reached the BPEL. Hence, there is no record of this transaction in the
FND_CONSOLE_TRANSACTION_INFO table.
1.4. AUTO RECOVERY: A transaction is registered in FND_CONSOLE_TRANSACTION_INFO

table, but either has not completed or has failed due to SOA infrastructure reasons or
service invocation issue and for which SOA is internally retrying on error.
1.5. ERRORED: A transaction has one or more open issues registered in the
FND_CONSOLE_ISSUE table.
2. Search. Administrators can quickly locate transactions by using keyword search against the
Name or the Process Name columns. To reset, nullify the field and click Search again.
3. Default Filter. The page parameter defaults to Failed status. Either select Clear or Remove to
perform a blind query covering all statuses. Or click Completed, Pending from the choice list.
Select Download for a spreadsheet copy.
4. Actions. Highlight a failed transaction for more Actions. Administrators can set Priority or
choose Alert Initiator on Error during the triage process, or choose Add Comment to document
a fix or a service request/bug numbers (see 5.3 Search Comments).
4.1. To diagnose the failed process, click the Name link.
4.2. Check or action a pending process:
4.3. Query the R12 upgraded processes created by a composite instance.
4.3.1. Remove the default filter and search for Preupgrade status. Only In Progress
transactions have a Withdraw option.
5. Filters. Click Hide Filters to close the pane. Choose Personalize Filters for configurable options.
5.1. For site level settings, choose Configure for Others and Activate Sandbox:
5.2. For the current user login session only, choose Configure for Self:
5.3. Enable Search Comments for the ability to search with the respective service request or
bug or helpdesk ticket number:
5.4. Create saved searches for frequent queries:
ANALYTICS
Log in to BI Answers (https://host:port/analytics/saw.dll?bieehome) – Catalog – Shared Folders –
Human Capital Management – Transaction Administration – Embedded Content – Transaction
Manager.
1. To preview, click Open the Transaction Summary
2. Parameters are defaulted.
3. To change or duplicate the dashboard for different defaults and permissions, choose Copy.
4. Navigate to /Shared/Custom folder, for example, the Human Capital Management subfolder,
and click Paste. Choose Edit dashboard to correct component settings.
5. Expand the Shared Folders in the Catalog pane, locate the Transaction Summary Prompt
and drag across, and then delete the copied prompt. Repeat this step for Transaction
Summary. Click Save. Click Run to verify that the dashboard continues to work.
6. To modify, return to the custom subfolder, locate the Transaction Summary and click Edit.
7. Select the Criteria tab for the subject area to proceed with changes.
8. Return to Transaction Console, select the Analytics tab.

9. Open the Search panel, enter Transaction Summary and Sort By Name then click Search
to return results.
10. Select the Dashboard icon for the Report Information popup dialog. Click Done to close.
11. Click Add Favorites. This is set at User level.
12. Repeat the search for another custom dashboard Completed Transactions View re: “Approval
Notification Archive Dashboard” from Report Sharing Center.
Or you can navigate directly to Reports and Analytics, select More for BI Answers.
to manage Favorites:
13. Select List View to see all favorites. Click the Name link to open dashboard.
14. Select E-mail option if and when necessary.
APPROVAL RULES
1. Bypass Approvals. If this option is selected, the transaction is automatically committed to the
database and no FYI notification will be triggered. In such cases, only errored transactions are
registered in the Transaction Summary.
2. Alert Initiator on Error. This option automatically sends an error notification to the initiator that
includes a link to resubmit the transaction if applicable.
2.1. The Runtime Alert API extracts the message content from the seeded data model onto the
TAC Error Alert template via Tools – Alerts Composer.
2.1.1. Click Edit for the Templates tab, select Manage Recipients and Message.
2.1.2. Variables available in different contexts are seeded.
2.1.3. Click Add Recipient and Mail for looping others in.
2.1.4. Configure Run Options, click Save and Close.
2.1.5. Click the Name link for the Translation Editor.
2.2. Check the results:
2.2.1. Assign the data issue back to the initiator:
2.2.2. Highlight the fault process and choose Alert Initiator on Error:
2.2.3. Login as line manager Robert Jackman.
Note: Actions in the FYI alert notification have no practical relevance – DO NOT USE.
Only Administrator can take actions via the Transaction Summary (see 4. Actions).
2.2.4. Check the external user’s inbox:
3. Configure Rules. The HCM Simplified UI does not allow you to modify rules that were created
using Advanced Mode in the BPM Worklist. If you originally created your rule conditions using
Advanced Mode in the BPM Worklist, you must continue to use the BPM Worklist to make
changes.
3.1. This Approve Goal use case demonstrates no approval actions but an FYI notification is sent
to a manager.
3.2. Create the approve goals routing rules, select Save and Submit.
3.3. Log in to the BPM Worklist (https://host:port/integration/worklistapp), select Administration
– Task Configuration – and search for the Approve Goal composite.
3.3.1. Click Edit and the Assignees tab, and then the GoalApprovalRule link.
3.4. Verify the FYI to be followed by Required Response Type, check Starting Participant, click
Validate then Save and Commit Task.
Note: in the Starting Participant field,

3.4.1. For multiple assignments with different managers, use this:
HierarchyBuilder.getManager("Supervisory",Task.payload.transactionApprovalRequest
.attribute16,Long.parseLong(Task.payload.transactionApprovalRequest.attribute15),nul
l,null)
3.4.2. If you want to only route to the primary assignment’s manager, use this:
HierarchyBuilder.getManager("supervisory",Task.payload.transactionApprovalRequest.
attribute16,-1,null,"LINE_MANAGER")
3.5. Select Edit then the Notifications tab and clear the Make notification actionable check
box, Save and Commit.
3.6. Ensure both profile options and feature choices are enabled for approvals.
3.7. Check the results:
RESOURCES
Oracle HCM Cloud Configurable Notifications and Subject Lines (Doc ID 2331021.1)
LCM Archive & Purge Processes (Doc ID 2323993.1)
Frequently Asked Questions About Approvals (Doc ID 1987850.1)
Configuring Approval Rules using Advanced Mode: Worked Example (Doc ID 2267369.1)
FAQS
How can I secure the Transaction Summary access for HR Specialists, Line Managers, and
Shared Service Approvers?
This enhancement is scheduled for the 19A release.
How do I recover a saved transaction from a terminated worker?

Only active initiator can withdraw or resume the transaction via the Worklist.
Administrator can terminate the draft transaction via the Transaction Summary.
Where to get more sample BPM approval business use cases for self-learning?
See postings on Cloud Customer Connect:
Role-based approval rules
CEO self auto approval
Approval rules for multinational shared services
ORACLE CORPORATION
Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA
Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com
CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.
blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed
orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0818
Oracle HCM Cloud Common Features Release 13 Transaction Console
August 2018
Author: Surlina Yin

Release 13 Using The Transaction Console

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Release 13 Using The Transaction Console

Diunggah oleh

Hak Cipta:

Format Tersedia

Using the

WHITE PAPER / AUGUST 31, 2018

Role Information .......................................................................................... 3

Approval Rules .......................................................................................... 16

Shared Service Approvers? ........................................................................................................25

How do I recover a saved transaction? ......................................................................................25

Based upon a new SOA fault handling mechanism, the Release 13

Transaction Console comprises three work areas:

UI/OTBI 17B UI/OTBI 18B

Saved Draft Draft User Action

Initiated/Submitted  Pending Submitted BPEL

In Progress  Pending In Progress BPEL

Completed  Completed Completed BPEL

Stuck  Pending Stuck Scheduled Process

Auto Recovery  Pending Auto Recovery Scheduled Process

Errored  Failed Failed Scheduled Process

Here are some further explanations of transaction statuses:

1.2. IN PROGRESS means the transaction is pending approval.

1.4. AUTO RECOVERY: A transaction is registered in FND_CONSOLE_TRANSACTION_INFO

4.2. Check or action a pending process:

1. To preview, click Open the Transaction Summary

2. Parameters are defaulted.

8. Return to Transaction Console, select the Analytics tab.

2.1.4. Configure Run Options, click Save and Close.

2.1.5. Click the Name link for the Translation Editor.

2.2.4. Check the external user’s inbox:

Note: in the Starting Participant field,

How do I recover a saved transaction from a terminated worker?

blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle

Anda mungkin juga menyukai