on 08-25-2015 2:35 PM
HI,
Quality system has got system refresh recently.After this system refresh I could not see Infopackages assigned to infoprovider earlier.
when i try to transport it again, Transport request fails with a message ' R3TRISIPxxxxxxxx was repaired in this system ' .
Please comment what could be corrective action for this issue.
Thanks.
Hi,
can you check the info packed locked in the quality system.
check the unwanted (do not transport reuqests) TR in quality.
some where you collected respective info pcagke under the TR.
delete the TR with help of Basis team.
then reimport to dev to quality same TR.
Thanks,
Phani,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ram,
I agree with , that infopackage which you are trying to move to QA is already locked in a transport request in QA system(someone tried to change IP in QA directly and collected in a TR).
So please find the TR of the IP in QA system, check the lock overview by going to IP , go to extras tab->click on object directory entry.
Unlock that TR in SE03 and remove this IP from the list. Once this is finished, you can re-import your TR from Dev to QA with 'overwrite originals' option.
Regards,
Vengal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vengal & Ramanjaneyelu,
There is a Transport in Quality system which has these infopackages (other user has tried to create infopackages in quality system directly).
This transport was in modifiable status, I have asked user to delete the transport.
Even now importing infopackages from Dev to Quality system gives me same error.
Thanks.
at Qua user have deleted the info pack which was in transport request?
if user created new info pack at qua then how it comes as same info pack from your transport?
Above error logs are old one which you shared two days back.
what kind of info pack is that? is it full one?
if yes then can you create new info pack at dev system and transport it?
Hi,
from Qua server, lets find the transport request which have info pack.
Later ask the user to move that transport to prod.
Later you can try to reimport your transport.
from SE03 0r SE09 lets try to find the out the TR which was locking your TR.
use Exerting tool and lock overview options.
Take basis team help.
Thanks
hi ram,
at Qua, something stopping your TR.
So you need to find that TR which have info pack(ISP structure)
Later you can unlock that and reimport your Tr.
Have you informed to basis team?
seek their help.
From starting itself we requesting check thru SE03 -display repaired obejcts. have you tried to find that TR which was locking your objects?
please do that. take basis team help.
Let see this discussion, followit. migth be helpful.
Thanks
Hi Raman,
I have checked this already as per your earlier recommendations.
SE03 > Objects > Display Repaired Objects > I do not see R3TR ISIP objects.
ISIP refers to Infopackages.
SE03 > Objects > Search Objects > R3TR ISIP (Info package name - Execute.
I could see that there are 2 Transport Request - Status is released.
But in transport log for that Transport Request has ' error' which i described earlier.
Thanks
Hi Ram,
It seems that you are not following the proper flow for transport, have you ensured that you have complete flow available in your Q system? Meaning : Infosource, Transfer rules (3.x), Data source (7.x) You need to ensure that the pre-flow is already present in the Q/A system before you try to transport the infopackage.
Also in the worst case scenario, if you have the proper flow then you can directly create an infopackage in the quality system. Mostly consultants have access to create Infopackages & DTP's directly in all environments.
Thanks
Pawan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Before doing retransport, have you rectified the error?
Above error information not much helpful to find the issue. please share long text error.
From SE03 - Have you tried to find the object which was repaired?
Lets try this way.
BW, Tx - RSA1-->transport connection.
lets find your info pack from middle pane and drag into extreme right side.
in right side screen, please check the existing transport request number.
Later find the user who created that and ask him to delete if not needed.
later you can collect your info pack into new transport.
Thanks
Hi Raman,
No other user is working on this infopackages. I am trying to transport it to quality system.
But it fails 3 times almost.
After system refresh in Quality system - Infopackage cannot be seen in Quality system anymore.
so i am trying to Reimport it.
Transport request has only infopackages ( 4 in number) .
Oss note 1626202 mentioned in Long text will not be valid for my system. I am in below version .
SAP_BW | 740 |
Attached is long text.
Thanks.
it means that there is an "open transport" for that InfoPackage in the system you're trying to import the new transport request
find the "open transport" (via transaction SE03 > Search for Objects in Requests/Tasks) and release it, then import your new transport request again
(you could also use the option "Overwrite Objects in Unconfirmed Repairs" as per the SAP Help)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
From Tx - SE03, you can unflag repair option for object ISIP.
later you can reimport the same transport request wit help of basis team.
To unflag repair option please take basis team help if you not authorized to access SE03.
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 |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.