Codeunit 903 "Release Assembly Document"

Base Application · Microsoft.Assembly.Document · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnAfterReleaseAssemblyDoc(var AssemblyHeader: Record "Assembly Header") (integration)
• OnAfterReopenAssemblyDoc(var AssemblyHeader: Record "Assembly Header") (integration)
• OnBeforeReleaseAssemblyDoc(var AssemblyHeader: Record "Assembly Header") (integration)
• OnBeforeReopenAssemblyDoc(var AssemblyHeader: Record "Assembly Header") (integration)

Procedures

• Reopen(var AssemblyHeader: Record "Assembly Header")

Triggers

OnRun

Relations

• runs on Table 900 “Assembly Header”

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 904 “Whse.-Assembly Release” (2 calls: OnRun → Release, Reopen → Reopen)

Called by

• Codeunit 414 “Release Sales Document” (2 calls: ReleaseATOs → (object), ReopenATOs → Reopen)
• Codeunit 900 “Assembly-Post” (1 call: InitPost → (object))
• Table 900 “Assembly Header” (1 call: PerformManualRelease → (object))
• Table 904 “Assemble-to-Order Link” (1 call: AsmReopenIfReleased → Reopen)

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: "Release Assembly Document"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.