Table extension 6906 "Exp. Project Ledg. Entry Ext"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Extends Job Ledger Entry.
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 | Expense Report No. | Code[20] | Specifies the number of the posted expense report associated with this project ledger entry. | TableRelation Table 6915 “Posted Expense Report Header” (“Posted Expense Report Header”.“No.”); DataClassification CustomerContent |
| 6901 | Expense Report Line No. | Integer | Specifies the line number of the posted expense report associated with this project ledger entry. | TableRelation Table 6916 “Posted Expense Report Line” (“Posted Expense Report Line”.“Line No.” where(“Document No.” = field(“Expense Report No.”))); DataClassification CustomerContent |
Relations
- extends Table 169 “Job Ledger Entry”
- Expense Report No.: TableRelation Table 6915 “Posted Expense Report Header”
- Expense Report Line No.: TableRelation Table 6916 “Posted Expense Report 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: "Exp. Project Ledg. Entry Ext"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.