Table 317 "Payable Vendor Ledger Entry"
Base Application · Microsoft.Purchases.Payables
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC282 fields changed
- BC29-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Purchases.Payables · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Payable Vendor Ledger Entry |
| 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 | Priority | Integer | — | |
| 2 | Vendor No. | Code[20] | — | TableRelation Table 23 “Vendor” |
| 3 | Entry No. | Integer | — | |
| 4 | Vendor Ledg. Entry No. | Integer | — | TableRelation Table 25 “Vendor Ledger Entry” (Vendor Ledger Entry) |
| 5 | Amount Δ BC28 | Decimal | — | |
| 6 | Amount (LCY) Δ BC28 | Decimal | — | |
| 7 | Currency Code | Code[10] | — | TableRelation Table 4 “Currency” |
| 8 | Positive | Boolean | — | |
| 9 | Future | Boolean | — |
Keys
- Key1: Priority, Vendor No., Currency Code, Positive, Future, Entry No. (clustered)
Relations
- Vendor No.: TableRelation Table 23 “Vendor”
- Vendor Ledg. Entry No.: TableRelation Table 25 “Vendor Ledger Entry”
- Currency Code: TableRelation Table 4 “Currency”
Countries that replace it
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). 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: "Payable Vendor Ledger Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.