Codeunit 5770 "Whse.-Service Release"
Base Application · Microsoft.Service.Document
Across versions
- BC23present
- BC241 procedures added
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Service.Document · BC23-30 · source at ea08af5e · facts from BC29
Events published
OnAfterCreateWhseRqst(var ServiceHeader: Record "Service Header"; var ServiceLine: Record "Service Line"; WhseType: Option)(integration)OnAfterRelease(var ServiceHeader: Record "Service Header")(integration)OnAfterReleaseSetFilters(var ServiceLine: Record "Service Line"; ServiceHeader: Record "Service Header")(integration)OnAfterReopen(var ServiceHeader: Record "Service Header")(integration)OnBeforeCreateWhseRequest(var WarehouseRequest: Record "Warehouse Request"; ServiceHeader: Record "Service Header"; ServiceLine: Record "Service Line")(integration)OnBeforeRelease(var ServiceHeader: Record "Service Header")(integration)OnBeforeReopen(var ServiceHeader: Record "Service Header")(integration)
Procedures
Release(ServiceHeader: Record "Service Header")Reopen(ServiceHeader: Record "Service Header")CreateWarehouseRequest(var ServiceHeader: Record "Service Header"; var ServiceLine: Record "Service Line"; WhseType: Enum "Warehouse Request Type")UpdateExternalDocNoForReleasedOrder(ServiceHeader: Record "Service Header")+ BC24
Plus 2 local procedures.
Triggers
OnRun
Called by
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 416 “Release Service Document” (2 calls:
Code → Release,Reopen → Reopen) - Codeunit 5980 “Service-Post” (1 call:
PostWithLines → Release)
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: "Whse.-Service Release"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.