This table holds all infotexts associated to the different table within the application.
Within multi-entity installations this table should be defined on entity level and thus might have different infotexts for the different entities / entity groups.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID | Text | 8 | 1 | Edit | Yes | Public | ||
| OBJTYP | Type of Associated Record | Text | 6 | 1 | Edit | Yes | Public | Embedded | |
| OBJINR | INR of Associated Record | Text | 8 | 1 | Edit | Yes | Public | ||
| SUBTYP | Subtype to enable multiple Infotexts per Object | Text | 3 | 1 | Edit | Yes | Public | Embedded | |
| SUBBUS | Business Sector | Text | 2 | 1 | Edit | Yes | Public | BUSTXT | |
| INFLEV | Infotext Level | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| INFTXT | Infotext | Stream | 60 | 1 | Source | Yes | Public | ||
| VER | Version | Text | 4 | 1 | Edit | Yes | Public | ||
| ETGEXTKEY | Entity Group of Infotext | Text | 8 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| OIT_ETGEXTKEY | ETGEXTKEY | |
| OIT_INR | INR | Unique |
| OIT_OBJIDX | 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 OIT. The field INR is used to maintain the standard technical links from other tables into this table (if required) and to support the standard database lock and access features of the application.
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 holds the table the associated object is stored in. The codetable holds the name to be used to identify the type of object in a heading.
This field holds the name of the table the associated object is stored in.
| Code | Text |
|---|---|
| PTY | Party |
| ACT | Account |
| LED | Export L/C |
| LID | Import L/C |
| CTY | Country |
| GID | Guarantee |
| RMD | Reimbursement |
| BCD | Import Collection |
| BOD | Export Collection |
| BPD | Advance |
| CPD | Clean Payment |
| LTD | Transferable L/C |
| MCD | Manual Contract |
| PAD | Participation |
| TRD | Loan |
| FEC | Condition |
| BED | Export L/C Documents |
| BRD | Import L/C Documents |
| BTD | Transfer Documents |
| RCD | Reimbursement Claim |
| PTA | Address |
| CUR | Currency |
INR of the object stored in the table identified by OBJTYP.
ID number of the object stored in the table.
This fields holds an the type describing the intended use of the information text. Thus where and in which context this information should be used. 'BUS' is used as trigger to use an available business sector as subselector. 'SET' is used to be suppressed if no settlement is included in the current transaction. The logic is coded in OitGetSqlForOitAccess. The codetable holds a name to be used in a heading to describe the intended use.
This fields holds the type describing the intended use of the information text. Thus, where and in which context this information should be used. 'BUS' is used as trigger to use an available business sector as subselector. 'SET' is used to be suppressed if no settlement is included in the current transaction.
| Code | Text |
|---|---|
| INF | General |
| STP | Stop |
| BUS | Business Sector |
| SET | Settlement |
This field holds the optional business sector this information is associated to. This field should be filled for all entries of type 'BUS' to identify the business sector.
This field holds the optional business sector this information is associated to. This field should be filled for all entries of type 'BUS' to identify the business sector.
This field identifies how a text should be handled. Thus whether the text should not be shown at all, or whether a potential block of a transaction within the application should be issued. The level used in here should fit to the logic implemented in the checking rules which use this level to determine where a blocking errormessage should be created. It should fit to the Stoplevel used in PTSPTA\STPLEV within the contract group for the different roles of a contract.
Determines how a text is to be displayed, or if a text is to be displayed at all.
| Code | Text |
|---|---|
| ! | Do not show |
| $ | Show |
| 0 | Warn |
| 1 | Stop new Risk |
| 2 | Stop Payments |
| 3 | Stop Transaction |
| 9 | Stop Processing |
Holds the information text associated to the object identified by OBJTYP/OBJINR and to be handled according to INFLEV. The text might optionally be a RTE text. Thus to get the content as pure text without Rich-Text-Enhancements StreamGetAdditional with the option “CHARDATA” should be used.
Field in which the desired text has to be entered.
This field holds the version counter to keep track of the version history of an OIT 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 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.