Creating OWB code artifacts
Code artifacts are normally time consuming and difficult to obtain. Oracle Warehouse Builder is no exception to this rule.
Getting ready
Subversion is an ideal place to store this kind of information. It is important to have a standard naming convention for where and how the code resides within Subversion. All incremental releases within the development environment and test environments are no longer important, when you hand over the code. It is important to have a single baseline of the code, in order to effectively hand over the environment.
How to do it...
Subversion is ideal to track code and changes to code. In order to do this effectively, code should be checked in at a level of granularity that will allow you to manage individual objects as follows:
1. Create a folder that relates to the target environment, say Production, as shown in the following screenshot:
2. Create a subfolder named OWB for the technology component under Baseline within the Production...
