I completely agree with the points that Jeff made. Unfortunately, none of your questions (1-5) are possible via the pre-packaged EBS/OTM integration and will require custom integration to accomplish. Many of these are possible, however, and I recommend that you reference the following files in your OTM install for more technical details about OTM's integration:
- $OTM_HOME/docs/integration/integration.pdf
- $OTM_HOME/glog/config/GLogXML.xsd
- $OTM_HOME/glog/config/GLogXML.wsdl
Specifically, I can ad a bit more about the Org <==> Domain mapping. OTM's concept of domains is very different from the Org concept within EBS and (I believe) much more flexible. Unfortunately, the pre-packaged integration flows don't allow you to take advantage of this, nor to reconcile the differences between the two systems. One thing you can do, however, is use multiple domains in BPEL and OTM to simplify your TEST and DEV environments.
For instance, I'm working with a client now who has 6 different EBS systems used for testing and development during their implementation (don't ask - it still confuses me). We've developed a way for them to integrate into only 2 OTM instances (TEST and DEV) by using multiple domains in both OTM and BPEL. So, for instance, your DATACONV domain in OTM integrates with your DATACONV domain in BPEL, which then integrates with your DATACONV EBS instance. This has allowed them to greatly simplify their implementation architecture and reduce the number of systems to manage with a minimal (though talented) IT department.
Thanks,
Chris