Codeunit 5806 "Item Ledger Entry-Edit"
Base Application · Microsoft.Inventory.Costing
Across versions
- BC23not present
- BC24added
- BC25-27unchanged
- BC281 procedures added
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Inventory.Costing · BC24-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Permissions | tabledata “Item Ledger Entry” = rm, tabledata “Item Application Entry” = rm, tabledata “Item” = rm |
Procedures
SetAppliedEntriesToAdjust(var ItemLedgerEntry: Record "Item Ledger Entry")
Plus 1 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 8703 “Feature Telemetry” (1 call:
SetAppliedEntriesToAdjust → LogUsage)
Called by
- Page 38 “Item Ledger Entries” (1 call:
SetAppliedEntriesToAdjust → SetAppliedEntriesToAdjust)
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: "Item Ledger Entry-Edit"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.