codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model text

Codeunit 88 "Sales Post via Job Queue"

Base Application · Microsoft.Sales.Posting

Across versions

  1. BC23present
  2. BC241 procedures added, 1 procedures removed
  3. BC25-30unchanged

Neighbourhood 11 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue EntryCodeunit 1380 "Batch Processing Mgt." (calls, 3 links)Batch Processing Mgt.Codeunit 2849 "Cost Adj. Scheduling Manager" (calls, 3 links)Cost Adj. Scheduling ManagerCodeunit 1371 "Sales Batch Post Mgt." (calls)Sales Batch Post Mgt.Codeunit 1373 "Batch Posting Print Mgt." (calls)Batch Posting Print Mgt.Codeunit 414 "Release Sales Document" (calls)Release Sales DocumentCodeunit 453 "Job Queue - Enqueue" (calls)Job Queue - EnqueueCodeunit 80 "Sales-Post" (calls)Sales-PostCodeunit 81 "Sales-Post (Yes/No)" (calls)Sales-Post (Yes/No)Codeunit 82 "Sales-Post + Print" (calls)Sales-Post + PrintTable 36 "Sales Header" (calls)

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
TableNo Job Queue Entry

Events published

  • OnBeforeEnqueueSalesDoc(var SalesHeader: Record "Sales Header"; var Handled: Boolean) (integration): Raised before enqueuing the sales document for background posting.
  • OnBeforeReleaseSalesDoc(var SalesHeader: Record "Sales Header") (integration): Raised before releasing the sales document prior to enqueuing.
  • OnBeforeSetJobQueueStatus(SalesHeader: Record "Sales Header"; NewJobQueueStatus: Option " ","Scheduled for Posting",Error,Posting; JobQueueEntry: Record "Job Queue Entry") (integration): Raised before setting the job queue status on the sales document.
  • OnEnqueueJobEntryOnBeforeEnqueue(SalesHeader: Record "Sales Header"; var JobQueueEntry: Record "Job Queue Entry") (integration): Raised before enqueuing the job entry for background posting.
  • OnRunOnAfterRunSalesPost(var SalesHeader: Record "Sales Header") (integration): Raised after the Sales-Post codeunit has successfully run in the job queue.
  • OnRunOnBeforeRunSalesPost(var SalesHeader: Record "Sales Header") (integration): Raised before the Sales-Post codeunit runs in the job queue.
  • OnBeforeBatchProcessingErrorReset(var JobQueueEntry: Record "Job Queue Entry"; var IsHandled: Boolean) (integration): Raised before resetting the batch ID after a posting error in the job queue.

Procedures

  • EnqueueSalesDoc(var SalesHeader: Record "Sales Header"): Enqueues the sales document for background posting via the job queue and displays a confirmation message.
  • EnqueueSalesDocWithUI(var SalesHeader: Record "Sales Header"; WithUI: Boolean): Enqueues the sales document for background posting via the job queue with optional user interface feedback.
  • CancelQueueEntry(var SalesHeader: Record "Sales Header"): Cancels the job queue entry for the sales document and resets the job queue status.
  • GetJobQueueCategoryCode(): Code[10] (internal): Gets the job queue category code for sales posting from setup, or creates a default category if needed.

Plus 6 local procedures.

Triggers

OnRun

Relations

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.

Called by

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

Evidence 1 sources