BC Observatoryunofficial, made by waldo
tableextensionFinanceofficial - Microsoftderived - from the source, no model text

Table extension 681 "Paym. Prac. Vend. Ledg. Entry"

PaymentPractices · Microsoft.Finance.Analysis

Open in Claude681.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Table 25 "Vendor Ledger Entry" (relates to)Vendor Ledger Entry

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.

PaymentPractices · Microsoft.Finance.Analysis · BC29-30 · source at ea08af5e · facts from BC29

Extends Vendor Ledger Entry.

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
680 SCF Payment Date Date Specifies when the supplier received payment from a finance provider under a supply chain finance arrangement. When filled in, replaces the payment posting date for calculating actual payment days. DataClassification CustomerContent

Relations

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

Evidence 1 sources