Insyt data dictionary
Every column in the Raket Parts tables: what it means, the traps to watch for and the values it holds.
How to interpret column profiles
Different values reports observed distinct values in this dataset snapshot. It does not prove that a column is a unique key in future data, or that a combination of fields will be unique.
Never empty means no nulls were observed in the snapshot. Empty strings, invalid codes and future missing records may still need checks.
Before joining: state each table's grain, check key uniqueness, choose an appropriate join and reconcile counts and measures. For a worked order-line join, open the data catalogue.
- absence_refText, 1,805 different values. Never empty.The unique reference for one absence.absences
- employee_refText, 421 different values. Never empty.The employee who was absent, as an employee reference.Watch out: Some employees have many absences, so count distinct employee_ref when counting people.absences
- absence_typeText, 3 different values. Never empty.The kind of absence: annual leave, sick or parental.Watch out: Codes rather than names; annual leave dominates, so sick and parental totals are small by comparison.absences
- start_dateDate, 272 different values. Never empty.The date the absence started.absences
- end_dateDate, 333 different values. 0% empty.The date the absence ended.Watch out: A blank end date marks an absence still open, not one that ended on an unknown day.absences
- hoursDecimal number, 48 different values. 0% empty.The number of working hours the absence covers.Watch out: Blank and zero are different; two sick absences record zero hours, and parental leave runs to hundreds of hours.absences
- assignment_refText, 441 different values. Never empty.The unique reference for one job assignment.assignments
- employee_refText, 425 different values. Never empty.The employee holding the assignment, as an employee reference.Watch out: A few employees have more than one assignment row, so count distinct employee_ref for headcount.assignments
- unit_idText, 13 different values. Never empty.A code for the organisational unit the assignment belongs to.Watch out: Codes such as X-PRD-MAC have no names table in this data set.assignments
- function_idText, 9 different values. Never empty.A code for the job function of the assignment.Watch out: Codes F-01 to F-09 have no names table here; F-08 covers most rows.assignments
- position_titleText, 54 different values. Never empty.The job title for the assignment, such as CNC machinist.assignments
- effective_fromDate, 423 different values. Never empty.The date the assignment started.Watch out: Dates go back to 1998, so this is a start date, not a 2025 event date.assignments
- effective_toDate, 34 different values. 91% empty.The date the assignment ended.Watch out: A blank means the assignment is still current; filter on it to avoid counting ended assignments.assignments
- touch_refText, 6,400 different values. Never empty.The unique reference for one contact being touched by one campaign.campaign_touches
- campaign_refText, 7 different values. Never empty.Links each touch to its campaign in campaigns.Watch out: One campaign in campaigns has no touches in this table.campaign_touches
- contact_refText, 1,179 different values. Never empty.The marketing contact the touch was aimed at.Watch out: Contacts appear in several campaigns, so count distinct contact_ref for people reached.campaign_touches
- touch_kindText, 2 different values. Never empty.Whether the email was sent or suppressed for this contact.Watch out: SUPPRESSED rows are not emails sent, so counting every row overstates reach.campaign_touches
- occurred_dateDate, 7 different values. Never empty.The date the touch happened.Watch out: Only seven dates appear, one per campaign send, so it cannot show daily patterns.campaign_touches
- campaign_refText, 8 different values. Never empty.The unique reference for one marketing campaign.campaigns
- campaign_kindText, 6 different values. Never empty.The type of campaign, such as a catalogue mailing or trade fair follow-up.Watch out: Two kinds repeat across campaigns, so group by campaign_ref when you need one row each.campaigns
- channelText, one value. Never empty.The channel the campaign used.Watch out: Every campaign is EMAIL, so this column cannot split results.campaigns
- start_dateDate, 8 different values. Never empty.The date the campaign started.campaigns
- end_dateDate, 8 different values. Never empty.The date the campaign ended.Watch out: Some campaigns end after the last month of other data, so later results may be missing.campaigns
- budgetDecimal number, 8 different values. Never empty.The budget amount recorded for the campaign.Watch out: No currency is stored with the budget, and a budget is not the same as actual spend.campaigns
- credit_note_refText, 29 different values. Never empty.The unique reference for one credit note issued to a customer.credit_notes
- customer_refText, 25 different values. Never empty.Links the credit note to its customer in customers.credit_notes
- invoice_refText, 29 different values. Never empty.Links the credit note to the invoice it reduces in customer_invoices.credit_notes
- reasonText, 2 different values. Never empty.Why the credit note was issued, such as an accepted return.Watch out: Codes rather than text; all but one are RETURN_ACCEPTED.credit_notes
- amountDecimal number, 29 different values. Never empty.The value credited back to the customer.Watch out: Invoice totals do not include credits, so subtract these to get net sales.credit_notes
- issue_dateDate, 26 different values. Never empty.The date the credit note was issued.Watch out: It falls weeks after the invoice date, so a credit can land in a later month than the sale.credit_notes
- invoice_refText, 12,377 different values. Never empty.Links each line to its invoice in customer_invoices.Watch out: Repeats once per line, so joining to customer_invoices repeats net_amount on every line.customer_invoice_lines
- line_noWhole number, 7 different values. Never empty.The position of the line within its invoice.Watch out: Only unique together with invoice_ref.customer_invoice_lines
- product_refText, 2,574 different values. Never empty.Links the line to the product sold in products.customer_invoice_lines
- qtyWhole number, 40 different values. Never empty.The number of units invoiced on the line.customer_invoice_lines
- line_amountDecimal number, 17,930 different values. Never empty.The amount invoiced on the line.Watch out: Sum line_amount after a join, not the header net_amount, which repeats per line.customer_invoice_lines
- invoice_refText, 12,377 different values. Never empty.The unique reference for one customer invoice.customer_invoices
- customer_refText, 414 different values. Never empty.Links the invoice to its customer in customers.customer_invoices
- invoice_dateDate, 276 different values. Never empty.The date the invoice was issued.Watch out: Dates start in October 2024, so a calendar year 2025 view needs a filter.customer_invoices
- net_amountDecimal number, 11,830 different values. Never empty.The invoice total, equal to the sum of its lines' line_amount.Watch out: Credit notes are held separately, so this overstates sales after returns.customer_invoices
- customer_refText, 436 different values. Never empty.The unique reference for one customer.customers
- segmentText, 3 different values. Never empty.The customer group: university, industrial or rocket builder.Watch out: Only six rocket builders exist, so averages for that segment rest on very few customers.customers
- countryText, 17 different values. Never empty.The customer's country, as a two-letter code.Watch out: Codes rather than names, such as NL and DE.customers
- entity_tableText, 2 different values. Never empty.Which table the label belongs to: customers or suppliers.Watch out: Mixes two tables, so filter on it before joining.display_labels
- entity_refText, 468 different values. Never empty.The customer or supplier reference the label describes.Watch out: Two customers and one supplier have no label here, so an inner join drops them.display_labels
- labelText, 468 different values. Never empty.A readable name for the customer or supplier.Watch out: Lessons treat this table as restricted, so not every role may open it.display_labels
- employment_refText, 425 different values. Never empty.The unique reference for one employment record.employment_versions
- employee_refText, 425 different values. Never empty.The employee the employment record belongs to.employment_versions
- contract_typeText, 2 different values. Never empty.Whether the contract is permanent or fixed term.Watch out: Codes rather than names.employment_versions
- start_dateDate, 413 different values. Never empty.The date the employment started.Watch out: Dates go back to 1998, so this is not a 2025 hiring date for most staff.employment_versions
- end_dateDate, 23 different values. 95% empty.The date the employment ended.Watch out: A blank means the employment is still active.employment_versions
- contracted_hours_weekWhole number, 4 different values. Never empty.The hours per week the employee is contracted to work.employment_versions
- fteDecimal number, 4 different values. Never empty.The full-time equivalent of the contract, where 1.0 is full time.Watch out: Sum fte, not rows, when measuring staffing capacity.employment_versions
- statusText, 2 different values. Never empty.Whether the employment is active or ended.Watch out: Check it agrees with end_date before relying on either.employment_versions
- enquiry_refText, 328 different values. Never empty.The unique reference for one sales enquiry.enquiries
- contact_refText, 279 different values. Never empty.The marketing contact who made the enquiry.Watch out: Some contacts made several enquiries, so count distinct contact_ref for people.enquiries
- received_dateDate, 151 different values. Never empty.The date the enquiry was received.enquiries
- channelText, 3 different values. Never empty.How the enquiry arrived: phone, email or web form.enquiries
- qualification_statusText, 3 different values. Never empty.Whether the enquiry was judged qualified, not qualified or unknown.Watch out: UNKNOWN is a recorded value, not a blank, so it will not show as empty.enquiries
- campaign_refText, 7 different values. 37% empty.Links the enquiry to a campaign in campaigns, where one was recorded.Watch out: A blank means no campaign was recorded, not proof the enquiry had no campaign.enquiries
- base_currencyText, one value. Never empty.The currency each rate converts from; always euros.fx_rate
- quote_currencyText, 3 different values. Never empty.The currency each rate converts into: GBP, SEK or USD.fx_rate
- rate_dateDate, 77 different values. Never empty.The date the exchange rate applies to.Watch out: Not every day has a rate, so a date join can miss invoices.fx_rate
- rate_typeText, 2 different values. Never empty.Whether the rate is a daily reference rate or a month-end closing rate.Watch out: Both types can exist, so pick one before joining or rows will double.fx_rate
- rateDecimal number, 121 different values. Never empty.Units of the quote currency for one euro.Watch out: Divide a foreign amount by the rate to get euros; multiplying gives the wrong answer.fx_rate
- inspection_refText, 8,593 different values. Never empty.The unique reference for one quality inspection.inspections
- lot_refText, 8,479 different values. Never empty.The lot that was inspected; receiving lots match lot_ref in goods_receipts.Watch out: 114 lots appear twice, so count distinct lot_ref when counting lots.inspections
- inspection_kindText, 3 different values. Never empty.The stage of the check: receiving, final or re-inspection.Watch out: Fail rates differ by kind, so compare within a kind, not across all rows.inspections
- resultText, 3 different values. Never empty.The outcome of the inspection: pass, fail or unknown.Watch out: UNKNOWN is a recorded value, not a blank, and is neither a pass nor a fail.inspections
- measured_dateDate, 356 different values. Never empty.The date the inspection was carried out.inspections
- employee_refText, 425 different values. Never empty.The employee the pay input belongs to.Watch out: One row per employee per month, so count distinct employee_ref for headcount.pay_inputs
- pay_periodText, 10 different values. Never empty.The pay month, written as year and month.Watch out: Stored as text such as 2025-07, not as a date.pay_inputs
- base_salary_gross_monthlyDecimal number, 427 different values. Never empty.The employee's gross monthly base salary for the pay period.Watch out: Summing across months gives total pay, not an annual salary per person.pay_inputs
- overtime_hoursDecimal number, 6 different values. Never empty.The overtime hours recorded for the employee in the pay period.pay_inputs
- unpaid_leave_hoursDecimal number, one value. Never empty.The unpaid leave hours recorded for the employee in the pay period.Watch out: Every value is zero, so this column cannot show unpaid leave patterns.pay_inputs
- product_refText, 2,830 different values. Never empty.Links the revision to its product in products.Watch out: Products with several revisions repeat, so joins to sales can double count.product_revisions
- revisionText, 2 different values. Never empty.The product revision letter, A or B.product_revisions
- revision_statusText, 2 different values. Never empty.Whether the revision is released or withdrawn.Watch out: Withdrawn rows sit beside released ones; filter on RELEASED for the current picture.product_revisions
- effective_fromDate, 339 different values. Never empty.The date the revision took effect.Watch out: A few dates fall after the last month of other data, so they are future revisions.product_revisions
- version_noWhole number, 2 different values. Never empty.The version number of a revision record.Watch out: Version 2 rows are withdrawn versions of revision A, so count each product once.product_revisions
- product_refText, 2,830 different values. Never empty.The unique reference for one product.products
- product_kindText, 6 different values. Never empty.The kind of product, such as catalogue part or flight computer variant.Watch out: Codes rather than names; catalogue parts make up most products.products
- familyText, 25 different values. Never empty.The product family, such as bracket or connector kit.Watch out: Codes rather than names.products
- make_or_buyText, 2 different values. Never empty.Whether Raket Parts makes the product or buys it in.products
- product_refText, 2,830 different values. Never empty.Links the extra details to their product in products.Watch out: One row per product, so it joins to products one to one.products_extra
- stock_policyText, 3 different values. Never empty.Whether the product is stocked, made to order or not applicable.products_extra
- safety_stock_qtyWhole number, 44 different values. 34% empty.The minimum stock quantity to hold for the product.Watch out: Blank means not applicable while zero is a real choice; read safety_stock_qty_state.products_extra
- safety_stock_qty_stateText, 2 different values. Never empty.Whether the safety stock quantity is known or not applicable.Watch out: Use it to tell a deliberate blank from missing data.products_extra
- uomText, 2 different values. Never empty.The unit of measure: pieces or kilograms.Watch out: Quantities in KG and PCS cannot be added together.products_extra
- introduced_dateDate, 136 different values. Never empty.The date the product was introduced.products_extra
- quote_refText, 1,346 different values. Never empty.Links each line to its quote in quotes.quote_lines
- quote_versionWhole number, 2 different values. Never empty.The version of the quote the line belongs to.Watch out: Some quotes have lines under two versions, so summing every line can double count a quote.quote_lines
- line_noWhole number, 5 different values. Never empty.The position of the line within its quote version.Watch out: Only unique together with quote_ref and quote_version.quote_lines
- product_refText, 460 different values. Never empty.Links the line to the product quoted in products.quote_lines
- qtyWhole number, 11 different values. Never empty.The number of units quoted on the line.quote_lines
- unit_priceDecimal number, 2,458 different values. Never empty.The price quoted for one unit.Watch out: Multiply by qty for a line value; this is not a line total.quote_lines
- currencyText, one value. Never empty.The currency of the quoted price.Watch out: Every line is EUR, so this column cannot split results.quote_lines
- lead_time_daysWhole number, 61 different values. Never empty.The number of days quoted to deliver the line.quote_lines
- quote_refText, 1,346 different values. Never empty.The unique reference for one quote.quotes
- customer_refText, 243 different values. Never empty.Links the quote to its customer in customers.quotes
- issued_at_utcText, 365 different values. Never empty.The date and time the quote was sent, in UTC.Watch out: Stored as text with a time and offset, so convert it before date maths.quotes
- valid_untilDate, 365 different values. Never empty.The last date the quote can be accepted.quotes
- statusText, 4 different values. Never empty.The quote's current status, such as accepted or expired.Watch out: Only the status today is kept; no acceptance date is stored.quotes
- return_refText, 54 different values. Never empty.The unique reference for one customer return.returns
- customer_refText, 48 different values. Never empty.Links the return to its customer in customers.returns
- shipment_refText, 54 different values. Never empty.Links the return to the shipment it came from in shipments.returns
- so_refText, 54 different values. Never empty.Links the return to its sales order in sales_orders.returns
- so_line_noWhole number, 5 different values. Never empty.The sales order line being returned.Watch out: Only unique together with so_ref.returns
- product_refText, 52 different values. Never empty.Links the return to the product returned in products.returns
- qty_requestedWhole number, 5 different values. Never empty.The number of units the customer asked to return.returns
- statusText, 4 different values. Never empty.How far the return has progressed, from requested to inspected.Watch out: Codes rather than names, running from REQUESTED through RECEIVED to INSPECTED_ACCEPTED or INSPECTED_REJECTED.returns
- qty_receivedWhole number, 5 different values. 20% empty.The number of returned units received back.Watch out: Blank on returns still REQUESTED, which have not arrived yet.returns
- so_refText, 7,235 different values. Never empty.Links each line to its order in sales_orders.sales_order_lines
- line_noWhole number, 5 different values. Never empty.The position of the line within its sales order.Watch out: Only unique together with so_ref.sales_order_lines
- product_refText, 2,764 different values. Never empty.Links the line to the product ordered in products.sales_order_lines
- qty_orderedWhole number, 14 different values. Never empty.The number of units ordered on the line.sales_order_lines
- net_unit_priceDecimal number, 15,765 different values. Never empty.The net price for one unit on the line.sales_order_lines
- line_valueDecimal number, 18,577 different values. Never empty.The value of the line: quantity times net unit price.Watch out: Cancelled lines keep their value, so filter on line_status before summing.sales_order_lines
- line_statusText, 2 different values. Never empty.Whether the line is open or cancelled.sales_order_lines
- so_refText, 7,235 different values. Never empty.The unique reference for one sales order.sales_orders
- customer_refText, 414 different values. Never empty.Links the order to its customer in customers.sales_orders
- order_dateDate, 341 different values. Never empty.The date the order was placed.Watch out: Dates start in October 2024, so a calendar year 2025 view needs a filter.sales_orders
- channelText, 3 different values. Never empty.How the order arrived: email, webshop or phone.sales_orders
- shipment_refText, 12,380 different values. Never empty.Links each line to its shipment in shipments.shipment_lines
- line_noWhole number, 7 different values. Never empty.The position of the line within its shipment.Watch out: Only unique together with shipment_ref.shipment_lines
- so_refText, 6,902 different values. Never empty.Links the line to its sales order in sales_orders.shipment_lines
- so_line_noWhole number, 5 different values. Never empty.The sales order line this shipment line fulfils.Watch out: Join on so_ref and so_line_no together, not on line_no.shipment_lines
- product_refText, 2,574 different values. Never empty.Links the line to the product shipped in products.shipment_lines
- qtyWhole number, 40 different values. Never empty.The number of units shipped on the line.shipment_lines
- shipment_refText, 12,380 different values. Never empty.The unique reference for one shipment.shipments
- so_refText, 6,902 different values. Never empty.Links the shipment to its sales order in sales_orders.Watch out: Some orders ship in several shipments, so counting shipments does not count orders.shipments
- customer_refText, 414 different values. Never empty.Links the shipment to its customer in customers.shipments
- dispatched_at_utcText, 276 different values. Never empty.The date and time the shipment left, in UTC.Watch out: Stored as text with a time and offset, so convert it before date maths.shipments
- supplier_invoice_refText, 979 different values. Never empty.The unique reference Raket Parts gives each supplier invoice.supplier_invoices
- supplier_refText, 34 different values. Never empty.Links the invoice to its supplier in suppliers.supplier_invoices
- supplier_invoice_noText, 978 different values. Never empty.The invoice number printed by the supplier.Watch out: One number appears twice because a duplicate was received; it is not unique.supplier_invoices
- invoice_dateDate, 224 different values. Never empty.The date on the supplier's invoice.supplier_invoices
- received_at_utcText, 229 different values. Never empty.The date and time the invoice was received, in UTC.Watch out: Stored as text with a time and offset, so convert it before date maths.supplier_invoices
- currencyText, 4 different values. Never empty.The currency the supplier invoiced in.Watch out: Amounts in GBP, SEK and USD cannot be added to euros without conversion.supplier_invoices
- claimed_amountDecimal number, 917 different values. Never empty.The amount the supplier claimed, in the invoice currency.Watch out: Mixed currencies; use book_amount for euro totals.supplier_invoices
- accepted_amountDecimal number, 917 different values. 0% empty.The amount Raket Parts accepted, in the invoice currency.Watch out: Blank on the rejected duplicate; still in mixed currencies.supplier_invoices
- book_amountDecimal number, 920 different values. 0% empty.The accepted amount converted to euros for the books.Watch out: For non-euro invoices it differs from accepted_amount; blank on the rejected duplicate.supplier_invoices
- posting_dateDate, 229 different values. 0% empty.The date the invoice was posted to the ledger.Watch out: Blank on the rejected duplicate, which was never posted.supplier_invoices
- statusText, 3 different values. Never empty.Whether the invoice was matched to an order, approved without one, or rejected.Watch out: NON_PO_APPROVED invoices have no order to match but are not wrong.supplier_invoices
- duplicate_of_refText, one value. 100% empty.The original supplier invoice that a rejected duplicate copies.Watch out: Filled only on the rejected duplicate, so leave that row out of totals.supplier_invoices
- supplier_refText, 35 different values. Never empty.The unique reference for one supplier.suppliers
- categoryText, 20 different values. Never empty.What the supplier provides, such as titanium bar or general services.Watch out: Codes rather than names.suppliers
- countryText, 7 different values. Never empty.The supplier's country, as a two-letter code.Watch out: Codes rather than names, such as NL and DE.suppliers
- invoice_currencyText, 4 different values. Never empty.The currency the supplier invoices in.suppliers
- payment_terms_daysWhole number, 3 different values. Never empty.The number of days Raket Parts has to pay the supplier.suppliers
- po_refText, 868 different values. Never empty.The unique reference for one purchase order.purchase_orders
- supplier_refText, 17 different values. Never empty.Links the purchase order to its supplier in suppliers.Watch out: Only 17 of the 35 suppliers appear, so many suppliers have no purchase orders.purchase_orders
- order_dateDate, 230 different values. Never empty.The date the purchase order was placed.purchase_orders
- currencyText, 4 different values. Never empty.The currency of the purchase order.Watch out: Values in GBP, SEK and USD cannot be added to euros without conversion.purchase_orders
- po_valueDecimal number, 866 different values. Never empty.The total value of the purchase order, in its currency.Watch out: Mixed currencies; convert with fx_rate before summing.purchase_orders
- approval_levelText, 2 different values. Never empty.Who had to approve the order: a buyer or the managing director.purchase_orders
- approver_refText, 7 different values. 0% empty.The employee who approved the purchase order.Watch out: One order has no approver; check approver_ref_state.purchase_orders
- approver_ref_stateText, 2 different values. Never empty.Whether the approver is known or missing.Watch out: MISSING marks the order with no recorded approver.purchase_orders
- approved_at_utcText, 230 different values. 0% empty.The date and time the purchase order was approved, in UTC.Watch out: Stored as text with a time and offset; one order has none.purchase_orders
- approved_at_utc_stateText, 2 different values. Never empty.Whether the approval time is known or missing.Watch out: MISSING marks the order with no recorded approval time.purchase_orders
- supplier_invoice_refText, 979 different values. Never empty.Links the extra details to their invoice in supplier_invoices.Watch out: One row per invoice, including the rejected duplicate.supplier_invoices_extra
- due_dateDate, 252 different values. Never empty.The date payment of the supplier invoice is due.Watch out: The rejected duplicate still carries a due date, so leave it out of amounts due.supplier_invoices_extra
- credit_note_refText, 29 different values. Never empty.Links the extra details to their credit note in credit_notes.credit_notes_extra
- proposed_by_refText, 21 different values. Never empty.The employee who proposed the credit note.credit_notes_extra
- posting_dateDate, 26 different values. Never empty.The date the credit note was posted to the ledger.credit_notes_extra
- po_refText, 868 different values. Never empty.Links each line to its purchase order in purchase_orders.purchase_order_lines
- line_noWhole number, one value. Never empty.The position of the line within its purchase order.Watch out: Every order has a single line, so this is always 1.purchase_order_lines
- item_refText, 492 different values. Never empty.A code for the item ordered on the line.purchase_order_lines
- qtyWhole number, 352 different values. Never empty.The quantity ordered on the line, in the line's unit of measure.Watch out: Quantities are in PCS or KG, so do not add them together.purchase_order_lines
- uomText, 2 different values. Never empty.The unit of measure: pieces or kilograms.purchase_order_lines
- unit_priceDecimal number, 782 different values. Never empty.The price for one unit, in the line's currency.Watch out: Mixed currencies; convert before comparing or summing.purchase_order_lines
- currencyText, 4 different values. Never empty.The currency of the line.purchase_order_lines
- promised_dateDate, 245 different values. Never empty.The date the supplier promised to deliver the line.Watch out: Some dates run into 2026, after the last month of other data.purchase_order_lines
- line_purposeText, 4 different values. Never empty.Why the item was bought, such as resale stock or material.Watch out: Codes rather than names.purchase_order_lines
- gr_refText, 877 different values. Never empty.The unique reference for one goods receipt.goods_receipts
- po_refText, 793 different values. Never empty.Links the receipt to its purchase order in purchase_orders.Watch out: Some orders arrive in several receipts, so counting receipts does not count orders.goods_receipts
- line_noWhole number, one value. Never empty.The purchase order line received.Watch out: Always 1, since every purchase order has one line.goods_receipts
- received_at_utcText, 212 different values. Never empty.The date and time the goods arrived, in UTC.Watch out: Stored as text with a time and offset, so convert it before date maths.goods_receipts
- qty_receivedWhole number, 315 different values. Never empty.The quantity received, in the receipt's unit of measure.Watch out: Quantities are in PCS or KG, so do not add them together.goods_receipts
- uomText, 2 different values. Never empty.The unit of measure: pieces or kilograms.goods_receipts
- lot_refText, 877 different values. Never empty.The lot created for the received goods; matches lot_ref in inspections.goods_receipts
- asn_refText, 65 different values. Never empty.The unique reference of the supplier's advance shipping notice.supplier_asn
- po_refText, 65 different values. Never empty.Links the notice to its purchase order in purchase_orders.supplier_asn
- line_noWhole number, one value. Never empty.The purchase order line the notice refers to.Watch out: Every row is line 1, so this column cannot tell lines apart here.supplier_asn
- claimed_ship_dateDate, 13 different values. Never empty.The ship date the supplier claims in the notice.Watch out: A supplier claim, not proof; compare with goods_receipts before treating it as fact.supplier_asn
- claimed_qtyWhole number, 64 different values. Never empty.The quantity the supplier claims to have shipped.Watch out: A claim from the supplier; the quantity actually received is in goods_receipts.supplier_asn
- conflict_refText, 71 different values. Never empty.The unique reference of one recorded disagreement between two sources.source_conflicts
- object_tableText, 2 different values. Never empty.The table holding the record the two sources disagree about.Watch out: Values are table names, so object_ref points to a different table depending on this column.source_conflicts
- object_refText, 71 different values. Never empty.The order or purchase order and line number the conflict is about.Watch out: Combines a reference and line number with #, so split it before joining to line tables.source_conflicts
- claim_nameText, 2 different values. Never empty.The fact the two sources disagree about, such as a late delivery cause.source_conflicts
- source_a_refText, 2 different values. Never empty.A code for the first source system making the claim.Watch out: System codes rather than names; look them up in source_systems.source_conflicts
- value_aText, 6 different values. Never empty.The value the first source asserts for the claim.Watch out: Holds both cause codes and dates as text, depending on claim_name.source_conflicts
- source_b_refText, one value. Never empty.A code for the second source system making the claim.Watch out: Always X-ERP-LEGACY in this data.source_conflicts
- value_bText, 13 different values. Never empty.The value the second source asserts for the claim.Watch out: Mixes cause codes and dates as text, so do not treat it as one data type.source_conflicts
- adjudication_statusText, 3 different values. Never empty.Whether the disagreement was resolved, disputed or left inconclusive.Watch out: Most rows are INCONCLUSIVE, so neither source's value should be reported as settled fact.source_conflicts
- adopted_valueDate, 2 different values. 97% empty.The date adopted as true once the conflict was resolved with evidence.Watch out: Read with the matching _state column, which says why a value is blank.source_conflicts
- adopted_value_stateText, 2 different values. Never empty.Says whether adopted_value is known or not applicable.source_conflicts
- assertion_refText, 500 different values. Never empty.The unique reference of one claimed cause for a late order line.delay_causes
- so_refText, 201 different values. Never empty.Links the claim to its sales order in sales_orders.delay_causes
- so_line_noWhole number, 4 different values. Never empty.The sales order line the delay claim is about.Watch out: Join on so_ref and so_line_no together, or lines of one order get mixed.delay_causes
- asserted_by_unitText, 2 different values. Never empty.The organisational unit making the claim, as a code from org_units.Watch out: Two units make claims, sometimes about the same line, so counts can double up.delay_causes
- cause_codeText, 4 different values. Never empty.The cause of the delay as claimed by the unit.Watch out: A claim, not a proven cause; source_conflicts shows many TITANIUM_LATE claims are inconclusive.delay_causes
- material_received_before_planned_startText, 2 different values. 51% empty.Whether material arrived before production was planned to start, as true or false text.Watch out: Stored as text, not a true boolean; blanks are not false.delay_causes
- material_received_before_planned_start_stateText, 2 different values. Never empty.Says whether the material-received flag is known or not applicable.delay_causes
- so_refText, 7,235 different values. Never empty.Links the line to its sales order in sales_orders.sales_order_lines_extra
- line_noWhole number, 5 different values. Never empty.The line's position within its sales order.Watch out: Line numbers repeat across orders, so always pair with so_ref.sales_order_lines_extra
- line_kindText, 3 different values. Never empty.The product line: CAT catalogue, BTO built-to-order or FC flight computers.Watch out: Codes rather than names, and on-time rates differ sharply between kinds.sales_order_lines_extra
- list_unit_priceDecimal number, 576 different values. Never empty.The catalogue list price for one unit.sales_order_lines_extra
- net_unit_priceDecimal number, 15,827 different values. Never empty.The price actually charged for one unit after any adjustment.Watch out: Can be above the list price, so do not assume net is always a discount.sales_order_lines_extra
- requested_dateDate, 477 different values. Never empty.The delivery date the customer asked for.sales_order_lines_extra
- promised_dateDate, 481 different values. Never empty.The delivery date promised to the customer.Watch out: Revised promises replace the original, so the first promise is not kept.sales_order_lines_extra
- version_reasonText, 4 different values. Never empty.Why the line was recorded or last changed, such as a revised promise.Watch out: Includes cancelled lines and price review changes, which need filtering before totals.sales_order_lines_extra
- shipment_refText, 12,153 different values. Never empty.Links the delivery record to its shipment in shipments.deliveries
- delivery_statusText, 2 different values. Never empty.Whether the shipment is confirmed delivered or its status is unknown.Watch out: UNKNOWN does not mean undelivered; it means no proof of delivery is held.deliveries
- delivered_at_utcText, 393 different values. 3% empty.The date and time the shipment was delivered, in UTC.Watch out: Stored as text with a time zone, so convert before date arithmetic.deliveries
- delivered_at_utc_stateText, 2 different values. Never empty.Says whether the delivery time is known.deliveries
- version_reasonText, 2 different values. Never empty.Whether the record is the original or updated by late proof of delivery.Watch out: Late proof of delivery can change outcomes after a report was run.deliveries
- case_refText, 83 different values. Never empty.The unique reference of one customer service case.service_cases
- customer_refText, 50 different values. Never empty.Links the case to its customer in customers.service_cases
- case_kindText, 2 different values. Never empty.The type of case, such as a return request or late delivery.service_cases
- statusText, 3 different values. Never empty.The current stage of the case.Watch out: A REOPENED case may have been counted as closed in an earlier report.service_cases
- proposed_credit_amountDecimal number, 31 different values. 63% empty.The credit amount proposed to settle the case.Watch out: Read with the matching _state column, which says why a value is blank.service_cases
- proposed_credit_amount_stateText, 2 different values. Never empty.Says whether a proposed credit amount is known or not applicable.service_cases
- credit_note_refText, 25 different values. 70% empty.Links the case to the credit note issued, in credit_notes.Watch out: A proposed credit does not always have a credit note, so do not treat proposals as issued.service_cases
- invoice_refText, 12,377 different values. Never empty.Links the row to its invoice in customer_invoices.customer_invoices_extra
- so_refText, 6,899 different values. Never empty.Links the invoice to its sales order in sales_orders.Watch out: One order can have several invoices, so counting invoices is not counting orders.customer_invoices_extra
- shipment_refText, 12,377 different values. Never empty.Links the invoice to the shipment it bills, in shipments.customer_invoices_extra
- invoice_dateDate, 276 different values. Never empty.The date the invoice was issued.customer_invoices_extra
- posting_dateDate, 276 different values. Never empty.The date the invoice was posted to the accounts.Watch out: Can differ from invoice_date, which shifts totals between periods.customer_invoices_extra
- due_dateDate, 332 different values. Never empty.The date payment is due.customer_invoices_extra
- customer_refText, 436 different values. Never empty.Links the terms to the customer in customers.customer_terms
- payment_terms_daysWhole number, 2 different values. Never empty.The number of days the customer has to pay an invoice.customer_terms
- credit_limitDecimal number, 4 different values. Never empty.The maximum amount the customer may owe at one time.customer_terms
- statusText, one value. Never empty.Whether the customer's terms are active.Watch out: Every row is ACTIVE, so this column cannot be used to filter.customer_terms
- mo_refText, 7,553 different values. Never empty.The unique reference of one manufacturing order.production_orders
- product_refText, 2,109 different values. Never empty.Links the order to the product being made in products.production_orders
- order_kindText, 2 different values. Never empty.Whether the order is made for a customer order or made for stock.production_orders
- so_refText, 3,914 different values. 22% empty.Links a make-to-order job to its sales order in sales_orders.Watch out: Blank for make-to-stock orders, which have no customer order.production_orders
- so_line_noWhole number, 5 different values. 22% empty.The sales order line the job is made for.Watch out: Blank for make-to-stock orders; pair with so_ref when joining.production_orders
- qty_plannedWhole number, 129 different values. Never empty.The number of units planned to be made.production_orders
- planned_startDate, 276 different values. Never empty.The date production was planned to start.production_orders
- statusText, 2 different values. Never empty.Whether the order is released or completed.Watch out: RELEASED orders have no actuals yet, so blanks in actual columns are expected.production_orders
- actual_startDate, 272 different values. 5% empty.The date production actually started.Watch out: Blank for released orders that have not finished.production_orders
- completed_onDate, 271 different values. 5% empty.The date production was completed.Watch out: Blank for orders not yet completed.production_orders
- qty_goodWhole number, 129 different values. 5% empty.The number of good units produced.production_orders
- qty_scrapWhole number, one value. 5% empty.The number of units scrapped.Watch out: Always zero where filled, so it shows no scrap rather than measuring it.production_orders
- work_refText, 7,270 different values. Never empty.The unique reference of one recorded piece of work.work_records
- mo_refText, 7,156 different values. Never empty.Links the work to its manufacturing order in production_orders.Watch out: Some orders have several records, such as rework, so hours per order need summing.work_records
- operationText, 3 different values. Never empty.The type of work done, such as machining, assembly or rework.work_records
- unit_idText, 2 different values. Never empty.A code for the organisational unit that did the work, from org_units.Watch out: Codes rather than names.work_records
- employee_refText, 195 different values. Never empty.Links the work to the employee who recorded it.work_records
- hoursDecimal number, 158 different values. Never empty.The number of hours recorded for the work.Watch out: Values reach 1,710 hours on one record, so check outliers before averaging.work_records
- recorded_at_utcText, 314 different values. Never empty.The date and time the work was recorded, in UTC.Watch out: Stored as text with a time zone; recording time may differ from when work happened.work_records
- employee_refText, 425 different values. Never empty.Links the weekly record to the employee.time_weekly
- iso_weekText, 43 different values. Never empty.The ISO week the hours belong to, such as 2025-W28.Watch out: ISO weeks do not line up with calendar months, so monthly totals need care.time_weekly
- contracted_hoursWhole number, 4 different values. Never empty.The hours per week in the employee's contract.time_weekly
- recorded_hoursDecimal number, 78 different values. 1% empty.The hours the employee recorded in the week.Watch out: Read with the matching _state column, which says why a value is blank.time_weekly
- recorded_hours_stateText, 2 different values. Never empty.Says whether recorded hours are known or missing.time_weekly
- overtime_hoursDecimal number, 5 different values. 1% empty.The overtime hours recorded in the week.Watch out: Blank where recorded hours are missing, which is not the same as zero overtime.time_weekly
- absence_hoursDecimal number, 17 different values. Never empty.The hours of absence in the week.time_weekly
- absence_refText, 1,805 different values. Never empty.The reference of the absence this version describes.Watch out: Some absences have two versions, so counting rows overcounts absences.absences_history
- employee_refText, 421 different values. Never empty.Links the absence to the employee.absences_history
- absence_typeText, 3 different values. Never empty.The kind of absence, such as annual leave, sick or parental.absences_history
- start_dateDate, 272 different values. Never empty.The date the absence started.absences_history
- end_dateDate, 333 different values. 0% empty.The date the absence ended.Watch out: Read with the matching _state column, which says why a value is blank.absences_history
- end_date_stateText, 2 different values. Never empty.Says whether the end date is known.absences_history
- hoursDecimal number, 48 different values. 0% empty.The number of hours of absence.Watch out: A few very large values exist, so check outliers before summing.absences_history
- hours_stateText, 2 different values. Never empty.Says whether the absence hours are known.absences_history
- version_noWhole number, 2 different values. Never empty.The version number of the absence record.Watch out: Use the latest version per absence_ref to avoid double counting.absences_history
- version_reasonText, 2 different values. Never empty.Why this version exists, such as sick leave extended and reported later.Watch out: Later versions can change past totals after a report was run.absences_history
- journal_refText, 2,080 different values. Never empty.The reference of the journal the line belongs to.Watch out: A journal has several lines, so count distinct journals, not rows.gl_journal_lines
- line_noWhole number, 68 different values. Never empty.The line's position within its journal.gl_journal_lines
- journal_kindText, 10 different values. Never empty.The type of journal, such as supplier invoice or daily sales summary.Watch out: Sales are posted as daily summaries, not one journal per invoice.gl_journal_lines
- posting_dateDate, 278 different values. Never empty.The date the line was posted to the accounts.gl_journal_lines
- fiscal_periodText, 13 different values. Never empty.The accounting period of the line, as year and month.gl_journal_lines
- account_refText, 25 different values. Never empty.Links the line to its general ledger account in accounts.Watch out: Codes rather than names; account_name gives the name.gl_journal_lines
- account_kindText, 4 different values. Never empty.The broad class of the account, such as balance sheet, cost or revenue.gl_journal_lines
- account_nameText, 25 different values. Never empty.The name of the general ledger account.gl_journal_lines
- amount_bookDecimal number, 5,020 different values. Never empty.The line amount in euros, debits positive and credits negative.Watch out: Each journal sums to zero, so totalling without filtering by account gives zero.gl_journal_lines
- source_tableText, 6 different values. Never empty.The table holding the document the line came from.Watch out: source_ref points to different tables depending on this value.gl_journal_lines
- source_refText, 1,917 different values. Never empty.The reference of the source document or summary behind the line.Watch out: Some refs are daily summaries or depreciation runs, not single documents.gl_journal_lines
- unit_idText, 13 different values. 87% empty.A code for the organisational unit charged, from org_units.Watch out: Mostly blank, so unit totals cover only part of the ledger.gl_journal_lines
- account_refText, 25 different values. Never empty.The unique code of one general ledger account.accounts
- account_kindText, 4 different values. Never empty.The broad class of the account, such as balance sheet, cost or revenue.accounts
- descriptionText, 25 different values. Never empty.The name of the account.accounts
- unit_idText, 13 different values. Never empty.The unique code of one organisational unit.org_units
- headcount_modelWhole number, 10 different values. Never empty.A modelled headcount for the unit.Watch out: A practice figure, not a count of employees on payroll.org_units
- bank_line_refText, 7,345 different values. Never empty.The unique reference of one line on the bank statement.bank_statement_lines
- booking_dateDate, 246 different values. Never empty.The date the bank booked the transaction.bank_statement_lines
- value_dateDate, 246 different values. Never empty.The date the bank treats the money as having moved.bank_statement_lines
- amountDecimal number, 7,145 different values. Never empty.The transaction amount in euros, receipts positive and payments negative.Watch out: Signed values, so summing all lines gives net cash flow, not receipts.bank_statement_lines
- currencyText, one value. Never empty.The currency of the bank line.Watch out: Always EUR here, even though some supplier invoices are in other currencies.bank_statement_lines
- transaction_kindText, 3 different values. Never empty.The type of transaction, such as customer receipt or supplier payment.Watch out: A returned payment reverses an earlier line, so both must be kept together.bank_statement_lines
- counterparty_tableText, 2 different values. Never empty.Whether the counterparty is a customer or a supplier.Watch out: counterparty_ref points to different tables depending on this value.bank_statement_lines
- counterparty_refText, 448 different values. Never empty.Links the line to its customer or supplier.bank_statement_lines
- reverses_bank_line_refText, one value. 100% empty.The earlier bank line this line reverses.Watch out: Only one reversal exists; include it or receipts are overstated.bank_statement_lines
- application_refText, 10,466 different values. Never empty.The unique reference of one matching of cash to a document.cash_applications
- bank_line_refText, 7,343 different values. Never empty.Links the application to its line in bank_statement_lines.Watch out: One bank line can pay several documents, so do not sum bank amounts after joining.cash_applications
- document_tableText, 3 different values. Never empty.The table holding the document the cash was applied to.Watch out: document_ref points to different tables depending on this value.cash_applications
- document_refText, 10,466 different values. Never empty.The reference of the invoice or credit note the cash settles.cash_applications
- amount_appliedDecimal number, 10,043 different values. Never empty.The amount of cash applied to the document.Watch out: Includes negative values, such as credit notes, which reduce the total.cash_applications
- applied_at_utcText, 246 different values. Never empty.The date and time the cash was applied, in UTC.Watch out: Stored as text with a time zone, so convert before comparing dates.cash_applications
- interface_refText, 7 different values. Never empty.The unique code of one data feed between two systems.it_interfaces
- from_system_refText, 7 different values. Never empty.A code for the system sending the data, from source_systems.Watch out: Codes rather than names.it_interfaces
- to_system_refText, 2 different values. Never empty.A code for the system receiving the data, from source_systems.it_interfaces
- payload_kindText, 7 different values. Never empty.The kind of data the interface carries, such as orders.it_interfaces
- scheduleText, 4 different values. Never empty.How often the interface runs.it_interfaces
- contract_versionWhole number, 2 different values. Never empty.The version number of the interface's agreed data contract.it_interfaces
- batch_refText, 1,243 different values. Never empty.The unique reference of one batch of records sent between systems.interface_batches
- interface_refText, 7 different values. Never empty.Links the batch to its interface in it_interfaces.interface_batches
- sequence_noWhole number, 304 different values. Never empty.The batch's running number within its interface.interface_batches
- sent_dateDate, 304 different values. Never empty.The date the batch was sent.interface_batches
- sent_at_utcText, 318 different values. Never empty.The date and time the batch was sent, in UTC.Watch out: Stored as text with a time zone.interface_batches
- received_at_utcText, 318 different values. Never empty.The date and time the batch was received, in UTC.Watch out: Stored as text with a time zone.interface_batches
- record_countWhole number, 96 different values. Never empty.The number of records in the batch.Watch out: Replays and stale batches carry records but no new business; use new_business_occurrences.interface_batches
- receipt_statusText, 3 different values. Never empty.Whether the receiving system accepted, qualified as stale or refused the batch.Watch out: Refused replays and stale batches add no new events.interface_batches
- replay_of_batch_refText, 4 different values. 100% empty.The earlier batch that this batch repeats.Watch out: A replay repeats existing records, so counting it double counts activity.interface_batches
- new_business_occurrencesWhole number, 97 different values. Never empty.The number of genuinely new business events in the batch.interface_batches
- acknowledgedText, 2 different values. Never empty.Whether the receiving system acknowledged the batch, as true or false text.Watch out: Stored as text rather than a true boolean.interface_batches
- incident_refText, 15 different values. Never empty.The unique reference of one IT incident.it_incidents
- system_refText, 7 different values. Never empty.A code for the affected system, from source_systems.Watch out: Codes rather than names.it_incidents
- opened_at_utcText, 15 different values. Never empty.The date and time the incident was opened, in UTC.Watch out: Stored as text with a time zone.it_incidents
- resolved_at_utcText, 15 different values. Never empty.The date and time the incident was resolved, in UTC.Watch out: Stored as text with a time zone, so convert before working out durations.it_incidents
- severityText, 4 different values. Never empty.The incident's priority, from P1 most severe to P4.Watch out: A lower number means more severe, so sorting ascending puts the worst first.it_incidents
- kindText, 7 different values. Never empty.The type of incident, such as a user lockout or interface timeout.it_incidents
- acknowledged_batches_before_failureWhole number, 2 different values. 87% empty.The number of batches acknowledged before a system failure.Watch out: Only filled for failure incidents; blank does not mean zero.it_incidents
- batches_recoveredWhole number, 2 different values. 87% empty.The number of batches recovered after a failure.Watch out: Only filled for failure incidents; blank does not mean zero.it_incidents
- batches_lost_with_named_rebuildWhole number, 2 different values. 87% empty.The number of lost batches rebuilt from a named alternative source.Watch out: Rebuilt data is reconstructed, not the original records.it_incidents
- change_refText, 50 different values. Never empty.The unique reference of one IT change request.it_changes
- system_refText, 8 different values. Never empty.A code for the system being changed, from source_systems.Watch out: Codes rather than names.it_changes
- change_kindText, 5 different values. Never empty.The type of change, such as configuration or a patch.it_changes
- requested_by_refText, 6 different values. Never empty.Links the change to the employee who requested it.it_changes
- approved_by_refText, 6 different values. 8% empty.Links the change to the employee who approved it.Watch out: Read with the matching _state column, which says why a value is blank.it_changes
- approved_by_ref_stateText, 2 different values. Never empty.Says whether the approver is known or missing.it_changes
- approved_at_utcText, 41 different values. 8% empty.The date and time the change was approved, in UTC.Watch out: Stored as text with a time zone.it_changes
- implemented_at_utcText, 35 different values. 20% empty.The date and time the change was implemented, in UTC.Watch out: Read with the matching _state column, which says why a value is blank.it_changes
- implemented_at_utc_stateText, 2 different values. Never empty.Says whether the implementation time is known or not yet recorded.it_changes
- statusText, 4 different values. Never empty.The change's current stage, including implemented without approval.Watch out: IMPLEMENTED_WITHOUT_APPROVAL is a control exception, not proof of misuse.it_changes
- riskText, 3 different values. Never empty.The assessed risk level of the change.it_changes
- grant_refText, 845 different values. Never empty.The unique reference of one grant of system access.it_access_grants
- employee_refText, 425 different values. Never empty.Links the grant to the employee given access.it_access_grants
- system_refText, 8 different values. Never empty.A code for the system the access is to, from source_systems.Watch out: Codes rather than names.it_access_grants
- access_levelText, 3 different values. Never empty.The level of access granted: read, write or approve.it_access_grants
- request_basisText, 3 different values. Never empty.The grounds on which the access was requested.Watch out: ROLE_LABEL_ONLY means no named request sits behind the grant.it_access_grants
- approval_refText, 787 different values. 7% empty.The reference of the approval for the grant.Watch out: Read with the matching _state column, which says why a value is blank.it_access_grants
- approval_ref_stateText, 2 different values. Never empty.Says whether an approval reference is known or missing.it_access_grants
- statusText, 4 different values. Never empty.The grant's current state, such as granted, refused or revoked.Watch out: Only GRANTED rows give access now; refused and pending rows should be excluded.it_access_grants
- effective_fromDate, 36 different values. 7% empty.The date the access took effect.Watch out: Blank where no approval is recorded.it_access_grants
- effective_toDate, 22 different values. 96% empty.The date the access ended.Watch out: Blank means still open, not unknown, for most grants.it_access_grants
- system_refText, 21 different values. Never empty.The unique code of one source system or reference source.source_systems
- system_kindText, 17 different values. Never empty.The kind of source, such as reference data or an external assertion.source_systems
- function_refsText, 14 different values. 19% empty.Codes for the business functions the system serves, separated by semicolons.Watch out: Several codes can share one cell, so split on semicolons before counting.source_systems
- descriptionText, 21 different values. Never empty.A plain description of what the source holds.source_systems
- policy_refText, 20 different values. Never empty.The unique code of one policy record.policy_fixtures
- domainText, 10 different values. Never empty.The business area the policy covers, such as finance or payroll.policy_fixtures
- statusText, 3 different values. Never empty.Whether the policy is proposed, held for review or reference only.Watch out: PROPOSED_FIXTURE is not an approved rule, so do not treat it as binding.policy_fixtures
- applies_toText, 20 different values. Never empty.The tables, fields or records the policy applies to.policy_fixtures
- rule_summaryText, 20 different values. Never empty.A plain summary of what the policy says.policy_fixtures
- contact_refText, 1,179 different values. Never empty.The unique reference of one marketing contact.mkt_contacts
- customer_refText, 414 different values. 19% empty.Links the contact to their customer in customers.Watch out: Read with the matching _state column, which says why a value is blank.mkt_contacts
- customer_ref_stateText, 2 different values. Never empty.Says whether the contact has a linked customer.mkt_contacts
- segmentText, 3 different values. Never empty.The market segment of the contact, such as university or industrial.mkt_contacts
- countryText, 17 different values. Never empty.The contact's country as a two-letter code.Watch out: Codes rather than names.mkt_contacts
- contact_refText, 1,179 different values. Never empty.Links the consent record to its contact in mkt_contacts.Watch out: Some contacts have two rows, so counting rows overcounts contacts.consent_history
- consent_statusText, 3 different values. Never empty.The contact's marketing consent: opted in, opted out or unknown.Watch out: UNKNOWN is not consent and must not be treated as an opt-in.consent_history
- consent_basisText, 5 different values. Never empty.How the consent status was obtained or recorded.Watch out: LEGACY_IMPORT_NO_RECORD means no consent evidence exists.consent_history
- effective_from_utcText, 641 different values. Never empty.The date and time this consent status took effect, in UTC.Watch out: Stored as text with a time zone.consent_history
- version_noWhole number, 2 different values. Never empty.The version number of the consent record.Watch out: Use the latest version per contact, as withdrawals come later.consent_history
- version_reasonText, 2 different values. Never empty.Why this version exists, such as consent being withdrawn.consent_history
- campaign_refText, 7 different values. Never empty.Links the snapshot row to its campaign in campaigns.audience_snapshots
- contact_refText, 1,179 different values. Never empty.Links the row to its contact in mkt_contacts.Watch out: A contact appears once per campaign, so counting rows across campaigns overcounts people.audience_snapshots
- consent_status_at_snapshotText, 3 different values. Never empty.The contact's consent status when the campaign audience was taken.Watch out: Can differ from current consent in consent_history.audience_snapshots
- eligibleText, 2 different values. Never empty.Whether the contact could be included in the campaign, as true or false text.Watch out: Stored as text rather than a true boolean.audience_snapshots
- exclusion_reasonText, 2 different values. 66% empty.Why the contact was excluded from the campaign.Watch out: Blank for eligible contacts, so blank means not excluded.audience_snapshots
- invoice_refText, 12,377 different values. Never empty.Links the row to its invoice in customer_invoices.Watch out: Repeats customer_invoices data, so combining both tables double counts sales.sales_extract
- invoice_dateDate, 276 different values. Never empty.The date the invoice was issued.sales_extract
- monthText, 13 different values. Never empty.The invoice month as year and month text.Watch out: Stored as text, so sort carefully and check it matches invoice_date.sales_extract
- customer_refText, 414 different values. Never empty.Links the invoice to its customer in customers.sales_extract
- segmentText, 3 different values. Never empty.The customer's market segment, such as university or rocket builder.sales_extract
- countryText, 17 different values. Never empty.The customer's country as a two-letter code.Watch out: Codes rather than names.sales_extract
- net_amountDecimal number, 11,830 different values. Never empty.The net amount of the invoice.sales_extract
- so_refText, 7,235 different values. Never empty.Links the summary row to its sales order in sales_orders.order_journeys
- customer_refText, 414 different values. Never empty.Links the order to its customer in customers.order_journeys
- channelText, 3 different values. Never empty.How the order came in: email, webshop or phone.order_journeys
- order_dateDate, 341 different values. Never empty.The date the order was placed.order_journeys
- order_monthText, 13 different values. Never empty.The order month as year and month text.Watch out: Stored as text; order month is not the promised delivery month.order_journeys
- order_weekdayText, 7 different values. Never empty.The day of the week the order was placed.Watch out: Weekday names sort alphabetically, not in week order.order_journeys
- n_linesWhole number, 5 different values. Never empty.The number of lines on the order.order_journeys
- n_cancelledDecimal number, 3 different values. Never empty.The number of the order's lines that were cancelled.order_journeys
- n_shipmentsWhole number, 7 different values. Never empty.The number of shipments sent for the order.Watch out: Zero for orders not yet shipped, which also leaves dispatch dates blank.order_journeys
- first_dispatch_dateDate, 275 different values. 5% empty.The date the first shipment for the order was sent.Watch out: Blank for orders never shipped.order_journeys
- last_dispatch_dateDate, 274 different values. 5% empty.The date the last shipment for the order was sent.Watch out: Blank for orders never shipped.order_journeys
- days_to_first_dispatchWhole number, 99 different values. 5% empty.The number of days from order to first shipment.Watch out: Blank for unshipped orders; treating blanks as zero flatters the average.order_journeys
- n_invoicesWhole number, 7 different values. Never empty.The number of invoices raised for the order.order_journeys
- first_invoice_dateDate, 275 different values. 5% empty.The date the first invoice for the order was issued.Watch out: Blank for orders not yet invoiced.order_journeys
- n_returnsWhole number, 2 different values. Never empty.The number of returns recorded against the order.order_journeys
- journeyText, 4 different values. Never empty.A label summarising how the order moved through shipping and invoicing.order_journeys
- so_refText, 7,235 different values. Never empty.Links the line to its sales order in sales_orders.order_line_delivery
- line_noWhole number, 5 different values. Never empty.The line's position within its sales order.Watch out: Line numbers repeat across orders, so always pair with so_ref.order_line_delivery
- line_kindText, 3 different values. Never empty.The product line: CAT catalogue, BTO built-to-order or FC flight computers.Watch out: Codes rather than names, and on-time rates differ sharply between kinds.order_line_delivery
- line_statusText, 2 different values. Never empty.Whether the line is open or cancelled.order_line_delivery
- qty_orderedWhole number, 14 different values. Never empty.The number of units ordered on the line.order_line_delivery
- requested_dateDate, 477 different values. Never empty.The delivery date the customer asked for.order_line_delivery
- promised_dateDate, 481 different values. Never empty.The delivery date promised to the customer.Watch out: Revised promises replace the original, so the first promise is not stored.order_line_delivery
- promised_monthText, 17 different values. Never empty.The promised delivery month as year and month text.Watch out: Not the same as the order month; check which month a report groups by.order_line_delivery
- promise_noteText, 4 different values. Never empty.Why the promise was recorded or last changed.order_line_delivery
- n_shipmentsWhole number, 4 different values. Never empty.The number of shipments that carried the line.order_line_delivery
- qty_shippedDecimal number, 18 different values. 11% empty.The number of units shipped for the line.Watch out: Blank for lines never shipped, which is not the same as zero ordered.order_line_delivery
- last_delivered_dateDate, 392 different values. 14% empty.The date the last shipment for the line was delivered.Watch out: Blank where delivery is not shipped or not confirmed.order_line_delivery
- n_unconfirmed_deliveriesDecimal number, 3 different values. Never empty.The number of the line's shipments with no proof of delivery.order_line_delivery
- days_lateWhole number, 69 different values. 15% empty.The number of days delivery came after the promised date.Watch out: Negative values mean early, and blanks are not zero.order_line_delivery
- days_after_requestedWhole number, 79 different values. 15% empty.The number of days delivery came after the requested date.Watch out: Measured against the request, not the promise, so it differs from days_late.order_line_delivery
- delivery_outcomeText, 5 different values. Never empty.Whether the line was on time, late, not shipped, unconfirmed or cancelled.Watch out: On-time rates should exclude not shipped, unconfirmed and cancelled lines.order_line_delivery
- enquiry_refText, 328 different values. Never empty.Links the summary row to its enquiry in enquiries.enquiry_journeys
- contact_refText, 279 different values. Never empty.Links the enquiry to its contact in mkt_contacts.Watch out: Some contacts made several enquiries, so counting rows is not counting people.enquiry_journeys
- received_dateDate, 151 different values. Never empty.The date the enquiry was received.enquiry_journeys
- received_monthText, 10 different values. Never empty.The month the enquiry was received, as year and month text.enquiry_journeys
- channelText, 3 different values. Never empty.How the enquiry came in: phone, email or web form.enquiry_journeys
- qualification_statusText, 3 different values. Never empty.Whether the enquiry was judged a real sales opportunity.Watch out: UNKNOWN is neither qualified nor unqualified.enquiry_journeys
- campaign_refText, 7 different values. 37% empty.Links the enquiry to the campaign credited with it, in campaigns.Watch out: Credit comes from a 30-day last-touch rule, not proof the campaign caused it.enquiry_journeys
- attribution_basisText, 2 different values. Never empty.The rule used to credit the enquiry to a campaign, or none.enquiry_journeys
- quote_refText, 159 different values. 52% empty.Links the enquiry to its quote in quotes.Watch out: Blank where no quote was made.enquiry_journeys
- quote_statusText, 2 different values. 52% empty.Whether the quote was accepted or expired.Watch out: Blank where no quote was made.enquiry_journeys
- so_refText, 101 different values. 69% empty.Links the enquiry to the resulting sales order in sales_orders.Watch out: Blank where the enquiry did not lead to an order.enquiry_journeys
- furthest_stageText, 3 different values. Never empty.The furthest stage the enquiry reached: enquiry only, quoted or ordered.enquiry_journeys
Nothing matches. Try a shorter word.
