Table 170 "Standard Sales Code"

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

Learn documents this table through its pages: Page 172 “Standard Sales Codes” (2 Learn pages), Page 170 “Standard Sales Code Card” (1).

Properties

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

Keys

Key1: Code (clustered)

Triggers

OnDelete

Relations

lookup page Page 172 “Standard Sales Codes”
Currency Code: TableRelation Table 4 “Currency”

Referenced by

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

Table 171 “Standard Sales Line”: Standard Sales Code
Table 172 “Standard Customer Sales Code”: Code

Pages and codeunits on this table

Page 170 “Standard Sales Code Card” (source table)
Page 172 “Standard Sales 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 Sales Code"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.