Every limit modification of the used amounts is kept in this table.
For limit modifications that are subject to release, the release status is kept additionally in separate LSS
entries, that are stored for every LSL of the owning LSR.
This is necessary in order to be able to handle the release for each limit node separately.
When the last LSS entry is released, the LSM entry will be released automatically.
If any LSS entry is rejected, every LSS entry will automatically be rejected and the LSM is rejected as well.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID Limit Modification | Text | 8 | 1 | Edit | Yes | Public | ||
| LSRINR | Owning Limit Request | Text | 8 | 1 | Edit | Yes | Public | ||
| TRNINR | Originating Transaction | Text | 8 | 1 | Edit | Yes | Public | ||
| CBEINR | Originating CBE Entry | Text | 8 | 1 | Edit | Yes | Public | ||
| LSMFLG | Release Status | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| MATDAT | Maturity of the Limit Usage | Date | 12 | 0 | Date | Yes | Public | ||
| CUR | Currency | Text | 3 | 1 | Edit | Yes | Public | CURTXT | |
| AMT | Amount | Numeric | 18 | 3 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| LSM_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 LSM. 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.
Refers to the entry of the limit request in Table LSR
INR of the transaction the Limit Amendment was triggered from
INR of CBE entry, this entry belongs to
This flag describes the overall acceptance status of this limit modification. The result of the last status check is stored in this field. Initially the status is set to blank and after all limits are checked, the result of that check is written back into the entry. If no acceptance is required, the status might be set to 'O', which is logically equivalent to 'Finally accepted'. The result of a status check might be: A = Finally accepted R = Finally rejected N = Not yet decided
This describes if, and how, changes made to the limit have been accepted. The field records the result of the last status check. Initially, the field is blank and after all limits have been checked, the results are written into the entry. If no acceptance is required, the status is 'O', the logical equivalent to 'Finally accepted'. Possible results are: A = Finally accepted R = Finally rejected N = Not yet decided
| Code | Text |
|---|---|
| A | Accepted |
| R | Rejected |
| N | Not yet decided |
| O | Outbooking |
| P | Prelimin. Outb. |
This field holds an optional maturity date for the limit modification. This value might be used to check when limits having a set expiry date are used. Modifications entries with a maturity exceeding the defined expiry will not automatically be accepted.
This field holds an optional maturity date for the limit modification. This value might be used to check when limits having a set expiry date are used. Modifications entries with a maturity exceeding the defined expiry will not automatically be accepted.
Currency of the Limit booking
The amount has to be logically inverted if the LSMFLG holds an 'O', as in that case the amount describes the outbooking amount.
If the Release Status field contains an 'O', the amount is to be inverted as in that case the amount describes the outbooking amount.