20.7 Maintain Function Code Preferences

The Function Code Preferences screen is used to define the workflow preferences (validation preferences and authorization preferences) for a function code.

For the list of function codes and the respective screen names, refer to List of Function Codes. The rule-based authorization option in this screen is used to configure multi-level authorization with AND or OR condition. The multi-level authorization feature is described with the following example.

The sample user roles are considered as follows:

• JUNIOR TELLER (Supervisor enabled)

• SENIOR TELLER1

• SENIOR TELLER2

• OFFICER LEVEL1

• OFFICER LEVEL2

• BRANCH MANAGER

The sample values for limits and roles maintained are as below:

Table 20-11 Sample Values for Multi-level Authorization

Transaction Limit	Primary Authorization	Alternate Authorization
50,000 to 9,99,999	SENIOR TELLER2, OFFICER LEVEL1, and OFFICER LEVEL2	OFFICER LEVEL2 and BRANCH MANAGER
10,00,000 to 99,99,99,99,999	SENIOR TELLER1 and OFFICER LEVEL1	OFFICER LEVEL2 or BRANCH MANAGER

The approval needs to be provided by the roles configured with AND or OR condition defined either in the primary authorization path or in the alternate authorization path. Based on the sample values provided, the following are some possible scenarios for multi-level authorization:

Table 20-12 Examples for Multi-Level Authorization

Condition	Authorization Process
Teller with JUNIOR TELLER role inputs a cash deposit transaction of amount 10,000	The transaction gets completed automatically without authorization.
Teller with JUNIOR TELLER role input a cash deposit of 60,000	The transaction gets assigned to all the roles mentioned in Primary and Alternate Authorization paths. For example, when a user with the OFFICER LEVEL2 role picks the transaction and authorizes it, the transaction gets assigned to the other three roles in the Primary and Alternate paths. Further, based on the user who picks for approval, the corresponding path will be chosen by the system. If a user with BRANCH MANAGER Role picks the transaction for approval, the system identifies the Alternate Path for approval and ends the authorization process. If a user with SENIOR TELLER2 role picks the transaction and authorizes, then the corresponding Primary Path will be chosen by the system for OFFICER LEVEL1 to authorize the transaction.
Teller inputs an account transfer of 20,00,000	The transaction gets assigned to all the roles mentioned in Primary and Alternate Authorization paths. When a user with BRANCH MANAGER role or OFFICER LEVEL2 role picks the transaction and authorizes it, the system identifies the path as Alternate and ends the authorization process. Else if a user with OFFICER LEVEL1 picks the transaction and authorizes it, the system identifies the path as Primary for SENIOR TELLER1 to authorize the transaction.

To maintain function code preferences:

1. On the Homepage, from Teller mega menu, under Branch Maintenance, click Function Code Preferences or specify Function Code Preferences in the search icon bar and select the screen.
   The Function Code Preferences summary screen is displayed.

   Figure 20-11 Function Code Preferences (Summary)

   
   

   
   Description of "Figure 20-11 Function Code Preferences (Summary)"

   
   
2. Click the icon.
   The Function Code Preferences screen is displayed.

   Figure 20-12 Function Code Preferences

   
   

   
   Description of "Figure 20-12 Function Code Preferences"

   
   

   Figure 20-13 Rule-Based Authorization

   
   

   
   Description of "Figure 20-13 Rule-Based Authorization"

   
   

   Figure 20-14 Transaction Limit Check

   
   

   
   Description of "Figure 20-14 Transaction Limit Check"

   
   
3. On the Function Code Preferences screen, specify the fields. For more information on fields, refer to the field description table.

   Note:

   The fields, which are marked with an asterisk, are mandatory.

   Table 20-13 Function Code Preferences - Field Description

   Field	Description
   Branch Code	Select the branch code from the list of values. Note: The list of values should have the *.* for the "All" option.
   Branch Description	Displays the description of the branch code.
   Function Code	Specify the function code. The list of values displays the valid function codes.
   Function Code Description	Displays the description of the function code.
   General Preferences	Specify the fields. This segment can be used to configure single-level authorization of the preferences with the use of the Authorizer Role field.
   Teller Sequence Request	Select this option to generate the Teller sequence number.
   Teller Sequence Prefix	Specify the prefix for the generation of the Teller sequence number. Note: This is mandatory only if the Teller Sequence Request is selected.
   Validation Preferences	Specify the fields.
   Charges Amendable	Select if the charges are allowed to modify for the transaction.
   Exchange Rate Amendable	Select if the exchange rate is allowed to modify for the transaction.
   Rule-Based Authorization	Select if the rule-based authorization is required for the transaction. Note: Assignment mode to be defined as 'Auto' if Rule based auth flag is selected.
   Email Approval Required	Select if authorization through email is required for a transaction. Note: If this option is selected in override confirmation, then an email will be sent as per the assignment mode maintained. This email will be sent to the selected approver or a list of approvers associated with the role maintained. The approvers will get an email for authorization only if receive email flag is selected in the User Preferences screen. Once the email is received, Approver can either approve or reject the transaction. When you click the Approve or Reject, an email will be automatically opened in the system where the approver can type their comments. The setup for Plato alerts needs to be completed and Kafka topics need to be created to enable e-mail alerts. For information on setup, refer to Oracle Banking Branch Installation Guide.
   Signature Verification Required	Select if the Teller needs to verify the customer’s signature while submitting the transaction.
   Authorization Preferences	Specify the fields.
   Authorization required for Interbranch Transaction	Select if the authorization is required for the inter-branch transaction.
   Authorization required for Charge Amendment	Select if the authorization is required in case you have amended the charge defaulted by the system.
   Authorization required for Exchange Rate Amendment	Select if the authorization is required in case you have amended the exchange rate defaulted by the system.
   Authorization required by Default	Select if the authorization is required by default for the transaction.
   Assignment Mode	Select to indicate whether remote authorization assignment is the automatic or manual operation for the transaction.
   Authorizer Role	Select the role of the authorizers. The users belonging to this role are the valid authorizers for this workflow. Note: This field is applicable, if assignment mode is Manual or if assignment mode is Auto and no default authorizer is maintained for the user.
   Rule-Based Authorization	Specify the fields. This segment can be used to configure multi-level authorization of the preferences with the use of Supervisor Role ID and Alternate Supervisor Role ID fields. Note: Rule Based Authorization cannot be applied for customer servicing transactions.
   Currency	Select the currency of the transaction from the LOV.
   From Amount	Specify the "From" cap amount.
   To Amount	Specify the "To" cap amount.
   Amend Charge	Select from the drop-down values (Yes or No).
   Amend Rate	Select from the drop-down values (Yes or No).
   Interbranch Transaction	Select from the drop-down values (Yes or No).
   Supervisor Role ID	Select the supervisor role ID from the list of values. The following conditions apply to this field: More than one role can be added for authorization. If multiple roles are added, it is not mandatory to authorize in sequential order of the roles added. The roles added in this field are considered for the primary level of authorization.
   Supervisor Role Logical Operator	Select the logical operator AND or OR. If AND is chosen, all the Supervisor role specified in primary path has to authorize the transaction. If OR is chosen, either of the Supervisor role has to authorize the transaction.
   Alternate Supervisor Role ID	Select the alternate role ID from the list of values. The following conditions apply to this field: More than one role can be added for authorization. If multiple roles are added, it is not mandatory to authorize in sequential order of the roles added. The roles added in this field are considered for the secondary level of authorization.
   Alternate Supervisor Role Logical Operator	Select the logical operator AND or OR. If AND is chosen, all the Supervisor role specified in primary path has to authorize the transaction. If OR is chosen, either of the Supervisor role has to authorize the transaction.
   Transaction Limit Check	Specify the details under this section. Double-click on a row to enable the fields.
   Transaction Currency	Click the search icon, and select the transaction currency from the list of values.
   Transaction Amount	Specify the transaction amount.
   Action	Click the necessary icon to save, edit, or delete the values of a row.

4. Click Save.
   The summary view is displayed with the configured function code preferences.