4.9 Default Information for Bulk Client Imports

This topic provides instructions to maintain default information for bulk imports from a bulk client, to be applicable for a distributor institution.

Maintain Default Information for Bulk Client Imports

In the Bulk Client Defaults Maintenance screen, you can maintain default information for bulk imports from a bulk client, to be applicable for a distributor institution. The specifications you make in any of the fields here, for each upload type, are accepted as the default values for the corresponding field or column name, for all bulk imports where the hand off files from the bulk client do not contain the corresponding information.

Accordingly, you must select the ID of the bulk client for whom the default information is applicable, in the Bulk Account Client Code field, and the AMC / distributor entity in the AMC / Distributor ID field.

For some of the upload types, the default information consists of fields from the corresponding maintenance in the system; therefore, the default information is very similar to a maintenance template or blueprint. For instance, when you define the defaults for fund rules import, you specify all the fund rules in the Bulk Clients Defaults Maintenance screen. This is just like filling in the fund rules in the system for a new fund; validations for all fields are similar to those made in the Fund Rules screens when a new fund is entered.

The default information for each upload type is listed in this topic; for field level information, you must refer the topics in the user manual where the corresponding entry screen in the system is discussed.

Note on Scheme/ Cross Reference Number

The Bulk Client would wish to export, in the hand off files, a unique identifying number for each upload type that might be different from that of the Oracle FLEXCUBE Investor Servicing generated identification. In such cases it is possible to set a reference between the Oracle FLEXCUBE Investor Servicing identification and the unique identifying number given by the bulk client. To specify such a request, use the Scheme/Cross Reference Number field; for transaction and unit holder related data imports, and the Fund Scheme / Cross Reference Number for fund information related imports.

Effect of applying Scheme / Cross Reference Number

For example, the Credit Card Number of investors can be a uniquely identifiable value. In such cases the credit card number can be setup as an additional information and this field can be referred to here as a unique value by making it the Scheme/Cross Reference number column in the Bulk Client -AMC default maintenance. This means that when the unit holder import file upload is performed, the relevant Scheme/Cross Reference Number field will be populated with the value given in the import file.

Note:

The Scheme/Cross Reference Number value should be given in the appropriate field position in the import file. This is not applicable where the Scheme/Cross Reference Number is, itself, the Unit Holder ID (for transaction and unit holder related imports) or the Fund ID (for fund information related imports).
When the transaction import file upload is performed for the Bulk Client - AMC combination, the Unit Holder ID field value should contain the Scheme/Cross Reference Number value.

Note:

The system will not validate for uniqueness if the same field is populated with duplicate values through the Unit Holder Additional Information Maintenance screen. It is assumed that such cross-reference numbers are populated only through import file uploads.
Scheme / Cross Reference Numbers for Transactions and Unit Holder Related Imports Scheme / Cross Reference Number from additional information

The specification made in the scheme/cross reference number field will pertain to any one of the fields mentioned below and should be properly specified (in the relevant field position) in the import file given for unit holder new accounts.

For example, if the Scheme/Cross Reference Number has been specified as the third additional information set, this information should correspond to being the AdditionalInformation3 field in the import file.
  • AdditionalInformation1
  • AdditionalInformation2
  • AdditionalInformation3
  • AdditionalInformation4
  • AdditionalInformation5
  • AdditionalInformation6
  • AdditionalInformation7
  • AdditionalInformation8
  • AdditionalInformation9
  • AdditionalInformation10

All the above fields are additional information that can be optionally set to capture additional data relating to the investor.

It is possible to set a restrictive list of values to be captured in the additional information value fields.

All additional information setup through the additional information master where the restrictive clause is not applied are considered to be free-format fields. These fields will be the candidates to be set as the scheme/cross reference numbers.

Scheme / Cross Reference Number as Unit Holder ID

If the Scheme/Cross Reference Number value is set the same as the Unit Holder ID, this means that the bulk client would supply the Unit Holder ID in all the file imports. If the Scheme/Cross Reference Number is another uniquely identifiable value then the relevant value should be specified in the import file. In such cases the system will map the Scheme/ Cross Reference Number to Unit Holder ID and the transaction will be tagged to the relevant unit holder

Scheme / Cross Reference Number as Unit Holder Reference Number

If the Scheme/Cross Reference Number value is set the same as the Unit Holder Reference Number, this means that the bulk client would supply the Unit Holder Reference Number in all the file imports. If the Scheme/Cross Reference Number is another uniquely identifiable value then the relevant value should be specified in the import file. In such cases the system will map the Scheme/Cross Reference Number to Unit Holder Reference Number and the transaction will be tagged to the relevant unit holder.

Scheme / Cross Reference Numbers for Fund Information Related Imports

For fund information related imports, the scheme / cross-reference number can be set as any of the following:
  • Fund ID
  • Fund Identification Number
  • Fund Ticker Symbol
Specify Generation of System Reference Numbers

It is required in the FCIS system that the reference numbers be mentioned along with the unit holder new account details and the transaction details. If this option is specified, the system will generate reference numbers wherever the reference number field in the import file is empty.

Specify Checking of Duplicates during Imports
You can choose this indicate that all the records that have duplicate Scheme/Cross Reference Number values should be rejected when the transaction or unit holder import file up-loads are performed. If this option is not chosen, the following processes would occur:
  • The system ignores the duplicates in the case of unit holder uploads, and creates unit holders in the system.
  • For transaction uploads, the system goes ahead and creates the transaction on behalf of the first Unit Holder ID occurrence found in the system.
Specify Generation of Authorized Data during Import

This option, if chosen, signifies which imported information sets would generate authorized records – fund rules, transactions, unit holder accounts, income distribution setup, standing instructions, fund price or transaction load override.

Redemption Payouts to Unit Holder Bank Accounts Only?

Optional

Check this box to indicate that, by default, it must be designated that for all unit holder accounts imported, redemption payouts are to be made to the unit holder bank account only.

Parent topic: Import Bulk Client Information