| Schema Version | 5.0.6 | |
| Partitioned | No | |
The PREPAID_TRANSAC_MAPPING 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 |
|---|---|---|---|---|---|---|
| CCON_OID | IX_PPTM_CCON | CHARGE_CONDITION (OID)
|
|
The ID of the charge condition | ||
| INDEX_IN_PPTM |
|
The index of the mapping | ||||
| TRANSACTION_FIELD |
|
The name of the field where the detail is stored in the prepaid transaction files | ||||
| PROPERTY_NAME |
|
The name of the detail to map | ||||
| STRING_VALUE |
|
The value of the detail when it is a string | ||||
| NUMBER_VALUE |
|
The value of the detail when it is a number | ||||
| DATE_VALUE |
|
The value of the detail when it is a date |
The database schema defines the following columns. Check the definitions, types, available indexes, and formats:
| Definition | The ID of the charge condition |
| Type | DECIMAL(28), NULL |
| Available Index | IX_PPTM_CCON |
| Definition | The index of the mapping |
| Type | DECIMAL(5), NOT NULL |
| Definition | The name of the field where the detail is stored in the prepaid transaction files |
| Type | NVARCHAR(4), NOT NULL |
| Definition | The name of the detail to map |
| Type | NVARCHAR(256), NULL |
| Definition | The value of the detail when it is a string |
| Type | NVARCHAR(64), NULL |
| Definition | The value of the detail when it is a number |
| Type | DECIMAL(28,6), NULL |
| Definition | The value of the detail when it is a date |
| Type | DATETIME, NULL |
The following database indexes are available in the PREPAID_TRANSAC_MAPPING database table to improve the speed of data retrieval operations during the business processes of SAP Convergent Charging:
| Indexed Column(s) | CCON_OID |
| Unique | No |
| Partitioned | No |
| Clustered | No |