Codeunit 4765 "Create Mfg Item Journal Setup"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Manufacturing · BC29-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• ItemTemplateName(): Code[10]
• StartManufacturingBatchName(): Code[10]
• ConsumptionTemplateName(): Code[10]
• OutputTemplateName(): Code[10]
• CapacityTemplateName(): Code[10]

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.

• Codeunit 5143 “Contoso Item” (2 calls: OnRun → InsertItemJournalBatch, OnRun → InsertItemJournalTemplate)
• Codeunit 5142 “Contoso Utilities” (1 call: OnRun → GetDefaultBatchNameLbl)

Called by

• Codeunit 4779 “Create Mfg Item Jnl Line” (1 call: OnRun → ItemTemplateName)
• Codeunit 4783 “Manufacturing Module” (1 call: CreateSetupData → (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: "Create Mfg Item Journal Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.