Table 6925 "Expense Location"

ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 6920 “Expense Location Card” (1 Learn page), Page 6937 “Expense Locations” (1).

Properties

Property	Value
Caption	Expense Location
Access	Internal
DataClassification	CustomerContent
LookupPageId	Expense Locations
DrillDownPageId	Expense Location Card

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	No.	Code[20]	Specifies the location number. via Page 6920 “Expense Location Card”	NotBlank
2	Description	Text[100]	Specifies the description of the expense location. Used for per-diem calculations. via Page 6920 “Expense Location Card”
3	Country/Region Code	Code[10]	Specifies the country/region code for the expense location. via Page 6920 “Expense Location Card”	TableRelation Table 9 “Country/Region” (“Country/Region”.Code)
4	City	Text[30]	Specifies the city for the expense location. This field is optional and used only when multiple locations exist in the same country/region. via Page 6920 “Expense Location Card”	TableRelation Table 225 “Post Code” (if (“Country/Region Code” = const(‘’)) “Post Code”.City else if (“Country/Region Code” = filter(<> ‘’)) “Post Code”.City where(“Country/Region Code” = field(“Country/Region Code”)))
5	County	Text[30]	Specifies the state, province or county as a part of the address.

Keys

PK: No. (clustered)

Procedures

1 local procedures, no public ones.

Triggers

OnInsert, OnModify

Relations

drill-down page Page 6920 “Expense Location Card”
lookup page Page 6937 “Expense Locations”
City: TableRelation Table 225 “Post Code” (conditional)
Country/Region Code: TableRelation Table 9 “Country/Region”

Referenced by

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

Table 6900 “Expense”: Expense Location
Table 6905 “Expense Per Diem”: Expense Location
Table 6907 “Expense Report Line”: Expense Location
Table 6916 “Posted Expense Report Line”: Expense Location
Table 6926 “Expense Rule Condition”: Expense Location
Table 6927 “Expense Rule Header”: Expense Location

Pages and codeunits on this table

Page 6920 “Expense Location Card” (source table)
Page 6921 “Expense Locations API” (source table)
Page 6937 “Expense Locations” (source table)
Page 6970 “Exp. Locations Preview” (source table)
Codeunit 7124 “Create Expense Locations” (codeunit runs on it)

Recent changes

2026-08-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (main, BC30, feature, added)

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