Sunday, 14 September 2014

F00165 and upgrades

F00165 has gone through a significant transformation between XE and 9.1.  One of the main changes is that it has been “normalised”, and by no means does this make the file normal.  This is the process by which multiple attachments for a single GDTXKY are separated out.

The classic JDE example is if you have 3 attachments to 1 address book record, this would have been stored in a single stg file, but in the new release – this will now be 3 separate files (if they were not text attachments).

What?  This means that the R8900165 actually writes all of the stg files again – YES!!  So there is a massive amount of disk IO outside the standard database IO, because the UBE is ripping apart all of the stg’s and making them singular.  Note also that it does change the existing, so be prepared to have twice the storage for all your stg’s on your deployment server (current project means 186GB!!!!).

The report that is produced contains the records that physical files could not be found for. R8900165U.

So you can go and find the files that were not changed on the day of conversion and delete them.  This is also how JD Edwards can serve up the old content and the new at the same time.

Note that you can refer to my notes on my vbs script to check for attachments, which is pretty handy too.

Remember to delete all of the work centre messages from F00165, this’ll make the conversion quicker and not many people care about those messages.

No comments:

Extending JDE to generative AI