This table holds all calculated fee entries processed in the
settlement. Depending on the processing flags these entries need to
be settled in the future or are already settled.
Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
---|---|---|---|---|---|---|---|---|---|
INR | Internal Unique ID | Text | 8 | 1 | Edit | Yes | Public | ||
FEECOD | Fee Code | Text | 6 | 1 | Edit | Yes | Public | ||
OBJTYP | Contract Type | Text | 6 | 1 | Edit | Yes | Public | CBOTXT | |
OBJINR | INR of Contract | Text | 8 | 1 | Edit | Yes | Public | ||
RELOBJTYP | Relevant Contract Type | Text | 6 | 1 | Edit | Yes | Public | ||
RELOBJINR | Relevant Contract INR | Text | 8 | 1 | Edit | Yes | Public | ||
EXTKEY | External Visible Name (Created from Transaction, Feecode Line) | Text | 20 | 1 | Edit | Yes | Public | ||
NAM | Text of Fee (from and to FEETXT) | Text | 100 | 1 | Edit | Yes | Public | ||
RELCUR | Currency of Relevant Amount | Text | 3 | 1 | Edit | Yes | Public | ||
RELAMT | Relevant Amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
DAT1 | Date 1 | Date | 12 | 0 | Date | Yes | Public | ||
DAT2 | Date 2 | Date | 12 | 0 | Date | Yes | Public | ||
MODFLG | Modified | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
UNT | Units | Numeric | 5 | 0 | Edit | Yes | Public | ||
UNTAMT | Rate Amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
RATCAL | Rate Calculation | Numeric | 14 | 6 | Edit | Yes | Public | ||
RAT | Rate | Numeric | 14 | 6 | Edit | Yes | Public | ||
MINMAXFLG | Minimum or Maximum Used | Text | 1 | 1 | Edit | Yes | Public | ||
CUR | Fee Currency | Text | 3 | 1 | Edit | Yes | Public | ||
AMT | Fee Amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
XRFCUR | Currency of Converted Amount (Usually SYSCUR, Optional) | Text | 3 | 1 | Edit | Yes | Public | ||
XRFAMT | Converted Amount (in XRFCUR, Optional) | Numeric | 18 | 3 | Edit | Yes | Public | ||
FEEACC | Profit Account for Fee | Text | 34 | 1 | Edit | Yes | Public | ||
INFDETSTM | Fee Calculation Details | Block | 80 | 999 | Block | Yes | Public | ||
PTYINR | INR of Party Paying | Text | 8 | 1 | Edit | Yes | Public | ||
SRCTRNINR | Transaction Creating or Modifying the Entry | Text | 8 | 1 | Edit | Yes | Public | ||
SRCDAT | Date of Creation | Date | 12 | 0 | Date | Yes | Public | ||
RPLTRNINR | Transaction which Replaced this Entry | Text | 8 | 1 | Edit | Yes | Public | ||
RPLDAT | Date Replaced | Date | 12 | 0 | Date | Yes | Public | ||
DONTRNINR | Transaction Settling the Fee | Text | 8 | 1 | Edit | Yes | Public | ||
DONDAT | Date Done | Date | 12 | 0 | Date | Yes | Public | ||
ADVTRNINR | Transaction Advising the Fee | Text | 8 | 1 | Edit | Yes | Public | ||
PREDBTFEPINR | Pool entry pre debited | Text | 8 | 1 | Edit | Yes | Public | ||
ADVDAT | Date Advised | Date | 12 | 0 | Date | Yes | Public | ||
ACRINR | INR of Accruing Control Record | Text | 8 | 1 | Edit | Yes | Public | ||
SEPINR | INR of Associated Temporary Settlement | Text | 8 | 1 | Edit | Yes | Public | ||
ROL | Role | Text | 3 | 1 | Edit | Yes | Public | ROLALL | |
RELAMTMAN | Manual Set Relevant Amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
FECUSE | condition used | Stream | 1 | 0 | Source | Yes | Public | ||
ETYEXTKEY | Entity holding Contract | Text | 8 | 1 | Edit | Yes | Public |
Name | Fields | Properties |
---|---|---|
FEP_ACR | ACRINR | |
FEP_DONTRNINR | DONTRNINR | |
FEP_ETYEXTKEY | ETYEXTKEY | |
FEP_INR | INR | Unique |
FEP_OBJIDX | OBJTYP, OBJINR | |
FEP_PTYINR | PTYINR | |
FEP_RELOBJIDX | RELOBJTYP, RELOBJINR | |
FEP_RPLTRNINR | RPLTRNINR | |
FEP_SEPDONRPL | SEPINR, DONTRNINR, RPLTRNINR | |
FEP_SRCTRNINR | SRCTRNINR |
/
INR
INR to uniquely identify a database entry.
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.
Code of the fee used to create this entry.
Code of the fee used to create this entry.
Type of contract the fee is associated to. This contract is a real contract (e.g. LID, BCD, BOD, GID, GCD) and no pseudo subcontract like PTS. This contract is used to select the relevant entries from pool.
Type of contract the fee is associated to. This contract is a real contract (e.g. LID, BCD, BOD, GID, GCD) and no pseudo subcontract such as PTS. This contract is used to select the relevant entries from the fee pool.
INR of the contract the fee is associated to. The table to be used can be taken from OBJTYP. This contract is used to select the relevant entries from pool.
Identification number of the contract the fee is associated to. This contract is used to select the relevant entries from the fee pool.
Type of relevant contract used for fee calculation (PTE for commissions from liability. Otherwise equal OBJTYP).
Type of relevant contract used to calculate the fee (PTE for commission from liability. Otherwise this is the same as the Object Type.
INR of relevant contract used for fee calculation (PTE\INR for commissions from liability. Otherwise equal OBJINR).
Identification number of the relevant contract used to calculate the fee.
Freetext field currently created from the fee code, the creating TRNINR and the running counter. This contents may be changed in the future to hold other freetext information and should not be used to technically identify a fee pool entry.
Free text field currently created from the fee code, the ID of the creating transaction and the running counter. This contents may be changed in the future to hold other free text information and should not be used to technically identify a fee pool entry.
Text of the fee as it was used in the settlement.
Text of the fee as used in the settlement.
Currency of the amount which was relevant for the calculation of the fee.
Currency of the amount used in the calculation of the fee.
Amount which was relevant for the calculation of the fee. The associated currency is in RELCUR.
Amount which was relevant for the calculation of the fee.
For fee calculations which are based on dates this is the date or the first date for calculations with two dates.
This indicates either the date for calculating fees that are based on dates or the first date for calculations that include two dates.
For fee calculations which are based on two dates this field holds the second date.
CAUTION: DAT2 holds the to date, not the day following the to date
This indicates the second of two dates used to calculate fees.
N.B.: Date 2 date identifies the 'to' date, not the day following the 'to' date.
Flags to identify which field of the different relevant fields was modified. The relevant codetable is in SETFEL:MODFLG.
Flags to identify which of the different relevant fields have been modified.
Code | Text |
---|---|
x | Rate changed |
r | Unmodified |
c | Code changed |
a | Amount changed |
u | Units changed |
d | Date changed |
Number of units for the fee calculation. The calculated amount is multiplied by the number of units. Thus setting the number of units to zero creates an empty result and setting the number of units to a negative value creates a negative result.
This field indicates the number of units used to calculate the fee. The amount calculated is multiplied by the number of units. Setting the number of units to zero generates a result of zero and setting the number of units to a negative value creates a negative result.
In calculations where an amount is required, this field is taken as the amount per unit.
In calculations where an amount is required, this field is taken as the amount per unit.
Rate used to calculate the fee.
Rate used to calculate the fee.
Obsolete field. Will be removed in future versions.
Obsolete field. Will be removed in future versions.
A flag that identifies whether the calculated amount was replaced by the minimum (= '<') or the maximum (= '>') amount. Otherwise the flag holds a blank value.
A flag that identifies whether the amount calculated was replaced by the minimum (= '<') or the maximum (= '>') amount. Otherwise, the field contains a blank value.
Currency of the fee pool entry.
Currency of the fee pool entry.
Amount of the fee pool entry.
Amount of the fee pool entry.
Currency of the converted value. Usually the current system currency.
Currency of the converted value. Usually the current system currency.
Converted amount. The relevant currency is XRFCUR.
Converted amount.
This is the profit account as taken from the fee definition.
This is the profit account as taken from the fee definition.
Internal details of the calculation in the creating transaction (taken from and set to INFDETSTM of DETTAB). These details are converted according to the current user interface language into the visible longtext.
Internal details of the calculation set in the creating transaction These details are converted into visible long text based on the current user language.
This INR identifies the party paying this fee.
This identification number identifies the party paying this fee.
INR of the transaction which created this pool entry. If an entry is modified, the original entry is marked as a replaced entry by setting the fields RPLTRNINR and RPLDAT and a newly created entry is stored in the database holding the modified data of the original entry.
Identification number of the transaction which created this pool entry.
Date when this entry was created (or modified if this entry is a modified copy). The date is relevant only if SRCTRNINR is set. Otherwise it should be a nulldate.
Date when this entry was created (or modified if this entry is a modified copy).
INR of the transaction which replaced this entry by a modified copy. All entries where the RPLTRNINR are filled with a non-blank value are kept for history reasons and do not represent a real fee. All this fee pool entries are modified. The modified data is stored in a separate new entry.
Identification number of the transaction which replaced this entry by a modified copy. All entries where the Fee Entry Replaced field is filled with a non-empty value are retained for historical reasons and do not represent a real fee. All these fee pool entries are modified. The modified data is stored in a separate new entry.
Date when this fee pool entry was replaced. The date is relevant only if RPLTRNINR is set. Otherwise it should be a nulldate.
Date when this fee pool entry was replaced. The date is relevant only if the Fee Entry Replaced field has been set. Otherwise this should be a 'nulldate'.
INR of the transaction where this fee was finally settled.
Identification number of the transaction where this fee was finally settled.
Date when the fee was finally settled. The date is relevant only if DONTRNINR is set. Otherwise it should be a nulldate.
Date when the fee was finally settled. The date is relevant only if the 'Transaction Settling the Fee' field has been filled in. Otherwise this should be set to null.
INR of the transaction where this fee was advised.
Identification number of the transaction where this fee was advised.
Date when the advising took place. The date is relevant only if ADVTRNINR is set. Otherwise it should be a nulldate.
This indicates when the advising took place. The date is relevant only if the 'Transaction Advising the Fee' field has been filled in. Otherwise, this should be set to null.
The INR of the accrual control entry in the table ACR is stored here.
The identification number of the accrual control entry is stored here.
If the pool entry is advised in a temporary settlement, the INR of this temporary settlement is stored here. If SEPINR is empty this means, that this entry has not been advised in a temporary settlement yet.
If the pool entry is advised in a temporary settlement, the identification number of this temporary settlement is stored here. If this field is empty this means that this entry has not yet been advised in a temporary settlement.
Corresponding role to fee stored in pool.
Amount which was relevant for the calculation of the fee. The associated currency is in RELCUR.
Amount which was relevant for the calculation of the fee. The associated currency is stored in 'Currency of Relevant Amount'.
Internal field for used fee conditions
Holds the INR of the original pool entry if this entry is a pre debit entry
This table is defined on entity level with separate entries for each entity. This field holds the EXTKEY of the owning entity 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 are visible to the user.
This field holds the external key of the owning entity 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 are visible to the user.