Table extension 7109 "Exp. Spend Req. Detail"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Extends Spend Request Detail.
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 |
|---|---|---|---|---|
| 6900 | Type | Enum “Exp. Spend Req. Line Type” | Specifies whether the line covers a specific expense category or a lump sum amount. via Page 7137 “Travel Request Subform” | enum Enum 7108 “Exp. Spend Req. Line Type”; DataClassification CustomerContent |
| 6901 | Expense Category Code | Code[20] | Specifies the expense category for the line. Available only when Type is Category. via Page 7137 “Travel Request Subform” | TableRelation Table 6921 “Expense Category” (“Expense Category”.Code where(Inactive = const(false))); DataClassification CustomerContent |
Procedures
1 local procedures, no public ones.
Relations
- extends Table 6841 “Spend Request Detail”
- Expense Category Code: TableRelation Table 6921 “Expense Category”
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: "Exp. Spend Req. Detail"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.