[chrisplough]

OTM uses domains (or sub-domains) to support multi-org functionality, plus they have a lot more flexibility than Orgs.

In the past, we've used a different OTM and BPEL domain for each EBS instance and/or Org in order to consolidate several of them (EBS instances and/or Orgs) into a single OTM instance. (Wow - say that 3 times fast!) If you're willing to customize the pre-packaged integration, then it may be possible to consolidate everything down into one OTM domain, but you'll also have to find a way to uniquely identify eacy order/shipment/voucher/etc, so that you can configure the BPEL flows to send the information back to each Org appropriately.

What's the need behind using a single OTM domain? It may be easier (and require much less coding/maintenance) to simply use multiple OTM domains.

--Chris