Scheduled collections fact table
bi_factscheduledcollections
Field | Field Type | Description | PrimaryKey | MappedDimensionTable DimensionTableField | |
|---|---|---|---|---|---|
centerwid | bigint | A unique identifier for the center, generated in Centre dimension(Bi_DimCentre). | Bi_DimCenter Centerwid | ||
collectedamount | float8 | amount collected | |||
collecteddateincenter | date | date on which amount is collected | |||
collecteddatetimeincenter | timestamp | date and time on which amount is collected | |||
collectionamount | float8 | amount to be collected | |||
collectiondateincenter | date | date on which amount is expected to be collected | |||
collectionsource | varchar(200) | This field tells if amount is collected manually/online/etc | |||
collectionstatus | varchar(200) | Status of scheduled collection | |||
considerinfinancials | boolean | This flag indicates whether the custom payment method should be considered in the sales or collections reports. This is a flag in the core system under Admin > Categories > Custom Payments. - True indicates that the custom payment method should be considered in the financial reports. - False indicates that the custom payment method should not be considered in the financial reports | |||
createddateincenter | date | date on which schedule is created | |||
createddatetimeincenter | timestamp | date and time on which schedule is created | |||
custompaymentname | varchar(800) | For custom payments, the name of the custom payment method gets populated in the custom payment name field. If the appropriate option isn't there, the user can enter the information in the Custom payment additional details field | |||
etlcreatedby | bigint | unique identfier in Table. Exists only in Analytics | |||
etlcreateddate | timestamp | Latest timestamp at which the corresponding record was either inserted or updated in this table. | |||
factsegmentid | bigint | Unique identifier for the row in the table | Yes | ||
invoiceid | varchar(36) | A unique identifier for the invoice. It is unique within the organization. | |||
lasttriedon | date | latest date on which collection is attempted | |||
nexttryat | date | upcoming date for scheduled collection. In case payment is to be made monthly, you will have one row each for all future payments with future collection date of each month for each row. In case payments fail or fall into "pending" status, Next Try at date still shoes original collection date | |||
organizationid | varchar(36) | A unique identifier for the organition for which this data belongs | Bi_DimCenter OrganizationId | ||
paymentoptiontype | varchar(200) | For card payments, the type of card gets populated here. For cheque payments, the name of the cheque gets populated here | |||
podid | bigint | Unique identifier for the POD on which customer data is hosted | |||
podname | varchar(20) | Internal to the ETL, says from which POD data is being synced the table | |||
scheduledcollectionpk | bigint | A unique identifier for every collection at the most granular level in this table. This is generated in Analytics, it does not exist in the core system | |||
scheduledcollectionwid | bigint | Unique identifier for the row in the table | |||
scheduledpaymenttype | varchar(200) | type of payment used to make payment | |||
userwid | bigint | A unique identifier for the guest. This is a non-blank value that gets populated for every guest | Bi_Dimuser userwid | ||
void | boolean | Indicates if the row should be inserted or deleted. 1- delete, 0-insert | |||
groupid | Internal to Zenoti. Used for data processing. | BIGINT | |||