Configure Universal Adapter 2 generate New BAW Tables or use Existings OBAW

Question

Hi Experts,
i have a doubt on if New OBAW tables have to be created as we add new subject areas from Universal Adapter Containers
or can use existing OBAW tables that are generated from Other containers.
For Example:
Our Existing contianer is PeopleSoft 9.0 and OBAW Tables are created usign Peoplesoft Container.
of all the subject areas from Peoplesoft Containers, Only Workforce Profile and HR Payroll is used.
as the container is created using Peoplesoft 9.0, all the Tables (532 tABLES) are created for all the subject areas.
now, we are planning to use Universal Adapters to configure rest of the subject areas like Absence Managementr and Recruitment because they are maintained by Third Party Vendors which have no relation with Peoplesoft.
my doubt is,
1. if i can use the same Existing OBAW Tables for Universal Adapters or create NEW OBAW tables using Universal Adapter container.
2. if ii have to create New tables using Universal Adapter containers, all the table belonging to other Universal Adapters Subject areas like Loyalty Analytics, call center analytics are also created by default. how to avaoid this. i tried to create OBAW by creating a container with Only HR-Absence Management subject area and Recruitment subject area, unfortunatley, all the tables are again created.
3. it looks like there are common dimension files used for this Universal Subject areas, is it Mandory to use them to Populate HR-Absence Managment subject area.
Please HELP
Is there is a good refernce guides on how to configure all this espically with Universal adapters in Out side world or in Metalink
Thanks
Kumar

Answer 1

Please take a look at this article which states SYSDATE is not supported in a
where clause.
http://www.oracle.com/technology/pub/articles/bpel_cookbook/qualcomm-bpel.html
Excerpt from the article:
Here are three important things you should do in implementing the above design:
Have the status of the record being processed stored in the database. The status includes the process state, next process attempt time, and processing attempt count.
Create an updatable view that exposes only records that are ready to be processed. A view is needed because the database adapter cannot handle a where clause that compares against SYSDATE.
Design logic that determines if a process instance that has faulted should be retried and when the retry should occur. This information will be updated in the database by use of a stored procedure. This can also be done with an update partner link and additional logic in BPEL.
mahalo,
a iii