CRO 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 | |
CUR | Currency | Text | 3 | 1 | Edit | Yes | Public | CURTXT | |
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 | ||
VALDAY | Default Valuta | Numeric | 2 | 0 | Edit | Yes | Public | ||
VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
FEECOD | additional Fee | Text | 6 | 1 | Edit | Yes | Public | ||
MAXCHK | Max. number of Checks per remittance | Numeric | 4 | 0 | Edit | Yes | Public | ||
ETGEXTKEY | Entity Group of Check Routing Entry | Text | 8 | 1 | Edit | Yes | Public |
Name | Fields | Properties |
---|---|---|
CRO_CHKROU | CUR, COLCTY, COD | Unique |
CRO_CHKROU | CUR, COLCTY, COD, ETGEXTKEY | Unique |
CRO_COD | COD | |
CRO_ETGEXTKEY | ETGEXTKEY | |
CRO_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 CRO. 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 a Check Routing can be defined.
Code | Text |
---|---|
D | Debit notes |
O | Checks to order |
T | Traveler Checks |
This field contains the currency of the presented payment document.
This field contains the currency code (ISO) of the payment documents and is required for defining a check routing.
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 for definition of a check routing.
This field contains the party INR, used as collecting bank in the business sector check handling (CH).
This field contains the party INR of the collecting bank in the business sector check handling (CH). A check routing has been defined for this party.
Technical INR of the Default Account
Technical INR of the Default Account
This field contains the number of future working days for which the Collecting Bank promised to pay the equivalent of remitted payment documents resp. authorized the sender of the payment documents to debit their account. The number of days entered will be used within the check-transactions to calculate future value dates.
This field contains the number of future working days for which the Collecting Bank promised to pay the equivalent of remitted payment documents resp. authorized the sender of the payment documents to debit their account. The number of days entered will be used within the check-transactions to calculate future value dates.
This field holds the version counter to keep track of the version history of a CRO 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.
This field is for foreign fees, i.e. Collecting Bank's fee. This fee will be charged to the Remitter of checks and credited to Collecting Bank. The credit of the fee-amount normally will be done on a monthly base. This feecod will be added in CHTOPN.
This field is for foreign fees, i.e. Collecting Bank's fee. This fee will be charged to the Remitter of checks and credited to the Collecting Bank when the check presentation contract is opened.
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.
This field defines the maximum number of checks allowed for the selected check route. If the number of checks exceeds the maximum number of checks, the user will receive an error message when processing the check presentation. The check remittance has to be sent before additional check presentations can be entered for the selected check route.