|
Caution: This topic is intended for administrators and integrators. You can maintain the old offers that you have created with SAP Convergent Charging 1.0, but you can no longer create new offers by using the old configuration related to prepaid or postpaid transactions. In addition, if you want to migrate the old offers to the new configuration related to charged items (SAP Convergent Charging 2.0), keep in mind that this process is irreversible. This means that if you use the Migrate Charged Item Mapping on All Charges or Migrate Charged Item Mapping commands (*) of the Action menu, the Charge Prepaid and Charge Postpaid tabs will be replaced by the Charged Item tab. (*): These commands are available only for the offers created with SAP Convergent Charging 1.0. |
Create or modify an offer before setting up a charge in a suboffer. In the left pane of the offer window, click a charge
to view, and then open the Postpaid Transactions tab.
The Postpaid Transactions tab allows you to filter transaction details. When a service is consumed, a transaction is produced for charging purposes. You can filter transaction details to allow storing only the details you want in the database.
Fill in or modify the Postpaid Transactions tab.
The fields Criteria #1, Criteria #2 and Criteria #3 can be used by administrators to tag certain parameters of a transaction. This makes it easier to search for a particular transaction within a set of transactions.
Criteria #1: Provides the list of all the properties related to transactions. Select the first property.
Criteria #2: Provides the list of all the properties related to transactions. Select the second property.
Criteria #3: Provides the list of all the properties related to transactions. Select the third property.
|
Note: If the Activate Filtering option is not selected, all transaction details will appear in transactions. |
Activate Filtering: Is selected by default. When the option is selected, standard default properties and charge-specific properties are available, but none of them is selected to avoid storing lot of data into the database. You can however select transaction details that you want to include in transactions. For example, you select the main properties, but you leave the secondary properties used to make intermediate calculations. To further optimize storage in database, you can also leave the check boxes Price Plan Name, Charge Code, and Offer Code cleared, but you select these labels if you want them to be included in transactions. You filter each transaction detail by selecting standard default properties
common to all charges, as well as properties that are specific to the charge:
User-defined properties, which were defined in the chargeable item class that the charge relates to
Generated properties, such as those produced by a translation table
Counters
Parameters