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

Codeunit 113 "Vend. Entry-Edit"

Base Application · Microsoft.Purchases.Payables

Across versions

  1. BC23-26present
  2. BC271 events added
  3. BC28unchanged
  4. BC291 events changed, 1 events added
  5. BC30unchanged

Neighbourhood 19 connected objects and pages

Table 25 "Vendor Ledger Entry" (relates to)Vendor Ledger EntryPage 233 "Apply Vendor Entries" (calls, 3 links)Apply Vendor EntriesTable 81 "Gen. Journal Line" (calls, 3 links)Gen. Journal LineCodeunit 370 "Bank Acc. Reconciliation Post" (calls, 2 links)Bank Acc. Reconciliation PostReport 393 "Suggest Vendor Payments" (calls, 2 links)Suggest Vendor PaymentsCodeunit 1207 "Pmt Export Mgt Vend Ledg Entry" (calls)Pmt Export Mgt Vend Ledg EntryCodeunit 1250 "Match General Journal Lines" (calls)Codeunit 1255 "Match Bank Payments" (calls)Match Bank PaymentsCodeunit 1278 "Exp. User Feedback Gen. Jnl." (calls)Exp. User Feedback Gen. Jnl.Codeunit 1404 "Purch. Cr. Memo. Hdr. - Edit" (calls)Purch. Cr. Memo. Hdr. - EditCodeunit 1405 "Purch. Inv. Header - Edit" (calls)Purch. Inv. Header - EditCodeunit 20111 "AMC Bank Exp. CT Feedback" (calls)Codeunit 227 "VendEntry-Apply Posted Entries" (calls)VendEntry-Apply Posted EntriesCodeunit 6620 "Copy Document Mgt." (calls)Copy Document Mgt.Page 1159 "Purchase Documents" (calls)Purchase DocumentsPage 1190 "Create Payment" (calls)Create PaymentPage 29 "Vendor Ledger Entries" (calls)Table 1294 "Applied Payment Entry" (calls)Table 38 "Purchase Header" (calls)

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
TableNo Vendor Ledger Entry
Permissions TableData “Vendor Ledger Entry” = m, TableData “Detailed Vendor Ledg. Entry” = m

Events published

  • OnBeforeVendLedgEntryModify(var VendLedgEntry: Record "Vendor Ledger Entry"; FromVendLedgEntry: Record "Vendor Ledger Entry") (integration)
  • OnBeforeOnRun(var VendorLedgerEntryRec: Record "Vendor Ledger Entry"; var VendorLedgerEntry: Record "Vendor Ledger Entry"; var DetailedVendLedgerEntry: Record "Detailed Vendor Ledg. Entry"; var IsHandled: Boolean) + BC27 (integration)
  • OnRunOnBeforeDtldVendLedgEntryModifyAll(FromVendLedgEntry: Record "Vendor Ledger Entry"; var DtldVendLedgEntry: Record "Detailed Vendor Ledg. Entry"; var VendLedgEntry: Record "Vendor Ledger Entry") (integration)
  • OnRunOnAfterVendLedgEntryMofidy(var VendorLedgerEntry: Record "Vendor Ledger Entry") Δ BC29 (integration, obsolete 29.0)
  • OnRunOnAfterVendLedgEntryModify(var VendorLedgerEntryRec: Record "Vendor Ledger Entry"; var VendorLedgerEntry: Record "Vendor Ledger Entry") + BC29 (integration): Raised after the vendor ledger entry has been modified.
  • OnAfterLogFieldChanged(CurrVendorLedgerEntry: Record "Vendor Ledger Entry"; NewVendorLedgerEntry: Record "Vendor Ledger Entry"; var Changed: Boolean) (integration)

Procedures

  • SetOnHold(var VendorLedgerEntry: Record "Vendor Ledger Entry"; NewOnHold: Code[3])

Plus 1 local procedures.

Triggers

OnRun

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.

Recent changes

Countries that replace it

RU

Deprecations

  • procedure OnRunOnAfterVendLedgEntryMofidy: Pending 29.0 (#if not CLEAN29), “Replaced by event OnRunOnAfterVendLedgEntryModify()”

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: "codeunit", object_name: "Vend. Entry-Edit"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources