Preface

Purpose

This guide helps you get started with the Oracle Banking Branch application. It also explains the basic design of the Oracle Banking Branch and the common operations that you can follow while using it.

Parent topic: Preface

Module Prerequisite

Specify User ID and Password, and login to Home screen.

Parent topic: Preface

Audience

This guide is intended for the Branch Tellers, Vault Operators, Branch Supervisors, and staff in charge of setting up new products in the bank.

Parent topic: Preface

Basic Actions

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

Table - Basic Actions

Action	Applicable Stages	Description
Next	Initiation, Approval and Hand off Retry	On completion of input of all parameters for a particular stage, user can click Next to navigate to the next tab.
Back	Initiation, Approval and Hand off Retry	In case user missed to specify or need to modify the details in the previous tab, click to navigate to the previous tab.
Save & Close	Initiation	On click of Save & Close, the input details are saved, and the transaction screen is closed. In case a transaction must be closed midway due to a lack of sufficient information, the maker of the transaction can choose this option. The saved transaction details will be available in My Task. User can select the transaction from My Task and proceed with the transaction or Delete it.
Cancel	Initiation, Approval and Hand off Retry	On click of Cancel, the transaction input is cancelled midway without saving any data. User are alerted that the input data would be lost before confirming the cancellation.
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, User can modify and resubmit or cancel the transaction. In case of an override, user can modify and resubmit or proceed with the transaction by accepting the overrides.
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 system displays an error message, and the transaction is moved to Hand-off retry stage. In this stage, the authorize can retry or reject the transaction. On reject, the transaction is sent back to the maker to modify or delete it.
Reject	Approval and Hand off Retry	On click of Reject, a transaction is rejected is by the authorize. 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. Subsequently, the maker can modify or delete the transaction details.
Minimize	Initiation, Approval and Hand-off Retry	On click of Minimize, the transaction input screen is minimized. When the screen is minimized, it appears as to a separate tab within the same web page.
Maximize	Initiation, Approval and Hand off Retry	On click of Maximize, the transaction input screen is maximized. User can proceed with the required action on the screen.
Reset	Hand off Retry	The Reset button clears all the details previously modified by user and populates the fields with default values.
Remarks	Initiation, Approval and Hand-off Retry	Remarks can be used either by the maker or the authorize of the transaction to optionally capture useful information about the transaction.
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 authorize of the transaction can view the reason for Host rejection and take appropriate action.
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 authorize. 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 authorize can either approve or reject the transaction. The existing Approve Transaction section is modified to display the overrides, if any overrides are raised during the initiation submits.
Document	Initiation, Approval and Hand-off Retry	The maker of the transaction can click Document to upload documents that are relevant to the transaction. Once uploaded, the documents are available for viewing during authorization or by the maker.
Change Log	Approval	When the authorize clicks 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 authorize can compare or verify the values and decide on further action. Also, the new values appear is red for easy recognition.
Delete	Initiation	The Delete button is applicable only for the Maker screen and that too when the screen is opened from the Task list. In other words, only saved tasks opened in editable mode have delete functionality.
Advices	Initiation	The Advices button helps the Maker to generate a pre-advice or acknowledgement to get a confirmation from his customer.
Auto Authorization	Initiation	The 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 LOAN and fact should be selected as LIFECYCLECODE. For example: IF ( LIFECYCLECODE == LNRDCH ) output Section1 LEVEL:0 Create or modify a Rule Group with Name ApprovalRuleGroup and map the Rule(s) created in the step (2). Note: User can define one single Rule for all the screens and add the expression for the life cycle code or user can define individual Rule for each screen and map to the Rule group. 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. User can define one single Rule for all the screens and add the expression for the life cycle code or user 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	User can set up multi-level authorization for 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 the lifecycle code of that screen. While creating a Rule the product processor should be given as LOAN and fact should be selected as LIFECYCLECODE. For Example: IF ( LIFECYCLECODE == LNRDCH ) output Section1 LEVEL:1~LSR_FA_LNRDCH_AUTH, LEVEL:2~LSR_FA_LNRDCH_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). User can define one single rule for all the screens and add the expression for the life cycle code or user can define individual rule for each screen and map to the rule group. The maker checker validation will be provided if the same maker tries to authorize single or multi-level approval transaction.

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 BulletinsCritical 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 AssuranceOracle Software Security Assurance.

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

Common Icons

The following are the symbols/icons, which are used frequently in the Oracle Banking Branch application.

Table - Symbols

Symbol	Description
	Add a row in the grid.
	Remove a row in the grid.
	Edit a row in the grid
	Navigate to the next page.
	Navigate to the previous page.
	Navigate to the first page.
	Navigate to the last page.
	Minimize screen. The minimized screen appears at the bottom left corner of the screen. You can click again to maximize the screen.
	Maximize screen.
	Closes the screen. If you are in the middle of creating/modifying the records in a selected screen, an error/warning message appears prompting you to save the changes.

Table - Common Icons and their descriptions

Action	Description
Submit	Complete the transaction or request.
Cancel	Cancel the transaction or request.
New	Creates a new record for the selected screen.
Query	View all the required information/configured records for the selected screen.
Unlock	Unlock the configured record for the selected screen.
Search	Search the configured record and select the required record for the selected screen.
Delete	Remove the configured record for the selected screen.
Reopen	Reopens a closed record for the selected screen.
Close	Closes the screen.
Authorize	Authorize the configured record for the selected screen.
Collapse	Minimizes the opened screen to the bottom left corner of the screen.
Audit	Check the history of the configured records for the selected screen.
Save	Save the configured record for the selected screen.

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

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

Related Resources

For more information on any related features, refer to the following documents:

Oracle Banking Microservices Platform Foundation User Guide
Oracle Banking Common Core User Guide
Routing Hub Configuration User Guide
Oracle Banking Security Management System User Guide
Teller User Guide
Retail 360 User Guide
Retail Onboarding User Guide
Corporate 360 User Guide
Corporate Onboarding User Guide
Small and Medium Business 360 User Guide
Small and Medium Business Onboarding User Guide
Small and Medium Enterprise 360 User Guide
Small and Medium Enterprise Onboarding User Guide
Servicing Configurations User Guide
Current and Savings Account User Guide
Loan Service User Guide
Deposit Services User Guide
Observability User Guide
Troubleshooting Guide

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

Icons

The lists of symbols, buttons and shortcut key that are used in the application to perform various tasks are covered in this topic.

Icons

Table - Icons

Icon	Function
	Click to minimize a screen.
	Click to maximize a screen.
	Click to close a screen.
	Click to perform a search.
	Click to Open a list.
	Click to add new record.
	Click to navigate to first page.
	Click to navigate to last page.
	Grid View
	List View
	Refresh
	Calendar
	Toggle On
	Toggle Off
	Click to unlock, delete, authorize or view the created record.
	Copy a record
	Click to view the created record.