Page 121 "G/L Budget Names"
Base Application · Microsoft.Finance.GeneralLedger.Budget
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Finance.GeneralLedger.Budget · captioned “G/L Budgets” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | G/L Budgets |
| SourceTable | G/L Budget Name |
| PageType | List |
| UsageCategory | Lists |
| 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 | Name | Name | Specifies the name of the general ledger budget. from the table field |
| Description | Description | Specifies a description of the general ledger budget name. from the table field | |
| Global Dimension 1 Code | GLSetup."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 | GLSetup."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. | |
| Budget Dimension 1 Code | Budget Dimension 1 Code | Specifies a code for a budget dimension. You can specify four additional dimensions on each budget that you create. from the table field | |
| Budget Dimension 2 Code | Budget Dimension 2 Code | Specifies a code for a budget dimension. You can specify four additional dimensions on each budget that you create. from the table field | |
| Budget Dimension 3 Code | Budget Dimension 3 Code | Specifies a code for a budget dimension. You can specify four additional dimensions on each budget that you create. from the table field | |
| Budget Dimension 4 Code | Budget Dimension 4 Code | Specifies a code for a budget dimension. You can specify four additional dimensions on each budget that you create. from the table field | |
| Blocked | Blocked | Specifies that the related record is blocked from being posted in transactions, for example a customer that is declared insolvent or an item that is placed in quarantine. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Edit Budget | Specify budgets that you can create in the general ledger application area. If you need several different budgets, you can create several budget names. | |
| Report | Trial Balance/Budget (Obsolete) obsolete Pending 28.0; #if not CLEAN28 | View budget details for the specified period. |
Procedures
GetSelectionFilter(): Text: Returns a selection filter string based on the currently selected budget names in the page. Used for filtering operations on selected budget records.
Triggers
OnOpenPage
Relations
- source table Table 95 “G/L Budget Name”
Pages and codeunits on this table
- Table 95 “G/L Budget Name” (lookup page)
Extended by
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 46 “SelectionFilterManagement” (1 call:
GetSelectionFilter → GetSelectionFilterForGLBudgetName)
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 Names"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.