MACA

Mapping Table Classes (in SAP Master Data > Pricing Configuration for End-Customer Services)

Definition


The MACA table contains the partial definitions of all the mapping table classes stored in master data by the SAP CC system

Description


The MACA database table stores the partial definitions of all the mapping table classes (in master data) that are managed by the SAP CC Core Server system.

Note

The rest of the definitions is stored in the following database tables:

For each end-customer service to monetize with SAP Convergent Charging, a pricing catalog includes all the pricing elements that are necessary to design and set up the pricing configuration.

A mapping table class defines a common structure for a subset of:

Technical Data


Schema Version 2025.0.0
Filegroup CATALOG_DATA
Partitioned No

Summary


The MACA 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_MACA       

The unique identifier of the mapping table class in the database. It is generated by the SAP CC system.
CLIENT_NUMBER        

    The client number associated to the mapping table class
    ID        

    The identifier (or NAME in some user interfaces) of the mapping table class that is configured in master data. It must be unique.

    More...

    DESCRIPTION        

      The textual and understandable description for a mapping table class
      OWNER       CATALOG_ENTRY (OWNER)
       

        The owner information of the pricing catalog that contains a mapping table class in this database table - or another owner reference that is not associated to a catalog

        More...

        Additional Information

        As of SAP CC 5.0 SP 3, Manage Mapping Table Classes is an app in the SAP CC Cockpit application that enables the SAP CC pricing specialists to create and maintain some mapping table classes in the pricing catalog for a service provider company that want to monetize its marketable end-customer services.

        You configure these data templates to define the multicolumn structure and key characteristics for some sets of mapping tables or subscriber mapping tables.

        Read more information...

        Mapping table classes in SAP Convergent Charging are master data that define the common characteristics and the multicolumn structures (input and output columns) for different sets of:

        • Mapping tables in a pricing catalog (in master data)
        • Subscriber mapping tables for a subscriber account and its associated provider contracts (in customer master data)

        A mapping table class is part of a service pricing catalog. It defines the following columns:

        • Input columns with the comparative data values
        • Output columns with result values

        A subset of data values from the input columns maps to a value subset in the output columns.

        The format is:

        Column Range Scope Column Count Column Types Typical Use or Example
        Default columns (predefined)
        Row identifiers

        1

        String

        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

        Validity periods 2 Date/Time

        Two columns include the definition period for each row in a mapping table:

        • Start dates and times
        • End dates and times
        Input columns with the comparative data values Pricing data or custom data Max. 20
        • String
        • Currency (only one input column)
        • SAP currencies
        • Comparison or segmentation keys
        • Tariff identifiers
        • Metadata
        Output columns Pricing data or custom data Max. 30
        • String
        • Number
        • Prices, tariffs per minute or distance, unit prices, credits, and other amounts
        • References
        • Any resulting information (pricing or technical)

        A mapping table class is viewable in SAP CRM (integrated SAP Solutions) or 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 in:


        See also:

        Column Details

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

        OID

        Definition The unique identifier of the mapping table class in the database. It is generated by the SAP CC system.
        Type DECIMAL(28), NOT NULL
        Primary Key PK_MACA

        CLIENT_NUMBER

        Definition The client number associated to the mapping table class
        Type DECIMAL(3), NOT NULL

        ID

        Definition The identifier (or NAME in some user interfaces) of the mapping table class that is configured in master data. It must be unique.
        Description

        The identifier or identification name of the mapping table class 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

        DESCRIPTION

        Definition The textual and understandable description for a mapping table class
        Type NVARCHAR(2000), NULL

        OWNER

        Definition The owner information of the pricing catalog that contains a mapping table class in this database table - or another owner reference that is not associated to a catalog
        Description

        Data values in the OWNER column are mandatory. Each pricing element or object such as a a mapping table class, a charge plan, a reusable charge, or a pricing macro must have some owner information as a technical key that is used by the SAP CC system.

        SAP Convergent Charging uses this key for grouping and associating some data objects together.

        • When a pricing element is included in a pricing catalog, the owner information that is set for the pricing element (aka data object) must be the same as the owner information that is set for this pricing catalog.
          See the OWNER column in the CATALOG_ENTRY database table.

        • Otherwise, the pricing element is orphan and not included in a pricing catalog some owner information must be set.

        Type NVARCHAR(256), NOT NULL

        Primary Key Details

        See the primary key information:

        PK_MACA

        Column(s) OID
        Filegroup CATALOG_DATA