User Tools
Add this page to your book 
Remove this page from your book 
Manage book (
Help Table of Contents
ATP - Application Transaction Profile
Module ATP
Datafields
| Name | Helptext Description | Data Type | Len | Codetable |
|---|---|---|---|---|
| INR | Internal Unique ID | Text | 8 | |
| COD | Transaction ID | Text | 6 | ATPTXT |
| ROUFLG | Routing Allowed | Text | 1 | |
| BUSTRNFLG | Business Transaction Flag | Text | 1 | |
| BUS | Business Sector | Text | 2 | BUSTXT |
| CONCREFLG | Allocate New Contract | Text | 1 | Embedded |
| DTAFLG | Need Transferred Data to Execute | Text | 1 | |
| SEPFLG | Temporary Settlement Allowed | Text | 1 | |
| JOBFLG | Job Operation Allowed | Text | 1 | |
| SUBFLG | Subcontract-creating Transaction | Text | 1 | |
| LNKOBJ | Associated Object Type | Text | 6 | |
| CCSTYP | Compliance Check Type | Text | 3 | Embedded |
| VER | Version | Text | 4 | |
| RELAMT | Relevant Amount for Release | Text | 1 | Embedded |
| RELTYP | Type of release | Text | 1 | Embedded |
| GETFLDNRM | Field holding the normalized search fields. | Text | 10 |
Datafield Description and Properties
Datafield INR Internal Unique ID
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.
Datafield COD Transaction ID
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).
Datafield ROUFLG Routing Allowed
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.
Datafield BUS Business Sector
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.
Datafield CONCREFLG Allocate New Contract
When set to a non-empty value, this flag allows the transaction to create a new contract.
Codetable
| Code | Text |
|---|---|
| Not creating Contracts | |
| X | Allocates Contract |
Datafield DTAFLG Need Transferred Data to Execute
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.
Datafield SEPFLG Temporary Settlement Allowed
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.
Datafield JOBFLG Job Operation Allowed
If this flag is set to a non-empty value it marks this transaction as open for use by the job control system.
Datafield SUBFLG Subcontract-creating Transaction
If this flag is set to a non-empty value it marks this transaction as a transaction capable of creating subcontracts.
Datafield LNKOBJ Associated Object Type
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.
Datafield CCSTYP Compliance Check Type
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.
Codetable
| Code | Text |
|---|---|
| None | |
| SMH | per Message |
| TRN | per Transaction |
Datafield VER Version
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.
Datafield BUSTRNFLG Business Transaction Flag
If this flag is set to a non-empty value it marks this transaction as being a business transaction.
Datafield RELAMT Relevant Amount for Release
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.
Codetable
| 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 |
Datafield RELTYP Type of release
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.
Codetable
| Code | Text |
|---|---|
| 1 | Source in Transaction |
| 2 | Signature required |
| 3 | No Release required |
Datafield GETFLDNRM Field holding the normalized search fields.
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.
