DOO_BILLING_PLANS
Billing Plan stores the information related to various Billing Types such as Periodic/Milestone etc. Details stored include number of bills, billing transaction date,override periods, and remaining billing amount per period.
Details
-
Schema: FUSION
-
Object owner: DOO
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
DOO_BILLING_PLANS_PK |
BILLING_PLAN_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
BILLING_PLAN_ID | NUMBER | 18 | Yes | Unique identifier for the billing plan. | |
FULFILL_LINE_ID | NUMBER | 18 | Yes | Foreign Key to DOO_FULFILL_LINES_ALL table | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
NET_BILLING_AMT_PER_PERIOD | NUMBER | This is the Net Amount that will be billed per billing period | |||
BILLING_PLAN_TYPE_CODE | VARCHAR2 | 30 | Yes | Type of Billing Plan for e.g - PERIODIC / MILESTONE. | |
PERIODICITY_CODE | VARCHAR2 | 30 | Yes | Period of the recurring invoice. Valid values are DAY, WEEK, MONTH, QUARTER, YEAR. | |
BILLING_NUM_OF_PERIODS | NUMBER | 9 | Yes | Number of recurring invoices to issue. | |
BILLING_PERIOD_START_DATE | DATE | The end date of the billing period corresponding to the billing period number.This date may be the contract end date for the first billing period or it may refer to the billing end date of the subsequent billing period if the previous invoice did not cover a full billing period. | |||
BILLING_PERIOD_END_DATE | DATE | The end date of the billing period corresponding to the billing period number.This date may be the contract end date for the first billing period or it may refer to the billing end date of the subsequent billing period if the previous invoice did not cover a full billing period. | |||
BILLING_TRX_DATE | DATE | Transaction date of the first invoice for recurring invoices or it may also refer to the Transaction date of the subsequent invoice for recurring invoices, if the previous invoice was for a partial period. | |||
BILLING_PERIOD_NUMBER | NUMBER | 9 | The period number corresponding to the Billing Start Date / End Date / Transaction Date. | ||
OVERRIDE_PERIOD | NUMBER | 9 | Number indicating the period that has an override amount. For example, the first invoice is for period 1, the second invoice is for period 2, and so on. | ||
OVERRIDE_PERIOD_AMOUNT | NUMBER | The override amount for the period indicated in First Override Period. | |||
CANCELLATION_EFFECTIVE_DATE | DATE | Effective date that the recurring billing should stop and no future billing should occur. | |||
SOURCE_BILLING_PLAN_ID | VARCHAR2 | 50 | The internal identifier for the Billing Plan as assigned by the system that captured the transaction | ||
OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
OVERRIDE_PERIOD_QUANTITY | NUMBER | Quantity to be used for Billing/ Credit generation during the Override Period. This applies to Recurring Billing. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
DOO_BILLING_PLANS | doo_fulfill_lines_all | FULFILL_LINE_ID |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
DOO_BILLING_PLANS_FK1 | Non Unique | Default | FULFILL_LINE_ID |
DOO_BILLING_PLANS_PK | Unique | Default | BILLING_PLAN_ID |