Codeunit 7126 "Create Expense Rule Conditions"

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

Properties

Procedures

• CreateExpenseRuleConditions(var ExpenseRulecondition: Record "Expense Rule Condition") (internal)
• InsertExpenseRuleCondition(var ExpenseRuleCondition: Record "Expense Rule Condition"; ExpenseCategoryCode: Code[20]; ExpenseLocationCode: Code[20]; EffectiveDate: Date; LineNo: Integer; ConditionType: Enum "Expense Rule Condition Type"; Value: Decimal) (internal)

Triggers

OnRun

Relations

• runs on Table 6926 “Expense Rule Condition”

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 7124 “Create Expense Locations” (255 calls: CreateExpenseRuleConditions → AfghanistanAll, CreateExpenseRuleConditions → AlandIslandsAll, CreateExpenseRuleConditions → AlbaniaAll, …)
• Codeunit 6973 “Create Expense Categories” (4 calls: CreateExpenseRuleConditions → GetENTERTAINTxt, CreateExpenseRuleConditions → GetMileageTxt, CreateExpenseRuleConditions → GetPERDIEMTxt, …)

Called by

• Codeunit 6973 “Create Expense Categories” (1 call: BuildRuleConditionSeeds → (object))

Recent changes

• 2026-09-15 #11425 Bug 650137: [29.x] Expense Locations and Per-diem rules in configuration - Backport (releases/29.x, BC29, feature, added)
• 2026-09-14 #11381 Slice 641293: [Expense Agent] Expense Locations and Per-diem rules in configuration - added check for existing country (main, BC30, fix)
• 2026-09-10 #10155 Slice 641293: [Expense Agent] Expense Locations and Per-diem rules in configurationAdded more locations (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: "codeunit", object_name: "Create Expense Rule Conditions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.