---
title: "PIT Objects"
canonical: "https://docs.vaultspeed.com/space/VPD/3013246979/PIT%20Objects"
format: markdown
---
**Table of Contents**

> Macro (toc)

## The PIT Objects Screen

The **PIT Objects screen** consists of three tabs:

- **PIT Templates** – Displays all **Point-in-Time (PIT) configurations** created. Users can **create, modify, and manage PIT templates**.
- **DV Objects** – Lists all **Data Vault (DV) objects** and their assigned **PIT configurations**. Users can **view and assign PIT configurations** to DV objects.
- **Business Views** – Lists all **Business Views** and their assigned **PIT configurations**. Users can **view and assign PIT configurations** to Business Views.

## PIT Templates

VaultSpeed uses **PIT templates**, which can be assigned to multiple Data Vault objects simultaneously. These templates are essential for managing **Point-in-Time (PIT) configurations** efficiently across multiple objects.

> ℹ️ #### **Important Notice**
> ℹ️ 
> ℹ️ When incorporating **multi-active satellites** into PIT object creation, **data duplication may occur**. This duplication is expected due to the nature of multi-active satellites but may cause confusion.
> ℹ️ 
> ℹ️ Including multi-active satellites in the scope will **increase the number of records** in the PIT table, as **one date can correspond to multiple records in the satellite tables**.
> ℹ️ 
> ℹ️ Users should be aware of this behavior when configuring PIT objects with multi-active satellites.

## Creating a PIT Template

To create a **PIT Template**, click the **"+ PIT Template"** button at the top right. In the **"Add PIT Template"** menu, provide the following options:

#### **PIT Name**

The name of the PIT template. The final **PIT Object name** consists of:

- **Prefix** (based on the parameter `PIT_TABLE_PREFIX`)
- **PIT Template Name**
- **Abbreviated Data Vault Name** or **Abbreviated Business View Name**
- **Suffix** (based on the parameter `PIT_TABLE_SUFFIX`)

#### **PIT Type**

Select one of the following PIT types:

- **Snapshots** – Defines an interval for different points in time (e.g., monthly).
- **Detail** – Uses all timestamps found in the **Satellites' selected date column** as the Points-in-Time.

#### **Snapshot Interval**

Defines the snapshot frequency (**only for PIT Type: "Snapshot"**).

#### **Interval Unit**

Defines the unit for the snapshot interval (**only for PIT Type: "Snapshot"**). Options include:

- Second
- Minute
- Hour
- Day
- Week
- Month
- Year

#### **Timestamp Attribute Type**

Select the column used for interval processing:

- **LOAD_TIMESTAMP** – System-generated timestamp, recorded with each load cycle.
- **TRANS_TIMESTAMP** – CDC timestamp, written by your **Change Data Capture (CDC) system**.

If the parameter `USE_CDC_TS_AS_LOAD_DATES` is set to **Y**, only the `LOAD_TIMESTAMP` column can be used.

> 📝 If the parameter `USE_CDC_TS_AS_LOAD_DATES` is set to **Y**, the **LOAD_TIMESTAMP** column must be used. The **TRANS_TIMESTAMP** column will not be available for selection.

> ⚠️ **Important Notice:**
> ⚠️ 
> ⚠️ If you use **TRANS_TIMESTAMP** for loading a **snapshot-based PIT**, you **cannot re-load** it unless you account for potential data changes.
> ⚠️ 
> ⚠️ If late-arriving data is present, fully reloading a snapshot PIT based on **TRANS_TIMESTAMP** may result in different output values.

![image](media://ed949ba9-f642-4c87-b96a-142aa1820440)

The **PIT Template** will be shown in the list:

![image](media://251706d9-4ccb-4b06-b2c9-820a7418d51e)

> ℹ️ The final name of PIT Objects created from this template follows this format:
> ℹ️ 
> ℹ️ **PIT_TABLE_PREFIX** = `PIT` → `PIT_<Snapshot_Interval>_<Object_Name>`
> ℹ️ 
> ℹ️ For example, if `PIT_TABLE_PREFIX` is set to **PIT** and the snapshot interval is **monthly**, the resulting name will be:
> ℹ️ 
> ℹ️ `PIT_MONTHLY_<object_name>` (e.g., `PIT_MONTHLY_CUSTOMERS`).


Once the **PIT Template** is defined, select the objects to apply it to.

1. Open the **Actions menu** at the end of the record to view associated objects.
2. Use the **checkboxes** to select objects and click the **"Link"** button to assign them to the template.
3. To remove objects from the template, click the **"Unlink"** button.

![image](media://63cf977e-5e29-4bed-8daf-ebcffb71638d)


> ⚠️ ### **Attention Point: PIT on BVV_HUB**
> ⚠️ 
> ⚠️ When issuing a **Point-in-Time (PIT) table** on a **BVV_HUB**, all **Business Views on the related SATs must be enabled**.
> ⚠️ 
> ⚠️ VaultSpeed assumes these Business Views exist when generating the PIT loading process. If they are not included in the release, the PIT load process may fail or produce incomplete data.
> ⚠️ 
> ⚠️ To prevent issues, verify that all related Business Views on SATs are enabled and included in the current release before executing a PIT on a **BVV_HUB**.

## Data Vault Objects and Business Views

These windows provide an overview of all **Data Vault objects** and **Business Views**, along with their assigned **PIT configurations**.

- Each object displays the number of **PIT Templates** it is assigned to.
- Clicking on an object shows a **detailed list** of all its assigned **PIT Templates**.

![image](media://f9578c9f-f08c-4406-9eab-b8e880db648b)

![image](media://f1c3bbf5-ef9f-47f6-86cd-1eebbce3c815)

At the top right, you also have two buttons:

- **"+ Add Objects to PITs"** – Add one or multiple objects to an existing PIT Template. Select the objects from the dropdown and assign them to a PIT template.

![image](media://7134650c-0007-4ceb-aa64-2f337f5a0d96)

- **"Remove Objects From all PITs"** – Removes selected objects from **all assigned PIT templates**. Use the **dropdown** to select the objects, then click **"Remove"** to unlink them from all PIT associations.

![image](media://47dbebdf-d729-4314-aa6a-ddff61909497)

### **PIT Naming Strategy**

The **PIT name** follows this structure:

- **PIT Table Name**
  - **Prefix**: Defined by the `pit_table_prefix` parameter.
  - **PIT Template Name**
  - **Object Name**:
    - If `pit_prefix = Y` → **Data Vault object** (full name, with prefix/suffix removed) or **Business View** (abbreviated name).
    - If `pit_prefix = N` → Uses `pit_table_name`.
  - **Suffix**: Defined by the `pit_table_suffix` parameter.