Hi,
Since promotion management shows you the object dependency, I would be careful before I would just move BI content from side to side.
By using the CMC you can run a dependency query that simple shows all the rest of the object that are related to another object, so a user can have hundreds of dependency objects surrounding him:
personal reports ,public reports ,universes he uses ,groups he belong to and more.
When it comes to connections, we must understand the immediate triangle relation:
- Report --> Universe -->Connection
When you move a universe or a report between SAP BI environments, they carry a dependency which is the connection.
When you don't choose the "add objects" option in the promotion job you create, you simply don't move those connections to the target environment since it's mapped against a different data base environment!
In this kind of scenario you can move your updated universe and reports from development to test environment without running over the different test connections which are most likely mapped to something like: DWH_Test
If you do choose the connections (not as a dependency which you simply can view in your promotion job),they will run over the other SAP BI environment unless :
- It's afresh new SAP BI environment
- You are using override setting (connection mapping )
Personal recommendation:
Manage jobs by their types:
- BI content-the data triangle: Universes, reports and connections – a must for managing different SAP BI environments which is mostly get updated by this content
- User management –users, folders ,security, applications
Using this method you can transfer content according to the different requirements and tasks (transfer today an updated universe to test environment, move specific groups to development environment )
Read here about the dependencies meaning and when to use them :