Transport management in BW 2004s

Question

Hello
We are moving our DWH in the quality and in the production environment.
We have a configuration management issue and would like some help on a few topic :
- how do we ensure that a transport contains all objects needed for its correct integration in the target environment ? We have many code 8 that are just : OK 1 object missing, have to transport it and send again the main transport.
- how do we ensure that we have the exact same DWH configuration (not meaning IT config but customizing and structures definition) between quality and production environment ? we have to order the transport in the most efficient way since we are allowed to run the transport only once in production (otherwise we have risks for the users).
- how do we split between an insignificant code 8 (object not activated : 10 minutes to correct) and a truly significant code 8 (programme error for example) ? 
Basically, we are reduced to build a transport, see all errors, build a transport with the correction, see all errors until we have no errors. Then in production, we reverse the order.
One last thing : we cannot rely only on "everybody does its best". We need to have a procedure and tools ensuring that after transport to quality, we reach 100% (OK a reasonnable 90%) without code 8 in production. As yet, all daily transports to production includes several transport in code 8.
If i am unclear, i will be glad to provide clarification since this is a very huge topic for us
Thanks
Fabrice

Answer 1

The only major change since BW 3.x is that the datasource now exists in NW 2004s BI and not on R/3 or mySAP ERP. 
There should be four logical groupings of objects and they should be transported in this order: 
1) DataSources
2) Data Warehousing Workbench
3) BEx Objects
4) Roles
This means that only these objects should be included in a CTS Request or Task, and you would not include a BEx object in the same Request or Task as an InfoSource, for example.
For Data Warehousing objects:
First, select “Grouping” and choose how the system should group the objects.  It’s recommended to choose either “only necessary objects” or “in data flow before”.
Next, you should transport the complete InfoSource(s) with the InfoCube.  Since InfoSources have the connection to the source system, the user has to choose which source systems are available for selection in the Transfer rules/Transformation, DataSources, and Infopackages.  Objects that have not been assigned to the specified source systems are ignored.  This is maintained from the “Transport connection”.  Goto the menu path “Edit -> Source system assignment”.  Choose which source systems are relevant.  Note:  This step isn’t necessary if you choose “only necessary objects” since no InfoSources are transported.
Lastly, select “Collection mode” and choose “collect automatically” or “start manual collection”.
Now the InfoCube can be selected, and then ‘drag & drop’ the object so that all dependent objects can be collected.
3) When you decide which Queries or Workbooks you want to transport, you first need to maintain two settings prior to collecting the objects:
First, select “Grouping” and choose how the system should group the objects.  For BEx objects, it’s recommended to choose “only necessary objects”.  If you choose “in data flow after”, it will include more objects like Workbooks.
Lastly, select “Collection mode” and choose “collect automatically” or “start manual collection”.
Now the Queries and/or Workbooks can be selected, then drag & drop the objects so that all dependent objects can be collected.
4) Roles are customizing objects so you need a Customizing request.
Roles that are delivered in the SAP Business Content can be transported via the Transport connection.