This table contains common contract information for archived
contracts
Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
---|---|---|---|---|---|---|---|---|---|
OBJTYP | Object Type | Text | 6 | 1 | Edit | Yes | Public | CBOTXT | |
OBJINR | INR of Associated Object | Text | 8 | 1 | Edit | Yes | Public | ||
OWNREF | Reference | Text | 16 | 1 | Edit | Yes | Public | ||
OWNUSR | Resp. User | Text | 8 | 1 | 20 | Edit | Yes | Public | <fixed-length> |
CREDAT | Date of Creation (Opening or Registry) | Date | 12 | 0 | Date | Yes | Public | ||
OPNDAT | Date L/C Opened/Issued | Date | 12 | 0 | Date | Yes | Public | ||
CLSDAT | Date L/C Closed | Date | 12 | 0 | Date | Yes | Public | ||
AMEDAT | Date of Last Amendment | Date | 12 | 0 | Date | Yes | Public | ||
EXPDAT | Valid until | Date | 12 | 0 | Date | Yes | Public | ||
ARCDAT | Archived | Date | 12 | 0 | Date | Yes | Public | ||
RELCUR | Currency of Relevant Amount | Text | 3 | 1 | Edit | Yes | Public | CURTXT | |
RELAMT | Relevant Amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
NAM | Externally Displayed Name to Identify the Contract | Text | 40 | 1 | Edit | Yes | Public | ||
FILID | File-Id of Archive File | Text | 80 | 1 | Edit | Yes | Public | ||
ETYEXTKEY | Entity holding Contract | Text | 8 | 1 | Edit | Yes | Public |
Name | Fields | Properties |
---|---|---|
CCA_ETYEXTKEY | ETYEXTKEY | |
CCA_IDX | OBJTYP, OBJINR | Unique |
CCA_IDX | OBJTYP, OBJINR, ETYEXTKEY | Unique |
CCA_OWNREF | OWNREF |
/
OBJINR, OBJTYP
Type of object the CCA entry refers to. This is the table the contract is stored in.
Type of object the CCA entry refers to. This is the table the contract is stored in.
INR of the associated contract record.
This is the identification number (INR) of the associated contract record.
The field holds the reference of the associated contract.
The field holds the reference of the associated contract.
This field holds the user ID of the person who is responsible for handling this contract. This field is an optional field. Within Demobank it is initially filled with the user ID of the user creating/opening the contract.
This field holds the User ID of the person responsible for the associated contract.
This date field holds the date when the entry was physically added to the database. This may happen when opening the contract, when reserving the reference number or when, for other reasons, a contract is added to the database.
This date field identifies the date the entry was physically added to the database.
The field holds the opening / issuing date of the associated contract.
The field holds the opening/issuing date of the contract. If this field is set, the contract has been legally established and it might be used for business transactions. This date describes the point in time when this contract became legally binding. This might be a date prior to the creation date, when the contract was legally binding before it was stored in the database.
This fields holds the closing date of of the associated contract.
This fields indicates the closing date of a contract. If an entry has been made, the contract is closed and may no longer be used to process business transactions except special transactions like Settling Charges or Common Messages.
This field holds the date of the last amendment.
This field contains the date of the last amendment processed under the contract. If it is empty the contract is still in its original condition. This date is automatically updated by the relevant amendment transactions.
This field describes the validity of the associated contract.
This field describes the validity of the associated contract.
This field contains the date when the contract was archived.
This field contains the date when the contract was archived.
Currency of Relevant Amount
Relevant Amount
Externally Displayed Name to Identify the Contract
This file ID identifies the location, where the archive in .xml format is stored.
Depending on the implementation, the file ID can be a relative file name, the relative filename of a .zip file or an external ID to separate storage system.
This file ID identifies the location of the archive stored in XML format.
Depending on the implementation, the file ID can be a relative file name, the relative filename of a ZIP file or an external ID to a separate storage system.
This table is defined on entity level with separate entries for each entity. This field holds the EXTKEY of the owning entity 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 are visible to the user.
This field holds the external key of the owning entity 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 are visible to the user.