Preface

Purpose

This guide helps you to familiarize yourself with the Deposit Services module of the Oracle Banking Branch. It gives an overview of the module and takes you through the different types of transactions that can be handled through this module.

Parent topic: Preface

Audience

This guide is intended for the deposit services Tellers and Supervisors to provide quick and efficient service to customers and prospects of your bank.

Parent topic: Preface

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.

Access to Oracle Support

Oracle customer access to and use of Oracle support services will be pursuant to the terms and conditions specified in their Oracle order for the applicable services.

Parent topic: Preface

Critical Patches

Oracle advises customers to get all their security vulnerability information from the Oracle Critical Patch Update Advisory, which is available at Critical Patches, Security Alerts and Bulletins Critical Patches, Security Alerts and Bulletins. All critical patches should be applied in a timely manner to ensure effective security, as strongly recommended by Oracle Software Security Assurance Oracle Software Security Assurance.

Parent topic: Preface

Diversity and Inclusion

Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.

Parent topic: Preface

Conventions

The following text conventions are used in this document:

Convention	Meaning
boldface	Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic	Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
`monospace`	Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Parent topic: Preface

Related Resources

For more information, see these Oracle resources:

Getting Started User Guide
Teller User Guide

Parent topic: Preface

Acronyms and Abbreviations

The list of the acronyms and abbreviations used in this guide are as follows:

Table - List of Acronyms and Abbreviations

Abbreviation	Description
CASA	Current Account Savings Account
GL	General Ledger
TD	Term Deposits
RD	Retail Deposits

Parent topic: Preface

Screenshot Disclaimer

Personal information used in the interface or documents is dummy and does not exist in the real world. It is only for reference purposes.

Parent topic: Preface

Basic Actions

Most of the screens contain buttons to perform all or few of the basic actions.

Table - Basic Actions and Definitions

Icon	Applicable Stages	Description
Approve	Approval	The system displays a section where approval remarks if any can be input. Click OK to submit. The transaction is sent to the Host system through OBRH. The Host system validates the transaction again and the transaction is created if all the validations are successful. If the transaction fails, the transaction is moved to Handoff retry stage, and user can view the error message. In this stage, the authorizer can retry or reject the transaction. On reject, the transaction is sent back to the maker to modify or delete it. Note: The maker checker validation will be provided if the same maker tries to approve the transaction.
Audit	Initiation, Approval, and Hand off Retry	Audit details provide the logs of users who have acted on the transaction, the transaction date, and the time for all stages that the transaction has passed through.
Back	Initiation, Approval, and Hand off Retry	In case the user missed to specify or need to modify the details in the previous segment, click to navigate to the previous segment.
Cancel	Initiation, Approval, and Hand off Retry	Cancel operation cancels the transaction input midway without saving any data. The user is alerted that the input data would be lost before confirming the cancellation.
Change Log	Approval and Handoff Retry	When the authorizer clicks on the Change Log button, the system displays the changes made to the transaction in a pop-up window. By default, the change log is set to display only modified values. The Change Log button has two options, they are, All and Updated. The All button displays both modified and non-modified fields and the Updated button displays only the modified fields. The old and new values are displayed so that the authorizer can compare or verify the values and decide on further action. Also, the new values appear is red for easy recognition.
Delete	Initiation	Delete operation deletes the transaction without saving any data. The user is alerted that the input data would be lost before confirming the deletion.
Host Error	Hand Off Retry	Hand off Retry comes into use whenever a transaction input from the mid-office system fails authorization due to Host System rejection. The authorizer of the transaction can view the reason for Host rejection and take appropriate action.
Next	Initiation, Approval, and Hand off Retry	On completion of input of all parameters for a particular stage, the user can click to navigate to the next segment.
Overrides	Initiation, Approval and Hand-off Retry	If override messages had appeared during initiation stage and they were accepted by the maker during submission, the Overrides button appears in the Initiation screen if the transaction is subsequently rejected by the authorizer. On the Override Details section, click Decline to go back to the transaction screen to modify or cancel it, or click Accept to complete the initiation stage and move the transaction to the approval stage.The Overrides button is displayed in the Approval and Hand-off retry stage if there were any override messages generated during initiation and accepted by the maker. When the Overrides button is clicked, the system displays the overrides accepted by the maker. After verifying the transaction and override details, the authorizer can either approve or reject the transaction. Existing Approve Transaction section is modified to display the overrides if any overrides are raised during the initiation submits.
Reject	Approval and Hand off Retry	When an authorizer chooses to reject a transaction, the Reject icon is used. The system displays a pop-up screen to capture the Rejection remarks if any. Click OK for the transaction to be routed back to the initiation stage and assign back to the maker. In my Pending Tasks, the maker can view and subsequentlycan modify or delete the transaction details.
Remarks	Initiation, Approval, and Hand-off Retry	Remarks can be used either by the maker or the authorizer of the transaction to optionally capture useful information about the transaction.
Submit	Initiation	After submitting the initiation stage, the system validates the transaction with the host and displays the errors or overrides if any. In case of an error, you can modify and resubmit or cancel the transaction. In case of an override, you can modify and resubmit or proceed with the transaction by accepting the overrides.
Save and Close	Initiation	In case a transaction has to be closed midway due to a lack of sufficient information, the maker of the transaction can choose this option. When you click Save and Close, the input details are saved and the transaction screen is closed. Saved transaction details will be available in My task. Users can select the transaction from My Task and proceed with the transaction or delete it.
Auto Authorization	Initiation	Auto authorization can be configured for the branch servicing screens by creating a Rule based on life cycle code. The steps to create the Auto authorization as follows: Create the fact value as LIFECYCLECODE. Create Rule to enable Auto authorization for any servicing screen and add the expression in Rule for that screen's lifecycle code. While creating a Rule the product processor should be given as DEPOSIT and fact should be selected as LIFECYCLECODE. For Example: `IF ( LIFECYCLECODE == TDPOMN )` output `Section1 LEVEL:0` Create or modify a Rule Group with Name ApprovalRuleGroup and map the Rule(s) created in the step (2). Note: You can define one single Rule for all the screens and add the expression for the life cycle code or you can define individual Rule for each screen and map to the Rule group. Note: For more information, refer to the Oracle Banking Common Core User Guide to create Fact, Rule and Rule Group.
Multi-Level Authorization	Initiation	Multi-level authorization can be configured for the branch servicing screens by creating a Rule based on life cycle code. The steps to create the Multi-level authorization as follows: Create the fact value as LIFECYCLECODE. Create Rule to enable Multi-level authorization for any servicing screen and add the expression in the Rule for that screen's lifecycle code. While creating a Rule the product processor should be given as DEPOSIT and fact should be selected as LIFECYCLECODE. For Example: `IF ( LIFECYCLECODE == TDPYIN )` output `Section1 LEVEL:1~DSR_FA_TDPAYIN_AUTH, LEVEL:2~DSR_FA_TDPAYIN_AUTH` Note: If customer wants to use separate Functional Activity Code for each Level then Rule output need to be define like `LVELE:1~<FUNCTIONAL_ACTIVITY_CODE1>, LVELE:2~<FUNCTIONAL_ACTIVITY_CODE2>` . Create or modify a Rule Group with name ApprovalRuleGroup and map the rule(s) created in the step (2). Note: You can define one single rule for all the screens and add the expression for the life cycle code or you can define individual rule for each screen and map to the rule group. Note: The maker checker validation will be provided if the same maker tries to authorize the single or multi-level approval tranaction.

The following shortcut keys can be used only for the screens, which has the buttons specified in the function:

Table - Shortcut Keys

Shortcut Key	Function
Tab	Used to shift focus from one input field to other. Note: The last field of the last accordion will shift focus to Submit/Cancel.
Alt + S	Used to select Submit.
Alt + C	Used to select Cancel.

Parent topic: Preface

Symbols and Icons

The following are the symbols and icons you are likely to find in this guide:

Table - Symbols and Icons

Symbols and Icons	Function
	Minimize
	Maximize
	Close
	Perform search
	Open a list
	Edit a row
	Delete a row
	Open calendar
	Navigate to the first page
	Navigate to the last page
	Navigate to the previous page
	Navigate to the next page
	Add a row
	Refresh details
OK	Confirm the details specified
Back	Navigate to the previous tab
Next	Navigate to the next tab
Save & Close	Save the details specified and exist from the screen. The task appears in my pending task, from where you can take the task ahead on your next login.
Cancel	Cancel the action performed and exist the screen
Submit	Submit the transaction for approval
Audit	View the audit details of a particular screen
Remarks	Add or view remarks related to a screen.

Parent topic: Preface

Shortcut Keys

The following shortcut keys can be used only for the screens, which has the buttons specified in the function:

Table - Shortcut Keys

Shortcut Key	Function
Tab	Used to shift focus from one input field to other. Note: The last field of the last accordion will shift focus to Submit/Cancel.
Alt + S	Used to select Submit.
Alt + C	Used to select Cancel.

Parent topic: Preface