Codeunit 5957 "Serv. Posting Selection Mgt."

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

Procedures

• ConfirmPostServiceDocument(var ServiceHeaderToPost: Record "Service Header"; var Ship: Boolean; var Consume: Boolean; var Invoice: Boolean; DefaultOption: Integer; WithPrint: Boolean; WithEmail: Boolean; PreviewMode: Boolean): Boolean
• CheckUserCanInvoiceService()

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 99 “Posting Selection Management” (4 calls: CheckUserCanInvoiceService → GetPostingInvoiceProhibitedErr, ConfirmPostServiceDocument → GetPostConfirmationMessage, ConfirmPostServiceDocument → GetShipConfirmationMessage, …)
• Codeunit 5700 “User Setup Management” (2 calls: CheckUserCanInvoiceService → GetServiceInvoicePostingPolicy, ConfirmPostServiceDocument → GetServiceInvoicePostingPolicy)
• Codeunit 27 “Confirm Management” (1 call: ConfirmPostServiceDocument → GetResponseOrDefault)
• Codeunit 9070 “Document Errors Mgt.” (1 call: ConfirmPostServiceDocument → GetNothingToPostErrorMsg)

Called by

• Codeunit 5981 “Service-Post (Yes/No)” (1 call: ConfirmPost → ConfirmPostServiceDocument)
• Codeunit 5982 “Service-Post+Print” (1 call: ConfirmPostAndPrint → ConfirmPostServiceDocument)

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. Posting Selection Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.