Page 857 "Cash Flow Manual Revenues"

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

Properties

Property	Value
Caption	Cash Flow Manual Revenues
SourceTable	Cash Flow Manual Revenue
PageType	List
UsageCategory	Lists
ApplicationArea	Basic, Suite

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
Control1000	Code	Code	Specifies the code of the record.
	Cash Flow Account No.	Cash Flow Account No.	Specifies the number of the cash flow account that the entry on the manual revenue line is registered to.
	Description	Description	Specifies a description of the cash flow forecast entry.
	Date	Starting Date	Specifies the date of the cash flow entry.
	Amount	Amount	Specifies the total amount in LCY that the manual revenue consists of. The entered amount is the amount which is registered in the given time period per recurring frequency.
	Recurrence	`Recurrence`	Specifies a date formula for calculating the period length. The content of the field determines how often the entry on the manual revenue line is registered. For example, if the line must be registered every month, you can enter 1M.
	Recurring Frequency	Recurring Frequency	Specifies how often the entry on the manual revenue line is registered, if the journal template used is set up to be recurring
	End By	Ending Date	Specifies the last date from which manual revenues should be registered for the cash flow forecast.
	Global Dimension 1 Code	Global Dimension 1 Code	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.
	Global Dimension 2 Code	Global Dimension 2 Code	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.

Actions

Group	Action	ToolTip	Runs
Revenues	Dimensions	View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.	Page 540 “Default Dimensions”

Procedures

3 local procedures, no public ones.

Triggers

OnAfterGetCurrRecord, OnAfterGetRecord, OnDeleteRecord, OnInsertRecord, OnNewRecord

Relations

source table Table 849 “Cash Flow Manual Revenue”

Pages and codeunits on this table

Table 849 “Cash Flow Manual Revenue” (drill-down page)
Table 849 “Cash Flow Manual Revenue” (lookup page)

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 841 “Cash Flow Management” (1 call: GetRecord → RecurringFrequencyToRecurrence)

Documented on Microsoft Learn

Analyze cash flows

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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