Table 410 "IC G/L Account"

Base Application · Microsoft.Intercompany.GLAccount · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 605 “IC Chart of Accounts” (3 Learn pages), Page 606 “IC G/L Account Card” (1), Page 607 “IC G/L Account List” (1).

Properties

Property	Value
Caption	IC G/L Account
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	No.	Code[20]	Specifies the number of the involved entry or record, according to the specified number series. via Page 606 “IC G/L Account Card”	NotBlank
2	Name	Text[100]	Specifies the name of the IC general ledger account. via Page 606 “IC G/L Account Card”
3	Account Type	Enum “G/L Account Type”	Specifies the purpose of the account. Total: Used to total a series of balances on accounts from many different account groupings. To use Total, leave this field blank. Begin-Total: A marker for the beginning of a series of accounts to be totaled that ends with an End-Total account. End-Total: A tot… via Page 606 “IC G/L Account Card”	enum Enum 16 “G/L Account Type”
4	Income/Balance Δ BC26	Enum “G/L Account Report Type”	Specifies whether a general ledger account is an income statement account or a balance sheet account. via Page 606 “IC G/L Account Card”	enum Enum 20 “G/L Account Report Type”
5	Blocked	Boolean	Specifies that the related record is blocked from being posted in transactions, for example a customer that is declared insolvent or an item that is placed in quarantine. via Page 606 “IC G/L Account Card”
6	Map-to G/L Acc. No.	Code[20]	Specifies the number of the G/L account in your chart of accounts that corresponds to this intercompany G/L account. via Page 606 “IC G/L Account Card”	TableRelation Table 15 “G/L Account” (“G/L Account”.“No.”)
7	Indentation	Integer	—

Keys

Key1: No. (clustered)

Triggers

OnInsert, OnModify, OnDelete

Relations

lookup page Page 607 “IC G/L Account List”
Map-to G/L Acc. No.: TableRelation Table 15 “G/L Account”

Referenced by

20 fields in 17 objects relate to this table (TableRelation or CalcFormula).

Table 181 “Posted Gen. Journal Line”: IC Account No., IC Partner G/L Acc. No.
Table 751 “Standard General Journal Line”: IC Account No., IC Partner G/L Acc. No.
Table 81 “Gen. Journal Line”: IC Account No., IC Partner G/L Acc. No.
Table 15 “G/L Account”: Default IC Partner G/L Acc. No
Table 156 “Resource”: IC Partner Purch. G/L Acc. No.
Table 415 “IC Outbox Jnl. Line”: Account No.
Table 417 “Handled IC Outbox Jnl. Line”: Account No.
Table 419 “IC Inbox Jnl. Line”: Account No.
Table 421 “Handled IC Inbox Jnl. Line”: Account No.
Table 427 “IC Outbox Sales Line”: IC Partner Reference
Table 429 “IC Outbox Purchase Line”: IC Partner Reference
Table 431 “Handled IC Outbox Sales Line”: IC Partner Reference
Table 433 “Handled IC Outbox Purch. Line”: IC Partner Reference
Table 435 “IC Inbox Sales Line”: IC Partner Reference
Table 437 “IC Inbox Purchase Line”: IC Partner Reference
Table 439 “Handled IC Inbox Sales Line”: IC Partner Reference
Table 441 “Handled IC Inbox Purch. Line”: IC Partner Reference

Pages and codeunits on this table

Page 30405 “API - IC G/L Accounts” (source table)
Page 605 “IC Chart of Accounts” (source table)
Page 606 “IC G/L Account Card” (source table)
Page 607 “IC G/L Account List” (source table)
Page 627 “IC Mapping CoA Incoming” (source table)

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Codeunit 428 “IC Mapping” (2 calls: OnInsert → GetFeatureTelemetryName, OnModify → GetFeatureTelemetryName)
Codeunit 8703 “Feature Telemetry” (2 calls: OnInsert → LogUptake, OnModify → LogUptake)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "IC G/L Account"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Across versions

Neighbourhood 28 connected objects and pages