Table extension 6976 "Gen. Journal Line"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 4 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Extends Gen. Journal Line.
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 |
|---|---|---|---|---|
| 6500 | Expense User No. | Code[20] | — | TableRelation Table 6923 “Expense User” (“Expense User”.“No.”); not editable; DataClassification CustomerContent |
| 6501 | Expense Category | Code[20] | Specifies the expense category for the journal line. via Page extension 7058 “WHT General Journal” | TableRelation Table 6921 “Expense Category” (“Expense Category”.Code); DataClassification CustomerContent |
| 6502 | Expense Subcategory Code | Code[20] | — | TableRelation Table 6929 “Expense Subcategory” (“Expense SubCategory”.Code where(“Expense Category Code” = field(“Expense Category”))); DataClassification CustomerContent |
Relations
- Expense Category: TableRelation Table 6921 “Expense Category”
- Expense User No.: TableRelation Table 6923 “Expense User”
- Expense Subcategory Code: TableRelation Table 6929 “Expense Subcategory”
- extends Table 81 “Gen. Journal Line”
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). 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: "Gen. Journal Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.