Skip to content
Contact us Go to Customer Portal
  • There are no suggestions because the search field is empty.

Business Current View

Applies to
Platform: Microsoft SQL Server · Snowflake · Snowflake dbt · Databricks · Databricks dbt · Fabric Lakehouse · Fabric Warehouse · Oracle
Architecture: Data Vault

A Business Current View shows the current values of the satellites of a Hub or Link, one row per key, as a view in the Business Vault layer. It works like a Current View and can also read Business Vault Hubs, Links, satellites and Business PITs. Use it to give marts or Vault Out the latest state of raw and business data in one view.

Sources and relationships

A Business Current View has exactly one dataflow with one dataflow set and no relationships. The dataflow set contains:

The satellites can be Satellites, Link Satellites, Business Satellites, Business Link Satellites and the four Effectivity satellite types. Vault Out can read a Business Current View.

Create the model object

There is no wizard. Create a model object of type Business Current View in the Business Vault layer, create a dataflow set, add the source model objects and map the terms you want to show: usually the hash key and business keys of the Hub or Link and the descriptive terms of the satellites. You do not write join expressions; the generator builds the joins. A filter expression of the dataflow set is added to the view.

How the view finds the current values

  • With a PIT: the view reads the rows of the PIT result view that are valid until the End of Universe, one per key. It joins the Hub or Link on the PIT key and each satellite table on the satellite key and BG_ValidFromTimestamp that the PIT row references. A satellite without a version at that point contributes the values of its unknown-member row.
  • Without a PIT: the view joins the Hub or Link result view with the satellite result view on the key and keeps the satellite version that is valid until the End of Universe. A key without a satellite version does not appear.

Properties

A Business Current View has no Default Terms.

Generated objects

On Microsoft SQL Server, a Business Current View generates one object, the view BDV_Current_<model object name> in the Business Vault schema, where <model object name> stands for the name of the model object. Its target object role is Result.

  • There is no source view, loader or table, and no unknown-member row.
  • The view exists also when the project property Create Result Views is false.
  • It reads the PIT or Business PIT result view, the Hub or Link result view and, with a PIT, the satellite tables or, without a PIT, the satellite result view.

A load does not run the view. It shows the data after these objects are loaded:

Hub or Link, satellites -> PIT (optional)
  -> BDV_Current_<model object name>

Example

The Business Current View based_on_hub_with_pit_bcv on Microsoft SQL Server reads the PIT customer_based_on_hub, the Hub load_customer_hub and the two Satellites of the PIT. load_customer_sat holds the customer name, and load_caching_hashing holds the address. The view maps them to its own terms, which this example names in lowercase, such as customer_id, customer, address_line1 and zip_code. The loads deliver these customers:

  • Load 1 on 2026-10-28 08:00: customer 1 Contoso Ltd at Bahnhofstrasse 1, 8001, and customer 2 Fabrikam AG at Unter den Linden 5, 10117.
  • Load 2 on 2026-10-29 08:00: customer 1 is renamed to Contoso Group, and customer 3 Northwind at Graben 10, 1010, arrives.
  • Load 3 on 2026-10-30 08:00: customer 1 moves to Hardturmstrasse 100, 8005.
  • Load 4 on 2026-10-31 08:00: no change.

Check the result

Query the view, here in the Business Vault schema p2b:

SELECT customer_id, customer, address_line1, zip_code
FROM p2b.BDV_Current_based_on_hub_with_pit_bcv
ORDER BY customer_id;

This is the result after load 4:

customer_id  customer       address_line1        zip_code
1            Contoso Group  Hardturmstrasse 100  8005
2            Fabrikam AG    Unter den Linden 5   10117
3            Northwind      Graben 10            1010
  • Customer 1 shows the name from load 2 and the address from load 3, the current version of each Satellite.
  • The view has one row per customer and uses the term names of the Business Current View.

Platform differences

  • Snowflake: names are in capitals. The dataflow property Warehouse Placeholder Variable Name applies.
  • Databricks and Fabric Lakehouse: the view name is in lowercase.
  • Databricks dbt and Snowflake dbt: the Business Current View becomes the dbt model bdv_current_<model object name>.
  • Fabric Warehouse: the same view as on Microsoft SQL Server, deployed by notebooks.
  • Oracle: names are in capitals.

Limitations

  • A Business Current View holds exactly one Hub, Link or Business Vault counterpart, and at most one PIT or Business PIT. Without a PIT it holds exactly one satellite. Validation reports an error otherwise.
  • When the view maps the DrivingKeyLink_HK of a Driving Key Link or Business Driving Key Link, it cannot read a PIT or Business PIT.
  • A Business Current View does not read Multi-Active, Record Tracking or Non-Historized satellites.

Related articles