1.1 Back Data Processing

This topic provides information on Back Data Processing.

Propagation of back data is a process wherein the system simulates all the relevant transactions for a Unit Holder from the date of propagation till current date, This is done by simulating the incomplete or incorrect transactions in a separate schema known as the report schema.

For the simulation, the transaction details need to be entered in the normal or business schema and then selected for data propagation. The system will then access the latest version of the transaction that is being propagated from the main tables in the business schema and update information accordingly. The updated information will be stored in the tables of the report schema and can be viewed from the business schema.

Propagation can be done for multiple transactions at the same time, for instance if you wish, you can modify a transaction and at the same time select another transaction for deletion. Each time propagation happens, the system will generate a unique reference to identify the process and store it along with the data in the business schema. This reference will be used to retrieve the propagation data for the corresponding transaction from the report data stores after propagation.

The following transactions can be propagated:

• UT Transactions
  • IPO
  • Subscription
  • Redemption
  • Normal Switch and Pseudo switch
  • Transfer
  • SI transactions
• LEP Transactions:
  • Policy Initial Investment
  • Top up
  • Premium
  • Annuity
  • Policy switches
  • Recurring switches
  • Surrender

Note:

• If the transaction is unavailable in the main tables of the business schema, the system will check for its existence in the archives (of the business schema) and display an error message if the transaction cannot be traced in either of these.
• The propagation will be only a simulation in the report schema. You will not be allowed to correct data or input data missed out in the business schema.
• You cannot perform multiple operations on the same transaction.
• If, after a transaction has been entered in the business schema, there is an NAV correction, the system will consider the corrected NAV for propagation.

The following details will be stored in the report data stores for the propagated transactions:

• Total confirmed units before propagation
• Total confirmed units after propagation
• Total Provisional units before propagation
• Total Provisional units after propagation
• Net profit
• Net Loss