Data cleanup and reload

(0) Share

Report

Posted on by Community Member

Hi All,

I have been tasked to look at the data integrity of our AX system when it comes to BOMS, naming conventions, ABC, safety stock levels, reorder points etc etc. I am not an IT expert on AX and it is relatively new to me.

My question is that all our data was loaded into AX from another system 9 months ago and i need to know if we can take a dump of the present data and cleanse it a reload it with the new file.

I have been told this is not possible but i have carried out similar projects on JDE, Oracle and SAP where we stop any processing to upload a new data base with the same but approved information.

Thanks,

Stuart

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

ZvikaR 170 on at

Like (0)

Report

If there are already transactions in the system you will not be able to simply delete the existing BOMS and create new ones.

You will need to build more sophisticated uploads that create new versions of BOMs and activate them.

You can also build uploads to update details on the item level (safety stock etc.)

Look into using the DIXF tool for that (you did not specify what version are you on, I assume 2012 or later)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for the reply.

I do not wish to delete any information that is relevant i merely want to extract what is there; enhance it and then reload it again.

So are you saying i can extract a raw file do all my updates and amendments/improvements and at an agreed outage from the system upload the full raw file back into AX whilst capturing all the details.

it is 2012 version.

Was this reply helpful? Yes No
Verified answer

Vilmos Kintera 46,149 on at

Like (1)

Report

I am afraid the correct approach would have been importing it right the first time and validating the data through multiple regression tests / user acceptance testing, before going live - as suggested by most project plan methodology and industry experts.

Some base data may be changed, some cannot be modified once you have transactions on them (or other certain criteria are met such as being invoiced, etc.).

You could have a look at the Data Import eXport Framework (DIXF), with which you could export entities into a file or database format of your choice, change some of the values, then import it back to update them.

You could play around with this tool in a Test environment to see how does it work in your case.

[View:https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/lifecycle-services/ax-2012/user-guide-dixf:750:50]

It would be a unique scenario that you have to validate for each type of entity you are about to create/update. Like it was mentioned before BOMs are based on BOM versions and you cannot change the original one, but it would be a new version.

Was this reply helpful? Yes No
Weaveriski 23,620 Moderator on at

Like (1)

Report

Hi Stuart

I would say yes you can extract it and then bring it back in and update it, with a caveat on what it is :-) However depending upon the volume and area I would not do this, I would make the users take ownership, so if the naming conventions are wrong get them to correct them, if you export, cleanse and import you are then the person that will always do this and they will continue to create the records incorrectly, but it is just a preference, the path of least resistance is to do it without them noticing!

I would also suggest running the ABC classification period batch job - it is a calculation that suggests the category based upon parameters and usage. I also suggest running the safety stock journal which will calculate based upon your metrics and usage what the safety stock should be and make it a suggestion you can choose to post and update.

Was this reply helpful? Yes No