Jeff,
The appsborg.zip and appsborg2.zip libraries are default libraries referenced by the EBS concurrent processes and appear to also affect the XML/XSL transformation of messages.
This client was the only one (out of 3) to experience this issue and they recently received a patch from Oracle to stop requiring the custom appsborg*.zip libraries. We're still waiting to see if this works, however, as the only way to tell is to see if future patches cause problems.
Let me know if you want me to send you the updated libraries that Oracle provided to us, though there's unfortunately no way of knowing if they'll help (i.e. - be sure to back up your originals). Here's the process we went through:
- login to the EBS server as applmgr
- copy the new libraries to $COMMON_TOP/java
- cd to $COMMON_TOP/java
- cp appsborg.zip appsborg.zip.<date>
- cp appsborg2.zip appsborg2.zip.<date>
- cp appsborg.zip.otm appsborg.zip
- cp appsborg2.zip.otm appsborg2.zip
In the current OTM / EBS implementations we've worked on - we've had to modify/customize the existing BPEL flows and we've had to add new ones that process from OTM to EBS -- though what you're attempting (new EBS to OTM) is somewhat new ground (read - all the fun and laughs that you'd expect).
Also - I apologize again for the delayed response. If you've made any progress on this in the meantime, I'd greatly appreciate an update.
Thanks,
Chris