Future Transaction Trigger

The Future Transaction Triggering chain uses data setup from transaction processing and entries created by users on the Future Transaction Triggering (FDT) page as input for scheduling and creates transactions on a scheduled basis. The chain will not only create and load transactions; it also creates later FDT entries when necessary as well as cleaning off transaction triggers past the Expire Date. The transactions created by the chain are not submitted by the chain. Some require manual intervention while others will be picked up by a System Maintenance Utility job defined to submit transactions.

On Transaction Control (DCTRL) there is an indication to control whether or not a transaction code can be established as triggered transaction - Recurring Transaction Allowed. Any transaction type that cannot be copied cannot work successfully as a recurring trigger.

There are three types of triggers. The most common is the recurring one where the system copies either the most current version or the version specified on the trigger. Another common type is the reversal, which is performed only by the Journal Voucher transaction type. Here a copy of the original trigger transaction is copied, the debits and credits are reversed, and memo reference is made to the original trigger transaction. The last type of trigger is the reclassification where the system modifies the triggered transaction specified. For reclassifications of unearned revenue on Receivable and Cash Receipt transactions, the Line Amount of the unearned accounting lines is reduced to equal the Closed Amount. A copy is then made of that accounting line which is inserted into the transaction with a Line Amount equal to the reduction that just occurred. The unearned revenue event type is not copied and allowed to default to an earned one based on Allowed Event Type for Transaction Code setup.

The following are the important pages related to this Chain job:

Future Transaction Triggering (FDT)Future Transaction Triggering (FDT)

The fields on the Future Transaction Triggering (FDT) page are as follows with common ones omitted. Many of these fields cannot be updated after the Triggered Transaction.

Field Name	Field Description
Start	The required date for which the page will apply frequency settings to determine when the next trigger should occur.
End	The date that triggering should stop.
Recurring JV Reversal Reclassification	The type of trigger generated: Recurring – Will create one or more copies. JV Reversal – Will create a copy of the source journal voucher where the debit and credit amounts on the Accounting tab are switched and memo references are created back to the source transaction. Reclassification – Certain transactions allow this action to create a subsequent version and make pre-defined updates (CR, RE, PRLLL, PRLCE, PRACR)
Frequency Type	Choices of: One Time Future – The default for JV Reversal and Reclassification. Weekly Monthly by Date Monthly by Day
Frequency Type 2	A second level of frequency required for Weekly, Monthly by Date, and Monthly by Day. Values in this field change for each of those three.
Frequency Type 3	A third level of frequency required for Weekly, Monthly by Date, and Monthly by Day. Values in this field change for each of those three.
Active	When true, the record is eligible for selection by the Future Transaction Triggering Process. When false, the trigger is paused until activated again.
Carry Forward Amount	When true, the record will create the triggered transaction with the Line Amount found on the accounting line of the source transaction. When false, the Line Amount field will be $0.00 with the intention of a user completing that amount once it is known. This option only applies to Recurring triggers.
Hold Transaction	When true, the transaction will be created with a Transaction Status of Hold with the intention of the transaction being skipped by an automated submit process.
Bypass Approvals	When allowed by setup on Future Transaction Triggering Options page, the indication of true will result in the Bypass Approvals action being applied to the triggered transaction. The idea is that the original transaction went through approvals so copies of it do not need to be approved.
Transaction Prefix	An optional prefix that will be used in Automatic Transaction Numbering for the creation of the target transaction. If specified in Future Transaction Triggering Options setup, that prefix will default and cannot be changed.
Expire Date	A date at which time a successful trigger record will be deleted by the Future Transaction Triggering Process. The default is six months after the Start Date, but that can be overridden for a future trigger. However, once triggered, the field is protected and the date cannot be changed.

Please note that organizational security row filtering can be configured for this page such that, based on the security role, the system will filter the records returned to match the organizational security of a user. The filtering is on the Department of the trigger transaction header.

Future Transaction Triggering Options (FDTO)Future Transaction Triggering Options (FDTO)

The Future Transaction Triggering Options (FDTO) page allows you to specify different options for different Transaction Codes or specific Transaction Code/Department combinations. Setup on this page is optional. FDTO edits are only performed when records are being inserted or updated on the Future Transaction Triggering (FDT) page. The FDT page allows you to set up, maintain and trigger future transactions.

The fields on the Future Transaction Triggering Options (FDTO) page are as follows with common ones omitted.

Field Name	Field Description
Transaction Code	The first part of two in the definition of a Future Transaction Triggering Option.
Department	The second part of two in the definition of a Future Transaction Triggering Option.
Bypass Approval Option	A required indication to control the Bypass Approvals field found on Future Transaction Triggering. Valid values for this field are: Do Not Allow – Users are not allowed to bypass approvals; therefore, the Bypass Approval indication will always be false. Allow – Users can make the choice for individual triggers to bypass approvals or not; therefore, the Bypass Approval indication will default to false but can be changed to true. Require – The Bypass Approvals indication will default to true and cannot be changed. Note: The Allow and Require values cannot be selected unless the Approval Override Allowed indication on Transaction Control (DCTRL) is selected for the specified Transaction Code.
End Date Limit	A required number of days to limit the time between the Start Date and the End Date. A value of 0 means there is no limit.
Copy Final Phase Only	When true, only a transaction version can be specified as the source in a trigger is the Transaction Phase is Final or Historical Final.
Transaction Prefix	An optional prefix, already setup with the Transaction Code, Department and current Fiscal Year on Automatic Transaction Numbering that must be used for all triggered transactions. That verification will use the wildcard of **** when the Department is ALL and after any specific Department did not match a record.

For detailed information on the job (such as when to run, input, output, and process parameters) refer to the associated run sheet in the CGI Advantage General Accounting Run Sheets guide.