Deferred Revenue Statistics UML

Added On: 03/20/12

SQL Table: DEFERRED_REVENUE_STATISTICS

Module: UniBill

Type: Entity Status: Active

Java Class: DeferredRevenueStatistics

Records consumption of prepaid services (paid-in-full contracts) over time. The statistics is generated on monthly basis and consumption is recorded using day as a basic unit.

The statistics is generated based on information in [o:Contract] and [o:Adjustment] objects taking into account effective and expiration dates of the contract, cancellations and freezes.

Available Fields:

Begin Date
Consumed Days Count
Consumed Value

Consumed Weeks Count
Contract FK
Create Date

Deferred Value
Description
End Date

Id
Merchant Account Code

Begin Date

Added On: 03/20/12

SQL Column: BEGIN_DATE

Java Field: beginDate

Status: Active

SQL Type: datetime

Java Type: Date

Attributes:

Begin date of the period which this statistics record covers

Consumed Days Count

Added On: 03/20/12

SQL Column: CONSUMED_DAYS_COUNT

Java Field: consumedDaysCount

Status: Active

SQL Type: int(11)

Java Type: Integer

Attributes:

Number of days of the contract that were consumed during this statistics period (number of days a customer used the service)

Consumed Value

Added On: 03/20/12

SQL Column: CONSUMED_VALUE

Java Field: consumedValue

Status: Active

SQL Type: int(11)

Java Type: Integer

Attributes:

Value of the contract that was consumed during this statistics period. The value is produced multiplying daily contract value by the consumed days count. The daily contract value is obtained by dividing total contract value by the length in month and subsequently by 30.

Thus, 12 months PIF contract priced at $1,200 would have a daily value of $1,200/12/30 = $3.33.

Consumed Weeks Count

Added On: 03/26/12

SQL Column: CONSUMED_WEEKS_COUNT

Java Field: consumedWeeksCount

Status: Active

SQL Type: int(11)

Java Type: Integer

Attributes:

Contract FK

Added On: 03/20/12

SQL Column: CONTRACT_FK

Java Field: contract

Status: Active

SQL Type: bigint(20)

Java Type: Long

References Contract

Attributes:

Reference to the contract record for which this statistics record is defined.

Create Date

Added On: 03/20/12

SQL Column: CREATE_DATE

Java Field: createDate

Status: Active

SQL Type: datetime

Java Type: Date

Attributes:

Date when the record was created

Deferred Value

Added On: 03/20/12

SQL Column: DEFERRED_VALUE

Java Field: deferredValue

Status: Active

SQL Type: int(11)

Java Type: Integer

Attributes:

Remaining value of the contract as of this period's end date. Remaining value is obtained by taking previous period's remaining value and subtracting consumed value for this period.

Description

Added On: 03/20/12

SQL Column: DESCRIPTION

Java Field: description

Status: Active

SQL Type: varchar(100)

Java Type: String

Attributes:

Comma separated list of actions describing activities that took place during this period on this contract. The description is maintained for analysis of potential issues.

Possible values are:

expired - the contract expired during the period

cancelled(Id) - the contract was cancelled during the period (cancellation adjustment's Id is added in parenthesis)

freeze(Id) - the contract was affected by a freeze during the period (freeze adjustment's Id is added in parenthesis)

End Date

Added On: 03/20/12

SQL Column: END_DATE

Java Field: endDate

Status: Active

SQL Type: datetime

Java Type: Date

Attributes:

End date of the period covered by this statistics record.

Added On: 03/20/12

SQL Column: ID

Java Field: id

Status: Active

SQL Type: bigint(20)

Java Type: Long

Identifier / Primary Key

Attributes: Unique, Required, CreateOnly, ReadOnly

Identifier of the object used for references; auto-incremented integer value.

Merchant Account Code

Added On: 03/20/12

SQL Column: MERCHANT_ACCOUNT_CODE

Java Field: merchantAccountCode

Status: Active

SQL Type: int(11)

Java Type: Integer

Attributes: Required

Code of Merchant Account to which instance of this object is attributed to. Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.