7 Automatic Processing

While discussing the various events in the life cycle of a deal, we have referred to the Automatic Contract Update function that carries out these events. In this chapter, we shall discuss the features of this function.

The Automatic Contract Update function should executed at least twice during the day, once before you begin transaction related activities for the day (that is, as a part of the beginning of day activities) and once after you have finished all the transaction related activities for the day.

If any transaction related activities are carried out after the function has been run as part of End-of-Day (EOD) activities, you have to execute it again so that the processing that may be necessitated by the transaction related activity is carried out.

• Automatic Events in the Lifecycle of a Deal
  This topic describes the Automatic Events that takes places in Beginning-of Day and End of day.
• Specify the Branch Parameters
  This topic provides the instructions to capture the Branch Parameter Details.
• Initiate the Automatic Contract Update Function
  This topic describes how to inquire the Automatic Contract Update function.
• Initiate a Future Value Dated Deal
  This topic describes the future value dates deal.
• Process an Automatic Repayment
  This topic describes the process of an automatic repayment.
• Automatic Rollover of a Deal
  This topic describes the automatic rollover a deal.
• Accrual of ICCF Components
  This topic describes the definition of accruals for the accruable ICCF components
• Profit Rate Revision on a Deal
  This topic describes the profit rate revision on a deal.
• Value Dated Changes
  This topic describes the value dated changes wand advices generated for value dated changes.
• Triggering the Year-end Batch Process for Collecting Contract-Wise Data
  This topic describes the batch process for Collecting Contract-Wise Data.
• Commodity Upload
  This topic describes the commodity upload option.