2.11.14 Collateral Notifications

This topic provides information on Notifications of colleteral maintenance.

1. On Collaterals Maintenance screen, click the Notifications tab.
   The Collateral Notifications screen is displayed.

   Figure 2-37 Collateral Notifications

   
   

   
   Description of "Figure 2-37 Collateral Notifications"

   
   

   Table 2-38 Notifications

   Field name	Screen	Modification	Old value relevance	Notification triggered when
   Collateral Value	Main screen	Direct/Batch	Yes	Collateral value changes.
   Lendable Margin	Main screen	Direct/Batch	Yes	Lendable margin changes because of revaluation on account of change in haircut or on changing the Haircut % directly.
   Covenant Revision Date	Covenants screen	Batch	No	Revision date is crossed and covenant expires.
   Valuation Amount	Valuation screen	Direct	Yes	Valuation amount changes.
   Haircut %	Main screen	Direct/Batch	Yes	Haircut percentage changed directly or based on haircut schedule or linked haircut code rate is modified resulting in haircut% in turn lendable margin.
   Charge Perfection Status	Perfection screen	Batch	No	Charge status is expired.
   Insurance End Date	Insurance screen	Batch	No	Whenever collateral is modified as part of EOD or manual screen update and Insurance end date is less than or equal to current date.
   Available Amount	Main screen	Direct/Batch	Yes	Available amount changes.

   Notification sub-system enables the particular collateral record to be a candidate for notification when the record is created / amended. At least one of the out of box supplied fields in notification sub-system must be enabled to bring this collateral under the purview of generating notification. When values in fields enabled for notification are modified as part of direct update process or as part of batch update process, all the details of the collateral are sent in the notification message along with old and new value details of the fields enabled for notification.

   Notification messages are logged in GETB_NOTIFICATION_LOG table with unique reference number. A new quartz job is required to read notification messages and publish it on configured queue/topic.

   Prerequisites for triggering notification:

   • CSTB_Param setting must be updated as JSON and the server must be restarted – Configure the following in CSTB_PARAM:
     1. PARAM_NAME as ELCM_NOTIF_REQ, PARAM_VAL as Y.
     2. PARAM_NAME as ELCM_NOTIF_TYPE, PARAM_VAL as JSON.
   • Scheduler job (ELCMNOTIFICATIONS) must be configured using STDJOBMT Screen
   • Entity must be configured in STDJOBMT with name ENTITY
   • The Job ‘ELCMNOTIFICATIONS’ must be resumed from SMSJOBBR
   • Notification queue (NOTIFY_DEST_QUEUE) and Connection factory (NotifyDestQCF) must be configured in Weblogic as per the below Document.

   https://docs.oracle.com/cd/F29383_01/PDF/Installation/Environment%20Setup/Application%20Server/FCUBS_Weblogic_JMS_Configuration.pdf

2. Click Save to save the record.