A P P E N D I X B

Reports

The Vending Manager provides daily statistical reports that enable you to view and track application download information and usage statistics. The Content Delivery Server can also store transaction data in a database table. Use this data to create your own reports.

A record of each purchase and refund transaction is stored in the REPORT_DOWNLOAD table in the Vending Manager database. See Section 4.12, Configure Support for Customized Reports for information on installing the schema. The following table describes the data that is stored for each transaction.

Note - This table could change in future releases.

TABLE B-1 Report Data
Name	Format	Description
`REPORT_DOWNLOAD_ID`	Number	Unique identifier for the transaction
`TRANSACTION_DATE`	Date	Timestamp of when the transaction occurred
`RESOURCE_INSTANCE_ID`	Number	Identifier for the edition of the content item involved in the transaction
`RESOURCE_CLASS_ID`	Number	Identifier for the content item involved in the transaction
`CONTENT_NAME`	String	Name of the content involved in the transaction
`CONTENT_DESCRIPTION`	String	Description of the content
`CONTENT_TYPE`	String	Type of content, for example, MIDlet
`CONTENT_PROVIDER_KEY`	String	Identifier that the content provider gave the content
`CONTENT_PROVIDER_ID`	Number	Identifier for the content provider
`CONTENT_PROVIDER`	String	Name of the content provider
`CONTENT_COST`	Float	Price assigned by the content provider
`PRICE`	Float	Price accepted by the subscriber
`FULFILLMENT_REQUEST_ID`	Number	Identifier for the fulfillment request
`FULFILLMENT_STATUS`	String	Status of the transaction, either `Purchased` or `Refunded`
`BILLING_MODEL`	String	Billing model for the content
`SUBSCRIBER_ID`	Number	Identifier for the subscriber
`MSISDN`	String	MSISDN associated with the subscriber
`FIRST_NAME`	String	First name of the subscriber
`LAST_NAME`	String	Last name of the subscriber
`MODEL`	String	Name of the subscriber's device

The information stored for each transaction is current at the time the transaction occurs and is never changed. If, for example, a subscriber changes the device used, only new transactions for that subscriber show the new device. Transactions that occurred with the old device continue to show that device in the MODEL field.