Hi ​@Thean 

I recommend to create an own migration job for the migration of DOCUMENT_TEXT.

When you create/migrate a purchase part then the field note_id will always get an auto-generated number by the database. That means when you have a look into the created/migrated data of the DB view purchase_part then the field NOTE_ID already has a value.

This value is needed for the migration of DOCUMENT_TEXT and this example is only related to purchase parts. There are also other LUs with a note_id field where the approach is the same.

You need at least the following information:

CONTRACT, PART_NO, OUTPUT_TYPE an NOTE_TEXT:

With the function purchase_part_api.get_note_id(contract,part_no) I’m fetching the value of the NOTE_ID of purchase_part.

In my example I’m using fixe values for the OUTPUT_TYPE, ‘PURCH’, and also for my NOTE_TEXT field, ‘I am a document text’. Please map these fields with your values.

It might also be possible to migrate PURCHASE_PART and DOCUMENT_TEXT in one step. For that purpose you have to inherit the value for NOTE_ID from PURCHASE_PART to DOCUMENT_TEXT in the method list attribute screen.

/Jens

Hi ​@Jens,

Thank you for your quick response.

Could you please explain this scenario more?-”It might also be possible to migrate PURCHASE_PART and DOCUMENT_TEXT in one step. For that purpose you have to inherit the value for NOTE_ID from PURCHASE_PART to DOCUMENT_TEXT in the method list attribute screen.”

I tried mapping the Note_Id in method list attribute but facing some error.

 

Thanks in advance,
Thean