Skip to content
  • There are no suggestions because the search field is empty.

BG_Effectivity_End

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

BG_Effectivity_End holds the end of the effectivity of a row in an Effectivity Satellite or Effectivity Link Satellite, mapped from the source. Use it for the date until which a business key or relationship is in effect. With Calculate Effectivity End From Begin, the result view shows the next BG_Effectivity_Begin instead.

Objects that carry it

Every Effectivity Satellite, Effectivity Link Satellite, Effectivity Business Satellite and Effectivity Business Link Satellite gets the term when it is created. The source, hashing, delta and loader views or procedures, the table and the result view carry it.

Value

Map the term to the source term with the end date. Calculate Effectivity End From Begin on the model object decides the value that the result view shows:

  • false (default): the value of the mapped source term. The term is part of BG_RowHash, so a changed end starts a new version.
  • true: the BG_Effectivity_Begin of the next row of the same Hub or Link key, ordered by BG_Effectivity_Begin. The last row gets the End of Universe. The calculated value replaces the mapped one, and validation reports warning ID-20004.

Generated versus result-view behavior

With Persist Validity false and Calculate Effectivity End From Begin true, the table stores the mapped value, and the result view calculates the end.

Data type

PlatformType
Microsoft SQL Server, Fabric Warehousedatetime2
OracleTIMESTAMP
Snowflake, Snowflake dbtTIMESTAMP_TZ
Databricks, Databricks dbt, Fabric Lakehousetimestamp

Example

The Effectivity Link Satellite load_loyaltycard_elsat on Microsoft SQL Server maps both effectivity terms to VALID_FROM and VALID_TO, with Calculate Effectivity End From Begin true and Persist Validity false. Its first load delivers cards 501 and 502, valid from 2026-01-01 to 2026-12-31. A later load renews card 501 from 2027-01-01 and ends card 502 on 2026-10-30. The result view shows:

CARD  BG_Effectivity_Begin  BG_Effectivity_End
501   2026-01-01            2027-01-01
501   2027-01-01            9999-12-31
502   2026-01-01            2026-01-01
502   2026-01-01            9999-12-31
  • The first row of card 501 ends at the begin of its renewal.
  • The second row of card 502 has the same begin as the first. The first row therefore ends at that begin, and the delivered end 2026-10-30 does not appear.

Related articles