CACI

Contract Items (in Charging Contracts)

Definition


The CACI table contains the contract items of the charging contracts as part of the master data related to the end customers of a service provider (see subscriber data)

Description


The CACI table contains the contract items of the charging contracts as part of the master data related to the end customers of a service provider (see subscriber data). A contract item mostly includes a referrence to the charge plan or the refill plan that is activated in this contract item. This definition is completed with different identifiers and with information stored in the CACI_xx database tables:

Technical Data


Schema Version 5.0.6
Partitioned Yes, when you use the partitioning scheme and corresponding SQL scripts

Summary


The CACI 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_CACI       

    The unique identifier of the charging contract item

    More...

    CACO_OID     IX_CACO_ITM  CACO (OID)
     

      The identifier of the charging contract that includes the contract item
      PARTITION_ID PK_CACI      SUBSCRIBER_ACCOUNT (PARTITION_ID)
       

        The database partition ID assigned to the subscriber account of the charging contract
        EXT_ID        

          The identifier of the contract item inside the charging contract
          EXT_ID_2        

            The optional non unique identifier of the charging contract item inside the charging contract
            CAPA_OID       CAPA (OID)
             

              The unique identifier of the charge plan or refill plan activated in this contract item
              TYPE        

                The type of the activated plan by the contract item

                More...

                Column Details

                The database schema defines the following columns. Check the definitions, types, available indexes, and formats:

                OID

                Definition The unique identifier of the charging contract item
                Description

                The unique identifier of the charging contract item. It is generated by the SAP CC system.

                Type DECIMAL(28), NOT NULL
                Primary Key PK_CACI

                CACO_OID

                Definition The identifier of the charging contract that includes the contract item
                Type DECIMAL(28), NOT NULL
                Available Index IX_CACO_ITM

                PARTITION_ID

                Definition The database partition ID assigned to the subscriber account of the charging contract
                Type DECIMAL(4), NOT NULL
                Primary Key PK_CACI

                EXT_ID

                Definition The identifier of the contract item inside the charging contract
                Type NVARCHAR(256), NOT NULL

                EXT_ID_2

                Definition The optional non unique identifier of the charging contract item inside the charging contract
                Type NVARCHAR(256), NULL

                CAPA_OID

                Definition The unique identifier of the charge plan or refill plan activated in this contract item
                Type DECIMAL(28), NULL

                TYPE

                Definition The type of the activated plan by the contract item
                Format

                The possible values are:

                • 0: Charge plan
                • 1: Refill plan

                Type DECIMAL(1), NOT NULL

                Primary Key Details

                See the primary key information:

                PK_CACI

                Column(s) PARTITION_ID,OID
                Segment SUBSCRIBER_INDX

                Index Details

                The following database indexes are available in the CACI database table to improve the speed of data retrieval operations during the business processes of SAP Convergent Charging:

                IX_CACO_ITM

                Indexed Column(s) CACO_OID
                Unique No
                Partitioned Yes
                Clustered No