Table 961 "Alt. Vendor Posting Group"
Base Application · Microsoft.Purchases.Vendor
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC281 fields changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Purchases.Vendor · captioned “Alternative Vendor Posting Group” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Alternative Vendor Posting Group |
| 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 | Vendor Posting Group | Code[20] | — | TableRelation Table 93 “Vendor Posting Group” (Vendor Posting Group) |
| 2 | Alt. Vendor Posting Group Δ BC28 | Code[20] | Specifies the vendor group for posting business transactions to general general ledger accounts. | TableRelation Table 93 “Vendor Posting Group” (Vendor Posting Group) |
Keys
- Key1: Vendor Posting Group, Alt. Vendor Posting Group (clustered)
Relations
- Alt. Vendor Posting Group: TableRelation Table 93 “Vendor Posting Group”
- Vendor Posting Group: TableRelation Table 93 “Vendor Posting Group”
Pages and codeunits on this table
- Page 936 “Alt. Vendor Posting Groups” (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: "Alt. Vendor Posting Group"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.