codeunitAdministration & Setupofficial - Microsoftderived - from the source, no model text

Codeunit 46943 "BC14 Vendor Ledger Migrator"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 4 connected objects and pages

Table 46941 "BC14 Vendor Ledger Entry" (relates to)BC14 Vendor Ledger EntryCodeunit 46863 "BC14 Journal Management" (calls, 3 links)BC14 Journal ManagementCodeunit 46851 "BC14 Migration Setup" (calls)BC14 Migration SetupCodeunit 46855 "BC14 Migration Loop" (calls)BC14 Migration Loop

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
TableNo BC14 Vendor Ledger Entry

Events published

  • OnMigrateVendorLedgerEntries(var IsMigrated: Boolean) (integration)
  • OnAfterMigrateVendorLedgerEntries(MigratorSuccess: Boolean) (integration)
  • OnBeforeCreateJournalLine(BC14VendorLedgerEntry: Record "BC14 Vendor Ledger Entry"; var IsMigrated: Boolean) (integration)
  • OnAfterCreateJournalLine(BC14VendorLedgerEntry: Record "BC14 Vendor Ledger Entry"; var GenJournalLine: Record "Gen. Journal Line") (integration)
  • OnTransferVendorLedgerEntryCustomFields(BC14VendorLedgerEntry: Record "BC14 Vendor Ledger Entry"; var GenJournalLine: Record "Gen. Journal Line") (integration): Integration event raised during vendor ledger migration to allow mapping of custom fields. Subscribe to transfer TableExtension fields from BC14 Vendor Ledger Entry to Gen. Journal Line.

Procedures

  • GetDisplayName(): Text[250]
  • RegisterReplicationMappings(CompanyName: Text)
  • IsEnabled(): Boolean
  • Migrate(): Boolean
  • GetRemainingPercentage(): Integer
  • CreateJournalLine(BC14VendorLedgerEntry: Record "BC14 Vendor Ledger Entry") (internal)

Plus 5 local procedures.

Triggers

OnRun

Relations

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.

Implements

Recent changes

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 Vendor Ledger Migrator"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources