Curated tables

Use the stable reporting tables for everyday shipment, quote, and delivery questions.

Curated views are the least-friction path. Use them for dashboards, recurring reports, and anyone who is not hunting through discovery fields.

Start with shipments

reporting.shipments is one current row per Forwarding Shipment job for your organization.

Column	From CargoWise
job_number	DataSource/Key
shipment_key	Join key for history (ForwardingShipment: + Key)
transport_mode	TransportMode/Code
origin_code / destination_code	PortOfOrigin/Code, PortOfDestination/Code
total_weight / total_volume	TotalWeight, TotalVolume
goods_description	GoodsDescription

SELECT
  job_number,
  transport_mode,
  origin_code,
  destination_code,
  total_weight,
  total_volume
FROM reporting.shipments
WHERE transport_mode = 'AIR'
ORDER BY job_number;

Cotizaciones (quotes)

reporting.quotes is one current row per OneOffQuote. Query it separately from shipments even when columns share names (transport_mode, total_weight, …).

Column	From CargoWise
quote_number	DataSource/Key
transport_mode / ports / weight / volume / goods	Same leaf names as shipments
is_approved	IsQuoteApprovedByManager
total_revenue / total_job_profit	JobCosting/TotalRevenue, TotalJobProfit
has_converted_shipment	Soft match to a shipment with the same bare number

After approve → convert, the bare number can match a shipment. Join with quote_number = job_number — not quote_key / shipment_key.

SELECT
  count(*) FILTER (WHERE has_converted_shipment) AS converted,
  count(*) AS quoted
FROM reporting.quotes;

Full node map: Reporting views.

Related curated views

View	Use it for
reporting.shipment_versions	Historical versions of a job
reporting.shipment_changes	When the current version changed
reporting.quote_versions	Historical versions of a quote
reporting.quote_changes	When the current quote version changed
reporting.cargowise_payloads	Payload metadata
reporting.cargowise_deliveries	Delivery receipt metadata
reporting.cargowise_messages	Classified message envelopes

Join shipment history with shipment_key:

SELECT
  shipments.job_number,
  count(changes.id) AS accepted_version_changes,
  max(changes.changed_at) AS latest_change_at
FROM reporting.shipments AS shipments
LEFT JOIN reporting.shipment_changes AS changes
  ON changes.shipment_key = shipments.shipment_key
GROUP BY shipments.shipment_key, shipments.job_number
ORDER BY latest_change_at DESC NULLS LAST;

Browse the contract in Lambda

Open Analytics and expand Reporting. That section lists the supported views and columns for your organization.

The same list is documented in Reporting views.

When curated data is not enough

If the column you need is not on shipments or quotes, do not assume the value is missing from Analytics.

1. Search Discover fields.
2. If the field is present in observations and becomes a permanent report need, ask Jaantonio to evaluate promoting it into a curated table.
3. Some business concepts need a different upstream feed before they can appear as curated columns. Operations Rep, Post Date, and Revenue are examples of that today.

Practical guidance

Prefer job_number / quote_number in business-facing filters and exports. Keep shipment_key / quote_key for joins. Use curated tables for Power BI overview pages. Leave discovery observations for field hunting and detail work, not for every visual on a busy dashboard.