Hi @CheHiroyK ,

As per my knowledge this issue caused when you haven’t done the position defining in File Mapping tab for the migration job.

You need to define the Position(Pos) in the migration job to match the CSV column position.

Hope this will help.

Regards,

Akila

Hi Akila,

Thanks for your reply! Actually I have done this, but this was not reflected in the Execute Job

screen in the Default tab.  Is this the reason?  If so please tell me how I can add this data to the tab.

Thanks!

Kind regards,

Kokubo

Hi @CheHiroyK ,

No, Mapping will not be reflect in the Execute Job. If you have done the mapping correctly it should work fine. Are you getting same error when use RMB option Unpack File also?

Regards,

Akila

Hi,

Thanks again for your quick reply.  Sorry but could you send me the screen shot of 

“RMB option Unpack File” please?

Thanks!

Kind regards,

Kokubo

Hi @CheHiroyK ,

It should available under same RMB option you used to Start the job.

Regards,

Akila

Hi,

Thanks a lot for your reply!  I tried but the result is the same.

Kind regards,

Kokubo

Hi @CheHiroyK ,

Is it possible you to share a screen shot of Migration Job header and Mapping Tab?

Regards,

Akila

Hi again,

I attach the images.

Thanks!

Kind regards,

Kokubo

Hi @CheHiroyK ,

Seems you haven’t updated the Pos field to reflect the uploaded csv file’s column number. For Example,  if you are using Column 1 for Analysis No then Pos value should be updated as 1 or 10 and Result is used in column 2 in CSV file Migration job pos should update as 2 or 20. Likewise you need to map the CSV column number with Migration job Pos no. 

This is the mechanism used by Application to identify which field from CSV should update which field in IFS application table. 

Pos 0 means that field is not assigned to any of the Columns in the CSV. 

Hope this will help

Regards,

Akila

Hi again Akila,

Great!  Now the error message became that of the content.

Thanks a lot!

Kind regards,

Kokubo

Hi @CheHiroyK ,

I’m glad you were able to resolve the issue. New Error message should be related to Field Validation. (I’m sorry, I’m not good with Japanese language). 

Regards,

Akila.