Page 558 "Analysis View Entries"
Base Application · Microsoft.Finance.Analysis
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Finance.Analysis · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Analysis View Entries |
| SourceTable | Analysis View Entry |
| PageType | List |
| UsageCategory | History |
| ApplicationArea | Dimensions |
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 |
|---|---|---|---|
| Control1 | Analysis View Code | Analysis View Code | Specifies the analysis view. from the table field |
| Business Unit Code | Business Unit Code | Specifies the code for the business unit that the analysis view is based on. from the table field | |
| Account No. | Account No. | Specifies the account that the analysis entry comes from. from the table field | |
| Account Source | Account Source | Specifies an account that you can use as a filter to define what is displayed in the Analysis by Dimensions window. | |
| Cash Flow Forecast No. | Cash Flow Forecast No. | Specifies a number for the cash flow forecast. from the table field | |
| Dimension 1 Value Code | Dimension 1 Value Code | Specifies the dimension value you selected for the analysis view dimension that you defined as Dimension 1 on the analysis view card. from the table field | |
| Dimension 2 Value Code | Dimension 2 Value Code | Specifies the dimension value you selected for the analysis view dimension that you defined as Dimension 2 on the analysis view card. from the table field | |
| Dimension 3 Value Code | Dimension 3 Value Code | Specifies the dimension value you selected for the analysis view dimension that you defined as Dimension 3 on the analysis view card. from the table field | |
| Dimension 4 Value Code | Dimension 4 Value Code | Specifies the dimension value you selected for the analysis view dimension that you defined as Dimension 4 on the analysis view card. from the table field | |
| Posting Date | Posting Date | Specifies the entry’s posting date. from the table field | |
| Amount | Amount | Specifies the amount of the analysis view budget entry. from the table field | |
| Debit Amount | Debit Amount | Specifies the total of the ledger entries that represent debits. from the table field | |
| Credit Amount | Credit Amount | Specifies the total of the ledger entries that represent credits. from the table field | |
| Add.-Curr. Amount | Add.-Curr. Amount | Specifies (in the additional reporting currency) the VAT difference that arises when you make a correction to a VAT amount on a sales or purchase document. from the table field | |
| Add.-Curr. Debit Amount | Add.-Curr. Debit Amount | Specifies, in the additional reporting currency, the amount of the debit entry. from the table field | |
| Add.-Curr. Credit Amount | Add.-Curr. Credit Amount | Specifies, in the additional reporting currency, the amount of the credit entry. from the table field |
Relations
- source table Table 365 “Analysis View Entry”
Pages and codeunits on this table
- Table 365 “Analysis View Entry” (drill-down page)
- Table 365 “Analysis View Entry” (lookup page)
Extended by
Called by
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.
- Page 9249 “Analysis by Dimensions Matrix” (1 call:
DrillDown → (object))
Documented on Microsoft Learn
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: "Analysis View Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.