codeunitProjectsofficial - Microsoftderived - from the source, no model text

Codeunit 1018 "Purchase Doc. From Job"

Base Application · Microsoft.Projects.Project.Job

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-27unchanged
  4. BC281 events added
  5. BC29-30unchanged

Neighbourhood 4 connected objects and pages

Codeunit 5521 "Make Supply Orders (Yes/No)" (calls, 4 links)Make Supply Orders (Yes/No)Codeunit 5522 "Order Planning Mgt." (calls)Order Planning Mgt.Page 50 "Purchase Order" (calls)Purchase OrderPage 9307 "Purchase Order List" (calls)Purchase Order List

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.Projects.Project.Job · BC25-30 · source at ea08af5e · facts from BC29

Events published

  • OnCreatePurchaseOrderOnAfterBuildNoFilter(var Job: Record Job; var NoFilter: Text) + BC28 (integration)

Procedures

  • CreatePurchaseOrder(Job: Record Job)
  • CreateContractEntryNoFilter(JobTask: Record "Job Task")

Plus 4 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: "Purchase Doc. From Job"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources