Preface

• Purpose
  
• Audience
  
• Documentation Accessibility
  
• Diversity and Inclusion
  
• Conventions
  
• Related Resource
  
• Screenshot Disclaimer
  
• Acronyms and Abbreviations
  
• Symbol and Icons
  
• Basic Actions
  

Purpose

Welcome to the Retail Loans Origination user guide for Oracle Banking Origination. This document provides an overview of the Retail Loan Origination process and takes you through the various steps involved in handling all the necessary activities in the life cycle of a Retail Loan Origination.

Audience

This user manual is intended for the Relationship Managers (RMs), other loan executive staff- member in-charge of maintenance for the loan accounts in the bank, and sales officer in-charge of sourcing the Retail Loan Origination products from prospect and customer of the bank. This user manual is also intended for the other bank personas such as bank operations manager, account opening officers or branch managers who may handle the specific stages of the lifecycle of the Retail Loans Origination process based on the bank’s internal operation and policies.

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 customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

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.

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.

Related Resource

The related documents are as follows:

• Operations User Guide
• Configuration User Guide
• Alerts and Dashboard User Guide

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.

Acronyms and Abbreviations

The list of the acronyms and abbreviations that you are likely to find in the manual are as follows:

Table -1 Acronyms table

Abbreviation	Description
DS	Data Segment
System	Oracle Banking Origination Module
OBA	Oracle Banking Accounts
OBO	Oracle Banking Origination

Symbol and Icons

Table -2 Symbols and Icons - Common

Symbol/Icon	Function
	Minimize
	Maximize
	Close
	Perform Search
	Open a list
	Add a new record
	Navigate to the previous record
	Navigate to the next record
	Refresh
	Calendar
	Alerts

Basic Actions

Table -3 Basic Actions

Actions	Functions
Request Clarification	Used to raise a new clarification request. The system allows placing a request for clarification that is needed from the Customer to proceed ahead with the application. The clarification can be for any additional details, confirming specific information, the requirement for any additional document, and so on, from the customer. For more information on Request Clarification, refer to the section Request Clarification.
Back	Used to navigate to the previous data segment within a stage.
Next	Used to navigate to the next data segment, after successfully capturing the data. The system validates all mandatory data segments and data fields. If mandatory details are not provided, the system displays an error message for the user to take action. Users will not be able to proceed to the next data segment, without capturing the mandatory data.
Save & Close	Used to save the data captured, provided all the mandatory fields are captured and will be available in the My Task list for the user to continue later.
Cancel	Used to close the application without saving. This tasks appears in Free Task, once the transaction is canceled.