The CACO database table stores the definitions for all the charging contracts (charging view of the provider contracts):
Each contract data belongs to an end customer for the service provider and its marketable
services.
These definitions are completed with information stored in the CACO_xx database tables
and in the tables dedicated to
the contract items (see the CACI table).
Important Note
For performances, the counters and allowances belonging to the provider contracts
are stored in dedicated tables and reserved storage spaces
(tablespaces, filegroups).
Refer to the:
| Schema Version | 5.0.6 | |
| Partitioned | Yes, when you use the partitioning scheme and corresponding SQL scripts | |
The CACO 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_CACO |
|
The unique identifier of the charging contract | |||
| EXT_ID | IX_CACO_EXT_ID |
|
The external identifier of the charging contract | |||
| SUAC_OID | IX_CACO_SUAC | SUBSCRIBER_ACCOUNT (OID)
|
|
The unique identifier of the subscriber account relating to the charging contract for a specific service provider | ||
| ROCO_OID | IX_CACO_ROCO | CACO (OID)
|
|
The identifier of the parent contract if the charging contract is linked this charging contract to share a pool of counters with linked charging contracts that can debit units | ||
| OP_STATUS |
|
The operational status of the parent charging contracts | ||||
| TECHNICAL_STATUS |
|
The technical status of the charging contract. | ||||
| PARTITION_ID | SUBSCRIBER_ACCOUNT (PARTITION_ID)
|
|
The database partition identifier of the subscriber account of the charging contract |
The database schema defines the following columns. Check the definitions, types, available indexes, and formats:
| Definition | The unique identifier of the charging contract |
| Description |
|
| Type | DECIMAL(28), NOT NULL |
| Primary Key | PK_CACO |
| Definition | The external identifier of the charging contract |
| Description |
The external identifier of the charging contract.
It includes a custom value set by an external provisioning system at creation time
when configuring the customer master data in SAP CC.
|
| Type | NVARCHAR(256), NOT NULL |
| Available Index | IX_CACO_EXT_ID |
| Definition | The unique identifier of the subscriber account relating to the charging contract for a specific service provider |
| Type | DECIMAL(28), NOT NULL |
| Available Index | IX_CACO_SUAC |
| Definition | The identifier of the parent contract if the charging contract is linked this charging contract to share a pool of counters with linked charging contracts that can debit units |
| Description |
The identifier of the parent contract if the charging contract is linked this charging
contract to share a pool of counters with linked charging contracts that can debit units.
Note
This ID can be the OID of the contract itself if the contract is a parent contract
or if the charging contract is not linked to a parent contract.
|
| Type | DECIMAL(28), NULL |
| Available Index | IX_CACO_ROCO |
| Definition | The operational status of the parent charging contracts |
| Description |
The operational status indicates if you can modify a charging contract and its linked
contracts
and use them in the SAP CC processes.
The value of the operational status for the linked charging contracts is always set
to O but this
value is not used. The linked charging contracts inherit from the operational status
of their
parent charging contract.
|
| Format |
The operational status has one of the following values:
|
| Type | DECIMAL(1), NOT NULL |
| Definition | The technical status of the charging contract. |
| Description |
The technical status indicates if some technical procedures have been applied to the
contract (for example, the packing procedure).
|
| Format |
This status is an unsigned short int whose each bit is attached to an existing technical
procedure or reserved for a future procedure.
If a bit is set to 1, the related procedure has been applied to the contract; otherwise,
the bit is set to 0.
Each new technical procedure is assigned to a bit from the LSB to the MSB.
For now, only the LSB is used for the PACKING technical procedure on contracts.
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][NOT_USED][PACKING]
|
| Type | DECIMAL(4), NOT NULL |
| Default | 0 |
| Definition | The database partition identifier of the subscriber account of the charging contract |
| Type | DECIMAL(4), NOT NULL |
See the primary key information:
| Column(s) | OID |
| Segment | SUBSCRIBER_INDX |
The following database indexes are available in the CACO database table to improve the speed of data retrieval operations during the business processes of SAP Convergent Charging:
| Indexed Column(s) | SUAC_OID |
| Unique | No |
| Partitioned | No |
| Clustered | No |
| Indexed Column(s) | ROCO_OID |
| Unique | No |
| Partitioned | No |
| Clustered | No |
| Indexed Column(s) | EXT_ID |
| Unique | No |
| Partitioned | No |
| Clustered | No |