This view represents the daily visit planning structure for sales representatives. It defines which customers are scheduled to be visited by each salesperson on specific dates.
SellerID + CustID + PathDate forms the logical unique key.This view represents planned sales visit routes and acts as a scheduling layer for salesperson-customer interactions. It can be connected to execution, sales, and performance views to compare planned vs actual activity.
| Related View | Join Keys | Description |
|---|---|---|
| CustAssignToSeller | SellerID, CustID | Validates customer ownership and assignment rules against planned visit routes. |
| CustomerPotentialAnalyticsView | CustID | Helps prioritize visit planning based on customer potential score, churn risk and opportunity value. |
| CustomerVisitLogsView | SellerID, CustID | Compares planned visits with actual visit execution logs to measure route effectiveness. |
| SalesInvoiceView | SellerID, CustID | Links visit planning with actual sales performance and invoice generation outcomes. |
| OrderFinancialSummaryView | CustID, SellerID | Analyzes financial impact of planned customer visits on order value and revenue generation. |
| OrderReturnSummaryView | CustID, SellerID | Evaluates whether visited customers generate higher return rates or product issues. |
| OrderCollectionAnalyticsView | CustID | Correlates visit planning with payment behavior and collection efficiency. |
| SellerVisitPathCustomersView (Current) | SellerID, CustID, PathDate | Core planning dataset defining which customers are assigned to each salesperson per scheduled date. |
SellerID → Salesperson ownership, routing and performance trackingCustID → Customer targeting, segmentation and engagement analysisPathDate → Temporal planning vs execution comparisonSellerID + CustID → Behavioral consistency between planning and actual sales| Field | Type | Description |
|---|---|---|
| SellerID | int | Identifier of the sales representative. |
| CustID | int | Identifier of the customer scheduled for visit. |
| PathDate | string | Planned visit date in YYYY/MM/DD format. |
PathDate is stored as a string in the format YYYY/MM/DD.
It is not a DateTime type and must be converted before performing date operations or filtering.
This view represents planned activities only. Actual execution and visit outcomes are stored in separate operational datasets.