Table 850 "Cash Flow Manual Expense"

Base Application · Microsoft.CashFlow.Setup · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 859 “Cash Flow Manual Expenses” (1 Learn page).

Properties

Property	Value
Caption	Cash Flow Manual Expense
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
2	Code	Code[10]	Specifies the code of the record. via Page 859 “Cash Flow Manual Expenses”	NotBlank
3	Cash Flow Account No.	Code[20]	Specifies the number of the cash flow account that the entry on the manual revenue line is registered to. via Page 859 “Cash Flow Manual Expenses”	TableRelation Table 841 “Cash Flow Account” (Cash Flow Account)
4	Description	Text[100]	Specifies a description of the cash flow forecast entry. via Page 859 “Cash Flow Manual Expenses”
5	Starting Date	Date	Specifies the date of the cash flow entry. via Page 859 “Cash Flow Manual Expenses”
6	Ending Date	Date	Specifies the last date from which manual expenses should be registered for the cash flow forecast. via Page 859 “Cash Flow Manual Expenses”
7	Recurring Frequency	DateFormula	Specifies how often the entry on the manual expense line is registered, if the journal template used is set up to be recurring via Page 859 “Cash Flow Manual Expenses”
8	Amount Δ BC27	Decimal	Specifies the total amount in LCY that the manual expense consists of. The entered amount is the amount that is registered in the given time period per recurring frequency. via Page 859 “Cash Flow Manual Expenses”
9	Global Dimension 1 Code	Code[20]	Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. via Page 859 “Cash Flow Manual Expenses”	TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Global Dimension No.” = const(1), Blocked = const(false)))
10	Global Dimension 2 Code	Code[20]	Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. via Page 859 “Cash Flow Manual Expenses”	TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Global Dimension No.” = const(2), Blocked = const(false)))

Keys

Key1: Code (clustered)
Key2: Starting Date

Events published

OnAfterValidateShortcutDimCode(var CashFlowManualExpense: Record "Cash Flow Manual Expense"; var xCashFlowManualExpense: Record "Cash Flow Manual Expense"; FieldNumber: Integer; var ShortcutDimCode: Code[20]) (integration)
OnBeforeValidateShortcutDimCode(var CashFlowManualExpense: Record "Cash Flow Manual Expense"; var xCashFlowManualExpense: Record "Cash Flow Manual Expense"; FieldNumber: Integer; var ShortcutDimCode: Code[20]) (integration)

Procedures

ValidateShortcutDimCode(FieldNumber: Integer; var ShortcutDimCode: Code[20])
InitNewRecord()

Triggers

OnDelete, OnInsert, OnRename

Relations

drill-down page Page 859 “Cash Flow Manual Expenses”
lookup page Page 859 “Cash Flow Manual Expenses”
Global Dimension 1 Code: TableRelation Table 349 “Dimension Value”
Global Dimension 2 Code: TableRelation Table 349 “Dimension Value”
Cash Flow Account No.: TableRelation Table 841 “Cash Flow Account”

Pages and codeunits on this table

Page 859 “Cash Flow Manual Expenses” (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 408 “DimensionManagement” (5 calls: OnDelete → DeleteDefaultDim, OnInsert → UpdateDefaultDim, OnRename → RenameDefaultDim, …)

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: "Cash Flow Manual Expense"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.