Codeunit 1033 "Job-Process Plan. Lines"

Base Application · Microsoft.Projects.Project.Planning · BC24-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnRunOnAfterSetFiltersOnJobPlanningLine(SalesHeader: Record "Sales Header"; SalesLine: Record "Sales Line"; var FilteredJobPlanningLine: Record "Job Planning Line") (integration)

Procedures

• SetSalesHeader(var SalesHeader2: Record "Sales Header")
• CreateInvLines(var JobPlanningLine2: Record "Job Planning Line")

Plus 3 local procedures.

Triggers

OnRun

Relations

• runs on Table 37 “Sales Line”

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 1002 “Job Create-Invoice” (1 call: CreateInvLines → CreateSalesInvoiceLines)

Called by

• Page 1043 “Get Job Planning Lines” (2 calls: CreateLines → CreateInvLines, CreateLines → SetSalesHeader)
• Page 47 “Sales Invoice Subform” (1 call: GetJobLines → (object))

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: "Job-Process Plan. Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.