Name | Helptext Description | Data Type | Len | Codetable |
---|---|---|---|---|
INR | Internal Unique ID | Text | 8 | |
TRN | Transaction ID | Text | 6 | |
TYP | Type | Text | 6 | Embedded |
VAR | Variant ID | Text | 3 | |
IGNFLG | Ignore Transaction Rule | Text | 1 | |
COD | Code | Text | 12 | |
ARG1 | Argument 1 | Text | 75 | |
ARG2 | Argument 2 | Text | 75 | |
ARG3 | Argument 3 | Text | 75 | |
ARG4 | Argument 4 | Text | 75 | |
ARG5 | Argument 5 | Text | 75 | |
ARG6 | Argument 6 | Text | 75 | |
ARG7 | Argument 7 | Text | 75 | |
ARG8 | Argument 8 | Text | 75 | |
ARG9 | Argument 9 | Text | 75 | |
EDTFLG | manually edited | Text | 1 | YESNO |
CND | Condition | Text | 3 | Embedded |
CNDFLD1TYP | Type for Condition Field 1 | Text | 6 | Embedded |
VER | Version | Text | 4 |
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.
For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.
This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.
Name of business transaction for which this dtc entry is valid.
Class of configuration definition. Each class needs special application logic in business transactions.
Code | Text |
---|---|
DIASAV | Save Diary |
FEESAV | Store Fee |
DOC | Document |
Unique identifier to classify this entry in the transaction. The content has to match the needs of the parameter class as identified in TYP.
For TYP = DIASAV the content of COD has to be the diary type (i.e. 'EXPIRE') of the corresponding TrnDiaSet rule.
If - depending on an additional condition - one of several variants of definitions for one COD of one TYP for one TRN exists, VAR allows to identify these different variants.
First argument for transaction configuration entry.
Second argument for transaction configuration entry.
Third argument for transaction configuration entry.
4th argument for transaction configuration entry.
5th argument for transaction configuration entry.
6th argument for transaction configuration entry.
7nth argument for transaction configuration entry.
8th argument for transaction configuration entry.
9th argument for transaction configuration entry.
Set to 'Y'es if entry was manually edited (e.g. manual resolutuion of argument)
Allows to protect record from being overwritten by next run of GENTDTC
Condition to be used for decision, if the rule has to be executed.
Code | Text |
---|---|
= | Equal |
<> | Not Equal |
> | Greater than |
< | Less than |
0 | Is Empty |
9 | Not is Empty |
Type of arguments content.
Code | Text |
---|---|
CONST | Constant Value |
FLD | Field |
If not empty, the corresponding rule in the source is ignored. i.e. diary entry defined in BCTAME.diasav is not created.