4.5 Imported Bulk Information

This topic explains how to process imported Bulk Information.

Process Imported Bulk Information

After you have set up the Scheduler Services to automatically perform the upload of bulk client information, the import and processing of data will proceed according to the defined frequencies.

1. You can find the unique Process ID for each file that is imported or exported.
   The import of each file containing bulk client information is given a unique Process ID. The export of rejected records corresponding to the import is likewise is given a unique Process ID. Therefore, the Process ID is unique for each file that is imported or exported.
2. The job that you have set up for the automatic execution of the imports will trigger processes that:
   1. Perform all system and business validations for the data that is being imported.
   2. Update the system database with the imported data.

   Note:

   The validations for the imported data are performed in the same manner, as they are applicable when you set up the default information for the bulk client in the Bulk Client Defaults Maintenance screen.

Bulk Import Processing Work flow

3. After you have set up the import interfaces and scheduled the imports, the system automatically performs the import and the processing of imported information in the following sequence.
   1. Import the unit holder new accounts and information change.
      If errors occur during this import, all subsequent processes are terminated. The details of the errors are logged into the interface error log table.
   2. Process the imported unit holder information.
      Again, if errors occur during this processing, all subsequent processes are terminated. The details of the errors are logged into the interface error log table.
      This results in updating the system database with the new unit holder accounts and the information change accounts.
   3. Import and process the unit holder information.
      The event Bulk UH is raised by the system upon successful completion of the unit holder information import and processing, and the subsequent bulk imports are triggered.
   4. Import and process the new, and amended transactions and standing instructions, load overrides, income distribution setup records and fund prices.
      The system database is updated with the new records created.
   5. Import and process the non-unit holder information.
      The event FAILEDRECS is raised by the system upon successful completion of all the non-unit holder imports and processing of the same.
   6. The FAILEDRECS event triggers the export of rejected records and reports the errors encountered during the processing.
      The entire import and processing cycle is now complete.
   7. You can find the import and processing cycle, that begins again according to the frequency defined for the unit holder import interface.

   Note:

   Sequences 1 and 2 are performed by the execution of interface definition you have set up for the unit holder import. Sequence 4 is performed by the execution of the interface definition you have set up for the non-unit holder information import. Sequence 6 is performed by the execution of the interface definition you have set up for the export of rejected records.