Codeunit 79 "Sales-Post and Send"

Base Application · Microsoft.Sales.Posting · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnAfterPostAndBeforeSend(var SalesHeader: Record "Sales Header") (integration): Raised after the document has been posted but before it is sent to the customer.
• OnAfterPostAndSend(var SalesHeader: Record "Sales Header") (integration): Raised after the document has been posted and sent to the customer.
• OnBeforeConfirmAndSend(SalesHeader: Record "Sales Header"; var TempDocumentSendingProfile: Record "Document Sending Profile" temporary; var Result: Boolean; var IsHandled: Boolean) (integration): Raised before displaying the send confirmation dialog.
• OnBeforeConfirmPostAndSend(SalesHeader: Record "Sales Header"; var TempDocumentSendingProfile: Record "Document Sending Profile" temporary; var Result: Boolean; var IsHandled: Boolean) (integration): Raised before confirming the post and send operation.
• OnBeforeValidateElectronicFormats(SalesHeader: Record "Sales Header"; DocumentSendingProfile: Record "Document Sending Profile"; var IsHandled: Boolean) (integration): Raised before validating electronic document formats.
  • subscribers: Codeunit 6103 “E-Document Subscribers” OnBeforeValidateElectronicFormats
• OnBeforePostAndSend(var SalesHeader: Record "Sales Header"; var HideDialog: Boolean; var TempDocumentSendingProfile: Record "Document Sending Profile" temporary) (integration): Raised before posting and sending the sales document.
• OnCodeOnAfterConfirmPostAndSend(var SalesHeader: Record "Sales Header") (integration): Raised after the user confirms the post and send operation.
• OnCodeOnBeforePostSalesHeader(var SalesHeader: Record "Sales Header"; var TempDocumentSendingProfile: Record "Document Sending Profile" temporary; HideDialog: Boolean; var IsHandled: Boolean) (integration): Raised before posting the sales header in the post and send process.
• OnConfirmPostAndSendOnBeforeGetDocumentSendingProfile(SalesHeader: Record "Sales Header"; Customer: Record Customer; var DocumentSendingProfile: Record "Document Sending Profile"; var IsHandled: Boolean) (integration): Raised before retrieving the document sending profile for the customer.

Procedures

3 local procedures, no public ones.

Triggers

OnRun

Relations

• runs on Table 36 “Sales 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 1630 “Office Management” (2 calls: ConfirmPostAndSend → AttachAvailable, ConfirmPostAndSend → IsAvailable)
• Codeunit 80 “Sales-Post” (2 calls: Code → (object), Code → SendPostedDocumentRecord)
• Codeunit 81 “Sales-Post (Yes/No)” (1 call: Code → PostAndSend)
• Codeunit 9070 “Document Errors Mgt.” (1 call: OnRun → GetNothingToPostErrorMsg)
• Codeunit 99 “Posting Selection Management” (1 call: Code → CheckUserCanInvoiceSales)
• Page 365 “Post and Send Confirmation” (1 call: ConfirmPostAndSend → (object))

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: "Sales-Post and Send"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.