Table 1827 "Business Unit Setup"
Base Application · Microsoft.Finance.Consolidation
Across versions
- BC23present
- BC24declaration changed
- BC25-28unchanged
- BC292 fields changed
- BC30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Finance.Consolidation · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 1827 “Business Units Setup Subform” (2 Learn pages).
Properties
| Property | Value |
|---|---|
| Caption | Business Unit Setup |
| 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 | Company Name Δ BC29 | Text[30] | Specifies the name of the company. | |
| 2 | Include Δ BC29 | Boolean | Specifies if the business unit is include on the subform. | |
| 3 | Completed | Boolean | — |
Keys
- Key1: Company Name (clustered)
Procedures
FillTable(ConsolidatedCompany: Text[30]): Populates the table with available companies for business unit consolidation setup, excluding the consolidated company.
Pages and codeunits on this table
- Page 1827 “Business Units Setup Subform” (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: "Business Unit Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.