A real customer profile defines the actual usage of one or more real consumers who have consumed one or more chargeable item classes.
To create a real customer profile, data that relate to a real customer usage event must first be exported from the database to an XML file that represents this usage traffic.
You can create a real customer profile by using data exported from your legacy system to a usage traffic XML file that is compliant with the definition of SAP Convergent Charging.
Real customer profile characteristics are defined by the user during the creation of the usage traffic XML file that uses SAP Convergent Charging. These characteristics consist of the following:
Start and end dates, which represent the duration periods of the transactions
A specific consumer or all consumers who have generated transactions between the specified dates
Transaction criteria that relate to offers created in SAP Convergent Charging
The usage traffic XML file includes a root element that is usageReport. It includes several usage elements. The usage element represents a real usage transaction that relates to a consumption event and includes all the mandatory properties (in property elements).
A usage element must include all the following property elements:
default.access_login: You must fill in this property, but it is not used during the rating.
default.agreement_creation_date: This property is mandatory.
default.ci_name: Name of the ticket.
default.consumption_date: Consumption date of the service, which is a default property of the chargeable item package. This property is mandatory.
default.product_code: Name of the chargeable item package.
default.service_identifier: You must fill in this property, but it is not used during the rating process. This property is a default property of the chargeable item package.
item.name_1: Ticket parameter (*).
item.name_2: Ticket parameter (*).
...
item.name_n: Ticket parameter (*).
(*) For example, item.title, item.author, item.volume, and so on.
The property element has several attributes: A name, a type, and a value. The possible values for the type attribute are:
0: String
1: Number
2: Date
|
Note: Make sure that the usage dates (consumption dates) are included in the simulation period. |
The following example shows a usage event:
<usageReport>
<usage>
<property name="default.access_login" type="0" value="customer1"/>
<property name="default.agreement_creation_date" type="2" value="2003-10T31T00:00:00"/>
<property name="default.ci_name" type="0" value="Music usage"/>
<property name="default.consumption_date" type="2" value="2004-09-12T14:49:46"/>
<property name="default.product_code" type="0" value="Content MMS"/>
<property name="default.service_identifier" type="0" value="GPRS"/>
<property name="item.title" type="0" value="1"/>
<property name="item.author" type="0" value="2"/>
<property name="item.volume" type="1" value="32"/>
</usage>
</usageReport>