Codeunit 46863 "BC14 Journal Management"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · BC29-30 · source at ea08af5e · facts from BC29

Procedures

• GetTemplateName(): Code[10] (internal)
• EnsureBatchExists(BatchName: Code[10]; BatchDescription: Text[100]) (internal)

Called by

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 46888 “BC14 G/L Entry Migrator” (3 calls: AssignJournalBatches → EnsureBatchExists, CreateJournalLine → GetTemplateName, GetRemainingPercentage → GetTemplateName)
• Codeunit 46939 “BC14 Cust. Ledger Migrator” (3 calls: AssignJournalBatches → EnsureBatchExists, CreateJournalLine → GetTemplateName, GetRemainingPercentage → GetTemplateName)
• Codeunit 46943 “BC14 Vendor Ledger Migrator” (3 calls: AssignJournalBatches → EnsureBatchExists, CreateJournalLine → GetTemplateName, GetRemainingPercentage → GetTemplateName)
• Codeunit 46896 “BC14 Journal Post Action” (1 call: RunAction → GetTemplateName)

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: "BC14 Journal Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.