Ship To Customer Dim
This dimension captures key information about Ship To Customers in the system, representing entities receiving shipments. It consolidates identifiers, status, types, warehouse associations, and modification dates to provide a comprehensive view of each customer destination for shipments.
| Output Column | Database Logic | Description |
|---|---|---|
| Ship To Customer Key | Unique identifier key for each Ship To Customer in the Ship To Customer data set. | This is the unique code used internally to identify each shipping destination customer, ensuring all data references the correct entity. |
| Ship To Customer Code | Code representing the Ship To Customer, used as a business reference for customers receiving shipments. | A customer-facing code that simplifies recognition and communication about the shipping destination. |
| Ship To Customer Status | Indicates the current operational status of the Ship To Customer (e.g., active, inactive). | Shows whether the shipping customer is currently active or inactive, helping manage active shipping destinations. |
| Ship To Customer Type | Categorization of the Ship To Customer by type for segmentation or operational purposes. | Defines the category or type for each shipping customer, aiding in classification and business analysis. |
| Warehouse | Identifies the warehouse associated with the Ship To Customer, indicating where shipments might be fulfilled or processed. | Links shipping customers to the warehouse locations, aiding logistics and supply chain decisions. |
| Deleted | Flag indicating if the Ship To Customer record has been marked as deleted or inactive in the system. | Shows whether the customer record has been removed or is no longer in use, keeping the data relevant. |
| Last Modified Datetime | Records the last date and time when the Ship To Customer information was updated. | Tracks the most recent update to customer information, ensuring data freshness and accuracy. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article