Table 2250 "Vendor Ledger Entry Buffer"

Base Application · Microsoft.Purchases.Payables · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 30073 “APIV2 - Apply Vendor Entries” (3 Learn pages).

Properties

Property	Value
Caption	Vendor Ledger Entry Buffer
TableType	Temporary
DataClassification	SystemMetadata

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	—
3	Vendor No.	Code[20]	—	TableRelation Table 23 “Vendor”
4	Posting Date	Date	—
5	Document Type	Enum “Gen. Journal Document Type”	—	enum Enum 6 “Gen. Journal Document Type”
6	Document No.	Code[20]	—
7	Description	Text[100]	—
8	Vendor Name	Text[100]	—
14	Remaining Amount Δ BC28	Decimal	—
36	Open	Boolean	—
47	Applies-to ID	Code[50]	—
63	External Document No.	Code[35]	—
8001	Vendor Id	Guid	—
8002	Gen. Journal Line Id	Guid	—

Keys

Key1: Entry No. (clustered)

Procedures

LoadDataFromFilter(VendorIdFilter: Text; GenJournalLineIdFilter: Text)

Relations

Vendor No.: TableRelation Table 23 “Vendor”

Pages and codeunits on this table

Page 30073 “APIV2 - Apply Vendor Entries” (source 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: "Vendor Ledger Entry Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.