Codeunit 95 "Purch Post Batch via Job Queue"

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

Properties

Events published

• OnPrintToPDFOnAfterReportInboxInsert(var ReportInbox: Record "Report Inbox"; var PurchaseHeader: Record "Purchase Header"; var RecRef: RecordRef) (integration)
• OnPrintToPDFOnBeforeReportRun(ReportId: Integer; RecRef: RecordRef; var OStream: OutStream; var IsSuccess: Boolean; var IsHandled: Boolean) (integration)

Procedures

• EnqueuePurchaseBatch(var PurchaseHeader: Record "Purchase Header"; var JobQueueEntry: Record "Job Queue Entry")

Plus 13 local procedures.

Triggers

OnRun

Relations

• runs on Table 472 “Job Queue Entry”

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 28 “Error Message Management” (2 calls: PostPurchaseBatch → LogLastError, PrintDocument → LogLastError)
• Codeunit 453 “Job Queue - Enqueue” (1 call: EnqueueJobQueueEntry → (object))
• Codeunit 90 “Purch.-Post” (1 call: PostPurchaseBatch → (object))

Called by

• Codeunit 1372 “Purchase Batch Post Mgt.” (1 call: ProcessBatchInBackground → EnqueuePurchaseBatch)

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: "Purch Post Batch via Job Queue"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.