Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
---|---|---|---|---|---|---|---|---|---|
INR | Internal Unique ID | Text | 8 | 1 | Edit | Yes | Public | ||
OBJTYP | Object Type of Owner (ETG, ETY,..) | Text | 6 | 1 | Edit | Yes | Public | ||
OBJINR | INR of Owner | Text | 8 | 1 | Edit | Yes | Public | ||
OBJKEY | Key of Owner (i.e. ETG\EXTKEY) | Text | 8 | 1 | Edit | Yes | Public | ||
BUS | Financing Product / Business Sector | Text | 2 | 1 | 30 | Edit | Yes | Public | BUSTXT |
FINTYP | Type of Financing | Text | 3 | 1 | Edit | Yes | Public | <fixed-length> | |
GRADAY | Grace Days | Numeric | 3 | 0 | Edit | Yes | Public | ||
PDUDAY | Past Due Days | Numeric | 3 | 0 | Edit | Yes | Public | ||
NPFDAY | Non Performance Days | Numeric | 3 | 0 | Edit | Yes | Public | ||
WOFDAY | Write Off Days | Numeric | 3 | 0 | Edit | Yes | Public | ||
INTCAPFLG | Interest Capitalized | Text | 1 | 1 | Edit | Yes | Public | ||
VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public |
Name | Fields | Properties |
---|---|---|
PDU_BUS | BUS, FINTYP | |
PDU_INR | INR | Unique |
PDU_KEY | OBJKEY, OBJTYP | |
PDU_OBJ | OBJTYP, OBJINR |
/
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 PDU. 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.
Type of object the config. entry refers to. Usually this is the table the object is associated to. Used values are ETG Entity Group ETY Entity
INR of the object within the table, defined in OBJTYP.
This field holds the external key to identify an Entity Group.
Code of the business sector to identify an application transaction which is associated to a business sector.
For Past due Parameter are only BP and TR used currently.
This field contains the type of financing.
Static value fields for defining Past Due stages.
Status to be calculated from the no of days defined here with respect to MATDAT (maturity date).
Example: If maturity date is 01Jun2021 and Grace is defined as 2 days, 02Jun and 03Jun will be in Grace stage. If Past Due is defined as 30 days. From 04Jun to 02Jul will be Past Due stage.
If no grace days are given, 02Jun to 30Jun will be Past due stage. Each stage starts when previous stage days end.
Static value fields for defining Past Due stages
Static value fields for defining Past Due stages
Static value fields for defining Past Due stages
If selected, once contract reaches Past due stage, pending TRCX/BPCX liability commission to be added to the Liability amount.
This field holds the version counter to keep track of the version history of an MLI 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.