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

Table 9151 "My Vendor"

Base Application · Microsoft.Purchases.Vendor

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC284 fields changed
  5. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Table 23 "Vendor" (relates to)VendorTable 380 "Detailed Vendor Ledg. Entry" (relates to)Detailed Vendor Ledg. EntryPage 9151 "My Vendors" (pages and codeunits on it)My Vendors

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.Vendor · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption My Vendor
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 User ID Code[50] — TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation
2 Vendor No. Δ BC28 Code[20] Specifies the vendor numbers that are displayed in the My Vendor Cue on the Role Center. TableRelation Table 23 “Vendor”; NotBlank
3 Name Δ BC28 Text[100] Specifies the name of the record. not editable
4 Phone No. Δ BC28 Text[30] Specifies the vendor’s phone number. not editable
5 Balance (LCY) Δ BC28 Decimal Specifies the balance. via Page 9151 “My Vendors” FlowField: - sum(“Detailed Vendor Ledg. Entry”.“Amount (LCY)” where(“Vendor No.” = field(“Vendor No.”))); not editable

Keys

  • Key1: User ID, Vendor No. (clustered)
  • Key2: Name
  • Key3: Phone No.

Procedures

  • SetVendorFields()

Relations

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: "My Vendor"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources