Contact Us
SAP Convergent Charging

Core Database Reference (MS SQL Server)

Target Audience

  • IT system architect
  • Technology consultant
  • Implementation project team
  • Database system administrator (DBA)
  • Support specialist

Caution

Direct SQL queries on the database are not allowed. Do not modify the data stored in the database system.

Consult first your customer project team during the implementation phase of SAP CC.

Important Note

SAP does not recommend that you use direct SQL queries for statistics or monitoring an SAP CC production system.

Consult first your SAP Support Team.

Recommendation

SAP recommends that you consult the SAP CC Application Help (aka SAP CC Library) for more information about the possible use conditions and technical implementation limitations that relate to your database.

Getting Started

This SAP product documentation is a complete reference of the schema of SAP CC Core Database, a component of the SAP Convergent Charging 4.1 software product. SAP CC Core Database is a back-end database of SAP CC Core Server.

It contains the different data related to the business and technical processes handled by the SAP CC Core Server system. This data includes:

Data in Database Main Data Comment
Businnes configuration data

Master data (MD)

The SAP Master Data (MD) is owned by a service provider of digital services charged with SAP Convergent Charging (SAP CC).

Business/custom data

  • Currencies, holidays, VAT rates and rules

The business/custom data is defined for the complete SAP CC system and all the service providers. This data is shared with all the pricing catalogs.

Customer master data (in high volume)

The customer master data is part of the SAP Master Data owned by the service provider of the digital services to monetize with SAP CC. Each data object in customer master data is assigned to the pricing catalog that contains the pricing logic for the relevant customer service.

Business processing data Charging session data (session-based charging services), counter snapshots Consider also the counter and allowance data.
Technical data
  • SAP CC users, custom audit filters, and audit data recordings (audited user operations, object change logs, object snapshots)
  • SAP CC System Settings
  

Refer to this information when administering the SAP CC system or the database system, installing/upgrading, or updpating/patching SAP CC tables in your database.

Database Schema

The database schema describes the structure, all the tables (entities), the columns (attributes), and the keys (relationships) in the SAP CC database. It defines the relevant database indexes to speed up the retrieval of data stored in the database tables.

Note

This schema is the logical schema. It informs the design of the database whatever the database system. It includes partial information about the physical schema (implementation in different database systems) and about the conceptual schema (concepts and relationships).

Refer to the SAP CC Application Help (aka SAP CC Library) for more information about the concepts of SAP Convergent Charging:

Depending on your business requirements, there are two classes of schemas: a schema with business partitions (large business) and a schema without database partition.

This schema defines some reserved spaces to optimize the physical storage of data in the database system.

Schema Version

The database schema is identified with a unique version. Refer to the VERSION table for more information about the version information format and version history.

Main Database Tables

Refer to the main database tables or view the index of tables.

Legend and Abbreviations

  • PK: Primary Key
  • FK: Foreign Key
  • UK: Unique Key
  • IX: Indexed Field

Database Indexes

This database schema defines the necessary database indexes to speed up the retrieval of data stored in the database tables. The initial installation of SAP CC creates these indexes that you manage during technical operations.

Reserved Space in Filegroups

This database schema defines some reserved spaces to optimize the physical storage of data in your database system. You configure and maintain these spaces.

Database Partitioning

SAP Convergent Charging provides advanced functions to ensure the highest level of performance (high volume of data, very high end-to-end throughput and latency) and high availability. These functions require database partitioning to improve the database performance with large and very large databases.

SAP CC associates a business partitioning mechanism to isolate some data during business operations.

For more information about the business partitioning in SAP Convergent Charging, consult the SAP CC 4.1 Application Help and the database section.

Schemas and Database Partitioning

SAP CC delivers two schemas of Core Database.

Class Scope
Schema With Database Partitions
  • Large and high volume of data
  • High performance
Schema Without Partition
  • Small-sized business environments (includ. production system landscapes)
  • or development system landscapes

Each relevant database table includes a PARTITION_ID column that refers to the partition ID of the associated subscriber account. Both objects belong to the same database partition.

For more information about the business partitioning in SAP Convergent Charging, consult the SAP CC 4.1 Application Help and the database section.

Note

SAP CC provides you with two corresponding sets of SQL scripts.

SQL Scripts

All the necessary SQL scripts are delivered with SAP Convergent Charging to:

  • Administer your database and SAP CC tables (initial creation and deletion scripts).
  • Change some SAP CC tables in your database (patch scripts) during the regular software maintenance of SAP CC or during an upgrade project from previous main release of SAP CC.
  • Fix some SAP CC tables in your database (correction scripts) during troubleshooting operations with your SAP Support Team.

Two Sets of Scripts

SAP CC delivers two sets of SQL scripts to install a new database system with or without database partitioning. The file naming convention uses the enterprise and standard terms:
Script Set Script Name Patern
Database With Partitions
  • <DB_TECHNO_KEY>_enterprise_<DB_SCHEMA_KEY>_create.sql
  • <DB_TECHNO_KEY>_enterprise_<DB_SCHEMA_KEY>_drop.sql
  • patch<SCHEMA_VERSION>to<_NEW_VERSION><DB_TECHNO>_enterprise_<DB_SCHEMA>.sql
Database Without Partition
  • <DB_TECHNO_KEY>_standard_<DB_SCHEMA_KEY>_create.sql
  • <DB_TECHNO_KEY>_standard_<DB_SCHEMA_KEY>_drop.sql
  • patch<SCHEMA_VERSION>to<_NEW_VERSION><DB_TECHNO>_standard_<DB_SCHEMA>.sql

Delivered SQL scripts are stored in one of the following SAP CC installation folders:

  • MS Windows: <DRIVE>:\usr\sap\<SID>\CCD<SAP_INST_NB>\exe\CC_CORE_SERVER\core_sql
    • or
  • UNIX and other operating systems: /usr/sap/<SID>/CCD<SAP_INST_NB>/exe/CC_CORE_SERVER/core_sql

Note

The delivered SQL scripts are stored in the SAP Central Repository of the SAP CC system. This file repository is available on the SAP Global Host in the following directory:

  • MS Windows: \\<SAP_GLOBAL_HOST>\sapmnt\<SID>\SYS\
  • UNIX and other OSs: /sapmnt/<SID>/SYS/

Where <SID> is the SAP system ID.

Implementation

To implement this database in your SAP system landscape, consider the following activities:

  • Sizing
  • Installation
  • Technical configuration in SAP CC
  • Validations
  • Technical operations (administration, software maintenance, purging and archiving, monitoring, and troubleshooting)

Sizing

Refer to the SAP CC Sizing and Performance Tuning Guide and SAP CC Sizing Guidelines for information about the the translation of your business requirements and IT strategy into hardware requirements based on predictions considering:

  • data volume
  • performance
  • robustness
  • scalability
  • high availability

The sizes of the hardware and database are influenced by both business aspects and technological aspects.

Notes

  • The regular growth of data volume and the load of the network must be taken into account as conditions for the initial sizing.
  • Confirm and adapt your initial sizing with performance and validation tests.

Installation

Refer to the SAP CC Installation Guide for information about the installation preparations, initial installation, and follow-up activities of this database system in your SAP CC system landscape.

Note

Refer to the information provided by the database supplier.

Technical Configuration in SAP CC

Refer to the SAP CC System Parameter Reference and SAP CC 4.1 Configuration Guide for more information about the configuration in SAP CC that relates to the databases. See the SQLHELPER_LOGIN system parameter.

Technical Operations

During the project implementation phase or during the productive operation phase, consider the following activities:

  • Administration
  • Software maintenance
  • Purging and archiving
  • Monitoring
  • Troubleshooting

Software Maintenance

Refer to the information provided by the database supplier for more information about the software maintenance of your database systems.

Note

The software maintenance of SAP Convergent Charging may change the database schema or the stored data. When the SAP CC system administrator implements a support package (SP) or a patch level of SAP Convergent Charging, the maintenance procedures modify the back-end database. Refer to the delivery notes (SAP Notes) provided with the new versions of SAP CC.

Monitoring

DBA Cockpit

Install and use DBA Cockpit in SAP Solution Manager to monitor the back-end databases of SAP Convergent Charging. Refer to the SAP CC Operations Guide for more information.

SAP CC Activities

You can monitor the performance and health metrics reported by the instances of the running SAP CC Core Server system. These instances are connected to the back-end database system and manage several internal functions. By using CA Introscope for SAP in SAP Solution Manager, you can view the back-end activities that relate to the database commits, rollbacks, and prepared SQL statements.

See the {Database Name} on {Hostname} ({Database Type} DB) metric node in the SAP CC Metric Reference and Performance Troubleshooting for more information and user assistance.

Troubleshooting

Communication From Logs Performance

You use SAP Solution Manager to detect connection or communication problems.

You use the SAP CC Admin+ user interface:

You use the logs of the database system.

You use the logs and traces recorded in the SAP CC system.

You use SAP Solution Manager.

 
SAP CC 4.1 © Copyright 2016 SAP SE or an SAP affiliate company. All rights reserved.