1.40 Operations on a BIC Record

This topic describes the operations performed on BIC records.

On an existing BIC code record, the user can perform any of the following operations (If a function under the Actions menu is disabled, it means that the function is not allowed for the record). Apart from defining a new BIC code record, the user can perform any of the following operations on an existing record (if any function under the Actions menu is disabled, it means that the function is not allowed).

• Amend the details of a record
• Authorize a record
• Copy the details of the record
• Close the record
• Reopen the record
• Delete the details of a record

Refer to the User Manual on Common Procedures for details of these operations.

It is assumed that the upload source contains details of all relevant BIC codes. The BIC records that are uploaded to Oracle FLEXCUBE Universal Banking should contain the following tags:

• U - If records do not exist in the Oracle FLEXCUBE Universal Banking BIC directory, the same would be inserted. For a record that already exists, it will be updated with that of the BIC upload.
• M - If there is no existing record in the Oracle FLEXCUBE Universal Banking BIC directory, the same would be inserted. Otherwise, the record will be updated with the one in the BIC upload.
• A - For an existing record in the Oracle FLEXCUBE Universal Banking BIC directory, an error will be logged and the upload will continue. If no records exist, then a new record will be updated with the one in the BIC upload.
• D - If there is no existing record in the Oracle FLEXCUBE Universal Banking BIC directory, an error will be logged and the upload will continue. If there is any record existing, then it will be marked as CLOSED.
• AM - For an existing record in the BIC file or AM file, the BIC code would be renamed in the upload file.

BIC addresses that have changed will be appropriately updated. Addresses bearing the tag D will be automatically deleted. New BIC records will be created for records that bear the tag N.

The network codes that are marked for exclusion in the BIC Upload Maintenance screen will not be uploaded.

The upload sequence is based on the modification tags in the BIC records. The sequence will occur in the following order:

• Deletion
• Modification
• Addition
• Unchanged

The file upload is processed asynchronously. The system prompts the user to check the logs.

Note:

The logs can be viewed by visiting Batch Operations, and then Intra Day Batch, and then Monitor (Fast Path: BASIDMTR). The function field can be given as ISDBICUP% for searching the up- load logs.