This transaction is used to maintain transaction configurations.
Transaction configurations are used to override or complete the hard-coded requests of particular rules in business transactions.
By means of the configuration panel, the following types can be overridden:
The following transactions can be started from here by clicking the icons in the list below for:
After entering at least one search term in the fields Transaction, Type or Code, the transaction configuration matching the selection will be displayed in the table on the “Search Panel”.
By double-clicking an entry a definition will be displayed on the configuration panel.
If the checkbox “Display Default Entry to compare” is checked and a DTC record exists, a popup with the DTC details is popped up and displayed.
If the checkbox “Suppress Default from Transaction” is checked, then the execution of the programmed rule will be suppressed without substitution. In this case no further entries can be made.
In case the transaction configuration rule has to be executed only under specific conditions, it can be defined here as simple 'IF' request. In doing so, up to two fields, constants or functions (e.g. 'today') can be specified and compared with an operator.
The following conditions are available by default:
The specified condition is displayed as converted TradeDesign source code on the screen. No syntax check is performed. A condition defined in the sources will be ignored at any rate, in case there is a transaction configuration available for the relevant key, irrespective of whether there was a condition defined in the transaction configuration.
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 field that is used for assigning the transaction configuration to the relevant part of the source code is specified in the “Code” field. The user could create a new (diary/fee) transaction configuration by clicking the 'Add New' icon.
Similar to defining a new diary/fee entry, existing rules from source could also be modified through this transaction configuration. For example, GENDTC generates the transaction configuration from the source (see Generating Application Transaction Configuration from Source). If diary option is selected, it downloads the diaries that are specified in the source code into the ATC table. Thereby making it easy for the user to view and amend (i.e.override) the already existing diaries, if needed. The user upon selecting the 'default' record (entry from source code), could click on the 'Add New' icon, by which the generated DTC record is mapped to the panel. The user could do the required changes and save the changed entry.
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:
In the source code, these calls are generally entered in the DIASAV 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. Technically, setting this flag adds a “$” symbol to the argument code, for e.g. “FOL$” in the diary call function. Predefined text could be created from the text module transaction DBITXM (see Maintaining Text Modules) which will be automatically used when the diary is processed.
“Sample flow for STP generation of tracer:”
Syntax of the rule within the source code: “AddFeeData( <Code>, <Defaulting>, <Units>, <From-Date>, <To-Date>)“
Usually, the requests are in rule RegisterSettlement in the source code.
Datafield | Description |
---|---|
Transaction ID | cf Appendix A, Table ATC field TRN |
Type | cf Appendix A, Table ATC field TYP |
Code | cf Appendix A, Table ATC field COD |
Datafield | Description |
---|---|
Transaction ID | cf Appendix A, Table ATC field TRN |
Type | cf Appendix A, Table ATC field TYP |
Code | cf Appendix A, Table ATC field COD |
Variant ID | cf Appendix A, Table ATC field VAR |
Ignore Transaction Rule | cf Appendix A, Table ATC field IGNFLG |
Condition | cf Appendix A, Table ATC field CND |
Type for Condition Field 1 | cf Appendix A, Table ATC field CNDFLD1TYP |
Condition Field 1 | cf Appendix A, Table ATC field CNDFLD1 |
Type for Condition Field 2 | cf Appendix A, Table ATC field CNDFLD2TYP |
Condition Field 2 | cf Appendix A, Table ATC field CNDFLD2 |
Conditions | cf Appendix A, Table ATC field CNDSTM |