--- title: "Template Base Types" canonical: "https://docs.vaultspeed.com/space/VPD/3364195117/Template%20Base%20Types" format: markdown --- ### Understanding Base Types and Dependency Visibility in Templates When you define a new template in VaultSpeed Studio, the first thing you need to pick is a **Base Type**. This choice sets a few key things: - How granular the output will be (e.g., one row per business key, per relationship, etc.) - What dependencies and Signature Objects you can use in your logic ### Understanding Base Types and Dependency Visibility in Templates When defining a new template in VaultSpeed Studio, you must select a **Base Type**. This Base Type determines: - The **expected granularity** of the target object (e.g., row-per-business-key, per relationship, etc.) - The **set of available dependencies** and Signature Objects you can reference in your template logic ### How to Explore Available Dependencies To inspect what Signature Objects and dependencies are available for a given Base Type: 1. **Create a temporary (dummy) template** 2. Add a to the dependency list 3. Open the dependency browser—this will show you all accessible objects, including: - Source metadata - System tables (like `LWT`, `LCI`, etc.) - **Signature Objects created by other templates **(see below for details) This step is especially important when chaining templates together—if you plan to **consume a Signature Object output from another template**, you'll need to verify it appears correctly in the dependency context of your current Base Type. ### Loading Metadata Once **FMC (Flow Management Control)** is activated, a set of technical metadata tables becomes available in the dependencies section. These tables contain detailed info on: - Load cycles - Windowing - Exceptions They're essential if your template needs to: - Work with orchestration logic - Track the current load status - Handle incremental logic properly > 📝 **Note:** These tables are **not available in every Base Type**. They're only included where they make sense. You’ll usually use them to: - Control time-bound or incremental loads - Reference load history or the current cycle’s metadata ### Signature Objects created by other templates **Signature Objects created by your templates become available for reuse in other templates**, as long as the **Base Type** they’re built on is compatible/available with the new template’s dependency context. In other words: - If Template A generates a Signature Object based on a specific Base Type - And Template B includes that Base Type as an allowed dependency - Then Template B will be able to see and reference that Signature Object in its dependency list This allows for **modular design** where one template’s output can seamlessly feed into the logic of another—supporting layered automation and consistent reuse across your VaultSpeed Studio projects. > 🔍 Tip: Use the dependency view in Studio to validate that upstream Signature Objects are correctly exposed when chaining templates. Understanding how to use these dependencies is key to writing robust, automation-ready templates for incremental loading. The list below is detailed per base type. > Macro (toc) # Data Vault Base Types ## 1. Hubs (HUB) ![image](media://0a462331-040a-4394-b19f-cd4e743eeb1d) ### 1.1. Dependent Objects: - BVV_HUB - SAT(SAT$) - BVV_SAT(BVV_SAT$) - RTS - BVV_RTS - PIT(PIT$) - SAT on PIT(PITSAT$) ### 1.2. Usage Used to build objects of the same granularity as a HUB Example: View on the hub, Pit object, …. ## 2. Satellites on Hubs(SAT) ### 2.1. Dependent objects: ![image](media://453fc831-0c88-4b85-a7cb-15b061a75d3e) - HUB - BVV_HUB - BVV_SAT ### 2.2. Usage Used to build objects of the same granularity as an SAT Example: Effectivity Sat, Calculated Sat, …. ## 3. Object-Based Links (LND) ### 3.1. Dependent objects: ![image](media://fed62577-f6c5-43cc-9e7d-9644a1cfe107) - BVV_LND - LDS(LDS$) - BVV_LDS(BVV_LDS$) - RTS - BVV_RTS - HUB(HUB_FK$) - BVV_HUB(BVV_HUB_FK$) - PIT(PIT$) - LDS(PITSAT$) ### 3.2. Usage Used to build objects of the same granularity as an LND Example: View on LND, Pit object, …. ## 4. Satellites on Object-Based Links (LDS) ### 4.1. Dependent Objects: ![image](media://39997d24-71bb-4206-9521-1eba15a23d76) - LND - BVV_LND - BVV_LDS ### 4.2. Usage Used to build objects of the same granularity as an LDS Example: Effectivity Sat, Calculated Sat, …. ## 5. Relationship Based Links (LNK) ### 5.1. Dependent Objects: ![image](media://f31d873d-4c3f-42d7-a7c3-ef37dc52634e) - BVV_LNK - LKS(LKS$) - BVV_LKS(BVV_LKS$) - RTS - HUB (HUB_PK) - BVV_HUB (BVV_HUB_PK) - HUB (HUB_FK) - BVV_HUB (BVV_HUB_FK) - SAT(SAT_PK$) - BVV_SAT(BVV_SAT_PK$) - SAT(SAT_FK$) - BVV_SAT(BVV_SAT_FK$) - PIT(PIT$) - LKS on PIT(PITLKS$) ### 5.2. Usage Used to build objects of the same granularity as an LNK Example: View on LNK, Pit object, …. ## 6. Satellites on Relationship-Based Links (LKS) ### 6.1. Dependent Objects: ![image](media://beed2793-12b6-4d31-8380-a8b26d254bf9) - LNK - BVV_LNK - BVV_LKS ### 6.2. Usage Used to build objects of the same granularity as an LKS Example: Effectivity Sat, Calculated Sat, …. ## 7. Non-historized Link (NHL) ![image](media://226bbcec-6274-4255-9029-e0623cdef36b) ### 7.1. Dependent Objects: - HUB(HUB_FK$) - BVV_HUB(BVV_HUB_FK$) - BVV_NHL ### 7.2. Usage Used to build objects of the same granularity as an NHL Example: View on NHL ## 8. Record Tracking Satellite (RTS) ![image](media://4beff199-f15c-40a5-bb20-91255d2e1529) ### 8.1. Dependent Objects: - BVV_RTS - HUB - BVV_HUB - LNK - BVV_LNK - LND - BVV_LND ### 8.2. Usage Used to build objects of the same granularity as an RTS Example: View on RTS ## 9. Reference Tables (REF) ![image](media://c539fe15-e109-48ba-82f7-5b92b97ee7b8) ### 9.1. Dependent Objects: - BVV_REF ### 9.2. Usage Used to build objects of the same granularity as a REF Example: View on REF # Business Vault Base Types ## 1. Business view HUBS (BVV_HUB) ![image](media://0a462331-040a-4394-b19f-cd4e743eeb1d) ### 1.1. Dependent Objects: - HUB - SAT(SAT$) - BVV_SAT(BVV_SAT$) - RTS - BVV_RTS - PIT(PIT$) - SAT on PIT(PITBVV_SAT$) ### 1.2. Usage Used to build objects of the same granularity as a Business View HUB Example: View on the Business View hub, Pit object, …. ## 2. Business View Satellites on Hubs (BVV_SAT) ### 2.1. Dependent Objects: ![image](media://453fc831-0c88-4b85-a7cb-15b061a75d3e) - HUB - BVV_HUB - SAT ### 2.2. Usage Used to build objects of the same granularity as a Business View SAT Example: Effectivity Sat, Calculated Sat, …. ## 3. Business View Object-Based Links (BVV_LND) ### 3.1. Dependent Objects: ![image](media://fed62577-f6c5-43cc-9e7d-9644a1cfe107) - LND - LDS(LDS$) - BVV_LDS(BVV_LDS$) - RTS - BVV_RTS - HUB(HUB_FK$) - BVV_HUB(BVV_HUB_FK$) - PIT(PIT$) - LDS(PITBVV_LDS$) ### 3.2. Usage Used to build objects of the same granularity as a Business View LND Example: View on LND, Pit object, …. ## 4. Business View Satellites on Object-Based Links (BVV_LDS) ### 4.1. Dependent Objects: ![image](media://39997d24-71bb-4206-9521-1eba15a23d76) - LND - BVV_LND - LDS ### 4.2. Usage Used to build objects of the same granularity as Business View LDS Example: Effectivity Sat, Calculated Sat, …. ## 5. Business View Relationship-Based Links (BVV_LNK) ### 5.1. Dependent Objects: ![image](media://f31d873d-4c3f-42d7-a7c3-ef37dc52634e) - LNK - LKS(LKS$) - BVV_LKS(BVV_LKS$) - RTS - HUB (HUB_PK) - BVV_HUB (BVV_HUB_PK) - HUB (HUB_FK) - BVV_HUB (BVV_HUB_FK) - SAT(SAT_PK$) - BVV_SAT(BVV_SAT_PK$) - SAT(SAT_FK$) - BVV_SAT(BVV_SAT_FK$) - PIT(PIT$) - LKS on PIT(PITBVV_LKS$) ### 5.2. Usage Used to build objects of the same granularity as a Business View LNK Example: View on LNK, Pit object, …. ## 6. Business View Satellites on Relationship-Based Links (BVV_LKS) ### 6.1. Dependent Objects: ![image](media://beed2793-12b6-4d31-8380-a8b26d254bf9) - LNK - BVV_LNK - LKS ### 6.2. Usage Used to build objects of the same granularity as a Business View LKS Example: Effectivity Sat, Calculated Sat, …. ## 7. Business View Non-historized Link (BVV_NHL) ![image](media://226bbcec-6274-4255-9029-e0623cdef36b) ### 7.1. Dependent Objects: - HUB(HUB_FK$) - BVV_HUB(BVV_HUB_FK$) - NHL ### 7.2. Usage Used to build objects of the same granularity as a Business View NHL Example: View on NHL ## 8. Business View Record Tracking Satellite (BVV_RTS) ![image](media://4beff199-f15c-40a5-bb20-91255d2e1529) ### 8.1. Dependent Objects: - RTS - HUB - BVV_HUB - LNK - BVV_LNK - LND - BVV_LND ### 8.2. Usage Used to build objects of the same granularity as a Business View RTS Example: View on RTS ## 9. Business View Reference Tables (BVV_REF) ![image](media://c539fe15-e109-48ba-82f7-5b92b97ee7b8) ### 9.1. Dependent Objects: - REF ### 9.2. Usage Used to build objects of the same granularity as a Business View REF Example: View on REF ## 10. Links Across Sources (LNA) ![image](media://ca5aab12-468a-4e2e-a726-994559e24939) ### 10.1. Dependent Objects: - LAS(LAS$) - HUB(HUB_PK) - BVV_HUB(BVV_HUB_PK) - HUB(HUB_FK) - BVV_HUB(BVV_HUB_FK) - SAT(SAT_PK$) - BVV_SAT(BVV_SAT_PK$) - SAT(SAT_FK$) - BVV_SAT(BVV_SAT_FK$) ### 10.2. Usage Used to build objects of the same granularity as a LNA Example: View on LNA ## 11. Satellites on Links Across Sources (LAS) ### 11.1. Dependent Objects: ![image](media://de61eee3-657b-4499-81a1-4df8ef6eafde) - LNA ### 11.2. Usage Used to build objects of the same granularity as a LAS Example: Effectivity Sat, Calculated Sat, …. ## 12. Point in Time Table (PIT) ![image](media://c769381b-fa31-4e81-8b63-9aa682cfc951) ### 12.1. Dependent Objects: - HUB - BVV_HUB - LNK - BVV_LNK - LND - BVV_LND - SAT on PIT(SAT$) - BVV_SAT on PIT(BVV_SAT$) - LKS on PIT(LKS$) - BVV_LKS on PIT(BVV_LKS$) - LDS on PIT (LDS$) - BVV_LDS on PIT(BVV_LDS$) ### 12.2. Usage Used to build objects of the same granularity as a PIT Example: Pit, View on PIT, Dimension, … ## 13. Bridge Table (BRIDGE) ![image](media://797dfce0-12d0-4a8a-af18-4c8288b644e9) ### 13.1. Dependent Objects: - HUB (DVO$) - BVV_HUB (DVO$) - LNK (DVO$) - BVV_LNK (DVO$) - LND (DVO$) - BVV_LND (DVO$) - NHL (DVO$) - BVV_NHL (DVO$) - LNA (DVO$) - SAT (SAT$) - BVV_SAT (SAT$) - LKS (SAT$) - BVV_LKS (SAT$) - LDS (SAT$) - BVV_LDS (SAT$) - LAS (SAT$) - PIT(PIT$) - SAT on PIT(PITSAT$) - BVV_SAT on PIT(PITSAT$) - LKS on PIT (PITSAT$) - BVV_LKS on PIT(PITSAT$) - LDS on PIT (PITSAT$) - BVV_LDS on PIT(PITSAT$) ### 13.2. Usage Used to build objects of the same granularity as a bridge Example: Bridge, View on Bridge, Fact, … # FMC Loading tables Available dependencies in most Signature Objects within VaultSpeed Studio. These dependencies are typically used to enrich logic templates with load metadata, historical context, or exception-handling capabilities during automation. When designing templates in VaultSpeed Studio, the following system tables are commonly available as dependencies for most Signature Objects. These tables support advanced automation logic by providing metadata about load windows, cycle tracking, and exceptions. ## FMC_LOADING_WINDOW_TABLE (LWT) Provides the active load window for raw layer loads. Use this to determine the valid time frame for the current data load cycle. Use case: Join on HUB or SAT to load only records within the current processing window. ## LOAD_CYCLE_INFO (LCI) Tracks metadata about each load cycle, including start and end times, status, and execution context for raw layer loads. Use case: Use in transformation logic to control or audit based on specific load cycles or retry behaviors. ## MTD_EXCEPTION_RECORDS (MEX) Contains records that were flagged as exceptions during metadata-driven transformations (MTD). Use case: Reference this table to isolate or filter out failed or problematic records in retry logic or quality checks. ## FMC_BV_LOADING_WINDOW_TABLE (BVLWT) Similar to LWT, but specific to the Business Vault layer. Provides the load window for business-layer logic templates. Use case: Used in BDV transformations to limit the processing to a specific business-defined window. ## LOAD_CYCLE_INFO (BVLCI) The Business Vault equivalent of LCI. Tracks the load cycle details for Business Vault processes. Use case: Helpful for tracing business logic executions, managing load dependencies between raw and business vaults. ## DV_LOAD_CYCLE_INFO (DVLCI) Extended version of load cycle tracking specific to Data Vault end-to-end loads. Use case: Use this for broader orchestration logic, e.g., PIT/Bridge creation, where combined historical and business views are needed. ## FMC_LOADING_HISTORY (FMCH) Stores historical records of past load executions, including timestamps and success status. Use case: Enables audit trails and historical performance checks, useful for conditional logic or performance benchmarking.