Codeunit 40108 "GP PO Migrator"

HybridGP · Microsoft.DataMigration.GP · BC29-30 · source at ea08af5e · facts from BC29

Procedures

• MigratePOStagingData()

Plus 12 local procedures.

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 1796 “Data Migration Error Logging” (3 calls: CreateLines → SetLastRecordUnderProcessing, MigratePOStagingData → SetLastRecordUnderProcessing, PostReceivedPurchaseLines → SetLastRecordUnderProcessing)
• Codeunit 1327 “Adjust Item Inventory” (1 call: CreateNegativeAdjustment → SelectItemTemplateForAdjustment)
• Codeunit 23 “Item Jnl.-Post Batch” (1 call: PostItemAdjustments → (object))
• Codeunit 4037 “Helper Functions” (1 call: CreateLines → ShouldMigrateItem)
• Codeunit 90 “Purch.-Post” (1 call: PostReceivedPurchaseLines → (object))

Called by

• Codeunit 4037 “Helper Functions” (1 call: CreateOpenPOsImp → MigratePOStagingData)

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