Page 120 "G/L Budget Entries"
Base Application · Microsoft.Finance.GeneralLedger.Budget
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Finance.GeneralLedger.Budget · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | G/L Budget Entries |
| SourceTable | G/L Budget Entry |
| PageType | List |
| UsageCategory | History |
| ApplicationArea | 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 |
|---|---|---|---|
| Control1 | Budget Name | Budget Name | Specifies the name of the G/L budget that the entry belongs to. from the table field |
| Date | Date | Specifies the date of the budget entry. from the table field | |
| G/L Account No. | G/L Account No. | Specifies the number of the G/L account that the budget entry applies to, or, the account on the line where the budget figure has been entered. from the table field | |
| Description | Description | Specifies a description of the budget figure. from the table field | |
| 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. from the table field | |
| 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. from the table field | |
| Budget Dimension 1 Code | Budget Dimension 1 Code | Specifies the dimension value code for the Budget Dimension 1 Code the budget entry is linked to. from the table field | |
| Budget Dimension 2 Code | Budget Dimension 2 Code | Specifies the dimension value code for the Budget Dimension 2 Code the budget entry is linked to. from the table field | |
| Budget Dimension 3 Code | Budget Dimension 3 Code | Specifies the dimension value code for the Budget Dimension 3 Code the budget entry is linked to. from the table field | |
| Budget Dimension 4 Code | Budget Dimension 4 Code | Specifies the dimension value code for the Budget Dimension 4 Code the budget entry is linked to. from the table field | |
| Business Unit Code | Business Unit Code | Specifies the code for the business unit that the budget entry is linked to. from the table field | |
| Amount | Amount | Specifies the amount of the budget entry. from the table field | |
| Entry No. | Entry No. | Specifies the number of the entry, as assigned from the specified number series when the entry was created. from the table field | |
| Dimension Set ID | Dimension Set ID | Specifies a reference to a combination of dimension values. The actual values are stored in the Dimension Set Entry table. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Entry | 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. | |
| Set Dimension Filter | Limit the entries according to the dimension filters that you specify. NOTE: If you use a high number of dimension combinations, this function may not work and can result in a message that the SQL server only supports a maximum of 2100 parameters. |
Procedures
4 local procedures, no public ones.
Triggers
OnDeleteRecord, OnInit, OnModifyRecord, OnNewRecord, OnOpenPage
Relations
- source table Table 96 “G/L Budget Entry”
Pages and codeunits on this table
- Table 96 “G/L Budget Entry” (drill-down page)
- Table 96 “G/L Budget Entry” (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 410 “Update Analysis View” (2 calls:
OnDeleteRecord → SetLastBudgetEntryNo,OnModifyRecord → SetLastBudgetEntryNo)
Called by
- Page 559 “Analysis View Budget Entries” (1 call:
DrillDown → (object)) - Page 9233 “G/L Balance by Dim. 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: "G/L Budget Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.