Mailing instruction
one row per party and application form class contains information
that mail of the specified class has to be sent/copied to another
addresses.
The destination addresses for a mailing instruction are stored in the
associated MLE rows.
If the application form class is empty, this mailing instruction has to be
used for every type (class) of message
Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
---|---|---|---|---|---|---|---|---|---|
INR | Internal Unique ID of Mail Instruction | Text | 8 | 1 | Edit | Yes | Public | ||
PTYINR | INR of Party | Text | 8 | 1 | Edit | Yes | Public | ||
APFCLA | Type of Message (Empty = <all>) | Text | 3 | 1 | Edit | Yes | Public | Embedded | |
CPYFLG | Flag, whether # Copies Taken from Here | Text | 1 | 1 | Edit | Yes | Public | YESNO | |
CPYNUM | # of Copies (2nd Column Primary Message) | Numeric | 2 | 0 | Edit | Yes | Public | ||
VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
ETGEXTKEY | Entity Group of Mail Instruction | Text | 8 | 1 | Edit | Yes | Public | ||
GETFLDNRM | Field holding the normalized search fields | Text | 100 | 1 | Edit | Yes | Public |
Name | Fields | Properties |
---|---|---|
MLI_ETGEXTKEY | ETGEXTKEY | |
MLI_INR | INR | Unique |
MLI_PTYINR | PTYINR, APFCLA |
/
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 MLI. 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.
This field contains the INR of the associated party in table PTY for which mailing instructions are stored.
This field contains the internal unique ID of the associated party in table 'Party' (PTY) for which mailing instructions are stored.
Application form classes for documents are set for each document in a call to TRNDOC:defdoceot.
Mailing instructions are set for either a specific application form class (or any document)
The list of application forms for mailing instructions is extended for definition of application forms by fixed classes, one for every type of correspondence (CORTYP) for technical messages.
Application form classes for documents are set for each document.
Mailing instructions are set for either a specific application form class (or any document)
The list of application forms for mailing instructions is extended for definition of application forms by fixed classes, one for every type of correspondence for technical messages.
Code | Text |
---|---|
all | |
LET | Letter |
GUA | Guarantee |
REV | Revers |
CPY | Copy |
INT | Intern |
TCO | TradeConnect |
If this flag is activated, the number of copies for a formset is specified here. This allows different number of copies for different parties using the same formset for messages.
If this flag is activated, the number of copies for a formset is specified here. This allows different number of copies for different parties using the same formset for messages.
This field contain the number of copies, which are created for the specified party and formset if CPYFLG is activated.
This field contains the number of copies, which are created for the specified party and formset if copy-flag is activated.
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.
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.