Functional Object creation via Migration Job

Hi @NishithDas 

If you only want to update records then only set the “Modify” flag to Yes and the “New” flag to No.

But to be able to update existing records in that case you also have to do a “key manipulation” in the method list attribute screen for EQUIPMENT_FUNCTIONAL:

Here you have the column Flags for the yellow-marked column names. The problem is that you don’t know the value for EQUIPMENT_OBJECT_SEQ because this Oracle sequence will be generated.

To update existing records you have do define another primary key instead of the EQUIPMENT_OBJECT_SEQ.

So declare the fields CONTRACT and MCH_CODE as K(ey)-fields for that migration job and the EQUIPMENT_OBJECT_SEQ field will get a - (minus sign).

That’s it.

Related to your question regarding SUP_MCH_CODE and SUP_CONTRACT you have to map the field FUNCTIONAL_OBJECT_SEQ in the Source Mapping tab:

And here you can either sub-select statement in brackets in the source column or default value field:

I used the default value field for that purpose and kept the source column field empty.

The content for the default value field is the following:

The alias i belongs to the fields of my source table (source name).

Happy data migration.

/Jens

Hello, I need help in a similar subject please. I created a mapping to mass import serial objects with an Excel file, I managed to get all the desired fields working except for a "Belongs to Object ID" and I don't understand why this field doesn't start working. update when I insert a new serial object. I modified the "Flags" several times but it didn't change anything.

Thank’s

*I specify that this field contains a list of objects already existing in the database