--- title: "Signature Attributes" canonical: "https://docs.vaultspeed.com/space/VPD/3496576910/Signature%20Attributes" format: markdown --- Signature Attributes in VaultSpeed act as **metadata tags** that inform the platform how to interpret and process source data during automation. Assigned through the **Source Editor**, they help VaultSpeed determine roles such as keys, indicators, timestamps, and lineage fields during code generation. The list below provides definitions and usage details for all supported Signature Attributes. > Macro (toc) # Signature Attributes linked to Functional Objects ## `BUSINESS_KEY` Used to flag the **business key attributes** that uniquely identify a record from a business perspective Can consist of **one or multiple columns** depending on the source table's primary identifier This is the core input used to generate **hash keys** in HUBs and to define relationships in links and bridges Configured via the **Source Editor**, typically during initial source setup Used in the following Signature Object Types: `HUB`, `BRIDGE`, `BVV` --- ## `BUSINESS_SRC_KEY` Used to replicate the **business key (BK) attributes** into the **Satellite (SAT)** structure Activated when the parameter `STORE_BK_FIELDS_IN_SAT` is set to **Y** for the table Allows for **direct traceability** of business identifiers within the satellite for auditing, filtering, or data validation purposes Can include **one or multiple attributes** per object, depending on the composite BK Used in the following Signature Object Types: `SAT`, `BVV_SAT` --- ## `CDC_LOGPOSITON` Used to capture the **log position or change tracking marker** from the source system in a CDC-enabled integration Represents a **unique and incrementing value** (e.g., SCN, LSN, offset) that allows VaultSpeed to determine the order and position of changes in the source stream Configuration is driven by parameters in the Source Editor or connection setup Used in the following Signature Object Types: `SAT`, `LKS`, `LDS`, `NHL`, `LAS`, `PIT`, `BVV` --- ## `CONCAT_BUSINESS_KEY` Used to identify the **concatenated representation of the business key attributes** for a given object This attribute is generated when the business key consists of **multiple columns**, and VaultSpeed combines them into a single string for **hashing, identification, and uniqueness enforcement** Always a **unique attribute per object**, regardless of how many components are in the original business key Configuration is managed in the **Data Vaults → HUB Management → Business Key screen** Used in the following Signature Object Types: `HUB`, `BRIDGE`, `BVV` --- ## `DELETE_FLAG` Used to indicate whether a record has been **logically deleted** in the source system VaultSpeed **automatically creates** this attribute when deletion tracking is enabled through parameter configuration It allows the system to identify and process deletions during data loading, especially in **soft delete** scenarios Used in the following Signature Object Types: `LDS`, `LAS`, `LKS`, `BVV`, `SAT` --- ## `FOREIGN_KEY` Used to flag attributes that act as **foreign keys**, establishing relationships between entities in the source model These keys are either **harvested from source metadata** (e.g., database constraints) or **auto-created by VaultSpeed** when defining relationships in the Source Editor They help VaultSpeed generate the appropriate **link structures** in the Data Vault model Used in the following Signature Object Types: `NHL`, `SAT`, `BVV`, `LAS`, `LDS`, `LKS` --- ## `HASH_DIFF` Used to store the **hash value of descriptive attributes** in a Satellite (SAT) or similar structure VaultSpeed uses this hash to **detect changes** in attribute values over time for historization purposes By comparing `HASH_DIFF` values across load cycles, the system determines whether a new record should be inserted into the target Used in the following Signature Object Types: `SAT`, `LDS`, `BVV_SAT`, `BVV_LDS` --- ## `LOAD_CYCLE_ID` Represents the **unique identifier of a load cycle** during which a record was processed Used to **track and group records** that belong to the same ingestion run across various object types Supports **auditing, reconciliation, and runtime traceability** by linking records to a specific load event Automatically assigned during pipeline execution Used in the following Signature Object Types: `SAT`, `LNK`, `REF`, `LNA`, `LKS`, `MEX`, `LCI`, `FMCOH`, `LND`, `BVV`, `LAS`, `BVLCI`, `LDS`, `NHL`, `FMCH`, `HUB` --- ## `LOAD_END_TIMESTAMP` Used to define the **end of the record’s validity period** in the Raw Data Vault Paired with `LOAD_TIMESTAMP` or `LOAD_START_DATE` to enable **historization** and track changes over time Auto-calculated during delta processing and updates the closing point of a satellite record’s validity Used in the following Signature Object Types: `SAT`, `LKS`, `LAS`, `LDS`, `BVV` --- ## `LOAD_TIMESTAMP` Used to capture the **exact timestamp when the record was loaded** into the Raw Data Vault Crucial for **delta detection**, **data lineage**, and **historization logic** in satellites and other structures Auto-generated by VaultSpeed during pipeline execution Used in the following Signature Object Types: `SAT`, `LKS`, `LAS`, `LDS`, `BVV` --- ## `OBJECT_F_H_KEY` Represents the **foreign (target) hash key** in a relationship between objects Used to indicate the **destination** of a link, where the relationship is pointing to Assigned automatically by VaultSpeed when defining relationships in the Source Editor Used in the following Signature Object Types: `LNK`, `LND`, `NHL` --- ## `OBJECT_H_KEY` Represents the **hash key of the main business object** Used to uniquely identify records across structures such as HUBs, SATs, and links, enabling consistent key referencing Automatically generated by VaultSpeed during model creation based on business key definitions Used in the following Signature Object Types: `HUB`, `SAT`, `LNK`, `REF`, `LNA`, `LKS`, `MEX`, `LCI`, `FMCOH`, `LND`, `BVV`, `LAS`, `BVLCI`, `LDS`, `NHL`, `FMCH` --- ## `OBJECT_L_H_KEY` Used to identify the **Link Hash Key** that connects the object to a **link structure** in the Data Vault model This attribute is typically added to represent relationships between business keys Auto-generated when defining relationships in the Source Editor Used in the following Signature Object Types: `LNK`, `LND`, `NHL` --- ## `OBJECT_P_H_KEY` Represents the **primary (origin) hash key** in a relationship between objects Used to indicate the **source** of a link — the object from which the relationship originates Automatically assigned by VaultSpeed when relationships are defined in the Source Editor Used in the following Signature Object Types: `LNK`, `LND`, `NHL` --- ## `ORIG_SUBSEQUENCE_ATTRIBUTE` Used when a **subsequence attribute** is also affected by the `DATA_QUALITY_BAD` configuration VaultSpeed creates an additional column to store the **original, uncasted value** of the subsequence attribute, allowing for comparison in case of casting issues This ensures **traceability** and supports **data quality auditing** for ordering-critical attributes Used in the following Signature Object Types: `SAT`, `LDS`, `BVV_SAT`, `BVV_LDS` --- ## `OTHER_ATTR` Used to flag **descriptive (non-key, non-technical) attributes** in source tables These are the business context fields (e.g., name, address, status) that do not serve as keys or control columns VaultSpeed uses this flag to **include the attribute in SAT or LDS structures**, applying historization or overwrite logic depending on configuration Automatically assigned when attributes are not tagged with another Signature Attribute Used in the following Signature Object Types: `SAT`, `LDS`, `BVV_SAT`, `BVV_LDS` --- ## `OTHER_ATTR_ORG` Used when the `DATA_QUALITY_BAD` parameter is activated VaultSpeed adds an `_ORG` column to the SAT for each affected `CHAR`-based attribute to **store the original source value** in case of **casting or data type conversion errors** This ensures traceability and allows users to **compare the original and casted values**, which is crucial for **data quality validation and troubleshooting** Used in the following Signature Object Types: `SAT` --- ## `PRIMARY_KEY` Used to designate **primary key attributes** in the source model Supports metadata harvesting, dependency tracking, and automation logic Automatically detected when defined in source metadata or manually configured Used in the following Signature Object Types: `HUB`, `LNK`, `SAT`, `BVV` --- ## `RECORD_SOURCE` Indicates the **origin of the record**, such as the system, schema, or application name Enables **lineage tracking**, **auditing**, and transparency across the model Auto-filled during metadata harvesting or configurable manually Used in the following Signature Object Types: `HUB`, `SAT`, `LKS`, `LAS`, `BVV`, `NHL` --- ## `RECORD_TYPE` Reserved for **advanced use cases** where records need to be **categorized**, such as by status, operation type, or source condition Can be used to **filter or segment data** during loading, especially in flexible or multi-purpose staging scenarios This attribute is **not used by default** and must be explicitly configured in the Source Editor or mapping logic Used in the following Signature Object Types: `SAT`, `BVV` *(conditional use)* --- ## `SAT_LOAD_TIMESTAMP` Used to **reference the load timestamp of a Satellite (SAT)** when creating a **Point-in-Time (PIT)** structure VaultSpeed uses this attribute to **track the most recent record from each SAT** linked to a HUB or LNK at a given point in time Essential for building PITs that allow **time-travel-style querying** across multiple SATs Used in the following Signature Object Types: `PIT` --- ## `SNAPSHOT_TIMESTAMP` Used in a **Point-in-Time (PIT)** object to record the **snapshot moment** — the point at which the PIT was evaluated This timestamp indicates **when the PIT structure was created**, allowing consumers to understand the state of all linked SATs at that specific moment Essential for reproducibility and **temporal consistency** in analytics and reporting Used in the following Signature Object Types: `PIT` --- ## `SUBSEQUENCE_ATTRIBUTE` Used to flag an attribute as a **“subsequence attribute”** in the source setup These attributes are used to **order multiple changes** within the same load cycle for a given business key VaultSpeed uses them in the Raw Data Vault to **determine change sequencing** in SATs or LDS objects Used in the following Signature Object Types: `SAT`, `LDS`, `BVV_SAT`, `BVV_LDS` --- ## `TRANS_INDICATOR` Used to indicate whether a record is **transactional** in nature Helps VaultSpeed determine if **transaction-level delta detection** is needed Often used with `TRANS_TIMESTAMP` to define **the time of a transactional event** Configured via the **Source Editor** Used in the following Signature Object Types: `SAT`, `LKS`, `LAS`, `BVV` --- ## `TRANS_TIMESTAMP` Used to define the **timestamp of a transactional event** Often paired with `TRANS_INDICATOR` to track **event order** and apply **transaction-level delta logic** Configured via the **Source Editor** Used in the following Signature Object Types: `SAT`, `LKS`, `LAS`, `BVV` --- ## `UNIQUE_IDENTIFIER` Used to flag an attribute that provides a **globally unique technical identifier** Not used as a business key — intended for scenarios where a source record has a GUID or UUID Configured via the **Source Editor** Used in the following Signature Object Types: `SAT`, `BVV`, `LKS` # Signature Attributes linked to FMC loading tables ## `DV_LOAD_CYCLE_ID` Used to uniquely identify each **load cycle** in the FMC (Full Metadata Capture) process This attribute allows VaultSpeed to group all records processed in the same batch or window, enabling **auditing, traceability**, and **load tracking** Automatically generated during execution of loading windows Used in the following Signature Object Types: `DVLCI` --- ## `FMC_BEGIN_LW_SEQUENCE` Represents the **starting sequence number** for a specific loading window Used to define the **lower bound** of the data extraction range during a batch run Important for identifying **which records belong to a specific load cycle**, especially in change tracking or incremental loading logic Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT` --- ## `FMC_BEGIN_LW_TIMESTAMP` Represents the **start timestamp** of the loading window for a given batch execution Used to define the **lower time boundary** of the data extraction range Helps VaultSpeed determine which records were captured from the source during a specific load interval Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT` --- ## `FMC_END_LW_SEQUENCE` Represents the **ending sequence number** for a specific loading window Used to define the **upper bound** of the data extraction range during a batch run Together with `FMC_BEGIN_LW_SEQUENCE`, it allows VaultSpeed to **track which records fall within a given load cycle**, supporting accurate incremental loads Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT` --- ## `FMC_END_LW_TIMESTAMP` Represents the **end timestamp** of the loading window for a given batch execution Used to define the **upper time boundary** of the data extraction range Together with `FMC_BEGIN_LW_TIMESTAMP`, it enables VaultSpeed to filter and load only the records that fall within a specific time-based load interval Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT` --- ## `LOAD_END_DATE` Records the **end date** of a specific load execution window Used in both the **loading history table** and the **loading window table** to indicate when the load process completed Essential for **tracking load durations**, verifying successful completion, and supporting audit and monitoring processes Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT` --- ## `LOAD_START_DATE` Records the **start date** of a specific load execution window Used in both the **loading history table** and the **loading window table** to indicate when the load process began Helps with **auditing, scheduling accuracy**, and analyzing load durations over time Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT` --- ## `OBJECT_NAME` Used when VaultSpeed is configured to run **object-based loading windows** Stores the **name of the table or object** being processed within each load window This attribute helps track which source objects were included in a specific load run The column name is configurable in the Source Editor and automatically receives this Signature Attribute Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT` --- ## `PIPELINE_NAME` Used to specify the **name of the pipeline or load group** that processed the data Helps correlate records with pipeline definitions in orchestration or monitoring layers Configured automatically or via pipeline setup Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT` --- ## `RUN_ID` Used to uniquely identify a **specific execution instance** of a data pipeline or load cycle Supports traceability, logging, and audit across the VaultSpeed runtime and target platform Auto-generated during each pipeline run and tracked in loading history Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT`, `DVLCI` --- ## `SOURCE_SYSTEM_NAME` Used to store the **name of the source system** that delivered the business key or record Included by default in every **HUB** to enable **lineage tracking** and to distinguish identical business keys across different systems VaultSpeed assigns this attribute automatically, and it is typically named `SRC_BK` unless otherwise configured Used in the following Signature Object Types: `HUB`, `SAT`, `LNK`, `BVV`, `NHL` --- ## `SUCCESS_FLAG` Used in the **loading history table** to indicate whether a given load cycle completed **successfully** Set to true/false (or 1/0) to support **monitoring, troubleshooting**, and **audit reporting** Allows VaultSpeed and orchestration tools to **validate load integrity** and flag failed or incomplete runs Used in the following Signature Object Types: `FMCH`, `BVLWT`, `FMCOH`, `LWT`