Not sure what is causing the UDT to not be displayed but you may want to consider backing up it's data, and after getting it to display, delete the table and recreate it under the SO module. Given the name, if you ever operate more than one company code out of that install, whether for testing on legitimate multi-company reasons, you will want each company to have it's own audit table under the SO module vs all of that install's companies trying to share a single SY UDT.

llevron20 you never said if you're on Premium, Advanced, or Standard and your version of Sage. I don't know the root cause of the error but the immediate cause seems likely that in the dictionary your UDT is defined as a view and therefore not added to the UDF Maint tree view. Do the following very carefully:

1. Make a backup of \mas90\ProvideX.ddf file.
2. Open Data File Display and Maintenance from Library Master / Utilities
3. Type in Providex.ddf and press Enter.
4. Hit the Move Last browse button in bottom center (the 4th of the 4 navigation buttons).
5. You're at the last record. If you don't see your SY_UDT_SO_Audit move back 1 record at a time until you do.
6. Once found look at Field 2. This is called the Physical Path expression. 
7. Several questions here. This is where you should stop, take a screenshot and post it as a reply. Also if you can provide the answers to the first 2 questions that would be helpful and relevant as well.
   1. Do you see an @ symbol for the 3rd character? If so then for whatever reason it's defined as a view instead of table. I'd like to see the screenshot before advising on how to fix it.
   2. Any chance you recently used Business Insights Reporter (not BI Explorer, not BI Dashboard) to create views?

Good point, I'm now on Sage 100c Avanced 2016 (v 5.30.5.0)

Here's a screenshot of Data File Display / Maint. with my table:

Where are you referring to seeing an @ symbol at the 3rd character? I don't see one anywhere in DFDM so I'm assuming that's a no.
I haven't used Business Insights Reporter to create any views.

Hey David, thanks for the feedback. I won't ever be running another company other than a test company in this environment and I have a company check in my writing script to avoid having the test company write to the table. Because of that I'm not too concerned, although you make a good point about separation. I'll be sure to consider that moving forward as it's really better practice to handle it like that anyway.

That looks normal. Last time I saw this issue it was the @ symbol at the 3rd char to represent a view. Any chance you added this UDT or any other you've created to the menu? Where I"m going with this is:

1. Role Maintenance the select your role
2. Tasks > Custom Office > Misc Tasks
3. Do you see any unchecked UDTs? I always check them ALL b/c of a certain issue even if this particular UDT is already checked. You might want to try the same then see if that works out.

It is actually added to the Sage menu and shows fine there:

I've got a few other UDT's that are added to the menu as well but they still display fine in User-Defined Field and Table Maintenance.

Everything is checked for my role, so no problems there. I also ensured that it's marked as visible with the sy_menu_ui run command, although that shouldn't make it disappear from User-Defined Field and Table Maintenance anyway, just the menu itself...

Just a WAG but any chance a different UDT record in Providex.ddf has the @ symbol for the 3rd char in Field 2 for Physical Path? It would be on a module UDT instead of system UDT. 

I did happen to find one, yeah:

What are you thinking might be the correlation between that and my missing table?

That is a malformed view record. Views for BIR start with "v" + a no spaces description (e.g. vCustomerOpenInvoice ) and if you actually used BIR it would start with "View:" + a no spaces desc. However it's never "v" + UDT name unless there's a new feature I don't know about

The last time I heard this issue that client had 10 UDTs and the last 5 he created suddenly weren't showing in UDF Maint just like your missing UDT. I'm thinking maybe he had a malformed record too which if fixed / deleted could make his last 5 UDTs visible.

I'm just conjecturing of course. I haven't reviewed the UDF Maint code to see if the treeview is set to filter in such a way. Just tread with caution if you decide to delete this rec. Suggest you do some backing up first.

Interesting. Thank you for all the input! Sounds like I could learn a lot from you.

I don't think I'll attempt deleting the record at all. Data is still being written to the table correctly and I can still view and manage the fields through a roundabout way. While it's not ideal, I'd rather not risk destroying stuff over it. It was just a small afterthought of data retention I was asked to create anyway and isn't strictly necessary for anything other than pointing blame as far as I'm concerned.