View Single Post
  #4 (permalink)  
Old November 2nd, 2007, 09:08
jeff.depaul jeff.depaul is offline
Member
 
Join Date: Jun 2007
Posts: 37
Groans: 0
Groaned at 0 Times in 0 Posts
Thanks: 1
Thanked 8 Times in 8 Posts
Rep Power: 0
jeff.depaul is on a distinguished road
Send a message via Yahoo to jeff.depaul
Re: Customer information

The seeded BPEL flow that comes with OTM for EBS integration will extract and send location information over to OTM. This info is tracked/logged in a series of synch tables on the EBS side. They make the determination of what to send/resend based on last_update_date.
We have found that fairly extensive modifications are needed to these flows but the location is likely the most straightforward (compared to the others).

The flow, as defined - pulls location information and sends when the concurrent request to send eligible delivery info over to OTM is run. Is this what you are looking to achieve or send only location information over (with no delivery info).

Within the BPEL process itself, location, item and delivery information is concatenated and sent to OTM for processing. Sending just the location information over might be a challenge both in how you invoke the process (if using the seeded conc. process) AND in xml transformation for processing into OTM.

Let us know more specific details of what you are looking to try to accomplish?
Reply With Quote