on 08-06-2015 1:31 PM
Hi Experts,
I am moving TR from sap bw dev to sap bw qas i am getting the above error.
Here i am using source is file and i maintain source system in sap be dev and sap bw qas with same name and description. source system is active in both systems.
my TR having these objects like info object,data source,info package,transformations,dtp's and target. but i am getting the below error also.
Regards
Sampath
Hi Sampath
I assume the transformation is source system dependent. If so, then check note 1825991.
br
Roland
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
after import i got the above error and i collect the new TR for only Transformation but i got the same error.
ThankQ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Transformation all are saved under custom package - Are you sure? cross check it
Cross check about source/target objects at bw qua. are active properly?
Check about source system settings. test source system connectivity.
RSA1-->source system-->find your source system-->rigth clik-->test connectivity
i am collected 3 transformations and DTP's in one TR only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But you said as - my TR having these objects like info object,data source,info package,transformations,dtp's and target. but i am getting the below error also??
at BW Qua all info objects and master data info object was active?
check your flat file source system settings at bw qua, is those are fine?
first send transformations, once those are active at bw qua, later you can dtp transports.
Hi Ram,
i assign the total flow into one TR. here my target is info object data source are attr,text,and hier so for that i made three transformations. i am assign those objects under my package only we can't move under $TMP objects.
Thanks for reply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sampath,
Please never collect whole flow objects one transport. its always problematic.
if transport was failed then we need to re do the same work. collecting and transporting.its time consuming work.
that's better split the objects and collect them into new transport requests(TR) respectively.
in BW - we need to follow the sequence to transports objects.
in my above reply 3point - you can collect your att/text and hier data source into one transport and move them.
once data source and master data info object was active at bw qua,
You can collect 3 transformations into one TR and move them to Qua.
Later collect info packs and dtps respectively in new TR.
Thanks
Dear Sampath,
Always follow the transport in the sequence mentioned by Raman, but you can also try reimporting the same TR once again, if the source & target are moved succesfully in QA.
Thanks
Vijayendra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Why you collected multiple transformations?
all those sources and targets are active at bw qua?
Try to to do below way.
1.collect all info objects into one transport and move to bw qua
2. collect targets into new transports and release to Qua.
3. collect data source into new transport and move to BW qua
4. collect transformations into new transport and move to bw qua
5. collect info pack and dtp into new transport and move them to qua.
Better to collect each/similar objects into one transport and move them by sequence other wise we get issue like above.
all obejcts need to be stoed undet custom package instead $TMP.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
74 | |
10 | |
8 | |
7 | |
6 | |
5 | |
5 | |
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.