Impact of Closing or Amending Subscriptions
When a subscription product or covered asset is closed or amended, causing any change to the billing schedule, the total bill amount for each charge in the product changes. The revenue contract must be revised accordingly.
This is also true for ad hoc bill adjustments or credit memos added to the billing schedule. All changes to billing schedule amounts are considered material changes for revenue revision purposes. Any change to bill amounts on an existing product charge cause a revision of the revenue document line (the revenue line ID is stored in OSS_BILL_LINES.REVENUE_LINE_ID). All bill lines for the same product charge will have the same revenue line ID (with the exception of the usage charges). When a credit memo is applied to a bill line, the new credit memo line in OSS_BILL_LINES will also have the same revenue line ID as the original invoice line. After the credit memo or adjustments are added, or unbilled lines are dropped from the schedule, the total bill amount of all the affected revenue lines are recomputed. This new amount is then used to revise the revenue line. A new record is inserted in VRM_SOURCE_DOC_LINES with the following values:
| VRM_SOURCE_DOC_LINES Attribute (Target) | Value (Source) | Comments | Different from Original Revenue Line Record |
|---|---|---|---|
| DOCUMENT_LINE_ID | VRM_SOURCE_DOC_LINES_S.nextval | Primary key based on VRM dequence | Yes |
| DOCUMENT_DATE | OSS_PRODUCTS.START_DATE | MIN(OSS_BILL_LINES.DATE_BILLED_FROM) | No |
| UOM_CODE | OSS_PRODUCTS.ITEM_UOM | Product item unit of measure | No |
| QUANTITY | NVL(OSS_PRODUCTS.QUANTITY,1) | Product quantity | No |
| UNIT_SELLING_PRICE | SUM(OSS_BILL_LINES.AMOUNT)/QUANTITY | Unit price for the charge (new value) | Yes |
| LINE_CREATION_DATE | Sysdate | Current system date | Yes |
| LINE_LAST_UPDATE_DATE | Sysdate | Current system date | Yes |
| DOCUMENT_TYPE_ID | 10 | Hard-coded | No |
| SOURCE_SYSTEM | FUSION | Hard-coded | No |
| DOC_LINE_ID_CHAR_1 | Old Value | Original Revenue Line ID | No |
| LINE_NUM | OSS_PRODUCTS.PRODUCT_NUMBER | Product line number | No |
| LINE_AMOUNT | SUM(OSS_BILL_LINES.AMOUNT) | Total bill amount for the charge (new value) | Yes |
| UNIT_SSP | SUM(OSS_BILL_LINES.LIST_PRICE)/QUANTITY | Unit standard selling price for the charge | No |
| ITEM_ID | OSS_PRODUCTS.INVENTORY_ITEM_ID | Product Item ID | No |
| INVENTORY_ORG_ID | OSS_PRODUCTS.DEFINITION_ORG_ID | Product Definition Org ID | No |
| SATISFACTION_MEASUREMENT_MODEL |
If a one-time charge, then: ORA_MEASURE_QUANTITY_SATISFIED otherwise: ORA_MEASURE_PERIOD_SATISFIED |
Hard-coded based on charge price type. ONE_TIME or ORA_ONE_TIME are considered a one-time charges. |
No |
| RULE_START_DATE |
If a one-time charge, then: NULL. otherwise: MIN(OSS_BILL_LINES.DATE_BILLED_FROM) |
The accounting rule start date is the earliest bill-from date for recurring charges. No rule dates are passed for one-time charges, since they aren't applicable for the immediate accounting rule. |
No |
| RULE_END_DATE |
If a one-time charge, then: NULL. otherwise: MAX(OSS_BILL_LINES.DATE_BILLED_TO) |
Accounting rule start date is the last bill to date for recurring charges. (This may change for each revision, since some of the billing schedules may be dropped during termination.) No rule dates are passed for one-time charges, since they aren't applicable for the immediate accounting rule. |
Yes |
| CUST_PO_NUMBER | OSS_PRODUCTS.PO_NUMBER | Product purchase order number | No |
| IMMATERIAL_CHANGE_CODE | MATERIAL | Hard-coded (new value) | Yes |
| VERSION_FLAG | Y | Hard-coded (new value) | Yes |
| VERSION_NUMBER | Next version number | NVL(MAX(version_number),0)+1 FROM vrm_source_doc_lines WHERE doc_line_id_char_1 = <original revenue line ID>; | Yes |
| BILL_TO_CUSTOMER_ID | OSS_PRODUCTS.BILL_TO_ACCT_ID | Product bill-to Account ID | No |
| BILL_TO_CUSTOMER_SITE_ID |
Customer account site ID for OSS_PRODUCTS.BILL_TO_SITE_USE_ID |
hz_cust_site_uses_all.cust_acct_site_id where site_use_id = OSS_PRODUCTS.BILL_TO_SITE_USE_ID |
No |
| REVISION_INTENT_TYPE_CODE | CM | Hard-coded (new value) | Yes |
| DATA_TRANSFORMATION_STATUS | 'FUSION_INIT' | Hard-coded | No |
| CREATED_BY | fnd_global.user_name | Current User | No |
| CREATION_DATE | sysdate | Current System Date | No |
| LAST_UPDATED_BY | fnd_global.user_name | Current User | No |
| LAST_UPDATE_DATE | sysdate | Current System Date | No |
| LAST_UPDATE_LOGIN | fnd_global.session_id | Current Session ID | No |
When a termination is done with full credit, one-time charges are also credited. Thus, the satisfaction event for one-time charges needs to be revised. This is done by creating an identical row in the VRM_SOURCE_DOC_SUB_LINES table as the original entry with the exception of the attribute SATISFACTION_EVENT_QUANTITY as 0.