Introduction
|
Relationship Managers (RM) are the staff of the bank serving the bank customers. They are the customer contact point regarding internet banking. The e-Banking application uses Relationship Managers defined in Retail e-Banking for customer communication (mail), request processing and for approval of special transactions. This functionality is controlled through the menu options of RMGR, RMGRM & RMGRV.
This section outlines the activities for RM Maintenance.
|
Steps to maintain RM
|
The Retail e-Banking administrators does the following to maintain the Relationship Manager:
-
List the existing RMs defined in the application.
-
Create, view, and modify details of RM.
-
Disable an existing RM. This sets the deletion flag to “Y”.
-
Set password for an RM. Password program randomly generates a password for the RM.
-
Enable a newly created RM or a disabled RM. An RM is enabled only after the password is printed.
|
Notes
|
This section outlines the important points in maintaining the RM:
-
The password print program prints the address details of the RM(in principal language id of the application).
-
The language codes available to the RM are taken from the entries made in the LANG table.
-
Country Codes (Common code of Code type = ‘CNT’), State codes and Menu profiles should be created before RM is created.
-
As per internationalization standards, two date and time formats are supported by Retail e-Banking: Short date format & Long date format. These formats are created in COCD table as seed data: Code type = ‘DFT’ & Common codes as 2 (Short date) & 3 (Long Date).The actual display format is decided based on user locale.
-
The amount formats supported by Retail e-Banking are determined as per user locale . The locale user is decided by the user’s language code and language country code.
-
Finacle retail e-Banking application uses the e-mail ID (not alternate e-mail ID) specified above for forwarding the Retail e-Banking mails to RM. RM can receive, read & reply Retail e-Banking from outlook mail client.
-
The RM details are maintained in CUSR table with user type value as “4”.
-
The password set by the administrator is checked against history of passwords set for an administrator id. Number of passwords in history is determined by the Retail e-Banking parameter MAX_PWD_IN_HISTORY. Any password in history should not be reused.
-
Whenever a new password is set for an administrator, he is forced to change the password on first log-on.
When e-Banking application is portlet enabled then the user ID and Signon password needs to created at the portal server.
Note:
To create the users, refer to Creation of e-Banking users in portal environment in the e-Banking installation guide.
|
Navigation
|
The following is the navigation for this option:
|
What you can do
|
The table below provides a brief description of the data displayed on the screen and the functions you can perform:
|