Oracle FLEXCUBE Direct
Banking
Transaction Release Workflow
Release 12.0.3.0.0
Part No. E52543-01
April 2014
Transaction Release Workflow
April 2014
Oracle Financial Services Software Limited
Oracle Park
Off Western Express Highway
Goregaon (East)
Mumbai, Maharashtra 400 063
India
Worldwide Inquiries:
Phone: +91 22 6718 3000
Fax:+91 22 6718 3001
www.oracle.com/financialservices/
Copyright © 2008, 2014, Oracle and/or its affiliates. All rights reserved.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any
programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial
computer software” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any
operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be
subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk
of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to
take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and
its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous
applications.
This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find
any errors, please report them to us in writing.
This software or hardware and documentation may provide access to or information on content, products and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services.
Oracle FLEXCUBE Direct Banking Transaction Release Workflow
ii
Contents
1.
Preface .................................................................................................................................................. 1
1.1.
Intended Audience ........................................................................................................................ 1
1.2.
Documentation Accessibility ......................................................................................................... 1
1.3.
Access to OFSS Support ................................................................................................................ 1
1.4.
Structure ....................................................................................................................................... 1
1.5.
Related Information Sources ........................................................................................................ 1
2.
Introduction .......................................................................................................................................... 2
3.
Technical Architecture – Release workflow .......................................................................................... 3
4.
3.1.
Transaction Release Authorization Module.................................................................................. 3
3.2.
Configurations ............................................................................................................................... 3
Service Requests Management............................................................................................................. 4
Oracle FLEXCUBE Direct Banking Transaction Release Workflow
iii
1. Preface
1.1.
Intended Audience
This Licensing Guide is intended for the following audience:




Application Architects
End to End Designers
Business Service Detailed Designers and Developers
Implementation Partners
1.2.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website
at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
1.3.
Access to OFSS Support
https://support.us.oracle.com
1.4.
Structure
This document, termed “Oracle FLEXCUBE Direct Banking Transaction Release Workflow”, is a single
reference for the understanding the transaction release workflow introduced as part of FCDB
Authorization Framework.
This document is intended to provide a technical overview of the transaction release functionality.
1.5.
Related Information Sources
For more information on Oracle FLEXCUBE Direct Banking Alerts 12.0.3.0.0, refer to the following
documents:

Oracle FLEXCUBE Direct Banking System Handbook Volume IV
Oracle FLEXCUBE Direct Banking Transaction Release Workflow
1
2. Introduction
Earlier system was directly submitting the transaction to host after it is authorized in FLEXCUBE Direct
Banking. However there can be a requirement for certain transactions to be processed manually in
FLEXCUBE Direct Banking before sending them to host.
There can also be a requirement to pass the transaction through a series of statuses after authorization.
In order to achieve this, generic workflow has been developed in FCDB. The detailed functioning of the
workflow along with necessary configurations is explained in subsequent sections.
Below are some features of this workflow:










Aim of this workflow is to provide a generic framework in which the transaction will move from
one status to another based on certain action by the FCDB user. This workflow will come into
picture only after the transaction is fully authorized in FCDB.
FCDB will not attach any special meaning to any of the ‘Statuses’ configured in the workflow, but
will treat them only as a state in which the transaction resides during its lifecycle.
Transactions configured for ‘Release’ will go in ‘Pending for Processing’ state after they are fully
authorized in FCDB.
A separate transaction will be available, from where the ‘Releaser’ can manually release the
transaction.
The ‘Releaser’ must have the corresponding transaction (to be released) mapped to his/her role
along with authorization access.
The system supports cross user type release functionality. Transactions initiated and authorized
by a corporate user can be released by a bank administrator user. This is configurable for each
type of transaction.
Based on the status flow configured for the transaction, it will accordingly move to the next
status. The configurations are given in below sections.
Service call can be configured for any of the status
The status transaction flow can be extended to any level and status call can be configured at any
status
A definite end state has been introduced for the service requests in the transaction release work
flow.
Oracle FLEXCUBE Direct Banking Transaction Release Workflow
2
3. Technical Architecture – Release workflow
The workflow is implemented using below components:


A new authorization module (TransactionReleaseInitAuthModule) that handles the flow of
transaction through various statuses based on the configuration.
A new transaction provided to both Admin and Business user for processing the transaction.
The authorization module and required configurations are explained in subsequent section.
3.1.



Transaction Release Authorization Module
A new module “TransactionReleaseInitAuthModule” has been introduced as for processing the
release requirement.
This module has been configured as a default module. So all transactions will flow through this
module.
This module checks if the current transaction requires release. If so, then it moves the
transaction to “Pending for Processing” status
3.2.
Configurations
Any transaction must satisfy below conditions for it to be available for Release Workflow







Authorization must be enabled (MSTCHANNELATS table – authrequired=’Y’) and appropriate
authorization engine must be configured for the transaction for given user type
MSTTXN table- adtnl_params - RELEASEREQUIRED=A/B/Y
o A – Transaction will be available for Admin user for release
o B – Transaction will be available for Business user for release
o Y – Transaction will be available for both Admin and Business user for release
The transaction should be mapped to the ‘Releaser’ in his/her role along with authorization
access.
If a new action is to be introduced, it can be configured in table MSTACTIONCONFIG
If a new status is to be introduced, it can be configured in table MSTSTATUSCONFIG
Service call can be configured in the table MSTSTATUSCONFIG (ISSERVICECALLREQ=’Y’)
Necessary button map has to be configured in appldata so that system displays the required
action buttons.
Oracle FLEXCUBE Direct Banking Transaction Release Workflow
3
4. Service Requests Management
All the ‘Service Requests’ go through the release module post authorization. Release is configurable for
individual service requests.




A new authorization module (ServiceRequestModule) has been introduced for service
requests. This module forces a finite end state to the service requests once their workflow is
complete.
“ServiceRequestModule” is a default module. The finite end state introduced for the service
requests is “Closed”.
A new type statistic ‘S’ has been introduced for the service requests.
A new property ‘<id entity>.<type user>. REQUEST_STATUS_VALID_DAYS’ has also been
introduced which specifies the number of days till which the closed and rejected service
requests will be available to the user on the dashboard widget.
Below is the list of Service Requests available as of now:
SERVICE REQUESTS
RELEASE
CONFIGURED
RELEASER
Account Closure
Yes
A
Apply for Credit Card
Yes
A
Activate Debit Card
Yes
A
Addition / Change of Mobile /
Email
No
Not Applicable
Apply for ATM / Debit Card
Yes
A
Autopay Register
Yes
A
Account Statement Request
No
Not Applicable
Change Billing Cycle
Yes
A
Change Address
No
Not Applicable
Activate Credit Card
Yes
A
Deactivation of Credit Card
Yes
A
Oracle FLEXCUBE Direct Banking Transaction Release Workflow
4
Change Credit Limit
Yes
A
Credit Card Replacement
Yes
A
N
Credit Card Hot Listing
Yes
A
N Withdrawal PIN Change
Cash
Yes
A
Deregister Auto Payment
Yes
A
Deregister Credit Card
Yes
A
Stop Payment of Drafts
Yes
A
Debit Card Hot Listing
Yes
A
Inquire Interest Rates
No
Not Applicable
Loan Account Statement Request
No
Not Applicable
SERVICE REQUESTS
RELEASE
CONFIGURED
RELEASER
Link ATM / Debit Card Request
Yes
A
New Account Opening Request
No
Not Applicable
Old New Account Summary
No
Not Applicable
Credit Card ATM PIN Change
Yes
A
Personal Loan Application
Yes
A
Reset ATM Debit Card PIN
Yes
A
Register Credit Card
Yes
A
Reissue Transaction Password
Yes
A
Supplementary Card Request
Yes
A
Customer Statement Request
No
Not Applicable
Stop Payment on Wired Transfer
Yes
A
NOTE :- There are three possible values for a ‘Releaser’ –A,B,Y. A stands for Bank Admin User.
B stands for Business User and Y stands for both (Bank Admin and Business User.)
Oracle FLEXCUBE Direct Banking Transaction Release Workflow
5