CBB - CBS Balance per Column and Date Range

This table holds all CBS balance entries. These balance entries store
all amount balances within the contracts managed by the
application.
The balances are associated to a relevant object, usually a real
contract or a pseudo contract (like PTE).

/

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 CBB. 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 'relevant object type' for the entry stored in the CBB table. The relevant object type may be: LID, BRD, PTE etc., i.e. the type of the contract (business sector) or the type of a pseudo contract like PTE or other object from which this entry has been originated.

This field contains the 'holding object type' for the entry.

This field contains the INR of the 'relevant object' this entry belongs to. The table of the relevant object is stored in OBJTYP.

This field contains the ID number of the 'holding object'. The table of the holding object is stored in the Object Type Field.

This is the column of the balance. The code might be decoded with the codetable CBCTXT to get the longtext description. The mapping of the stored entries of CBE into the different columns is part of the CBS configuration and might be viewed via DBICBC, DBICBA and DBICBI.

This field contains the pointer for the column in the CBS (Contract Balance Sheet) table.

To be able to store multiple amounts of the same type per contract, this additional field is provided. The CBS subsystem always keeps track of balances per used external ID. Thus, using different external IDs when storing the CBE entries creates different balances within CBB. This is for example used in L/C contracts to differentiate the base amount and additional amount.

Additional external ID to optionaly differentiate groups of entries.

This date defines the beginning date when this balance has its starting validity. When the ENDDAT is lower or equal to BEGDAT, the balance is just kept for the completeness and is never valid. That balance might only get valid, when the following entry is deleted or modified in its starting validity.

The starting date for validity of the entry.

This date defines the day following the ending validity of this balance. If the ENDDAT is equal to BEGDAT, which happens if there are more than one entry for a given date, the entry is never valid and just kept for completeness.

This date defines the day following the ending validity of this remaining amount. If the end date is equal to the start date, which happens if there are more than one entry for a given date, the entry is never valid and just kept for sake of completeness.

This is the currency of the balance amount.

This field contains the currency identified by its ISO code for the adjacent amount.

This is the balance which is valid for the time between the specified dates.

This is the balance that is valid for the relevant date.

This field identifies the last CBE entry which defines this balance.

This field identifies the last CBE entry which defines this balance.

Currency of the converted amount. This currency is usually set from SYSCUR. This field is an optional field and may be empty, if no converted amount of the specific balance is known.

Currency of the converted amount. This currency is usually set from System Currency. This field is an optional field and may be empty, if no converted amount of the specific balance is known.

The converted amount of AMT. If XRFCUR has been set, this field holds the converted amount based on the middle rate of the date, when entering the originating CBE entry. If XRFCUR is empty, this field has to be zero.

The converted amount of the Amount field. If the Currency field for the converted amount has been set, this field holds the converted amount based on the middle rate of the date, on which the original CBE entry was made. If XRFCUR is empty, this field has to be zero.

This field holds the currency of an optional committed balance.

This field holds the currency of an optional committed balance.

This field holds the total balance of all CBE entries which modify this column value and which are marked as committed (normally via execution of the service SRVCOM).

This field holds the total balance of all CBE entries which affect the column value and which are marked as committed.

Currency of the converted committed amount. This currency is usually set from SYSCUR. This field is an optional field and may be empty, if no converted amount of the specific balance is known.

Currency of the converted committed amount. This currency is usually set from System Currency. This field is an optional field and may be empty, if no converted amount of the specific balance is known.

The converted amount of COMAMT. If XCOCUR has been set, this field holds the converted committed amount based on the middle rate of the date, when entering the originating CBE entry. If XCOCUR is empty, this field has to be zero.

The converted amount of the Committed Balance. Ifthe Currency field for the committed balance has been set, this field holds the converted committed amount based on the middle rate of the date, on which the original CBE entry was made. If the Currency field is empty, this field has to be zero.