For every object where there is a limit, the limit static data is kept in this
table. The identification of the object is implemented in the fields with name starting with LSN. In further documentation this entry is named as limit node. The limit utilization is stored in associated LSA entries.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of Limit Balance | Text | 8 | 1 | Edit | Yes | Public | ||
| LSN | LSN - Type of Node | Text | 6 | 1 | Edit | Yes | Public | Embedded | |
| LSNTYP1 | Type of Level 1 Object | Text | 6 | 1 | Edit | Yes | Public | ||
| LSNINR1 | INR (or Code/Key) of Level 1 Object | Text | 8 | 1 | Edit | Yes | Public | ||
| LSNTYP2 | Type of Level 2 Object | Text | 6 | 1 | Edit | Yes | Public | ||
| LSNINR2 | INR (or Code/Key) of Level 2 Object | Text | 8 | 1 | Edit | Yes | Public | ||
| LSNTYP3 | Type of Level 3 Object | Text | 6 | 1 | Edit | Yes | Public | ||
| LSNINR3 | INR (or Code/Key) of Level 3 Object | Text | 8 | 1 | Edit | Yes | Public | ||
| LSNTYP4 | Type of Level 4 Object | Text | 6 | 1 | Edit | Yes | Public | ||
| LSNINR4 | INR (or Code/Key) of Level 4 Object | Text | 8 | 1 | Edit | Yes | Public | ||
| CUR | Currency | Text | 3 | 1 | Edit | Yes | Public | CURTXT | |
| AMT | Limit Amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
| LSS | Status of Limit | Text | 8 | 1 | Edit | Yes | Public | Embedded | |
| EXPDAT | Expiry Date of the Limit | Date | 12 | 0 | Date | Yes | Public | ||
| NONREVFLG | Flag to Mark Non-revolving Limits | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| LSNTYP5 | Type of Level 5 Object | Text | 6 | 1 | Edit | Yes | Public | ||
| LSNINR5 | INR (or Code/Key) of Level 5 Object | Text | 8 | 1 | Edit | Yes | Public | ||
| EXTKEY | External Key | Text | 42 | 1 | Edit | Yes | Public | ||
| NAM | Name | Text | 48 | 1 | Edit | Yes | Public | ||
| SEQ | Sequence for multiple Limits for one Business Sector | Numeric | 3 | 0 | Edit | Yes | Public | ||
| VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
| ETGEXTKEY | Entity Group of Limit System Balance | Text | 8 | 1 | Edit | Yes | Public | ||
| GETFLDNRM | Field holding the normalized search fields | Text | 100 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| LSB_ETGEXTKEY | ETGEXTKEY | |
| LSB_EXTKEY | EXTKEY | |
| LSB_INR | INR | Unique |
| LSB_LSN | LSN, LSNTYP1, LSNINR1, LSNTYP2, LSNINR2, LSNTYP3, LSNINR3, LSNTYP4, LSNINR4, LSNTYP5, LSNINR5 |
/
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 LSB. The field INR is used to maintain links from other tables to 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.
Type of limit node. This type usually determines the structure of instance IDs that are used to set up the identification of the limit node.
This type of node usually determines the structure of instance IDs used to identify the limit node.
| Code | Text |
|---|---|
| CTY | Liability per Country |
| HEQ | Liability per Headquarter |
| PTY | Liability per Party |
| PSB | Liability per Pairing Buyer/Supplier |
| FCL | Liability per Party/Facility |
| BUS | Liability per Party/Facility/Bus. Sector |
Type identification of the LSNINR1 field. This is usually, like an OBJTYP, the name of the associated table. It can also be the field type, if the field LSNINR1 holds a field content.
This identifies the type of Level 1 object. This is usually the name of the associated table. It can also be a field type, if the INR of the object contains a field content.
This field holds the identification as specified by LSNTYP1. This might be an INR of the table identified by LSNTYP1 or a field content, if a code is used.
This field contains the identification code specified by the Type of Level 1 Object field. This might be the identification number of a table, or field content, if a code is used.
Type identification of the LSNINR2 field. This is usually, like an OBJTYP, the name of the associated table. It can also be the field type, if the field LSNINR2 holds a field content.
This identifies the type of Level 2 object. This is usually the name of the associated table. It can also be a field type, if the INR of the object contains a field content.
This field holds the identification as specified by LSNTYP2. This might be an INR of the table identified by LSNTYP2 or a field content if a code is used.
This field contains the identification code specified by the Type of Level 2 Object field. This might be an identification number of a table, or field content, if a code is used.
Type identification of the LSNINR3 field. This is usually, like an OBJTYP, the name of the associated table. It can also be the field type, if the field LSNINR3 holds a field content.
This identifies the type of Level 3 object. This is usually the name of the associated table. It can also be a field type, if the INR of the object contains a field content.
This field holds the identification as specified by LSNTYP3. This might be an INR of the table identified by LSNTYP3 or a field content if a code is used.
This field contains the identification coded specified by the Type of Level 3 Object field. This might be an identification number of a table, or field content, if a code is used.
Type identification of the LSNINR4 field. This is usually, like an OBJTYP, the name of the associated table. It can also be the field type, if the field LSNINR4 holds a field content.
This identifies the type of Level 4 object. This is usually the name of the associated table. It can also be a field type, if the INR of the object contains a field content.
This field holds the identification as specified by LSNTYP4. This might be an INR of the table identified by LSNTYP4 or a field content if a code is used.
This field contains the identification codce specified by the Type of Level 4 Object field. This might be an identification number of a table, or field content, if a code is used.
Currency of the defined limit.
Currency of the defined limit.
Defined limit amount up to which requests might use this limit node.
The field defines the amount up to which requests might use this limit node.
Status to control the possibility of using the limit node. 'B' - A blocked limit node can not be used to draw limits. 'U' - An unlimited limit node might be used without any limit checking. The node just keeps the balance. 'N' - A normal limit might be used, whenever there is enough unused limit amount. ' ' - A node marked with no limit blocks any usage as there is no limit defined. The amount fields might be zero and the currency is blank in this case.
Selection options to control the use of the limit node. 'B' - A blocked limit node cannot be used in transactions. 'U' - An unlimited limit node can be used without running limit checks. The node just maintains the balance. 'N' - A normal limit can be used whenever there are sufficient unutilized amounts. ' ' - A node marked with no limit blocks any usage as no limit has been defined. In this case, amount fields might be zero and the currency is blank.
| Code | Text |
|---|---|
| No Limit | |
| B | Blocked |
| N | Normal |
| U | Unlimited |
Limit requests after the expiry date are automatically rejected.
No expiry date is represented by NULLDATE.
Limit requests after the expiry date are automatically rejected.
No expiry date is represented by NULLDATE.
With this flag, limits might be marked as non-revolving. In this case, the release of a limit will keep the available amount instead of increasing it.
Blank content means a normal, thus revolving, limit. Any non-blank contents mark this limit as a non-revolving limit.
This flag is used to mark limits as non-revolving. In this case, the release of a limit will keep the available amount instead of increasing it.
Blank content means a normal, thus revolving, limit. If the field is empty, the limit is non-revolving.
| Code | Text |
|---|---|
| Revolving | |
| N | Nonrevolving |
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.
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.
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.
Type identification of the LSNINR5 field. This is usually, like an OBJTYP, the name of the associated table. It can also be the field type, if the field LSNINR5 holds a field content.
Type identification of the LSNINR5 field. This is usually, like an OBJTYP, the name of the associated table. It can also be the field type, if the field LSNINR5 holds a field content.
This field holds the identification as specified by LSNTYP5. This might be an INR of the table identified by LSNTYP5 or a field content if a code is used.
This field holds the identification as specified by LSNTYP5. This might be an INR of the table identified by LSNTYP5 or a field content if a code is used.
An unique limit key used for identification. It is a combination of party id, limit facility id followed by business sector and sequence
An unique limit key used for identification. It is a combination of party id, limit facility id followed by business sector and sequence
Specifies the limit name. It is a combination of business sector, sequence, limit facility id followed by party name.
Specifies the limit name. It is a combination of business sector, sequence, limit facility id followed by party name.
Sequence for multiple Limits for one Business Sector.
Sequence for multiple Limits for one Business Sector.
This field holds the version counter to keep track of the version history of an LSB 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.