Codeunit 5955 "Serv. Dimension Management"

Base Application · Microsoft.Service.Document · BC25-30 · source at ea08af5e · facts from BC29

Events published

• OnAfterServiceLineTypeToTableID(LineType: Enum "Service Line Type"; var TableId: Integer) (integration)

Event subscriptions

• DimensionManagementOnAfterSetSourceCodeWithVar subscribes to Codeunit “DimensionManagement” OnAfterSetSourceCode
• DimensionManagementOnAfterDefaultDimObjectNoWithoutGlobalDimsList subscribes to Codeunit “DimensionManagement” OnAfterDefaultDimObjectNoWithoutGlobalDimsList
• OnAfterGetDefaultDimTableList subscribes to Table “Default Dimension Priority” OnAfterGetDefaultDimTableList

Procedures

• ServiceLineTypeToTableID(LineType: Enum "Service Line Type"): Integer

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 408 “DimensionManagement” (2 calls: DimensionManagementOnAfterDefaultDimObjectNoWithoutGlobalDimsList → DefaultDimInsertTempObject, OnAfterGetDefaultDimTableList → InsertObject)

Called by

• Table 5902 “Service Line” (2 calls: GetTableValuePair → ServiceLineTypeToTableID, InitDefaultDimensionSources → ServiceLineTypeToTableID)
• Codeunit 5988 “Serv-Documents Mgt.” (1 call: CheckDimValuePosting → ServiceLineTypeToTableID)
• Table 5997 “Standard Service Line” (1 call: InitDefaultDimensionSources → ServiceLineTypeToTableID)

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: "codeunit", object_name: "Serv. Dimension Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.