Table 46945 "BC14 Item Ledger Entry"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · captioned “Item Ledger Entry Migration Data” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Item Ledger Entry Migration Data
Extensible	false
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	Entry No.	Integer	—
2	Item No.	Code[20]	—	TableRelation Table 27 “Item”
3	Posting Date	Date	—
4	Entry Type	Enum “Item Ledger Entry Type”	—	enum Enum 78 “Item Ledger Entry Type”
5	Source No.	Code[20]	—
6	Document No.	Code[20]	—
7	Description	Text[100]	—
8	Location Code	Code[10]	—
12	Quantity	Decimal	—
13	Remaining Quantity	Decimal	—
14	Invoiced Quantity	Decimal	—
29	Open	Boolean	—
33	Global Dimension 1 Code	Code[20]	—
34	Global Dimension 2 Code	Code[20]	—
61	External Document No.	Code[35]	—
79	Document Type	Enum “Item Ledger Document Type”	—	enum Enum 79 “Item Ledger Document Type”
100	Journal Batch Name	Code[10]	—

Keys

Key1: Entry No. (clustered)
Key2: Item No., Posting Date
Key3: Open

Relations

Item No.: TableRelation Table 27 “Item”

Pages and codeunits on this table

Codeunit 46948 “BC14 Item Ledger Migrator” (codeunit runs on it)

Recent changes

2026-08-04 #9663 Migrate customer, vendor and item transactions for BC14 cloud migration (main, BC30, feature, added)

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: "BC14 Item Ledger Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.