Skip to content
NetSuite Reference

previoustransactionlinelink

transaction

The backward line-link table: the exact mirror of nexttransactionlinelink, travelling upstream from an invoice line to the sales-order line it originated on.

Module: TransactionsNo partition column
Notes

Same eight column ids as the Next record, with the labels swapped: here previous* is the upstream document being linked to and next* is the line you are standing on. Pick the direction that matches your traversal rather than joining both.

What the badges mean
master
Data class: what the record holds — master data, transaction documents, control/configuration, or a documented convenience record. NetSuite has no product-family or schema axis, so this is the whole classification.

Structural facts — how the record is partitioned, not a trap by itself

Subsidiary-scoped
The record carries a subsidiary column that partitions its rows, so the generated SQL anchors it. On a few records the column is a multiselect rather than a scalar foreign key — the table notes say which (see the quirks guide).
Location-scoped
The record carries a location column — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way.

Join & extract hazards — verify before you rely on this

View
A documented convenience record rather than a stored one. Land the records it stands in for instead of assuming it extracts as-is — the table notes say where the rows actually live.
In field listings, the Key chip marks a primary-key field, and the T/F chip marks a check-box column Connect returns as a 'T'/'F' string.

Fields

8 fields · 4 key

8 fields.

Table fields: position, field name, description, data type, and flags. 8 fields.
#FieldDescriptionTypeFlags
1previousdocUpstream document being linked to (internal id)NUMBER
Primary-key field
2previouslineUpstream line being linked to (internal id)NUMBER
Primary-key field
3previoustypeType of the upstream documentVARCHAR
4nextdocThe document you are standing on (internal id)NUMBER
Primary-key field
5nextlineThe line you are standing on (internal id)NUMBER
Primary-key field
6nexttypeType of the document you are standing onVARCHAR
7linktypeLink type (internal id)NUMBER
8foreignamountLinked amount in transaction currencyNUMBER

Field provenance: hand-curated. 4 key fields.

Boilerplate SQL

Starting point for reading the Connect-landed copy of previoustransactionlinelink on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. This record carries no modification stamp, and the snippet says so where the watermark would otherwise go. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.

Query parameters

6 parameters not filled: <catalog>, <schema>, <previousdoc>, <previousline>, <nextdoc>, <nextline>

-- ============================================================
-- Table  : previoustransactionlinelink — The backward line-link table: the exact mirror of nexttransactionlinelink, travelling upstream from an invoice line to the sales-order line it originated on.
-- Purpose: Column-selected read of previoustransactionlinelink — auto-generated from field metadata
-- Grain  : One row per previousdoc + previousline + nextdoc + nextline
-- Notes  : Auto-generated skeleton for NetSuite data landed in your lakehouse from a SuiteAnalytics Connect (or SuiteQL) extract — it never addresses live NetSuite. Identifiers are lowercase as NetSuite2.com renders them. Select-type columns hold numeric internal ids: BUILTIN.DF() display resolution exists only at extraction time, so decode ids by joining the landed list records; see quirks #display-values. Check-box columns arrive as 'T'/'F' strings; see quirks #tf-booleans.
-- ============================================================
SELECT
  t.previousdoc AS "Upstream document being linked to (internal id)",
  t.previousline AS "Upstream line being linked to (internal id)",
  t.nextdoc AS "The document you are standing on (internal id)",
  t.nextline AS "The line you are standing on (internal id)",
  t.previoustype AS "Type of the upstream document",
  t.nexttype AS "Type of the document you are standing on",
  t.linktype AS "Link type (internal id)",
  t.foreignamount AS "Linked amount in transaction currency"
FROM <catalog>.<schema>.previoustransactionlinelink t
WHERE
  1 = 1  -- no partition column on this record; the filters below are optional
  -- AND t.previousdoc = <previousdoc>
  -- AND t.previousline = <previousline>
  -- AND t.nextdoc = <nextdoc>
  -- AND t.nextline = <nextline>
  -- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.previousdoc;

Verified August 2026 · Analytics Browser 2021.1 · corroborated 2025.2

Select columns hold internal ids, not display text — see decoding display values.

Relationships

Diagram of 1-hop neighbors — join details below. Document-link edges are highlighted; they chain one document to the next and are the joins newcomers most often get wrong.

Join details

  • previoustransactionlinelinktransactionlinedocument link · N:1
    ON previoustransactionlinelink.previousline = transactionline.id
  • previoustransactionlinelinktransactionlinedocument link · N:1
    ON previoustransactionlinelink.nextline = transactionline.id
  • previoustransactionlinelinktransactiondocument link · N:1
    ON previoustransactionlinelink.previousdoc = transaction.id
  • previoustransactionlinelinktransactiondocument link · N:1
    ON previoustransactionlinelink.nextdoc = transaction.id

Browse more Transactions tables

More Transactions tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle or NetSuite. NetSuite is a registered trademark of Oracle and/or its affiliates.