Customer.Details

Purpose

The Customer Details view serves as a unified source for basic business customer information, accessible across departments for consistent reporting and analysis. It excludes transactional data (like dates or measures) and provides a limited set of dimensional attributes, designed for integration with fact tables in reporting scenarios.

Use Case

Owner: Data Engineering
Typical Use Case: Supports cross-departmental applications requiring consistent and reliable customer data for integration with fact tables and reporting systems.
Style: Dimension, A single row per Customer ID with standardised dimensional attributes.

Source & Aggregation

DIM_COMPANY_CUSTOMER_OL

Join Table: ifs.DIM_CUSTOMER_OL to supplement details, ensuring enriched dimensional data by matching on the code field.

DataMarts Integration

This view can be utilised across the following DataMarts:

• Company
• Customer

Sample Exec

For sample data execution, use the code:

EXEC get.myView @dataMart = 'Customer', @viewName = 'Details', @token = '<myToken>', @version = '<202404>'

Response

COMPANY: The customer’s associated company.
CUSTOMER_ID (CODE): Unique identifier for each customer.

Description

CUSTOMER_NAME: Name of the customer.
Customer_Title: A truncated (40-character limit) customer title, combining CODE and CUSTOMER_NAME with an ellipsis if it exceeds 40 characters.

Customer Category (JSON Format)

PAY_TERM: Payment term code and description.
VAT: VAT code and description, providing taxation details.

Codes (JSON Format)

COUNTRY: Customer's country code and description.
GROUP: Customer group code and description for segmenting customers.
CORPORATE_FORM: Corporate form code and description, indicating business structure.
ASSOCIATION_NO: Association number, providing an additional identification layer if applicable.

SQL Code

To access the full SQL structure, refer to…

BMT-DWH-DEV/Customer_Details.sql