codeunitPurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Codeunit 7181 "Purchases Info-Pane Management"

Base Application · Microsoft.Purchases.Document

Across versions

  1. BC23-24present
  2. BC251 events added
  3. BC26-30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 5790 "Available to Promise" (calls)Available to Promise

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.Purchases.Document · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnBeforeCalcAvailability(var Item: Record Item; PurchaseLine: Record "Purchase Line"; var AvailableQuantity: Decimal; var IsHandled: Boolean) (integration)
  • OnBeforeGetItemOnPurchasesInfoPaneManagement(var PurchaseLine: Record "Purchase Line"; var Result: Boolean; var IsHandled: Boolean) + BC25 (integration)

Procedures

  • CalcAvailability(var PurchLine: Record "Purchase Line"): Decimal
  • CalcNoOfPurchasePrices(var PurchLine: Record "Purchase Line"): Integer
  • CalcNoOfPurchLineDisc(var PurchLine: Record "Purchase Line"): Integer

Plus 1 local procedures.

Triggers

OnRun

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: "Purchases Info-Pane Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources