ATC is the data table for the Application Transaction Configuration data.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of Application Transaction Configuration | Text | 8 | 1 | Edit | Yes | Public | ||
| TRN | Transaction ID | Text | 6 | 1 | 20 | Edit | Yes | Public | |
| TYP | Type | Text | 6 | 1 | Edit | Yes | Public | Embedded | |
| VAR | Variant ID | Text | 3 | 1 | Edit | Yes | Public | ||
| IGNFLG | Suppress Default from Transaction | Text | 1 | 1 | Edit | Yes | Public | ||
| COD | Coded reason | Text | 12 | 1 | Edit | Yes | Public | ||
| ARG1 | Argument 1 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG1TYP | Type for Argument 1 | Text | 6 | 1 | Edit | Yes | Public | ||
| ARG2 | Argument 2 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG2TYP | Type for Argument 2 | Text | 6 | 1 | Edit | Yes | Public | ||
| ARG3 | Argument 3 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG3TYP | Type for Argument 3 | Text | 6 | 1 | Edit | Yes | Public | ||
| ARG4 | Argument 4 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG4TYP | Type for Argument 4 | Text | 6 | 1 | Edit | Yes | Public | ||
| ARG5 | Argument 5 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG5TYP | Type for Argument 5 | Text | 6 | 1 | Edit | Yes | Public | ||
| ARG6 | Argument 6 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG6TYP | Type for Argument 6 | Text | 6 | 1 | Edit | Yes | Public | ||
| ARG7 | Argument 7 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG7TYP | Type for Argument 7 | Text | 6 | 1 | Edit | Yes | Public | ||
| ARG8 | Argument 8 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG8TYP | Type for Argument 8 | Text | 6 | 1 | Edit | Yes | Public | ||
| ARG9 | Argument 9 | Text | 75 | 1 | Edit | Yes | Public | ||
| ARG9TYP | Type for Argument 9 | Text | 6 | 1 | Edit | Yes | Public | ||
| CND | Condition | Text | 3 | 1 | Edit | Yes | Public | Embedded | |
| CNDSTM | Condition | Stream | 3 | 1 | Source | Yes | Public | ||
| CNDFLD1TYP | Type for Condition Field 1 | Text | 6 | 1 | Edit | Yes | Public | Embedded | |
| CNDFLD1 | Condition Field 1 | Text | 75 | 1 | 20 | Unknown | Yes | Public | |
| CNDFLD2TYP | Type for Condition Field 2 | Text | 6 | 1 | Edit | Yes | Public | Embedded | |
| CNDFLD2 | Condition Field 2 | Text | 75 | 1 | 20 | Unknown | Yes | Public | |
| VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
| ETGEXTKEY | Entity Group of ATC | Text | 8 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| ATC_ETGEXTKEY | ETGEXTKEY | |
| ATC_INR | INR | Unique |
| ATC_KEY | TRN, TYP, COD, VAR |
/
INR
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 ATC. The field INR is used to maintain links from other tables into this table.
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 to keep track of the version history of a ATC entry. The individual versions are controlled by entries in the SLG table.
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 ATC entry is valid.
The name of the business transaction for which this ATC entry is valid.
Class of configuration definition. Each class needs special application logic in business transactions.
Class of configuration definition. Each class needs a special application logic in business transactions.
| Code | Text |
|---|---|
| DIASAV | Diary |
| FEESAV | Fee |
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.
This is the banking definition of the reason of the diary entry.This code describes the user defined resubmission code which might be used for selection of diary entries. The associated codetable is modifiable by the bank and can be adopted to the needs of the specific installation.
Unique identifier used to classify this entry in the transaction. The content needs to match the requirements of the parameter class as identified in the Type field.
If - depending on an additional condition - one of several variants of definitions for one ID (COD) of one type (TYP) for one transaction (TRN) exists, this field allows to identify these different variants.
If - depending on an additional condition - several variants of definitions for one ID of one type for one transaction exist, this field allows to identify these different variants.
First argument for transaction configuration entry.
First argument for the transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
Second argument for transaction configuration entry.
Second argument for the transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
Third argument for transaction configuration entry.
Third argument for the transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
4rth argument for transaction configuration entry.
Fourth argument for the transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
5th argument for transaction configuration entry.
Fifth argument for the transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
6th argument for transaction configuration entry.
6th argument for transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
7nth argument for transaction configuration entry.
Seventh argument for the transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
8th argument for transaction configuration entry.
Eighth argument for the transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
9th argument for transaction configuration entry.
Ninth argument for the transaction configuration entry.
Type of arguments content. Normally field or constant. Might be a special function as i.e. DateAddW in rare cases.
This describes a type of content. This is normally a field or a constant, but in rare cases might also be a special function.
If not empty, the corresponding rule in the source is ignored. i.e. diary entry defined in BCTAME.diasav is not created.
If not empty, the corresponding rule in the source is ignored.
Condition to be used for decision, if the rule has to be executed.
A condition that determines whether the rule has to be executed.
| Code | Text |
|---|---|
| = | Equal |
| <> | Not Equal |
| > | Greater than |
| < | Less than |
| 0 | Is Empty |
| 9 | Not is Empty |
| F | Free Formula |
| U | Unconditional |
Condition as Free formula. Free conditions can be entered in this field. The syntax of these conditions is reviewed
Free conditions can be entered in this field. The syntax of these conditions is reviewed.
Type of arguments content.
This field identifies the type of content for the argument.
| Code | Text |
|---|---|
| CONST | Constant Value |
| FLD | Field |
First field to be used in condition.
The first field used in the condition.
Type of arguments content.
This field identifies the type of content for the argument.
| Code | Text |
|---|---|
| CONST | Constant Value |
| FLD | Field |
Second field to be used in condition.
The second field used in the condition.
This table is defined on entity group level with separate entries for each entity group. This field holds the EXTKEY of the entity group which is the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the entity group of the currently active entity are visible to the user.
This field holds the external key of the owning entity group to identify the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity group are visible to the user.