This article explains the fields involved in the Detail. 

After entering the code of the related transaction in the Transaction, Type, or Code fields, the application transaction configuration (ATC) corresponding to the selection will be displayed in the table in the search panel.

Double-clicking on an entry will display a definition in the configuration panel.

Displaying the default entry

If the Display default entry to compare checkbox is selected and a DTC record exists, a popup with the details of the DTC is displayed.

Suppressing/canceling a scheduled rule.

If the Suppress default from transaction checkbox is selected, the execution of the scheduled rule is suppressed without replacement. No further entries can be made in this case.

Definition of conditions.

If the transaction configuration rule is to be executed only when specific conditions are present, it can be defined as a simple 'IF' request. In this way, up to two fields, constants or functions (e.g., "today") can be specified and compared with an operator.

By default, the following conditions are available:

• Equals
• Not equal
• Greater than
• Less than

• Is Empty
• Not is Empty
• Free Formula
• Unconditional

The specified condition is displayed as converted TradeDesign source code on the screen. No syntax check is performed.

If an ATC rule exists for a condition, then any rules defined in the sources for that same condition will be ignored.

Also , if there is an ATC rule set up for a condition it will be invoked, irrespective of whether there was a source code rule for that condition.

A transaction configuration overrides a concrete request of a TradeDesign rule in a business transaction. At present, requests of TrnDiaSet and AddFeeData can be overridden. The arguments for requesting the rule are specified in the same sequence as in the source code. The user could create a new (diary/fee) transaction configuration by clicking the 'Add New' icon.

For the rules described in more detail here, transaction configurations can be stored for overriding the source code:

Syntax of the rule within the source code: TrnDiaSet(<Record Group>,<Code>,<Date>,<Coded Reason>,<Description Text>,<Target Description>,<Action>)
In the source code, these calls are generally entered in the DIASAV rule.

• Record Group: The module group of the defined business transaction for which the diary is to be created is specified here.
• Date: The target date to be specified in the diary This will be the base date for diary calculation.
• Days: The number of days to be added/reduced to the base date defined. The processing of diary will be calculated accordingly.
• Code: Freely definable term that is used to identify the diary technically (e.g. when it is updated). Example: “EXPIRE”.
• Coded Reason: Combo box for selecting the reason of the diary (e.g. expiry warning).
• Automatic Processing: Checking this field allows the target transaction defined to be automatically processed on the date the diary is executed.
• Description Text: Long text that is stored with the diary and which will always be displayed when the diary is shown.
• Target Transaction: Business transaction to be started when the diary is taken up for processing (e.g. in DIASEL).
• Target Role for Message: In case the target transaction defined is a common message, this field specifies the addressee/receiver of the message.
• Action: 'Replace' or 'Write'. Describes the action that has to be done, if an already stored diary has been found for the current contract and code when executing this rule.

Introduction of 'Automatic Processing' checkbox in the type 'Save Diary', enables automatic processing of the 'Target Transaction' provided. This generates automated (SPT) tracer/free message with a predefined text, at predefined intervals, to the 'Target Role for message' defined. 

Store Fee (Arguments for AddFeeData)