Retail User

Introduction

This option allows you to  view the bank retail user activities. The administrator creates the user and provides various privileges based on the customer profile.

The administrator sets the initial password for the user. Such a password should be changed later and is subsequently used for further logins. The administrator can create, modify or delete users.

Note:

• Administrator creates the e-Banking retail user ID in the application, the customer ID and customer details is fetched online (through FI), that is, from CIF database. Customer details are filled in the user creation page after fetching CIF ID, but the administrator specifies only the e-Banking specific fields.

• For important notes, click here.

  • The password print program prints the communication address details in the principal language of the application of the user.

  • The language codes available to the user are derived from the entries made in the LANG table.

  • Country Codes (Common code of Code type = ‘CNT’), State codes, and Menu profiles must be created before creating any user.

  • According to the internationalization standards, two date and time formats are supported by Retail e-Banking: Short date format and Long date format. These are created in COCD Table as seed data: Code type = ‘DFT’ and Common codes as 2 (Short date) & 3 (Long Date). Based on the locale of the user (i.e. language code), the actual display format is decided. Example if the language code is 001 (English), the short format implies mm/dd/yy and the long date format will be mmm dd yyyy.

  • The amount formats supported by Retail e-Banking are determined in accordance to the locale of the user. The locale of the user is decided by the user’s language code and country code.

  • Salutation is a common code of code type SAL. The common code is expected to be numeric and the code description is displayed in the list of salutations available to the administrator while creating a user. Salutation is used for greeting the user at the time of logging.

  • The admin (RM) ID specified in user maintenance is one of the RMs to which the user can communicate with through the mail facility of Retail e-Banking.

  • A user can be enabled or disabled for multi-currency transaction by using the “multi currency allowed” flag. The bank can effectively control such that only a few users within the retail have the right to do multi-currency transaction.

  • Customer status is common code of code type CST, Residential status is common code of code type as RSC, marital status is COCD of code type MST, Employment status is code type EST, Education level is code type EDL and Income range is code type INR. The common code descriptions are displayed in the respective drop down lists while adding/modifying a retail user.

  • A new user created is always disabled. Thereafter the user will need to be specifically enabled.

  • The users created by the above options are maintained in the CUSR table, with user type value as “1”.

• When e-Banking application is portlet enabled then the user IDand signon password needs to created at the portal server. Please refer to the section of Creation of e-Banking users in portal environment in the e-Banking installation guide to know how to create the users.

• A custom hook is provided at the time of fetching the list of retail user wherever applicable in the application. This is to fetch branch specific retail user details and thus enhancing it to cater to de-centralized banking operations as well.

• Analytics is used in various areas of business for better decision making. Finacle e-Banking integrates with open source web analytical engine Piwik as an out-of-the-box (OOTB) feature to analyse user activities. Piwik can pull data regarding activities of both bank users and end users from e-Banking using javascripts through the web analytical application login. The data consumed can result in various types of reports and analysis as per the capabilities of Piwik.

Navigation

The following is the navigation for this option:

• Click User Maintenance in the RETAIL ADMINISTRATION menu.

• The User Maintenance screen is displayed.

What you can do

The table below provides a brief description of the data displayed on the screen and the functions you can perform:

Field

Description

Option Button

Select the option for initiating a retail user search.

Note:

None of the options are mandatory for search. The search will happen even though all the three fields are null. Search will consider any non-null field out of the three fields.

User Id

The ID of the retail user. Click  Lookup to retrieve the list of retail users whose details are to be updated.

Note:

The User ID Search is an exact search.

Mobile Number

Type the mobile number of the user to search for the user details.

Cust ID

The CIF ID of the retail user.

Note:

Search on CIF ID is an exact search. It would be case-sensitive if CIF ID contains alphabets.

Cust Bank ID: The Bank ID of the CIF ID.

Note:

If the CIF ID belongs to Other Bank, the Bank ID has to be mentioned. Incase the Bank ID for the CIF is not mentioned, by default it would be taken as the home bank ID of the administrator.

Account Number

Account number search has two options:

Within Bank Account

Other Bank Account

Note:

Search on Account Number is the best search for users-with account number. Type of access on the account does not matter. If the account is closed, it will be treated as no users have access to that account.

Cust Bank Id: The Bank ID of the CIF ID.

Note:

If the account number belongs to Other Bank, the Bank ID has to be mentioned. Incase the Bank ID for the account number is not mentioned, by default it would be taken as the home bank ID of the administrator.

All Retail Users

Indicate to list all the retail users.