codeunitInventoryofficial - Microsoftderived - from the source, no model text

Codeunit 910 "Asm. Item Jnl.-Check Line"

Base Application · Microsoft.Inventory.Journal

Across versions

  1. BC23-25not present
  2. BC26added
  3. BC27-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 5777 "Whse. Validate Source Line" (calls)Whse. Validate Source Line

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.Inventory.Journal · BC26-30 · source at ea08af5e · facts from BC29

Events published

  • OnAfterAssignInvtPutAwayRequired(ItemJournalLine: Record "Item Journal Line"; Location: Record Location; var InvtPutAwayLocation: Boolean) (integration)
  • OnAfterAssignInvtPickRequired(ItemJournalLine: Record "Item Journal Line"; Location: Record Location; var InvtPickLocation: Boolean) (integration)
  • OnAfterAssignWhsePickRequired(ItemJournalLine: Record "Item Journal Line"; Location: Record Location; var WhsePickLocation: Boolean) (integration)

Event subscriptions

  • OnRunOnCheckWarehouse subscribes to Codeunit “Item Jnl.-Check Line” OnRunOnCheckWarehouse

Procedures

2 local procedures, no public ones.

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.

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: "Asm. Item Jnl.-Check Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources