Skip to main content
Solved

PURCHASE_ORDER_LINE_PART migration issue when PROJECT_ID and ACTIVITY_SEQ are present

  • May 7, 2026
  • 2 replies
  • 21 views

Forum|alt.badge.img+3

Hi all,

Here the data is extracted from company1 and migrated to company2 with new project_id and activity_seq updated in the source data file to input to the migration job  (say project_id1, activity_seq1 in company1, the new data file will have project_id2, activity_seq2 for company2)

 

I use a FNDMIG job to migrate the purchase_order_line_part  for Loram. 

In the first migration, I remove the project_id and activity_seq fields from source mapping. No migration errors. The row was inserted.

 

But the project_id1 and insert it in code_c field in purchase_order_line_part. And that was wrong and it should take project_id2.

Anyone has thoughts on why this is happening and how to resolve this situation?

Any clue or advice is much appreciated!.

 

Thank you!

Best answer by malik.sally

It is quite fiddly. Check the PrePosting_ID field, that is essentially bringing in the code part values.

2 replies

Forum|alt.badge.img+12
  • Hero (Partner)
  • Answer
  • May 8, 2026

It is quite fiddly. Check the PrePosting_ID field, that is essentially bringing in the code part values.


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Partner)
  • May 8, 2026

Hi Malik, 

You were correct, I had data in the PRE_ACCOUNTING_ID field and it was mapped in the source column of the migration job. Once it was removed  from the source mapping and updated the flags in the method list attribute, the PO line migration was successful. 

Appreciate your guidance!

 

 

Thank you!

Disna M.