pagePurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Page 62 "Applied Vendor Entries"

Base Application · Microsoft.Purchases.Payables

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 25 "Vendor Ledger Entry" (relates to)Vendor Ledger EntryCodeunit 1313 "Correct Posted Purch. Invoice" (calls)Correct Posted Purch. InvoiceReconcile vendor payment receipts or refunds in the payment journal (Learn pages)Reconcile vendor payment rec…

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.Purchases.Payables · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Applied Vendor Entries
SourceTable Vendor Ledger Entry
PageType List

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Control1 Posting Date Posting Date Specifies the vendor entry’s posting date. from the table field
Document Type Document Type Specifies the document type that the vendor entry belongs to. from the table field
Document No. Document No. Specifies the vendor entry’s document number. from the table field
Description Description Specifies a description of the vendor entry. from the table field
External Document No. External Document No. Specifies a document number that refers to the customer’s or vendor’s numbering system. from the table field
Global Dimension 1 Code Global Dimension 1 Code Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field
Global Dimension 2 Code Global Dimension 2 Code Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field
Purchaser Code Purchaser Code Specifies which purchaser is assigned to the vendor. from the table field
Currency Code Currency Code Specifies the currency code for the amount on the line. from the table field
Original Amount Original Amount Specifies the amount of the original entry. from the table field
Amount Amount Specifies the amount of the entry. from the table field
Debit Amount Debit Amount Specifies the total of the ledger entries that represent debits. from the table field
Credit Amount Credit Amount Specifies the total of the ledger entries that represent credits. from the table field
Closed by Amount Closed by Amount Specifies the amount that the entry was finally applied to (closed) with. from the table field
Closed by Currency Code Closed by Currency Code Specifies the currency code of the entry that was applied to (and closed) this vendor ledger entry. from the table field
Closed by Currency Amount Closed by Currency Amount Specifies the amount that was finally applied to (and closed) this vendor ledger entry. from the table field
User ID User ID Specifies the ID of the user who posted the entry, to be used, for example, in the change log. from the table field
Source Code Source Code Specifies the source code that specifies where the entry was created. from the table field
Reason Code Reason Code Specifies the reason code, a supplementary source code that enables you to trace the entry. from the table field
Entry No. Entry No. Specifies the number of the entry, as assigned from the specified number series when the entry was created. from the table field

Actions

Group Action ToolTip Runs
Entry Dimensions View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.
Detailed Ledger Entries View a summary of the all posted entries and adjustments related to a specific vendor ledger entry. Page 574 “Detailed Vendor Ledg. Entries”
Processing Find entries… Find entries and documents that exist for the document number and posting date on the selected document. (Formerly this action was named Navigate.)
Show Posted Document Show details for the posted payment, invoice, or credit memo.
Show Document Attachment View documents or images that are attached to the posted invoice or credit memo.

Procedures

  • GetCreateVendorLedgerEntry(): Record "Vendor Ledger Entry"

Plus 2 local procedures.

Triggers

OnAfterGetCurrRecord, OnInit, OnOpenPage

Relations

Called by

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.

Documented on Microsoft Learn

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). 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: "page", object_name: "Applied Vendor Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources