Table extension 6908 "Expense Spend Request"

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

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	Requested For	Code[20]	Specifies the expense user for whom the spend request is being created.	TableRelation Table 6923 “Expense User” (Expense User); DataClassification CustomerContent
6901	Business Justification	Text[2048]	Specifies the business justification for the travel.	DataClassification CustomerContent
6902	Travel Policy Acknowledgment	Boolean	Specifies whether the travel policy has been acknowledged.	DataClassification CustomerContent
6903	International Travel	Boolean	Specifies whether the travel is international.	DataClassification CustomerContent
6904	Origin Country/Region Code	Code[10]	Specifies the origin country for the travel.	TableRelation Table 9 “Country/Region” (“Country/Region”.Code); DataClassification CustomerContent
6905	Dest. Country/Region Code	Code[10]	Specifies the destination country for the travel.	TableRelation Table 9 “Country/Region” (“Country/Region”.Code); DataClassification CustomerContent
6906	Restrictions	Text[250]	Specifies any travel restrictions that apply.	DataClassification CustomerContent
6907	Per Diem Included	Boolean	Specifies whether per diem is included in the requisition.	DataClassification CustomerContent
6910	Requested For Name	Text[100]	Specifies the name of the expense user for whom the spend request is being created.	FlowField: lookup(“Expense User”.Name where(“No.” = field(“Requested For”)))
6911	Actual Start Date and Time	DateTime	Specifies the actual start date and time of the travel.	DataClassification CustomerContent
6912	Actual End Date and Time	DateTime	Specifies the actual end date and time of the travel.	DataClassification CustomerContent

Procedures

InsertRequestedForTraveler() (internal)

Plus 5 local procedures.

Triggers

OnDelete

Relations

extends Table 6840 “Spend Request”
Requested For Name: CalcFormula Table 6923 “Expense User”
Requested For: TableRelation Table 6923 “Expense User”
Dest. Country/Region Code: TableRelation Table 9 “Country/Region”
Origin Country/Region Code: TableRelation Table 9 “Country/Region”

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: UpdateRequestedForTraveler → GetResponseOrDefault)
Codeunit 9500 “Sequence No. Mgt.” (1 call: GetNextTravelerLineNo → GetNextSeqNo)

Recent changes

2026-10-02 #12074 Expense Agent: travel request expense location, per-traveler reports, activity log and submitter comment (main, BC30, feature)
2026-09-23 #11595 [Master] Bug 650348: [Expense Agent] Closed travel requests are editable and are missing approver info. (main, BC30, fix)
2026-09-23 #11593 [29.x] - Bug 650481[Expense Agent] Closed travel requests are editable and are missing approver info. (releases/29.x, BC29, fix)
2026-09-09 #11007 Add Travel Request API lifecycle to Expense Agent (main, BC30, feature)
2026-08-10 #9391 [Master] - Slice 616928: [Expense Management] [App part] Expense Managements Travel Requisitions 💸 (main, BC30, feature, added)

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