Hi ​@ASIFSHAIKH ,

Did you manage to resolve this issue?

Best Regards,
Devin

Hi ​@ASIFSHAIKH, ​@devin.amarasekara 

I had a quick look into the API for BASIC_DATA_TRANSLATION.

The issue is related to the PATH field which the content will always be created based on the values of LU, MODULE and ATTRIBUTE_KEY.

That means the provided value in the PATH field will be ignored in the API.

You already provide the value for MODULE, INVENT, which is correct for your case.

Ok, how can you now add the columns for LU and ATTRIBUTE_KEY in your migration job because they don’t exist in the SOURCE MAPPING at the moment?

LU is ‘CustomsStatisticsNumber’ (default value) in your case

ATTRIBUTE_KEY must have the Customs Statistic Number for your example.

Another challenge is that the PATH column is a Key Field and a part of the Primary Key.

Following solution which I have not tried out:

Go to your EXCEL_MIGRATION migration job and to the tab METHOD LIST.

Select the line with the view name BASIC_DATA_TRANSLATION and then press the button “Method List Attribute”

In the following screen you have to add 2 new rows (column sequence 100 and 110) for the column names LU and ATTRIBUTE_KEY.

Please set the flags to a K (Key field) and On Modify needs to be ticked on.

As the column name PATH will be ignored because it will be created automatically by the API, change the flag from K to - (minus sign).

Now you have a new (unique) primary key for this migration job which consists of all fields where the flag has the value K. The PATH column will be ignored because of the - (minus sign). With this setup you should be able again to insert and update records.

When you now go to the tab SOURCE MAPPING, probably you have to refresh the screen, then you’ll find the 2 new fields at the bottom.

Please change the length of these 2 fields as shown in the red cycle and you can also use the defaalt value for the LU column (that means there is no need to map the source column LU in that case).

There is also no more need to map the PATH column.

In the field ATTRIBUTE the user now has to enter the Customs Statistic Number. No more need to enter values in the PATH column or LU column (when you use the default value).

I tried this out with a MIGRATE_SOURCE_DATA job and it works.

So I assume it should also work with your EXCEL_MIGRATION migration job.

/Jens