Data Feed 63 Release
- Installment Schedule (EXTRACT-9734, EXTRACT-10150, EXTRACT-10151, EXTRACT-10153, EXTRACT-10154)
- Plan:NSO Ref Uses client_item_id Instead of client_sku—Bug Fix (EXTRACT-10291)
- Credit Memo LOM changes for DEV-11788 (EXTRACT-10365)
- Adding Transaction Qualifiers in Transaction Update Side Effect (EXTRACT-10470)
- Installment Term Attribute Cleanup/Parity With Installment Schedule (EXTRACT-10614)
Installment Schedule (EXTRACT-9734, EXTRACT-10150, EXTRACT-10151, EXTRACT-10153, EXTRACT-10154)
(Data Feed, Universal Connector, Snowflake)
Installment schedule is a new LOM introduced to the data feed. This is part of the installment project. Whenever an installment schedule is created, updated, or deleted on the core side, we will create the installment objects on the data feed.
The structure of Installment Schedule will look like the following:
Sample Created Installment Schedule Payload
{ "account": { "ids": { "account_no": 269908, "userid": "z8kAGeU4MVhVs6fNEmVgrNBjD8GYIJdf" }, "type": "Account" }, "aligned_master_plan_instance": { "ids": { "client_plan_instance_id": "533031", "plan_instance_no": 533031 }, "type": "Plan_Instance" }, "billing_group": { "ids": { "billing_group_no": 275552, "client_billing_group_id": "mYK0ESNnrXFxBviVYXHXB9xzYFFeW277E2pfv2" }, "type": "Billing_Group" }, "charge_transaction": { "ids": { "transaction_no": 3345622 }, "type": "Transaction" }, "created_tstamp": "2025-04-15T13:29:54+02:00", "installment_no": 164, "installment_term": { "ids": { "client_term_id": "QA_PR1qVMwR5qphIEBgfwnbK0IOsVXqWsIntgnhgf0FbYotyHDGct5pP87PugZ4VDLSDraFPoge44FWu3BnHWNaFIqCkMzoeuby2", "term_no": 444 }, "type": "Installment_Term" }, "invoice": { "ids": { "invoice_no": 1115727 }, "type": "Invoice" }, "is_aligned": false, "lump_sum": { "allocation": { "ids": { "type_cd": "P" }, "type": "Lump_Sum_Allocation" }, "amount": 12, "days": null, "days_til_due": null, "days_til_notify": 33, "is_aligned": false, "notification": null }, "number_of_installments": 3, "payment_status": { "ids": { "status_no": 1 }, "type": "Installment_Schedule_Payment_Status" }, "previous_installment_schedule": null, "status": { "ids": { "status_no": 0 }, "type": "Installment_Schedule_Status" }, "status_comment": null, "status_updated_tstamp": "2025-04-15T13:29:54+02:00", "total_charge_amount": 160, "total_tax_amount": 16 }
Update Installment Schedule Payload
We can only modify the aligned master plan instance, payment status, status, status comment, and status update time stamp. Hence, we are exposing only those fields in the update payload.
{ "aligned_master_plan_instance": { "ids": { "client_plan_instance_id": "537579", "plan_instance_no": 537579 }, "type": "Plan_Instance" }, "installment_no": 674, "payment_status": { "ids": { "status_no": 2 }, "type": "Installment_Schedule_Payment_Status" }, "status": { "ids": { "status_no": 1 }, "type": "Installment_Schedule_Status" }, "status_comment": null, "status_updated_tstamp": "2025-07-05T01:18:04+02:00" }
Snowflake Changes for Installment Schedule
VC_INSTALLMENT_SCHEDULES
| Table Name | Column Name |
|---|---|
| VC_INSTALLMENT_SCHEDULES | CLIENT_NO |
| VC_INSTALLMENT_SCHEDULES | BATCH_ID |
| VC_INSTALLMENT_SCHEDULES | CHG_ID |
| VC_INSTALLMENT_SCHEDULES | REF_PK |
| VC_INSTALLMENT_SCHEDULES | EVENT_TSTAMP |
| VC_INSTALLMENT_SCHEDULES | EVENT_ID |
| VC_INSTALLMENT_SCHEDULES | CREATETIME |
| VC_INSTALLMENT_SCHEDULES | ACTIONS |
| VC_INSTALLMENT_SCHEDULES | INSTALLMENT_NO |
| VC_INSTALLMENT_SCHEDULES | ACCOUNT_NO |
| VC_INSTALLMENT_SCHEDULES | CLIENT_ACCOUNT_ID |
| VC_INSTALLMENT_SCHEDULES | USERID |
| VC_INSTALLMENT_SCHEDULES | INVOICE_NO |
| VC_INSTALLMENT_SCHEDULES | BILLING_GROUP_NO |
| VC_INSTALLMENT_SCHEDULES | CLIENT_BILLING_GROUP_ID |
| VC_INSTALLMENT_SCHEDULES | INSTALLMENT_TERM_NO |
| VC_INSTALLMENT_SCHEDULES | INSTALLMENT_CLIENT_TERM_ID |
| VC_INSTALLMENT_SCHEDULES | ALIGNED_MASTER_PLAN_INSTANCE_NO |
| VC_INSTALLMENT_SCHEDULES | ALIGNED_MASTER_CLIENT_PLAN_INSTANCE_ID |
| VC_INSTALLMENT_SCHEDULES | CHARGE_TRANSACTION_NO |
| VC_INSTALLMENT_SCHEDULES | PREVIOUS_INSTALLMENT_SCHEDULE_NO |
| VC_INSTALLMENT_SCHEDULES | NUMBER_OF_INSTALLMENTS |
| VC_INSTALLMENT_SCHEDULES | TOTAL_CHARGE_AMOUNT |
| VC_INSTALLMENT_SCHEDULES | TOTAL_TAX_AMOUNT |
| VC_INSTALLMENT_SCHEDULES | PAYMENT_STATUS_NO |
| VC_INSTALLMENT_SCHEDULES | STATUS_NO |
| VC_INSTALLMENT_SCHEDULES | STATUS_COMMENT |
| VC_INSTALLMENT_SCHEDULES | STATUS_UPDATED_TSTAMP |
| VC_INSTALLMENT_SCHEDULES | LUMP_SUM_ALLOCATION_TYPE_CD |
| VC_INSTALLMENT_SCHEDULES | LUMP_SUM_AMOUNT |
| VC_INSTALLMENT_SCHEDULES | LUMP_SUM_DAYS_TIL_NOTIFY |
| VC_INSTALLMENT_SCHEDULES | LUMP_SUM_DAYS_TIL_DUE |
| VC_INSTALLMENT_SCHEDULES | LUMP_SUM_IS_ALIGNED |
| VC_INSTALLMENT_SCHEDULES | IS_ALIGNED |
| VC_INSTALLMENT_SCHEDULES | CREATED_TSTAMP |
VM_INSTALLMENT_SCHEDULES
| Table Name | Column Name |
|---|---|
| VM_INSTALLMENT_SCHEDULES | CLIENT_NO |
| VM_INSTALLMENT_SCHEDULES | IS_DELETED |
| VM_INSTALLMENT_SCHEDULES | REF_PK |
| VM_INSTALLMENT_SCHEDULES | INSTALLMENT_NO |
| VM_INSTALLMENT_SCHEDULES | ACCOUNT_NO |
| VM_INSTALLMENT_SCHEDULES | CLIENT_ACCOUNT_ID |
| VM_INSTALLMENT_SCHEDULES | USERID |
| VM_INSTALLMENT_SCHEDULES | INVOICE_NO |
| VM_INSTALLMENT_SCHEDULES | BILLING_GROUP_NO |
| VM_INSTALLMENT_SCHEDULES | CLIENT_BILLING_GROUP_ID |
| VM_INSTALLMENT_SCHEDULES | INSTALLMENT_TERM_NO |
| VM_INSTALLMENT_SCHEDULES | INSTALLMENT_CLIENT_TERM_ID |
| VM_INSTALLMENT_SCHEDULES | ALIGNED_MASTER_PLAN_INSTANCE_NO |
| VM_INSTALLMENT_SCHEDULES | ALIGNED_MASTER_CLIENT_PLAN_INSTANCE_ID |
| VM_INSTALLMENT_SCHEDULES | CHARGE_TRANSACTION_NO |
| VM_INSTALLMENT_SCHEDULES | PREVIOUS_INSTALLMENT_SCHEDULE_NO |
| VM_INSTALLMENT_SCHEDULES | NUMBER_OF_INSTALLMENTS |
| VM_INSTALLMENT_SCHEDULES | TOTAL_CHARGE_AMOUNT |
| VM_INSTALLMENT_SCHEDULES | TOTAL_TAX_AMOUNT |
| VM_INSTALLMENT_SCHEDULES | PAYMENT_STATUS_NO |
| VM_INSTALLMENT_SCHEDULES | STATUS_NO |
| VM_INSTALLMENT_SCHEDULES | STATUS_COMMENT |
| VM_INSTALLMENT_SCHEDULES | STATUS_UPDATED_TSTAMP |
| VM_INSTALLMENT_SCHEDULES | LUMP_SUM_ALLOCATION_TYPE_CD |
| VM_INSTALLMENT_SCHEDULES | LUMP_SUM_AMOUNT |
| VM_INSTALLMENT_SCHEDULES | LUMP_SUM_DAYS_TIL_NOTIFY |
| VM_INSTALLMENT_SCHEDULES | LUMP_SUM_DAYS_TIL_DUE |
| VM_INSTALLMENT_SCHEDULES | LUMP_SUM_IS_ALIGNED |
| VM_INSTALLMENT_SCHEDULES | IS_ALIGNED |
| VM_INSTALLMENT_SCHEDULES | CREATED_TSTAMP |
| VM_INSTALLMENT_SCHEDULES | CREATED_BATCH_ID |
| VM_INSTALLMENT_SCHEDULES | CREATED_BATCH_TSTAMP |
| VM_INSTALLMENT_SCHEDULES | UPDATED_BATCH_ID |
| VM_INSTALLMENT_SCHEDULES | UPDATED_BATCH_TSTAMP |
Plan:NSO Ref Uses client_item_id Instead of client_sku—Bug Fix (EXTRACT-10291)
(Snowflake)
We were not exposing the client sku field in available_nonsubscription_offerings; as part of this ticket, we are adding client_sku to the tables below. The new structure will look like:
VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS
| Table Name | Column Name |
|---|---|
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | CLIENT_NO |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | BATCH_ID |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | CHG_ID |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | EVENT_TSTAMP |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | EVENT_ID |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | CREATETIME |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | ACTIONS |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | PLAN_NO |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | NONSUBSCRIPTION_OFFERING_NO |
| VC_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | CLIENT_SKU |
VM_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS
| Table Name | Column Name |
|---|---|
| VM_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | CLIENT_NO |
| VM_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | PLAN_NO |
| VM_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | NONSUBSCRIPTION_OFFERING_NO |
| VM_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | CLIENT_SKU |
| VM_PLAN_AVAILABLE_NONSUBSCRIPTION_OFFERINGS | CLIENT_NONSUBSCRIPTION_OFFERING_ID |
Credit Memo LOM changes for DEV-11788 (EXTRACT-10365)
(Data Feed, Universal Connector, Snowflake)
Added new fields to the credit memo object as part of the core upgrade done in DEV-11788.
Field Added in credit memo object
"period_end_date": "2026-05-07", "period_start_date": "2024-11-20", "supp_fields": [ { "field_name": "CM_Qual_Name", "field_value": "CM_Qual_Value" } ],
Snowflake changes
Field period_end_date and period_start_date will be part of
VC_CREDIT_MEMOS
VM_CREDIT_MEMOS
Aria created a new view to support the supp fields added to the credit memo LOM.
VC_CM_SUPP_FIELDS
| Table Name | Column Name |
|---|---|
| VC_CM_SUPP_FIELDS | CLIENT_NO |
| VC_CM_SUPP_FIELDS | BATCH_ID |
| VC_CM_SUPP_FIELDS | CHG_ID |
| VC_CM_SUPP_FIELDS | EVENT_TSTAMP |
| VC_CM_SUPP_FIELDS | EVENT_ID |
| VC_CM_SUPP_FIELDS | CREATETIME |
| VC_CM_SUPP_FIELDS | ACTIONS |
| VC_CM_SUPP_FIELDS | CREDIT_MEMO_NO |
| VC_CM_SUPP_FIELDS | FIELD_NAME |
| VC_CM_SUPP_FIELDS | FIELD_VALUE |
VM_CM_SUPP_FIELDS
| Table Name | Column Name |
|---|---|
| VM_CM_SUPP_FIELDS | CLIENT_NO |
| VM_CM_SUPP_FIELDS | CREDIT_MEMO_NO |
| VM_CM_SUPP_FIELDS | FIELD_NAME |
| VM_CM_SUPP_FIELDS | FIELD_VALUE |
Adding Transaction Qualifiers in Transaction Update Side Effect (EXTRACT-10470)
(Data Feed, Universal Connector)
When an API call alters an account transaction, the core feature adds qualifiers to the updated transaction. We do not have a separate event for transaction updates in data feeds, thus transaction qualifiers should be included in the transaction update side effect. Currently, we do not include qualifiers in transaction update sideeffect payload. As part of this change, we will include the SUPP fields in the update sideeffect payload.
Installment Term Attribute Cleanup/Parity With Installment Schedule (EXTRACT-10614)
(Data Feed, Universal Connector, Snowflake)
We made a few modifications to the Installment term LOM fields, which were deprecated and substituted with a new field name that aligned with the functionality.
remove/deprecate → replace with
- frequency => number_of_installments
- days_til_start => days_til_notify
- lump_sum.days => lump_sum.days_til_notify
- lump_sum.notification => lump_sum.is_aligned