tableFinanceofficial - Microsoftderived - from the source, no model text

Table 1661 "Import G/L Transaction"

Base Application · Microsoft.Finance.Payroll

Across versions

  1. BC23present
  2. BC241 fields changed
  3. BC25-27unchanged
  4. BC281 fields changed
  5. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Table 15 "G/L Account" (relates to, 2 links)G/L AccountPage 1661 "Payroll Import Transactions" (pages and codeunits on it)Payroll Import TransactionsImport payroll transactions (Learn pages)Import payroll transactions

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Finance.Payroll · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 1661 “Payroll Import Transactions” (1 Learn page).

Properties

Property Value
Caption Import G/L Transaction
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 App ID Guid — not editable
2 External Account Code[50] —
3 G/L Account Code[20] — TableRelation Table 15 “G/L Account” (“G/L Account” where(Blocked = const(false), “Direct Posting” = const(true), “Account Type” = const(Posting)))
4 G/L Account Name Δ BC24 Text[100] — FlowField: lookup(“G/L Account”.Name where(“No.” = field(“G/L Account”))); not editable
5 Entry No. Integer — AutoIncrement
10 Transaction Date Date —
12 Amount Δ BC28 Decimal —
13 Description Text[100] —

Keys

  • Key1: App ID, Entry No.
  • Key2: App ID, External Account, Transaction Date (clustered)

Relations

Pages and codeunits on this table

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: "Import G/L Transaction"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources