3 Bulk Upload Maintenance

This topic describes about the detailed information on bulk upload Maintenance.

Note:

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

The limit entities such as Facilities, Collaterals, Pools, Liabilities, and Exposures can be processed in bulk through files or queues in the Bulk upload Maintenance screen. The system also supports parallel processing of entities.

The bulk processing of all the following actions are supported:

• Creation of Limit Entities
• Maintenance of limit entities
• Transactions such as utilization and block

1. On the Home screen, specify GEDBLUPD in the text box and click the icon.
   The Bulk Upload Maintenance screen displays.

   Figure 3-1 Bulk Upload Maintenance

   
   

   
   Description of "Figure 3-1 Bulk Upload Maintenance"

   
   
2. On Bulk Upload Maintenance screen, click New and specify the fields.
   For more information on fields, refer to the field description table.

   Table 3-1 Bulk Upload Maintenance - Field Description

   Field	Description
   External System	Click the icon and select the name of external system from which the bulk processing request is to be received.
   Communication Mode	Specify the mode of communication to be established with the external system. The options available are: File JMS Queue
   Folder Location	Specify the path of location where the request files from the external system and response files from the Enterprise Limits and Collateral Management (ELCM) will be placed. This is applicable only if file is selected as Communication Mode. Note: The folder location must be a valid location in the ELCM application server and must contain the following sub-folders: REQUEST (location for placing request files from the external system) COMPLETED (location for storing the files successfully processed by ELCM) ERROR (location for storing the files for which processing is failed) RESPONSE (location for storing the response files generated by ELCM)
   Data Type	Select the data type for the selected communication mode. The options available are: JSON XML

   Types of Processing:

   • Sequential - Let’s consider a request file which contains ‘n’ number of records in the body. COMMITTYPE value is FULL. In this case, Request will be successfully processed only if all the records are processed successfully. If any of the records fail, then none of the records will be processed.
   • Parallel - Let’s consider a request file which contains ‘n’ number of records in the body. COMMITTYPE value is EACH. In this case, all records in the request will be processed. Both failed and successful responses will be written to the response file. The below validations are available for Bulk Upload request:
     • SOURCE_REF_NO tag is mandatory
     • SOURCE_REF_NO should not be identical
     • COMMITTYPE defaults to FULL if COMMITTYPE tag not is available in the request header.
     • Request files should be placed under correct folder name. If not, system throws “Request files should be placed in <FILE_PATH> for <SOURCE>”
     • External system needs to have an entry in Bulk Upload Maintenance. If not maintained system throws “<SOURCE> does not have an entry in Bulk Upload Maintenance”
     • Invalid Service Name and Operation is validated.
     • If action is invalid in the request, response will tell the right action for the source and operation
     • ELPoolService - If SOURCE is not provided in Collateral linkages section, system throws ‘SOURCE is mandatory in Pool Collaterals Linkage
     • When SOURCE is EXTSYS for Collateral Pool Bulk upload but collaterals are created Internally, system throws “Collateral Code must be External collateral for Source except ELCM”
     • When SOURCE is ELCM for Collateral Pool Bulk upload but collaterals are created Externally, system throws “Collateral Code must be Internal collateral for Source ELCM”
     • In case of EACH type for Collateral Pool, if Collateral Code is duplicated under same Liability no, then system validates.
     • If the file contains Duplicate record - Response file will contain Duplicate Liab no/Coll code/Line code/Pool Code are present.
     • If the DB contains Duplicate record-Response file will contain An Identical record exists for this record.

   Tag in the request header named COMMITTYPE can have the below possible values:

   • EACH – Request will be processed parallelly
   • FULL – Request will be processed sequentially
3. Click Save to save the record.

• Bulk Upload Status View
  This topic describes about the detailed information on bulk upload status view.