| Schema Version | 2022.0.2 | |
| Filegroup | CATALOG_DATA | |
| Partitioned | No | |
The CHARGE_COMPONENT table is defined by the following columns in your back-end database. See the column details for more information.
| Name | PK | FK | IX | Uses | Used by | Definition |
|---|---|---|---|---|---|---|
| OID | PK_CHARGE_COMPONENT |
|
The charge component unique ID | |||
| CODE | IX_CC_CODE |
|
The code of the charge component | |||
| TYPE | IX_CC_CODE |
|
The type of the charge component | |||
| DESCRIPTION |
|
The description of the charge component | ||||
| CURRENCY_CODE | CURRENCY (CODE)
|
|
The currency code of the charge component | |||
| MULTI_CURRENCIES |
|
Specifies whether the charge component is multicurrencies or not | ||||
| OWNER | IX_CC_OWNER |
|
The owner of the charge component | |||
| DEPENDENT |
|
The DEPENDENT field indicates if the charge component is a master or dependent charge | ||||
| ATTRIBUTES |
|
The attributes (represented as binary flags) which qualify the charge component. |
The database schema defines the following columns. Check the definitions, types, available indexes, and formats:
| Definition | The charge component unique ID |
| Description |
|
| Type | DECIMAL(28), NOT NULL |
| Primary Key | PK_CHARGE_COMPONENT |
| Definition | The code of the charge component |
| Type | NVARCHAR(256), NOT NULL |
| Available Index | IX_CC_CODE |
| Definition | The type of the charge component |
| Format |
The possible values are:
|
| Type | DECIMAL(1), NOT NULL |
| Available Index | IX_CC_CODE |
| Definition | The description of the charge component |
| Type | NVARCHAR(2000), NULL |
| Definition | The currency code of the charge component |
| Type | NVARCHAR(5), NULL |
| Definition | Specifies whether the charge component is multicurrencies or not |
| Type | DECIMAL(1), NOT NULL |
| Default | 0 |
| Definition | The owner of the charge component |
| Type | NVARCHAR(64), NOT NULL |
| Available Index | IX_CC_OWNER |
| Definition | The DEPENDENT field indicates if the charge component is a master or dependent charge |
| Format |
The possible values are:
|
| Type | DECIMAL(1), NOT NULL |
| Definition | The attributes (represented as binary flags) which qualify the charge component. |
| Description |
The attributes which qualify the charge component. Example: SHAREABLE flag indicates
if an allowance logic is shareable.
|
| Format |
This column is an unsigned short int whose each bit is attached to an existing attributes
or reserved for attributes implemented later on (see the bits NOT_USED).
If a bit is set to 1, the charge component has the related attribute; otherwise, the
bit is set to 0.
Each new attribute is assigned to a bit from the LSB to the MSB.
For now, only the LSB is used for indicating:
- if an allowance logic is shareable
- if a charge component or an allowance logic is managed by cockpit
MS Byte: [NOT_USED][NOT_USED][NOT_USED][NOT_USED][NOT_USED][NOT_USED][NOT_USED][NOT_USED]
LS Byte: [NOT_USED][NOT_USED][NOT_USED][NOT_USED][NOT_USED][NOT_USED][MANAGED_BY_COCKPIT][SHAREABLE]
|
| Type | DECIMAL(4), NOT NULL |
| Default | 0 |
See the primary key information:
| Column(s) | OID |
| Filegroup | CATALOG_DATA |
The following database indexes are available in the CHARGE_COMPONENT database table to improve the speed of data retrieval operations during the business processes of SAP Convergent Charging:
| Indexed Column(s) | CODE, TYPE |
| Unique | Yes |
| Partitioned | No |
| Clustered | No |
| Filegroup | CATALOG_INDX |
| Indexed Column(s) | OWNER |
| Unique | No |
| Partitioned | No |
| Clustered | No |
| Filegroup | CATALOG_INDX |
