This view records actual visit activities performed by sales representatives. It provides detailed logs of each visit attempt including time, outcome, and failure reasons when applicable.
NotOrderCouse = 0 indicates a successful visit that resulted in an order.NotOrderCouse <> 0 indicates a failed visit with a reason code.This view represents the field execution layer of customer visits. It captures actual sales activities performed by representatives and connects them to planning, sales outcomes, and downstream business processes including financial performance, logistics, and customer behavior analysis.
| Related View | Join Keys | Description |
|---|---|---|
| SellerVisitPathCustomersView | SellerID, CustID, VisitDate | Compares planned vs actual visits to measure execution accuracy, route adherence, and field productivity. |
| CustAssignToSeller | SellerID, CustID | Validates whether executed visits align with assigned territories and ownership structure. |
| SalesInvoiceView | SellerID, CustID (indirect via Visit outcome) | Measures conversion impact of visits on actual sales generation (visit → order pipeline relationship). |
| OrderFinancialSummaryView | CustID (indirect), SellerID | Analyzes financial impact of customer visits including revenue generation and order value trends. |
| OrderCollectionAnalyticsView | CustID (indirect) | Evaluates whether visit frequency improves payment behavior and reduces overdue balances. |
| OrderReturnSummaryView | CustID (indirect) | Correlates visit activity with return behavior and product dissatisfaction signals. |
| CustomerPotentialAnalyticsView | CustID | Measures how execution intensity influences customer potential score and engagement level. |
| DeliveryOperationAnalyticsView | SellerID, CustID (indirect chain) | Links downstream logistics performance with customer engagement patterns and visit outcomes. |
| InventoryView | Indirect via SalesInvoiceView | Connects visit outcomes to demand generation and resulting inventory consumption patterns. |
| CustomerVisitLogsView (Current) | AID, SellerID, CustID | Core execution fact capturing real customer visits, outcomes, timing, and success/failure reasons. |
SellerID → Field force performance and productivity measurementCustID → Customer engagement and interaction historyVisitDate → Temporal alignment with planning and sales cyclesAID → Unique visit execution identifier (event-level grain)NotOrderCouse → Conversion efficiency signal (visit → order success rate)
VisitDate is stored as a STRING in format YYYY/MM/DD (not DateTime).
StartTime and EndTime are stored as STRING values in format HH:MM:SS.
This view represents actual executed visits. It must be used together with visit planning views to compare planned vs actual performance.