on 09-24-2012 2:16 PM
hi gurus,
i have to transport the infocube, dso, infoojbect to qua system , now my question is should we have to create different transport request for each object or is it enough to have one transport request for all object.
what is the main intention for keeping all objects in different transport request .
tnx,
praveen kodam.
Hi Praveen,
It is enough to have a single transport for all the objects.
There is no specific intention in keeping different objects in different transports, except for the fact that additional work for the basis team to move all the individual TRs.
So, one transport is fair and enough.
Br,
H
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi harish,
tnx for the reply,
then what is the use of keeping that objects in the package ? and one more question which action we have to perform first like first we have to keep that objects in the package or assigning the transport request .
and one more question is :
------------------------------------
what is the best recommended way for creating the transport request like creating different transport request for each and every objects or assigning only one transport request for all the Objects.
tnx,
praveen kodam;
Hi Praveen,
Keeping objects in a package is application specific. Consider you have multiple applications running in your BW system. In order to keep the objects owned by a particular application intact and to maintain authorizations for these objects, we have to specify the package for the objects.
Keeping it in a separate package enables for creating roles and authorizations.
Second, assigning objects to a package is the default first step and then to a transport request.
Cos, the objects in %tmp are not transportable. Always systems prompts you to store the object in a package followed by TR request when you create a new object.
Third, there is no recommended practice for TRs, as all your objects are stored in a TR in organized manner. Drill down the TR request and see the objects are perfectly organized.
Hope this answers your question.
Hi Praveen answers to your other questions.
what is the use of keeping that objects in the package ?
:- to classify different components in system. It is SAP process nothing specific to BW, so if your system has 4/5 modules and you want to keep all components different to identify which this Transport request contains at high level.
what is the best recommended way?
:- See SAP don't recommend you anything on same, because it is based on how you use options provided by system. For example, your process says always transport from front end job and one by one TR (whatever may be a reason). Then you need to defiantly keep component count in single TR as less as possible.
keeping components in different TR helps in a way to find TR failures. keeping all component helps to reduce chance of failure as per my view to looking to different options.
So check what you do and decide how to do
Regards,
Ganesh
Hi Praveen,
When you transport request time taken by Transport based on components you have transported. Chance of transport will get failed gets increased if it takes more time. (can be any reason like memory)
As if Transport gets failed it may move some components and some will not and which will be more time consuming for fixing this.
So If you don't want to take a risk, keep components less and transport will happen faster and no chance of loosing time due to rework
Regards,
Ganesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
96 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.