tableAdministration & Setupofficial - Microsoftderived - from the source, no model text

Table 46905 "BC14 Vendor Posting Group"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Across versions

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

Neighbourhood 1 connected objects and pages

Codeunit 46905 "BC14 Vend. Post. Grp. Migrator" (pages and codeunits on it)BC14 Vend. Post. Grp. Migrator

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.

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · captioned “Vendor Posting Group Migration Data” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Vendor Posting Group Migration Data
Extensible false
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 Code Code[20] —
2 Payables Account Code[20] —
3 Service Charge Acc. Code[20] —
4 Payment Disc. Debit Acc. Code[20] —
5 Invoice Rounding Account Code[20] —
8 Debit Curr. Appln. Rndg. Acc. Code[20] —
9 Credit Curr. Appln. Rndg. Acc. Code[20] —
10 Debit Rounding Account Code[20] —
11 Credit Rounding Account Code[20] —
12 Payment Disc. Credit Acc. Code[20] —
13 Payment Tolerance Debit Acc. Code[20] —
14 Payment Tolerance Credit Acc. Code[20] —
20 Description Text[100] —

Keys

  • Key1: Code (clustered)

Pages and codeunits on this 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: "BC14 Vendor Posting Group"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources