Table 6903 "Expense Rule Violation"

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

Properties

Property	Value
Access	Internal
DataClassification	CustomerContent

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	Expense No.	Code[20]	—	TableRelation Expense.“No.”
2	Line No.	Integer	—
3	Description	Text[500]	Specifies the description of the rule violation. via Page 6962 “Expense Rule Violations”

Keys

Key1: Expense No., Line No. (clustered)

Procedures

ClearRuleViolations(ExpenseNo: Code[20])
AddRuleViolation(ExpenseNo: Code[20]; Violation: Text[500])

Plus 1 local procedures.

Triggers

OnInsert

Referenced by

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

Table 6900 “Expense”: Rule Violations

Pages and codeunits on this table

Page 6962 “Expense Rule Violations” (source table)
Page 6963 “Expense Rule Violations API” (source table)

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

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