CORE Future Transaction Triggering Function Summary

Overview

This job aid explains the Future Transaction Triggering (FDT) function in CORE.

The Future Transaction Triggering process uses the FDT table to schedule and create transactions on a scheduled basis. The FDT screen lists all current FDT setup, where the Expire Date has not passed yet. The table lists all records at the top and detailed information of each record at the lower section. The page can also be separated into several elements to review a transaction triggering setup.

1. Triggering Transaction: Code, Dept, ID, and Version of the source transaction for all current triggering setup.

2. Trigger type: There are three basic types of future transaction triggers available within CORE:

• Recurring - Copies of the existing transactions based on the triggering configurations established on the FDT table. Recurring triggers can be entered by navigating to the FDT table via the Global Search. 

• Reversal - Copies of the existing Transactions with reversed Debits and Credits and memo reference of the original one, which is limited to JV type transactions. Reversal triggers have to be set up by entering the reversal date in the Header of the JV transactions before they are submitted. The reversal triggering record will be populated to the FDT table after the JV is finalized.

• Reclassification - Modification of specified transactions, such as adding a line in the RE or CR to reclassify unearned revenue to earned revenue. Reclassification triggers have to be set up in the CR or RE by entering the reclassification date in the Accounting Line before they are submitted. The reclassification triggering record will be populated to the FDT table after the RE/CR is finalized.

3. Dates: The Start Date is required, and the End Date and Expire Date are optional. Without an End Date, the trigger will operate indefinitely for recurring triggering. The system defaults an Expire Date 6 months from the Start Date if it is not entered. The records will drop off the table after the Expire Date.

4. Triggering Frequency: Frequency Type 2 and Type 3 have to be entered when Weekly or Monthly is selected as Frequency Type 1 for recurring triggering.

5. Two options to carry forward the amount from the triggering transaction and keep the generated transaction in held status when created. When Carry Forward Amount is unchecked, the generated transaction will not include any dollar amount. Regardless of the flag of the “Hold Transaction” field, the system will always create the transaction in draft status to allow users modify, comment or attach supporting backup documentation as needed.

6. Generated Transaction ID and Status of the record. The trigger will be in Ready Status with Active Flag checked after it is entered. Once it has been processed, the generated transaction will appear as a hyperlink, the Status will be updated to Successful, the Active flag will be unchecked, and all fields in the detailed session will become uneditable. For recurring triggers, a new record for the next scheduled triggering will be automatically created with a Ready Status, a new Start Date and new Expire Date.