Table 95 "G/L Budget Name"
Base Application · Microsoft.Finance.GeneralLedger.Budget
Across versions
- BC23present
- BC24declaration changed
- BC25-28unchanged
- BC297 fields changed
- BC30unchanged
Neighbourhood 17 connected objects and pages
Base Application · Microsoft.Finance.GeneralLedger.Budget · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 121 “G/L Budget Names” (2 Learn pages).
Properties
| Property | Value |
|---|---|
| Caption | G/L Budget Name |
| 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 |
|---|---|---|---|---|
| 1 | Name Δ BC29 | Code[10] | Specifies the name of the general ledger budget. | NotBlank |
| 2 | Description Δ BC29 | Text[80] | Specifies a description of the general ledger budget name. | |
| 3 | Blocked Δ BC29 | Boolean | 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. | |
| 4 | Budget Dimension 1 Code Δ BC29 | Code[20] | Specifies a code for a budget dimension. You can specify four additional dimensions on each budget that you create. | TableRelation Table 348 “Dimension” |
| 5 | Budget Dimension 2 Code Δ BC29 | Code[20] | Specifies a code for a budget dimension. You can specify four additional dimensions on each budget that you create. | TableRelation Table 348 “Dimension” |
| 6 | Budget Dimension 3 Code Δ BC29 | Code[20] | Specifies a code for a budget dimension. You can specify four additional dimensions on each budget that you create. | TableRelation Table 348 “Dimension” |
| 7 | Budget Dimension 4 Code Δ BC29 | Code[20] | Specifies a code for a budget dimension. You can specify four additional dimensions on each budget that you create. | TableRelation Table 348 “Dimension” |
Keys
- Key1: Name (clustered)
Events published
OnOnModifyOnAfterCalcShouldUpdateDimensions(var GLBudgetName: Record "G/L Budget Name"; xGLBudgetName: Record "G/L Budget Name"; var ShouldUpdateDimensions: Boolean)(integration): Integration event raised during modify to determine if dimensions should be updated. Allows subscribers to customize the logic for when budget entry dimensions need updating.OnUpdateGLBudgetEntryDimOnBeforeModify(var GLBudgetName: Record "G/L Budget Name"; var GLBudgetEntry: Record "G/L Budget Entry")(integration): Integration event raised before modifying G/L Budget Entry dimensions during budget name updates. Allows subscribers to perform additional processing before budget entry dimension changes.
Procedures
2 local procedures, no public ones.
Triggers
OnDelete, OnModify
Relations
- lookup page Page 121 “G/L Budget Names”
- Budget Dimension 1 Code: TableRelation Table 348 “Dimension”
- Budget Dimension 2 Code: TableRelation Table 348 “Dimension”
- Budget Dimension 3 Code: TableRelation Table 348 “Dimension”
- Budget Dimension 4 Code: TableRelation Table 348 “Dimension”
Referenced by
12 fields in 12 objects relate to this table (TableRelation or CalcFormula).
- Table 135 “Acc. Sched. KPI Web Srv. Setup”: G/L Budget Name
- Table 15 “G/L Account”: Budget Filter
- Table 334 “Column Layout”: Budget Name
- Table 366 “Analysis View Budget Entry”: Budget Name
- Table 374 “G/L Acc. Budget Buffer”: Budget Filter
- Table 376 “G/L Account (Analysis View)”: Budget Filter
- Table 6225 “Sust. Account (Analysis View)”: Budget Filter
- Table 840 “Cash Flow Forecast”: Default G/L Budget Name
- Table 846 “Cash Flow Worksheet Line”: G/L Budget Name
- Table 847 “Cash Flow Forecast Entry”: G/L Budget Name
- Table 85 “Acc. Schedule Line”: G/L Budget Filter
- Table 96 “G/L Budget Entry”: Budget Name
Pages and codeunits on this table
- Page 121 “G/L Budget Names” (source table)
- Page 30305 “API Finance - GL Budgets” (source table)
Ask your agent
Procedure bodies are not stored here (D10). 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: "G/L Budget Name"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.