Table 4040 "GP Segment Name"
HybridGP · Microsoft.DataMigration.GP
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
HybridGP · Microsoft.DataMigration.GP · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| DataClassification | SystemMetadata |
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 | Text[50] | — | DataClassification OrganizationIdentifiableInformation |
| 2 | Segment Number | Integer | — | |
| 3 | Segment Name | Text[30] | — |
Keys
- PK: Segment Name, Company Name (clustered)
Referenced by
5 fields in 2 objects relate to this table (TableRelation or CalcFormula).
- Table 4044 “GP Company Migration Settings”: NumberOfSegments, Global Dimension 1, Global Dimension 2
- Table 40105 “GP Company Additional Settings”: Global Dimension 1, Global Dimension 2
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: "GP Segment Name"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.