PART_CATALOG_CFT is the custom table that holds the custom fields, and the link between that and the PART_CATALOG_TAB is the rowkey (objkey in the view). You need to have the PART_CATALOG_API in your method list when you’re creating new part records, and then refer to the OBJID from that method in the PART_CATALOG_CFP method list attribute. You can read more about how it works here → 
https://docs.ifs.com/techdocs/foundation1/040_administration/260_data_management/050_data_migration/003_data_migration_in_custom_objects/080_custom_fields/default.htm

Hi @ynwkm .

Yes, there is a good foundation documentation about tips and tricks available as @anmise already mentioned.

If you’re not so familiar about data migration at IFS then I recommend to order a training, e.g. TAA3P, where you’ll get much more information about this topic.

/Jens

H,

I have faced a similar issue.

Any ideas on this?

Hi @Vinoy Heshan 

it would be fine if you could provide some screenshots of your migration job please. 

→ Formatting, Source Mapping, Method List and Method List Attribute

/Jens

Hi Jens,

Thanks for the prompt response, the issue is solved. The culprit was an integration during invoicing fee lines. Thanks you

/Heshan