18.7 Upload Security Instruments for Amendment

This topic describes the how to upload security instruments for amendment.

From an external system, you can upload Securities that require amendment in Oracle Banking Treasury Management. The system will distinguish between the new and the ones that require amendment based on the action code of the uploaded record. For an instrument requiring amendment, the action code will be ‘AMND’. If the action code is ‘AMND’, Oracle Banking Treasury Management will first check whether the instrument exists in the system or not. If it does not exist in the system, an error message will be displayed to notify that the instrument cannot be amended.

The Security ID provided by the external system has to same if it is a new instrument or if it is an amendment to an existing one. When you upload a new instrument, the external security Id number will be displayed in the ‘Security ID’ field for that instrument.

The Security ID will be the basis for checking whether the instrument exists or not. The upload for the security amendment will trigger the ‘AMND’ event. The same event is triggered even when you amend the ‘Securities Definition’ screen itself. The fields that can be amended for Security are as follows:

• ISIN Identifier
• Description
• Redemption/Expiry Date
• Outstanding Issue Size
• Payment Currency

At the time of uploading a securities instrument, if only the Security Id and Product is provided and the source preference has ‘Put on Hold’ on Exception then the instrument will be uploaded with status Hold. Subsequently, any user can modify the same. If the instrument is created from the front end and kept on hold only then can the same user modify the instrument. If the instrument is created having a market code whose country code is different, then the country code of the home branch in which the instrument is created will be treated as ‘Foreign Market Instrument’. Otherwise, the instrument will be treated as ‘Local Security Instrument’. In Oracle Banking Treasury Management the following batch functions will be created to handle triggering of notification:

• Notification for Local Instrument Changed
• Notification for Securities Coupon Revision Announcement
• Notification for Local Market Security Price

This batch function will log a notification into the Database queue. This will, in turn, be picked up by the Gateway and will be sent to the external system. During batch hand-off for security instruments, only the Local Security Instrument will be handed off and not the Foreign Market Instrument.