Table 173 "Standard Purchase Code"

Base Application · Microsoft.Purchases.Document · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 177 “Standard Purchase Codes” (2 Learn pages), Page 175 “Standard Purchase Code Card” (1).

Properties

Property	Value
Caption	Standard Purchase Code
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 Δ BC28	Code[10]	Specifies a code which identifies this standard purchase code.	NotBlank
2	Description Δ BC28	Text[100]	Specifies a description of the standard purchase code.
3	Currency Code Δ BC28	Code[10]	Specifies the currency code of the amounts on the standard purchase lines.	TableRelation Table 4 “Currency”

Keys

Key1: Code (clustered)

Triggers

OnDelete

Relations

lookup page Page 177 “Standard Purchase Codes”
Currency Code: TableRelation Table 4 “Currency”

Referenced by

2 fields in 2 objects relate to this table (TableRelation or CalcFormula).

Table 174 “Standard Purchase Line”: Standard Purchase Code
Table 175 “Standard Vendor Purchase Code”: Code

Pages and codeunits on this table

Page 175 “Standard Purchase Code Card” (source table)
Page 177 “Standard Purchase Codes” (source table)

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Codeunit 27 “Confirm Management” (1 call: OnDelete → GetResponseOrDefault)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Standard Purchase Code"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.