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

Table 460 "Purchase Prepayment %"

Base Application · Microsoft.Purchases.Document

Across versions

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

Neighbourhood 3 connected objects and pages

Table 23 "Vendor" (relates to)VendorTable 27 "Item" (relates to)ItemPage 665 "Purchase Prepmt. Percentages" (pages and codeunits on it)Purchase Prepmt. Percentages

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

Properties

Property Value
Caption Purchase Prepayment %
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 Item No. Δ BC28 Code[20] Specifies the number of the item for which the prepayment percentage is valid. TableRelation Table 27 “Item”; NotBlank
2 Vendor No. Δ BC28 Code[20] Specifies the number of the vendor that the prepayment percentage for this item is valid for. TableRelation Table 23 “Vendor”
3 Starting Date Δ BC28 Date Specifies the date from which the purchase prepayment percentage is valid.
4 Ending Date Δ BC28 Date Specifies the date to which the purchase prepayment percentage is valid.
5 Prepayment % Δ BC28 Decimal Specifies the prepayment percentage to use to calculate the prepayment for purchases.

Keys

  • Key1: Item No., Vendor No., Starting Date (clustered)
  • Key2: Vendor No.

Procedures

1 local procedures, no public ones.

Triggers

OnInsert

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

Evidence 1 sources