Customer
How customer, contract, and billing records are modeled in DPU.
Customer data covers who holds a contract at a service point, and the billing relationships that hang off it. Like metering data, it lands through the same file-based ingestion path (see Metering) and is then modeled into a dedicated set of tables.
What DPU models
business_partner— the customer record (name, identifiers)contract/contract_account— the agreements and billing accounts tied to a customerinstallation— links a contract to a physical service point
Where it ends up
Customer records are conformed into core_dim_customer, a slowly-changing (SCD2) dimension in the Core mart — one row per contract per version, so history is preserved as customers move in and out or accounts change. Rate classification (customer_class and related rate fields) is enriched onto this dimension from the service_agreement model at the same time.
A separate bridge table, core_int_sdp_occupant, resolves which customer occupied a given service point at any point in time — this is what lets consumption and exception data be attributed to the right customer even as occupancy changes.