I’ve got a major problem at a client site. A custom module utilizes Workflow heavily, and calls concurrent programs directly.
In custom PL/SQL nodes in the workflows the original coder called FND_GLOBAL.APPS_INITIALIZE and then either FND_WF_STANDARD.EXECUTECONCPROGRAM, or sometimes FND_REQUEST.SUBMIT.
After upgrading to Oracle Apps 11.5.10.2, the frequency at which they receive “can’t find Oracle name” errors has risen to around 30%.
I’ve tried rewriting the code to raise a Business Event which call scustom code to set the apps environment and then call the workflow, we’ve tried using the SET_CTX mode of running the workflow using a selector function, and several other things, all to no avail.
We’ve a long running service request which has been escalated to Duty Managers several times, and we’re getting no help from Oracle.
Has anyone any idea what the problem is? If we could only figure out what the problem is maybe we could find a way around it.
