About mapping tables

Caution: Do not modify or delete mapping tables with Core Tool when SAP Convergent Charging is integrated with a CRM application or a provisioning system.

Modifying or deleting mapping tables may result in inconsistencies between the two systems because of data replication and synchronization mechanisms. To modify a range table, you must use the CRM or provisioning system.

  • Consult the SAP CC Library (Application Help) for more information about the product modeling process.

  • Consult the SOAP API Specification for Web Services if you need to integrate your CRM or provisioning system by implementing the Web Services technical interface provided by SAP Convergent Charging to manage this master data in the pricing catalog of a the service provider.

 

The manual procedures detailed in this section are relevant in:

  • A production system landscape with few contracts directly managed with Core Tool (No CRM interfaced with SAP CC)

  • A test, demo, or training system landscape

A mapping table allows you to create new properties that you can use in the price plan, in the refill logic, or in the allowance logic.

A mapping table is an n-dimensional table composed of a set of rows. You define the structure of a mapping table in a mapping table class.

Each row of the mapping table consists of a set of values of input columns (I1, I2, I3,..., In) to which corresponds a set of values of output columns (O1, O2, O3,..., On). For each row, you have to specify the period during which the row is valid.

A mapping table is included in the pricing catalog of the service provider and is part of its master data. It is available for all the end customers of this service provider.

You use mapping tables to configure the pricing logic with convergent charging services based on provider contracts.

Redefinition

You can redefine this table for a specific customer or for a group of end customers by using subscriber mapping tables.

Mapping table step by step

Before creating a mapping table, you must create, set up, and save a mapping table class. You must perform the following steps to use mapping tables:

  1. Create a mapping table

  2. Set up the mapping table

  3. Save the mapping table

  4. Use the mapping table in the refill logic or in one or several price plans by using a Mapping Table Introducer as Comparator component. See the Component Help for more information on this logic components. We recommend that you determine the appropriate customization level of the mapping table that must be processed by the SAP CC system.

  5. Delete the mapping table.

You can use the same mapping table class to build different mapping tables.

After you have created a mapping table, you can then add it to the price plan of a charge or to the refill logic. You can use the same mapping table more than once in any price plan or refill logic.

Price table instance

We call 'price table instance' a mapping table which references a price table as a mapping table class. Note that only an SAP CRM system creates price table instances.

Caution: An SAP CRM system creates and maintains the price table instances automatically. Creating, modifying, or deleting price table instances may result in inconsistencies between these two systems. We strongly recommend that you do not modify or delete existing price table instances except under support supervision.

Integration

This master data may be created an maintained by an external system connected to the SAP CC system during the provisioning process.

SAP CRM manages some mapping tables stored in SAP CC.

Versions

You cannot modify and save different versions of a mapping table.

Transport

You can:

Maintenance

The only mapping table which is available is the last modified one. You can modify and delete the rows of a mapping table, but you cannot change the name of a mapping table or the related mapping table class.