Codeunit 5113 "Create FA Class"

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

Procedures

• TangibleClass(): Code[10]
• InTangibleClass(): Code[10]
• FinancialClass(): Code[10]
• GoodwillSubClass(): Code[10]
• EquipmentSubClass(): Code[10]
• PlantSubClass(): Code[10]
• PropertySubClass(): Code[10]
• VehiclesSubClass(): 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 5115 “Create FA Posting Group” (5 calls: OnRun → Equipment, OnRun → Goodwill, OnRun → Plant, …)
• Codeunit 4776 “Contoso Fixed Asset” (2 calls: OnRun → InsertFAClass, OnRun → InsertFASubClass)

Called by

• Codeunit 5118 “Create Fixed Asset” (3 calls: CreateFixedAsset → EquipmentSubClass, CreateFixedAsset → TangibleClass, CreateFixedAsset → VehiclesSubClass)
• Codeunit 4774 “FA 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 FA Class"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.