The OCM QBE Ambush

Ok, I’ve been working as a CNC Admin for the past 14 years or so. I’ve come across many odd and unexplainable things. My first exposure was to JDE OneWorld Xe. One of the most difficult issues during that time was the “fat” client hosted on Citrix and trying to control where things ran using OCMs. So, I’ve had quite a bit of experience with the Object Configuration Manager (OCM) and how and why to set things up.

What I learned today is that I don’t know all there is to know about this seemingly simple function and the table behind it (F986101).

There is a setting on each OCM record that I have ignored in the past. It is the “Allowed QBE” field:
 

DO NOT IGNORE IT! It will bite you when you least expect it.

There are 3 options to this setting:

• 1 – ALL QBE Allowed
• 2 – No QBE Allowed
• 3 (DEFAULT) – Indexed Fields QBE Allowed

Unless there is a security requirement or performance issue, I would suggest changing all values to a 1.

You can do that with the SQL below:

 UPDATE SY910.F986101 SET OMOCM2='1' 

That right there my friends is why I have a love/hate relationship with my job as a JDE CNC Admin. The simplest little things from the least obvious place can either ruin or make your day.

Author

Stewart Schatz

Career: Principal CNC Consultant for Syntax Systems Limited specializing Oracle JD Edwards EnterpriseOne and the technology that supports it. Side Hustle: Owner/Operator of E1Tips.com Location: Lancaster, PA USA  What I like to do: Invest in Family, Explore Technology, Lead Teams, Share Knowledge/Experience, Hunt, Hike, etc.

stewart@9rains.com

http://stewartschatz.com