Table extension 7110 "Expense Employee"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-29not present
- BC30present
Neighbourhood 2 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC30 · source at f18567dc · facts from BC30
Extends Employee.
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 |
|---|---|---|---|---|
| 7100 | Is Expense User | Boolean | Specifies whether the employee is linked to an expense user. via Page 6917 “Employees API” | FlowField: exist(“Expense User” where(“Employee No.” = field(“No.”))) |
| 7101 | Travel Request SystemId Filter | Guid | — | FlowFilter |
Relations
- extends Table 5200 “Employee”
- Is Expense User: CalcFormula Table 6923 “Expense User”
Recent changes
- 2026-09-17 #11333 Align travel request APIs with employee travelers and expense report lifecycle (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: "tableextension", object_name: "Expense Employee"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.