Adding free fields to transaction files in OIS, STS, COS, and MOS

Legacy Contributor

As most of you know in October it will not be possible anymore to use the CUGEX1 extension table to store data against transactional tables. The suggested alternate solution is to use XtendM3. For Rudd this means that we have to make changes to a handful interfaces which were developed using the CUGEX1 table before XtendM3 was available.

The XtendM3 option will work and is probably the best solution if you have multiple interface with multiple customers, but if you only need to store a small number of additional fields it would be much easier if these could be stored in the actual M3 table. It would be less costly to develop the solution and fields would be automatically available in filters, lists etc.

Below are links to the ER-s. Note that I did not enter an ER for purchasing, since this is already on the roadmap. Also we are not using manufacturing orders, so I encourage someone else to create an ER for the main manufacturing tables

Please vote!

ER for OI (71352):

https://ers.infor.com/Ers/SoHoXi/Request/XiDetails.aspx?ced=true&erID=71352&AER=false&tbv=1

ER for Rental (71354):
https://ers.infor.com/Ers/SoHoXi/Request/XiDetails.aspx?ced=true&erID=71354&AER=false&tbv=1

ER for MCO-s (71357):
https://ers.infor.com/Ers/SoHoXi/Request/XiDetails.aspx?ced=true&erID=71357&AER=false&tbv=1

ER for WO-s (71360):
https://ers.infor.com/Ers/SoHoXi/Request/XiDetails.aspx?ced=true&erID=71360&AER=false&tbv=1

Legacy Contributor

Very good initiative Fons, we constantly running into the issue of not having enough fields to store data. But instead of entering enhancements requests for each and every table (don't get me wrong, I still think some of the "main" tables like the once in your ER are still valid). I think XtendM3 is in the right direction and has the potential of being the "solve it all" solution for not having enough fields.

But, what is really missing in my opinion is a no-code option. Creating a new table is super simple and takes a couple of minutes. They are also very standardized so having the option to auto-generate a full set of CRUD APIs to your newly created table shouldn't be too complicated. So if you don't need to enhance M3 functionality or anything like that, you just need a couple of extra fields to store data, you don't need to learn how to program yet another language and you don't run the risk of doing it wrong!