codeunitInventoryofficial - Microsoftderived - from the source, no model text

Codeunit 20456 "Qlty. Batch Notif. Helper"

Quality Management · Microsoft.QualityManagement.Utilities

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 5 connected objects and pages

Codeunit 20411 "Qlty. Receiving Integration" (calls, 24 links)Qlty. Receiving IntegrationCodeunit 20407 "Qlty. Manufactur. Integration" (calls, 4 links)Qlty. Manufactur. IntegrationCodeunit 20412 "Qlty. Assembly Integration" (calls, 4 links)Qlty. Assembly IntegrationCodeunit 20438 "Qlty. Warehouse Integration" (calls, 4 links)Qlty. Warehouse IntegrationCodeunit 20404 "Qlty. Inspection - Create" (calls, 2 links)Qlty. Inspection - Create

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.

Quality Management · Microsoft.QualityManagement.Utilities · BC29-30 · source at ea08af5e · facts from BC29

Procedures

  • BeginBatch() (internal): Starts a batch and clears the tracked inspection numbers.
  • EndBatch() (internal): Ends the active batch and displays the newly created inspections when configured.
  • TrackCreatedInspection(InspectionNo: Code[20]; IsNewlyCreated: Boolean) (internal): Tracks a newly created inspection while a batch is active.
  • ConfigureForBatch(var QltyInspectionCreate: Codeunit "Qlty. Inspection - Create") (internal): Prevents immediate inspection display while a batch is active.

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

Recent changes

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: "Qlty. Batch Notif. Helper"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources