Relationship Diagrams

Relationship diagrams serve as an introduction to the Gotransverse data model. The first two diagrams below provide a high-level overview of main data objects in the GTV platform. The remaining diagrams display key GTV views in the data lake and focus on a view’s relationship to other key objects and views. These diagrams allow you to further understand views and relationships to successfully build joins as you create your SQL queries.

Common Fields Found in Views

You can evaluate views by using Premier Data Access, including reviewing fields contained in views. There are several field types that are commonly found in the views. These fields include:

  • ID—All main objects and relations have an internal GTV ID. This ID is the primary key for these objects and is unique within a GTV instance.
  • Created_on/Updated_On—Audit fields on transactional tables that indicate when the row was created and when it was last updated.
  • Created_by/Updated_by—Audit fields on transactional tables that show the user who created a row and the user who updated a row. The user name system indicates that the create or update action was caused by a background process.
  • Occurred_on—Field related to dates that indicate the AR-related impact of a transaction. For example, the Invoice occurred_on is the invoice date. The payment occurred_on is the payment date relevant for impacting the account balance.

The transactions are sometimes allowed to be backdated and, in those cases, the created_on would be today, but the occurred_on could be 10 days ago.

GTV Platform Main Object Relations

The following diagram shows the logical relationships between the main data objects in the GTV platform.

GTV Customer/Billing Account Main Object Relations

The following diagram shows the logical relationships between the main data objects pertaining to GTV’s Customer Billing application.