ATP is the data table for the application transaction profile data.
This table holds configuration information about all transactions of
the installation.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of Application Transaction | Text | 8 | 1 | Edit | Yes | Public | ||
| COD | Transaction ID | Text | 6 | 1 | 40 | Unknown | Yes | Public | ATPTXT |
| ROUFLG | Routing Allowed | Text | 1 | 1 | Edit | Yes | Public | ||
| BUSTRNFLG | Business-Transaction-Flag | Text | 1 | 1 | Edit | Yes | Public | ||
| BUS | Business Sector | Text | 2 | 1 | 30 | Edit | Yes | Public | BUSTXT |
| CONCREFLG | Allocate New Contract | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| DTAFLG | Need Passed Data to Execute | Text | 1 | 1 | Edit | Yes | Public | ||
| SEPFLG | Temporary Settlement Allowed | Text | 1 | 1 | Edit | Yes | Public | ||
| JOBFLG | Job Operation Allowed | Text | 1 | 1 | Edit | Yes | Public | ||
| SUBFLG | Subcontract-creating Transaction | Text | 1 | 1 | Edit | Yes | Public | ||
| LNKOBJ | Associated Object Type | Text | 6 | 1 | Edit | Yes | Public | ||
| CCSTYP | Compliance Check Type | Text | 3 | 1 | Edit | Yes | Public | Embedded | |
| VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
| RELAMT | Relevant Amount for Release | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| RELTYP | Method of Release | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| GETFLDNRM | Field holding the normalized search fields | Text | 10 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| ATP_COD | COD | Unique |
| ATP_INR | INR | Unique |
/
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 ATP. 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.
Technical short name of the application transaction. This name is made up of the base name of the name of the file of the transaction file(s).
Technical short name of the application transaction. This name is made up of the base name of the name of the file of the transaction file(s).
If this flag is set to a non-blank value it marks this transaction as being able to handle incoming messages.
If this checkbox is checked it marks this transaction as being able to handle the rerouting of incoming messages. If this checkbox is unchecked, an error message will be displayed when the user tries to reroute an incoming message to this transaction.
Code of the business sector to identify an application transaction which is associated to a business sector. In a business sector with subcontracts, this field is set to the main contract, even in transactions handling the subcontract. For non-business transactions this field is left blank.
The code of the business sector used to identify a transaction associated to a business sector. In a business sector with subcontracts, this field is set to the main contract, even in transactions handling the subcontract. For non-business transactions this field is left blank.
When set to non-blank, this flag marks that this transaction is able to create a new contract.
When set to a non-empty value, this flag allows the transaction to create a new contract.
| Code | Text |
|---|---|
| Not creating Contracts | |
| X | Allocates Contract |
If this flag is filled with a non-blank value, the transaction needs passed data to successfully execute. This flag marks transactions, which may not be launched directly from the office.
Caution: Even transactions which might be launched without passed data might optionally handle passed data.
If this flag contains a non-empty value, the transaction needs transferred data in order to be executed successfully. This flag marks transactions that may not be launched directly from the office.
N.B.: Even transactions that can be launched without transferred data have an option to handle transferred data.
If this flag is set to a non-blank value it marks this transaction as being able to handle temporary settlement.
Must be deleted if DOKA 5.06 SP2 is active
If this flag is set to a non-blank value it marks this transaction as being able to handle temporary settlement.
With Version 5.06 the correspondent field in ETP is used.
If this flag is set to a non-blank value it marks this transaction as being able to be used by the job control system. This implies, that this transaction might be started from the JOBTSK.
If this flag is set to a non-empty value it marks this transaction as open for use by the job control system.
If this flag is set to a non-blank value it marks this transaction is subcontract-creating transaction.
If this flag is set to a non-empty value it marks this transaction as a transaction capable of creating subcontracts.
The table ID the transaction is operating on is identified by the field. Entries of this type might be passed to the transaction. (Incoming message, or SPT or via SYSSTREAM)
In most business transactions this code is identical to the prefix of the MTABUT\REC instance. In Subcontract creating transactions this is the parent contract and not the MTABUT/REC contract (which is the subcontract).
The intention is to be able to have this code available without access to an absolute reference.
This field identifies the table ID the transaction is working on. Normally contracts of this type may be passed to a transaction.
The aim is to be able to have this code available without having to access an absolute reference.
This field is not needed in DOKA-NG any more as it is replaced by ETP\ccstyp. This field remains only to ease upgrading from DOKA 5 to DOKA-NG.
Any non-empty value triggers generation of compliance check by SRVCCS. Standard values are SMH Check all generated external Messages TRN Check contract/transaction data (generically generated from TRNDATA File).
If any customization is needed it has to be done in ETP\ccstyp.
Any non-empty value triggers generation of compliance check by SRVCCS. Standard values are SMH Check all generated external Messages TRN Check contract/transaction data (generically generated from TRNDATA File.
Other values can be added in customization.
| Code | Text |
|---|---|
| None | |
| SMH | per Message |
| TRN | per Transaction |
This field holds the version counter to keep track of the version history of an ATP 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.
If this flag is set to a non-blank value it marks this transaction as being a business-transaction. Only when filled the additional flags defining features of busines transactions might be defined.
If this flag is set to a non-empty value it marks this transaction as being a business transaction.
This field holds the relevant amount for release. It is not a sum, it is for example MAXAMT of transaction.
Must be deleted if SP2 is active
This field holds the relevant amount for release. It is not a sum, it is for example MAXAMT of transaction.
With Version 5.06 the correspondent field in ETP is used.
| Code | Text |
|---|---|
| M | Maximum Amount |
| O | Open Amount |
| N | Nominal Amount |
| A | Maximum Amount with additional Amount |
| P | Open Amount with additional Amount |
| C | Confirmation Amount |
| T | No Amount |
| S | Amount Settled |
| L | Liability Amount |
Method of release, which is used. 1 = Standardrule - Set_Wfs_Release of transaction is used 2 = Signature required - TRN\RELREQ is set to “A”
Must be deleted if SP2 is active
Type of release used: 1 = Standard rule - Set_Wfs_Release of transaction is used 2 = Signature required 3 = No release required
From version 5.06, the field by the same name is used in ETP.
| Code | Text |
|---|---|
| 1 | Source in Transaction |
| 2 | Signature required |
| 3 | No Release required |
Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.
Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.