The MATA database table stores the partial definitions of all the mapping tables (in master data)
that are managed by the SAP CC Core Server system.
In SAP Convergent Charging, mapping tables may be high volume data tables.
Note
The data content of each mapping table is stored in the MARO database table.
In SAP CC, the structure of each mapping table is specified
in a mapping table class (see the MACA table).
| Schema Version | 2025.0.0 | |
| Filegroup | CATALOG_DATA | |
| Partitioned | No | |
The MATA 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_MATA |
|
The unique identifier of the mapping table in the database. It is generated by the SAP CC system. | |||
| CLIENT_NUMBER | IX_MATA_AGREEMENT_ID |
|
The client number associated to the mapping table | |||
| ID |
|
The identifier (or NAME in some user interfaces) of the mapping table that is configured in master data. It must be unique. | ||||
| DESCRIPTION |
|
The full description of the mapping table | ||||
| AGREEMENT_ID | IX_MATA_AGREEMENT_ID |
|
The agreement ID of the mapping table | |||
| OWNER | CATALOG_ENTRY (OWNER)
|
|
The owner information of the pricing catalog that contains this mapping table. It is the same as the owner that is declared in the mapping table class that defines the structure for this specific mapping table. | |||
| MACA_OID | IX_MATA | MACA (OID)
|
|
The identifier (OID) of the mapping table class used as schema and structure | ||
| VERSION_ID |
|
Determined at mapping table level, this identifier is incremented each time a modification is performed on the mapping table. | ||||
| DELETED_ROW_COUNT |
|
The total number of rows of the mapping table that have been deleted |
As of SAP CC 5.0 SP 3, Manage Mapping Tables is an app in the SAP CC Cockpit application that enables
the SAP CC pricing specialists to create and maintain some mapping tables in the
pricing catalog for a service provider company that want to monetize its marketable
end-customer services.
You configure these data tables and the associated pricing logic (reusable charges,
pricing macros)
to model multicurrency and multidimensional pricing.
Mapping tables in SAP Convergent Charging are business data tables or price lists that facilitate
the multidimensional and multicurrency pricing for the end-customer services to monetize
with SAP CC.
SAP CC uses a mapping table to determine or compute prices dynamically.
At runtime, SAP CC looks up data values from input columns in a specific mapping table.
It compares row by row
these table values with a reference set of values from a rating and charging context.
The comparison algorithm takes into account the validity period for each row and a
reference date and time such as the service usage date/time.
When several rows match the reference value subset, the comparison searches for the
shortest period whose start date/time is closest to the reference date/time.
The comparison option Longest Prefix Match (aka maximum prefix length match) is available.
First of all, all the first possible matches are found and then the longest match
is selected.
When you design a mapping table, it includes the following data:
1
The first column includes unique technical IDs for the row definitions to facilitate
the data table maintenance for a given row
and for a given period
Two columns include the definition period for each row in a mapping table:
Column Range
Scope
Column Count
Column Types
Typical Use or Example
Default columns (predefined)
Row identifiers
String
Validity periods
2
Date/Time
Input columns with the comparative data values
Pricing data or custom data
Max. 20
Output columns
Pricing data or custom data
Max. 30
A mapping table or a subscriber mapping table is viewable and also configurable in SAP CRM (integrated SAP Solutions) or in another interfaced CRM application or provisioning system.
Note
To facilitate your integration, SAP CC provides you with two technical interfaces (Web Services (WS) and HCI) to implement in your SAP system landscape. Refer to the available service operations and their specifications in the SOAP APIs or Java APIs:
The database schema defines the following columns. Check the definitions, types, available indexes, and formats:
| Definition | The unique identifier of the mapping table in the database. It is generated by the SAP CC system. |
| Type | DECIMAL(28), NOT NULL |
| Primary Key | PK_MATA |
| Definition | The client number associated to the mapping table |
| Type | DECIMAL(3), NOT NULL |
| Available Index | IX_MATA_AGREEMENT_ID |
| Definition | The identifier (or NAME in some user interfaces) of the mapping table that is configured in master data. It must be unique. |
| Description |
The identifier or identification name of the mapping table in a service pricing catalog for the end-customer services to monetize with SAP Convergent Charging.
ID must be unique in the SAP CC system and in its back-end database system.
Note
The ID information is also visible in the following SAP CC user interfaces as the
Name fields:
|
| Type | NVARCHAR(256), NOT NULL |
| Definition | The full description of the mapping table |
| Type | NVARCHAR(2000), NULL |
| Definition | The agreement ID of the mapping table |
| Type | NVARCHAR(256), NULL |
| Available Index | IX_MATA_AGREEMENT_ID |
| Definition | The owner information of the pricing catalog that contains this mapping table. It is the same as the owner that is declared in the mapping table class that defines the structure for this specific mapping table. |
| Type | NVARCHAR(256), NOT NULL |
| Definition | The identifier (OID) of the mapping table class used as schema and structure |
| Type | DECIMAL(28), NOT NULL |
| Available Index | IX_MATA |
| Definition | Determined at mapping table level, this identifier is incremented each time a modification is performed on the mapping table. |
| Type | DECIMAL(28), NOT NULL |
| Definition | The total number of rows of the mapping table that have been deleted |
| Type | DECIMAL(28), NOT NULL |
See the primary key information:
| Column(s) | OID |
| Filegroup | CATALOG_DATA |
The following database indexes are available in the MATA database table to improve the speed of data retrieval operations during the business processes of SAP Convergent Charging:
| Indexed Column(s) | MACA_OID |
| Unique | No |
| Partitioned | No |
| Clustered | No |
| Filegroup | CATALOG_INDX |
| Indexed Column(s) | CLIENT_NUMBER, AGREEMENT_ID |
| Unique | No |
| Partitioned | No |
| Clustered | No |
| Filegroup | CATALOG_INDX |
