Bimp data in BigQuery is available as views of the bimp_public dataset: directories (v_dim_*), facts (v_fact_*), cash views and calculated monthly balances. This reference describes every field of every view. Fields with the _guid suffix link tables, company_id is in every table, and exported_at, created_at, updated_at are technical dates, not business dates.
General rules for working with views
All Bimp data is available as views in the “bimp_public” dataset of the “Bimpsoft” project. The view and field names in this reference match those you see and use in queries, Looker Studio and Power BI. For connection, see BigQuery and Looker Studio and Power BI.
Rule
What it means
Fields with the _guid suffix
A unique identifier for linking to the corresponding directory. For example, “item_guid” links a fact to “v_dim_nomenclature”
“company_id”
Present in every table; the company identifier (for companies with several databases or branches)
“exported_at”, “created_at”, “updated_at”
Technical dates of export or record change, not a business date. For reports use “document_date” or “movement_date”
End-of-month balances
The “opening_” columns are values at the start of the month, “closing_” at the end. The current month is not filled in the calculated views because it is not finished
Batches
Product balances are kept by batches. If the company does not track batches, “batch_guid” is empty in all rows. If it does, aggregate by batches when you do not need the batch
Two currencies
In the cash views, “amount” and “_balance” are in the company’s base currency, and “_currency” is in the currency of the account or cash desk. Do not mix them in one sum
Prices
Updated once a day, the rest of the data more often. If a report shows an “old” price, first check “exported_at”
Which views are available
The “bimp_public” dataset contains directories (dimension), facts (fact), cash views and calculated views.
The “v_dim_nomenclature” view contains goods, services and their variants (characteristics). It is this view’s “item_guid” that is used in the fact views.
Field
Description
company_id
Company
item_guid
Unique identifier of a product or service (used in the fact views)
product_guid
Identifier of the base product (if the row is a variant or characteristic)
variant_guid
Identifier of the product variant (characteristic)
product_name
Name of the base product
variant_name
Name of the variant or characteristic
full_name
Full name (product + variant)
is_variant
This is a variant (characteristic), not a main product
Reason for the request or description of the fault
acceptance_date
Date the equipment was accepted for repair
completion_date
Repair completion date
return_date
Date the equipment was returned to the customer
item_guid
Product, spare part or service related to the repair
quantity
Quantity
order_guid
Linked order
order_date
Order date
order_number
Order number
order_type
Order document type
exported_at
Date the record was exported
v_fact_additional_costs: additional costs for sales
Field
Description
company_id
Company
document_guid
Additional costs document
item_guid
Product the cost is allocated to
batch_guid
Product batch
sales_document_guid
Sales document the cost is attributed to
movement_date
Operation date
cost_amount
Additional cost amount
exported_at
Date the record was exported
v_fact_service_costs: cost price of services
Field
Description
company_id
Company
document_guid
Base document
item_guid
Service or product
order_guid
Linked order
movement_date
Operation date
cost_amount
Cost price amount
exported_at
Date the record was exported
v_fact_stock_movements: product movements by warehouse
Field
Description
company_id
Company
movement_id
Unique identifier of the movement
document_guid
Base document of the movement
document_type
Document type
document_number
Document number
document_date
Document date
movement_date
Date and time of the product movement
warehouse_guid
Warehouse
item_guid
Product
batch_guid
Product batch
batch_name
Batch name
quantity
Movement quantity
amount
Movement amount
sign
Movement direction: receipt or write-off (+1 / −1)
exported_at
Date the record was exported
v_cash_movements: cash movements
The “v_cash_movements” view covers receipts and expenses on accounts and cash desks: payments, transfers between accounts and cash desks, receipt and repayment of loans and investments.
Field
Description
company_id
Company
movement_id
Row key: document_guid:row number
document_guid
Base document
document_type
Document type
document_number
Document number
document_date
Document date
movement_date
Movement date
account_guid
Account or cash desk
account_kind
bank_account or cash_desk
cash_type_guid
Cash type
cash_type_name
Cash type name
currency_guid
Currency
currency_code
Currency code per ISO 4217
amount
Amount in base currency
amount_currency
Amount in the currency of the account or cash desk
sign
Movement direction: receipt or expense (+1 / −1)
comment
Payment purpose
exported_at
Date the record was exported
v_customer_prices: prices for customers
The “v_customer_prices” view contains the current prices of products for each price list. It is a snapshot of current prices, not a history of changes: for each “product + price list” pair there is exactly one row with the latest price. The view is updated once a day at 02:00, so a price changed during the day appears the next night.
Field
Description
company_id
Company
item_guid
Product (for products with characteristics, the specific characteristic)
price_list_guid
Price list (link to v_customer_price)
price
Price
currency_code
Currency code per ISO 4217; taken from the price list
price_date
Date from which this price applies
exported_at
Moment the snapshot was taken, the same for all rows of one update
Calculated views are not exported from the accounting system directly: the rows are calculated by accumulating movements. The “v_dim_monthly_stock_balances” view shows product balances by warehouse at the start and end of each completed month.
Field
Description
company_id
Company
warehouse_guid
Warehouse
item_guid
Product
batch_guid
Product batch (empty if the company does not track batches)
month_start
First day of the month the row belongs to
net_quantity
Net movement of product quantity for the month
opening_balance
Quantity balance at the start of the month
closing_balance
Quantity balance at the end of the month
net_amount
Net movement of value for the month
opening_amount
Value of the balance at the start of the month
closing_amount
Value of the balance at the end of the month
average_cost
Cost price of a unit of the balance: closing_amount / closing_balance
calculated_at
Date the record was calculated
v_monthly_cash_balances: monthly cash balances
The “v_monthly_cash_balances” view shows turnovers and balances for each account or cash desk at the start and end of a completed month, in the base currency and in the account currency.
Field
Description
company_id
Company
account_guid
Account or cash desk
account_kind
bank_account or cash_desk
currency_code
Currency code per ISO 4217
month_start
First day of the month the row belongs to
net_amount
Turnover for the month in base currency
opening_balance
Balance at the start of the month
closing_balance
Balance at the end of the month
net_amount_currency
Turnover for the month in the account currency
opening_balance_currency
Balance at the start of the month in the account currency
closing_balance_currency
Balance at the end of the month in the account currency
calculated_at
Date the record was calculated
Which views are not described in the reference
Two views in the dataset have no field descriptions.
View
Note
v_fact_sales_enriched
A derived view on top of sales; the set of fields depends on its definition
test_whoami
Service view for checking access; contains no business data
FAQ
How do I link BigQuery tables to each other?
Through fields with the _guid suffix. For example, item_guid in v_fact_sales corresponds to item_guid in v_dim_nomenclature, and counterparty_guid corresponds to contractor_guid in v_dim_counterparties.
Why do the balance tables not include the current month?
Balances are calculated as of the end of the month, and the current month is not finished yet, so it is not filled in the calculated views.
Why is batch_guid empty?
If the company does not track batches, batch_guid is empty in all rows, which is normal. If it does, aggregate by batches when the batch is not needed in the report.
Why is the price in my report out of date?
Prices in v_customer_prices are updated once a day at 02:00, so a price changed during the day appears the next night. Check the exported_at field.
Why is average_cost empty?
In v_dim_monthly_stock_balances, average_cost is empty when closing_balance is zero: there is nothing to divide by. Filter by closing_balance != 0, not by average_cost IS NOT NULL.
Was this article helpful?Thanks for your feedback!