Import Scenario: Last Cost not getting updated

Hi @Harshita  Please share the XML format of your Import Scenario by using below option.

@Naveen Boga Thank you for your prompt reply. Here’s the required XML format.

Hi @Harshita  I have modified a little bit of your import scenario and verified it and working as expected.

Please find the screenshot for reference.

You can modify accordingly and verify 

Thank you @Naveen Boga for the solution. I’ve tried on the basis of the above mentioned scenario but still my “Last Cost” isn’t getting updated.

 

@Harshita  The above import scenario is working fine.

Can you please let me know what is the  Valuation Method you have to give for the Stock Item?

If you have given the “Standard” then the system will not allow us to update the Last Cost. 

The valuation method selected here is “Average”
 

@Harshita  Why this field is a non-editable field?

Do you have any customization on this Last Cost field?

No @Naveen Boga . There isn’t any customisation applied.
Even I checked for other stock items where Valuation Method=Average. The field is editable.
 

Removed.

Hello @Naveen Boga thank you for your prompt replies. I again tried to import some stock items with the below scenarios. And hence now the “Last Cost” field is editable where Valuation Method=Average
 

Hence, resolved.

@Harshita Awesome. Thanks a lot for the update.

To whoever is also running into this issue, this is related to a missing Default Warehouse. During the Import, the Last Cost Field is then locked down somehow.

Workaround is to set a Default Warehouse as the Last Cost / the Cost Layer is typically tied to a specific Warehouse (i.e. in Tables like INSiteStatus).

Not sure if it is considered a Bug as the Cost should be tied to a Warehouse.

​@krausef77 Did you get any chance to identify this is a bug?