Remove Schema from Generated Code

Question

Hi,
I have the common situation where I want to extract data from tables in multiple schemas on a database seperate to both my runtime/staging schema and my target schema.
This is handled quite simply through the use of db_links, created through locations, this is fine. However occasionally the source schema that I am trying to extract from can be changed due to a quirk in the source application. Now this is fine from a location point of view I just unregister the location and point it to the new schema. However for some reason the code owb is generating has both the schema and db_link meaning any schema name changes will require a complete regeneration of the code (e.g. "NON_PERS"."ET_OCLIENT_COSTS"@"CEPPRD@PLAN_NON_PERS_LOCATION"), so if the table (ET_OCLIENT_COSTS) moves from the NON_PERS schema to CY_NON_PERS the code is now invalid.
Is there anyway around this it seems unnecessary to have both the schema and the db_link as the link only has access to the one schema anyway! Therefore can the schema be removed systematically through OWB?
fyi, I'm running OWB 10g Release 2.
Thanks...Jonathan

Answer 1

Here is some info which might be useful too....
If you use an unbound table/view as the source in OWB, the code will generate with no schema or dblink. With this approach when the map is deployed as long as the name is resolved you can magic up what the object actually is at execution time. For example it could be a view/synonym where you replace its definition before execution.
To add an unbound table operator....say you have a table T in module S, add S.T into the map (it will be operator T), add a new table operator T1 into map, map from T.INOUTGRP1 to T1.INOUTGRP1, delete operator T from map, rename T1 to T. You now have an unbound table operator which when the code is generated will just reference the name T.
Cheers
David