Codeunit 4773 "Create FA GL Account"

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

Events published

• OnAfterAddGLAccountsForLocalization() (integration)

Procedures

• DepreciationEquipment(): Code[20]
• DepreciationEquipmentName(): Text[100]
• GainsAndLosses(): Code[20]
• GainsAndLossesName(): Text[100]
• IncreasesDuringTheYear(): Code[20]
• IncreasesDuringTheYearName(): Text[100]
• DecreasesDuringTheYear(): Code[20]
• DecreasesDuringTheYearName(): Text[100]
• AccumDepreciationBuildings(): Code[20]
• AccumDepreciationBuildingsName(): Text[100]
• Miscellaneous(): Code[20]
• MiscellaneousName(): Text[100]

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.

• Codeunit 5133 “Contoso GL Account” (8 calls: AccumDepreciationBuildings → GetAccountNo, AddGLAccountsForLocalization → AddAccountForLocalization, DecreasesDuringTheYear → GetAccountNo, …)
• Codeunit 3 “G/L Account-Indent” (1 call: OnRun → Indent)

Called by

• Codeunit 5115 “Create FA Posting Group” (6 calls: OnRun → AccumDepreciationBuildings, OnRun → DecreasesDuringTheYear, OnRun → DepreciationEquipment, …)
• 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 GL Account"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.