Codeunit 38502 "AR External Events"

ExternalEvents · Microsoft.Integration.ExternalEvents · BC29-30 · source at ea08af5e · facts from BC29

Event subscriptions

• OnAfterFinalizePostingSalesInvoice subscribes to Codeunit “Sales-Post” OnAfterFinalizePosting
• OnAfterValidateCustomerBlocked subscribes to Table “Customer” OnAfterValidateEvent (Blocked)
• OnAfterCustLedgEntryInsert subscribes to Codeunit “Gen. Jnl.-Post Line” OnAfterCustLedgEntryInsert

Procedures

• SalesInvoicePosted(SalesInvoiceAPIId: Guid; SalesInvoiceSystemId: Guid; Url: Text[250]; WebClientUrl: Text[250])
• SalesCreditMemoPosted(SalesCreditMemoAPIId: Guid; SalesCreditMemoSystemId: Guid; Url: Text[250]; WebClientUrl: Text[250])
• SalesShipmentPosted(SalesShipmentId: Guid; Url: Text[250]; WebClientUrl: Text[250])

Plus 4 local procedures.

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 38500 “External Events Helper” (3 calls: OnAfterCustLedgEntryInsert → CreateLink, OnAfterFinalizePostingSalesInvoice → CreateLink, OnAfterValidateCustomerBlocked → CreateLink)

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: "AR External Events"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.