Table 285 "Transaction Specification"

Base Application · Microsoft.Inventory.Intrastat · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 406 “Transaction Specifications” (3 Learn pages).

Properties

Property	Value
Caption	Transaction Specification
DataClassification	CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Code Δ BC28	Code[10]	Specifies a code for the transaction specification.	NotBlank
2	Text Δ BC28	Text[50]	Specifies a description of the transaction specification.

Keys

Key1: Code (clustered)

Relations

lookup page Page 406 “Transaction Specifications”

Referenced by

48 fields in 46 objects relate to this table (TableRelation or CalcFormula).

Table 247 “Intrastat Setup”: Default Trans. Spec. Code, Default Trans. Spec. Ret. Code
Table 4810 “Intrastat Report Setup”: Default Trans. Spec. Code, Default Trans. Spec. Ret. Code
Table 110 “Sales Shipment Header”: Transaction Specification
Table 111 “Sales Shipment Line”: Transaction Specification
Table 112 “Sales Invoice Header”: Transaction Specification
Table 113 “Sales Invoice Line”: Transaction Specification
Table 114 “Sales Cr.Memo Header”: Transaction Specification
Table 115 “Sales Cr.Memo Line”: Transaction Specification
Table 120 “Purch. Rcpt. Header”: Transaction Specification
Table 121 “Purch. Rcpt. Line”: Transaction Specification
Table 122 “Purch. Inv. Header”: Transaction Specification
Table 123 “Purch. Inv. Line”: Transaction Specification
Table 124 “Purch. Cr. Memo Hdr.”: Transaction Specification
Table 125 “Purch. Cr. Memo Line”: Transaction Specification
Table 169 “Job Ledger Entry”: Transaction Specification
Table 210 “Job Journal Line”: Transaction Specification
Table 263 “Intrastat Jnl. Line”: Transaction Specification
Table 32 “Item Ledger Entry”: Transaction Specification
Table 36 “Sales Header”: Transaction Specification
Table 37 “Sales Line”: Transaction Specification
Table 38 “Purchase Header”: Transaction Specification
Table 39 “Purchase Line”: Transaction Specification
Table 4812 “Intrastat Report Line”: Transaction Specification
Table 5107 “Sales Header Archive”: Transaction Specification
Table 5108 “Sales Line Archive”: Transaction Specification
Table 5109 “Purchase Header Archive”: Transaction Specification
Table 5110 “Purchase Line Archive”: Transaction Specification
Table 5740 “Transfer Header”: Transaction Specification
Table 5744 “Transfer Shipment Header”: Transaction Specification
Table 5746 “Transfer Receipt Header”: Transaction Specification
Table 5900 “Service Header”: Transaction Specification
Table 5902 “Service Line”: Transaction Specification
Table 5990 “Service Shipment Header”: Transaction Specification
Table 5991 “Service Shipment Line”: Transaction Specification
Table 5992 “Service Invoice Header”: Transaction Specification
Table 5993 “Service Invoice Line”: Transaction Specification
Table 5994 “Service Cr.Memo Header”: Transaction Specification
Table 5995 “Service Cr.Memo Line”: Transaction Specification
Table 6010 “Service Header Archive”: Transaction Specification
Table 6012 “Service Line Archive”: Transaction Specification
Table 6650 “Return Shipment Header”: Transaction Specification
Table 6651 “Return Shipment Line”: Transaction Specification
Table 6660 “Return Receipt Header”: Transaction Specification
Table 6661 “Return Receipt Line”: Transaction Specification
Table 753 “Standard Item Journal Line”: Transaction Specification
Table 83 “Item Journal Line”: Transaction Specification

Pages and codeunits on this table

Page 406 “Transaction Specifications” (source table)

Countries that replace it

AT, CH, DE

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Transaction Specification"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.