View Single Post
  #2 (permalink)  
Old December 10th, 2007, 06:59
jeff.depaul jeff.depaul is offline
Member
 
Join Date: Jun 2007
Posts: 36
Thanks: 1
Thanked 8 Times in 8 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 0
jeff.depaul is on a distinguished road
Send a message via Yahoo to jeff.depaul
Re: Otm-ebs Integration

Kishore,
I can provide some insight as it relates to a few of the items you are looking for feedback on - see my comments below...

I am the tech lead on a year-long OTM project integrating Oracle EBS applications 11.5.10.2 with OTM v. 5.5 CU2 using Fusion v. 10.1.3.3 BPEL integration interfaces. We started with the "seeded" Oracle BPEL flows that come with the purchase of the OTM application and have had to completely modify each one of them in order to use for our real-world application.

#1 I am not exactly sure what you are referring to why you say "GL code integration" - there is a seeded BPEL flow to bring invoice voucher information from OTM back into EBS - but this feeds into the Accounts Payable subledger API - not GL directly. We had to modify this BPEL flow logic to include support for allocations and transaction rollups which were requirements for our users. There are several data elements which we pass into OTM (via other interfaces) which are used in this interface for allocation purposed - specifically EBS item/category related information.

#3 In my experience, OTM does not support true Multi-Org functionality as it is defined in EBS. There are different schools of thought on how best to configure OTM to support multi-org operability with EBS which mainly depend on business requirements. In OTM, you can create different domains which roughly equate to "orgs" in EBS. There are limitations to this approach which I will not go into here but in short we went with a single domain and limit user data by VPD in OTM. If you are familiar with EBS multi-org, you can guess this causes issues with items that are enabled for multiple Inventory Orgs. We decided to customize the item nomenclature in OTM to include the org name in EBS. We also concatenate the item UOM and store it at the ship unit level of the item. This met our needs but would need to be evaluated against requirements as it does have its drawbacks as well.

#4 Although we did not include AR integration as part of our project scope, we have a follow-up phase which will include integration with AR invoicing. In order to get actual ship costs for prepaid & add included on the invoice, our conceptual approach is to have the AutoInvoice set check OTM for actual freight and include on the customer invoice. There may be other integration touch-points between OTM and AR but we are not considering them.

Hope this feedback helps and let me know if you have further questions.
-Jeff
Reply With Quote