Preface

Purpose

This guide provides step-by-step instructions to onboard a retail customer using Oracle Banking Enterprise Party Management.

Parent topic: Preface

Before You Begin

Kindly refer to the Getting Started User Guide for information on common functionalities like login, navigation, and general settings before proceeding with this guide.

Parent topic: Preface

Module Definitions

Table - Terms & Definitions

Terms	Definitions
Consumer Application	The product that requires integration with another product for retrieving information or posting transactions does not need to know the following details while coding.
Service Consumer	It is an Oracle banking solution that utilizes the Oracle Banking Routing Hub API for integration purposes. Analyze the Oracle Banking Routing Hub and assess the destination product processor.
Import Service Consumer	The user can create a service consumer by importing the JSON file and manually selecting the service providers or select all providers that needs to be imported.
Environment Variables	A set of variables that will be accessible across the particular configuration of the consumer.
Service Providers	Service Providers are systems designed to handle requests sent by the Oracle Banking Routing Hub for service consumers. They include information about destination integration.
Parameter Group	Parameter mapping is used to establish the relationship between parameters of 2 different systems i.e., consumer and provider.
Import Implementation	The user can create an implementation by importing the JSON file.
Consumer Services	It specifies the service ID that is transmitted by the service consumer. It also handles transitions and route definitions, including the details for source integration.
Transformation	It involves gathering and changing data from one source to another and back again. This process occurs within consumer services. It changes the data from the service consumer into a format suitable for the service provider.
Routing	It determines which service provider receives the actual request by considering maintenance and assessment factors.
Chaining	The sequence of transformations for each routing in which the request needs to be processed.
Template Extensibility	It is achieved by specifying the extended templates for request and response kernel transformation templates. And as part of extensibility, Routing Hub merges the output of kernel template and custom template in terms of JSON / XML merging.
SPI	It is used to make Routing Hub more extensible. SPI provides an option to extend interfaces without modifying the core application.
Monitoring dashboard	It provides to System integrators and IT administrators to review the health of the integrations. It displays data using different type of widgets to help users to assess the performance of integrations and identify the areas that requires attention.

Parent topic: Preface

Module Pre-requisite

Specify User Id and Password, and login to the Home screen.

Parent topic: Preface

Audience

This guide is intended for the bankers who are responsible for onboarding retail customers into the 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.

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. All critical patches should be applied in a timely manner to make sure effective security, as strongly recommended by 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
Retail 360 User Guide

Parent topic: Preface

Basic Actions

Most of the screens contain icons to perform all or a few of the basic actions. The actions which are called here are generic, and it varies based on the usage and the applicability. The table below gives a snapshot of them:

Table - Common Icons and its Definitions

Icon	Operation
Submit	Click Submit to default the checklists applicable for the stage based on the application category. On verifying all the checklists and on the selection of the outcome, the task will be submitted.
Post	Click Post to post the comments below the Comments text box.
Cancel	Once you click Cancel, the system will ask for confirmation, and on confirming, the task will be closed without saving the data.
Hold	Click Hold to save the captured details and suspend the task status. The suspended task will be available in the Hold queue. This option is used if there is any pending information to be captured. If mandatory fields have not been captured, the system will display an error until the mandatory fields have been captured.
Next	Click Next to save the captured details and then the system will move to the next screen. If mandatory fields have not been captured, the system will display an error until the mandatory fields have been captured. If mandatory fields have not been captured, the system will display an error until the mandatory fields have been captured.
Back	Click Back to save the captured details and move to the previous screen.
Save and Close	Click Save and Close to save the captured details. If mandatory fields have not been captured, the system will display an error until the mandatory fields are captured.