Importance of collecting a list of active BW objects in the landscape
Wally will never forget what happened this Monday morning after his scheduled BW transports moved to the production system.
Everything was red in his monitor screen. Error in DTP due to inactive transformation!! Active version of the target object not found!! Now what on earth does that supposed to mean? Most of the users were unable to execute their workbooks. ‘Strange system behavior’ he wrote in his email. I can imagine the scowl in his forehead when he was writting it to everyone in the BW mailing list.
So, what did he do? Sabotage? As far as we know he has no reason to do so; got a handsome hike this quarter. Any way- let me come to the point now. Isn’t it quite a regular phenomenon when we send a hundred thousand BW transports in the weekend as a part of the new release?
An inactive multiprovider somewhere, missing infoobject, a strange DTP error message, a process chain failure. Hundreds of concerned mails, as if the whole Business has gone down the drain because you messed up. (An unmanaged infoobject can wreck havoc in the system- trust me! as there might be severe dependency in the flow upward or downward)
And all these without any major error in code or design; a little jinx in the transport sequence may be? In short- a potential risk is involved whenever you are sending new/enhanced objects to the production landscape as a part of the new release or enhancement.
Now here is what I suggest you to do. Have a list of all the active objects in the system before your transport moves.
- Cubes
- ODS
- Transformation
- Datasource
- DTP
How to do it?
Go to the following tables for Cubes, ODS, transformation, datasource, and DTP and check for the active version of the objects.
|
Cube |
RSDCUBE (obj ver= A, cubetype = B(basic cube), M(multiprovider)) |
|
ODS |
RSDODSO (obj ver= A) |
|
DTP |
RSBKDTP (obj ver= A) |
|
Datasource |
RSTSFIELD(obj ver= A) |
|
Transformation |
RSTRAN(obj ver= A) |
|
Query/reporting components |
RSZCOMPDIR (obj ver= A) |
Extract the data in an Excel.
Armed with this list you have the idea of the active available BW objects currently available in the system landscape.
Once your transports have moved, repeat the above process and reconcile with the previous state of the landscape.
Now, if anything has turned inactive, at least you know where to focus; and might just fix the issue before the sky comes tumbling down.
You may have to use the following reports to activate your inactive stuffs. There are more to be found on google.
|
RSDG_CUBE_ACTIVATE |
Activation of InfoCubes |
|
RSDG_ODSO_ACTIVATE |
Activation of all ODS Objects |
|
RSDG_IOBJ_ACTIVATE |
Activation of all InfoObjects |
|
RSDG_MPRO_ACTIVATE |
Activating Multiproviders |
|
RRHI_HIERARCHY_ACTIVATE |
Activate Hierarchies |
|
RS_COMSTRU_ACTIVATE_ALL |
Activate all inactive Communication Structures |
|
RS_TRANSTRU_ACTIVATE_ALL |
Activate Transfer Structure |
|
RSAU_UPDR_REACTIVATE_ALL |
Activate Update Rules |
BI4.0 solves a lot of issues but when we are using BOXI R3 it is a pandemonium. 🙂
Transport Management has to be dealt with utmost importance & the participating team has to make sure that they're equipped with all the required info. As Kenneth pointed out, we do require something new & better from SAP on Transport Mgmt.