Thread: [SOLVED] Bpel
View Single Post
  #7 (permalink)  
Old March 31st, 2007, 20:36
chrisplough's Avatar
chrisplough chrisplough is offline
Site Moderator
 
Join Date: Jun 2006
Location: West Chester, PA
Posts: 821
Blog Entries: 7
Thanks: 53
Thanked 201 Times in 121 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 10
chrisplough has a spectacular aura aboutchrisplough has a spectacular aura aboutchrisplough has a spectacular aura about
Send a message via AIM to chrisplough
Re: Bpel

Just for everyone's benefit, here's the information that I sent to Marinus:

Quote:
Okay - I couldn't find the original doc, but I was able to put together a list of steps:
  1. 5.5CU2 had some material changes to XML integration configuration
  2. 5.5CU2 BROKE the standard integration mapping between OTM and EBS - only impacting a newly configured instance not one that was upgraded from CU1
  3. To update the XML mapping, navigate to Business Process Automation > Power Data > Out XML Profiles
  4. Search for and edit the XML.MIN framework
  5. Add the following fields to XML.MIN: Release/ReleaseRefnum and Release/ReleaseStatus
  6. This is a known OTM bug 6141674.993
  7. Now add the same fields to GLOG.MIN, as that's the one utilized by the OTM > EBS BPEL communication.
BTW - I believe this may be fixed in OTM v5.5 CU2 RP (Rollup Patch) 1.

Hope this helps!

--Chris
__________________
Chris Plough
MavenWire

www.MavenWire.com