CRI is the data table for the Check Routing data.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of Check Routing | Text | 8 | 1 | Edit | Yes | Public | ||
| COD | Type of payment document | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| COLCTY | Collecting Bank's Country Code | Text | 2 | 1 | Edit | Yes | Public | CTYTXT | |
| COLPTAINR | Collecting Bank's Address | Text | 8 | 1 | Edit | Yes | Public | ||
| ACTINR | INR of account to be debited | Text | 8 | 1 | Edit | Yes | Public | ||
| VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
| BNKGRP | Bank Group Identifier | Text | 1 | 1 | Edit | Yes | Public | BNKGRP | |
| BLZBEG | Bank Code Number Begin | Numeric | 3 | 0 | Edit | Yes | Public | ||
| BLZEND | Bank Code Number End | Numeric | 3 | 0 | Edit | Yes | Public | ||
| ETGEXTKEY | Entity Group of Check Routing Entry | Text | 8 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| CRI_CHKROU | COLCTY, COD | |
| CRI_CHKROU | COLCTY, COD, ETGEXTKEY | |
| CRI_COD | COD | |
| CRI_ETGEXTKEY | ETGEXTKEY | |
| CRI_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 CRI. 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 contains the type of payment document and holds the external used code to identify a Check Routing. This code might be decoded into a language dependent longtext in embedded codetable.
This field contains the type of payment document for which an import check routing can be defined.
| Code | Text |
|---|---|
| D | Debit notes |
| O | Checks to order |
| T | Traveler Checks |
This field contains the country code of the Collecting Bank. It will be used to preload the Collecting Bank in combination with the type and the currency of the presented payment documents.
This field contains the country code of the collecting bank. It is used to preload the collecting bank in combination with the type and the currency of the presented payment documents.
This field contains the party INR, used as collecting bank in the business sector check handling (CH).
This field contains the party number (INR) of the collecting bank in the business sector check handling. A check routing for import checks has been defined for this party.
Technical INR of the Default Account
Technical INR of the Default Account
This field holds the version counter to keep track of the version history of a CRI 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.
The Bank Group Identifier corresponds with the 4th digit of th bank identification code or the 8th digit of the german IBAN
This field contains the first three digits of the German Bank Code Identifier (BLZ) and is used to define a check routing for the selected Bank Code range.
This field contains the first three digits of the German Bank Code Identifier (BLZ) and is used to define a check routing for the selected Bank Code range.
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.