This blog is going to explain you about "Managing Transports by using common sense". I am not going to talk about standard Steps to be carried out.
Common Mistakes :
- We tend to collect multiple(too many) objects in a single TR
- We collect our objects in other's transport requests via separate tasks without our/their knowledge
- We collect different types of objects in a single TR. Eg: Transformations and DTPs together
- We overlook dependent objects while collecting our objects
- We do not know whether RSLOGSYSMAP table has got right entries in Target systems or not.
- We don't bother about dependent objects are active in Target Systems or not
How to use our common sense while managing transports
Scenario : In our projects, we use some standard infoobjects like 0plant, 0Division, 0material etc., Please observe all these standard infoobjects belongs to their respective standard Infoareas and Application Components.
How to handle above scenario?
We need not to collect their respective Infoareas and Application Components every time. Because these standard Infoareas and Application Comps will be already available in target systems.
How to transport DSOs/Infocubes first time to the target systems?
As we might have already moved our infoobjects, we just need to collect only DSOs/Infocubes and move to target systems. We need not to collect any underlying infoobjects it is pointing to, like below. The infoobjects which has Expand icon can be collected with "Do not Transport Any below". This will reduce the burden on the TR. Note : It's better to use "Only Necessary Objects" and Collect Automatically".
What to do when DSOs/Infocubes becomes inactive target systems?
Just collect the active version of DSOs/Infocubes and move to target systems. You need not to collect anything below.
How to transport Transformations and DTPs first time to the target systems?
We all are aware that Transformations are between Source and Target. That's exactly is the reason to collect Source and Target along with Transformation like below. We need not to collect all infoobjects of our Cubes and DSOs, because those objects have already been moved. Same explanation applies to DTPs also.
How to transport Transformations and DTPs after the first time to the target systems?
We just need to collect the active version of Transformation and DTP. It's not required to collect Source and Target as they are already actively available in Target systems. This procedure can avoid running RDG_TRFN_ACTIVATE program directly in Target systems. You can run this program if you want to activate Transformations/DTPs in mass.
Tips to consider while managing Transports
We tend to collect multiple(too many) objects in a single TR
How to set your system Transport Request settings
If you switch on standard, then every activity will ask you for transport request through a pop up instantly.
If youSwitch -off standard, then all your activities will get saved in to local objects. Finally you will have to collect from RSA1-->Transprt tab-->Object types
You can observe this functionality in above image. This can be used to provide a privilege for us to edit the objects directly in Target Systems. Eg: Queries, Web Templates, DTPs, Infopackages etc. This setting has to be done in Target systems