Transport Request import to Test System

Hi,
I imported a request from Dev to Test
But it seems to running from past 2 hours..
Logs                                Complete
Selection of Import             Complete
ImportCheck Versions         Complete
How can i check whats happening behind
Thanks

Hi,
while trasporting from DED to test .
before you some other has released TR which having routines and some TR's are merged into One.so it might took longer period to complte transport.
while relesing u r TR ,please chk is any other TR 's are realsed.so if released wait until there TR to complte then release your TR.
some times if queue has struck also it will take time ,at that time contact BASIS team will act to solve this
mahesh

Similar Messages

Error in Transport Request PRD to Test application

Dear all,
We are in process of doing reverse transport from PRD to TEST system. i have opened the PRD system and collected the objects in TR and once again done the transport of copies in PRD system
after transport of copies, i tried to import the TR in TEST transport queue. once i tried to import the same i got the below error.
Please advise what needs to be done. Any help would be appreciable.
Transport control program tp ended with error code 0247
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: ADDTOBUFFER PBWK900028 TBW pf=/usr/sap/trans/bin/T
Return code: 0247
Error text: addtobuffer has problems with data- and/or cofile
Request: PBWK900028
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.
regards,
mohankumar.G

Hi,
when creating Transport Requests in the Production system the requests are created as local requests that can't be transported between systems, and when the Transport Request is released the Data and Cofiles are not created.
You need to change the client settings with Tx SCC4 to allow the creation of Transport Requests.
You need to create a Temporary Transport Layer and Temporary Transport Route from Production to Test System. When you create the Transport Request make sure the transport request is using this newly created transport layer and has a target system.(Package also) when you release this request, the data and cofiles will be created. The transport request should also appear in the import queue of the Test system.
Satish.K

Who moved the transport to a particular test system?

Hi,
I would like to find out that which user id has moved a particular transports in a given test system? I was unable to find this in the transport log? Any idea on where to look for this info (source system, target system....) ?
thanks for the quick help.
regards,
HB

Hello,
You can get this information inthe STMS queue.
First goto the STMS queue and then select the option of the Import History.
once in the impot history following the following path EDIT--> Dsplay More and you will get the details as to which client the transport was imported and the user who has imported the transport request.
Please Note :The Import Histroy would show only the list of the imports that have happenend in that week. To increase the selection increase the date range by making use of the filter option.
Regards,
Sowmya

Where i can find the deleted transport request in SAP development system?

where i can find the deleted transport request in SAP development system?

Hi,
When you delete the transport request from SE10 , you can not find the request entry from E070 and E071.
and only local change request are possible to delete from SE10 /SE09
if you are try to delete the change request with target system then it's gives you the error that request cannot be deleted because it contains locked objects.
It's not possible to find out the deleted request from SE10.
regards,
kaushal

How do I find from which terminal transport request imported to PRD

Hi Experts,
Let me know how can I find from which terminal transport request imported to PRD
Thank you in advance.
Regards,
Raj

Hi Raj,
Please find the answer for your question in below discussion.
How to find out workstation of a transport request created
I hope it will help you
BR
AKJ

How to compare the transports requests in the same system

HI ,
Is there any option to compare transport requests in the same system whether both contain the same objects or not.

Ambarish, you can perform check in two ways.
-you can go to /usr/sap/trans compare the data files and cofiles andcheck the physical size whether it is same or not.
-you open the TR in SE01 tcode, select the sub TR and expand it it will show you the list of objects/programs included in that TR.
Hope it addresses your query.
Regards, Amber S | ITL

Transport Request Import E-mail Notification

Experts ,
Whenever we transport an change request to Target system , say to QA system , Can we get an E-mail notification that the transport request has reached Target system. If yes, How can this be achieved. ???
Would appreciate your reply .
Thanks,
Ashutosh

Hi
You need to setup a workflow for Transport requests.The mail can be sent to Business workplace(t-code SBWP) inbox or sent to exchange server for a internet email. Go to SE09 and click on Transport Proposal Tab which is right next to Global Information Tab. You can read the SAP HELP there to activate this mechanism.
Reward points if helpful

Transport request import scheduled in background fails

Hi folks,
In our landscape we have PRD and an Application server. We want to import transport requests in background at a defined time. Though the job status shows up as finished however in the job log it reports - Transport control program tp ended with error code 0232.
In the STMS queue, the request is in still being imported status for long time unless SAP is restarted.
If I change the job in SM37 and give one of the servers (PRD or Appl server) as the execution target the job finishes successfully and request is imported.
My Question is how can I get the job to finish properly without having to enter the execution target each time? I should schedule the transport in background in STMS and it should finish without error.
Regards,
Sai Rolla

Hi SAI,
See this SAP Note 165708 - Test call for tp ended with error code 0232 :
Cause and prerequisites
In the transport configuration file TP_DOMAIN_<TDC_SID>, where <TDC_SID> is the SID of the R/3 system which is used as transport domain controller, the database name of the affected R/3 system is written in lower case, thus you will find the following entry:
     <SID>\DBNAME = <<sid>>
Solution
From within the transport domain controller <TDC_SID> change the transport log in the affected system. To do this, proceed as follows:
      1. Call up Transaction STMS.
      2. Choose "Overview/Systems". On the following screen select the affected system.
      3. Choose "Transport tool" and "Display <--> Change".
      4. For DBNAME write the SID in upper case.
      5. Save and let configuration distribute immediately.
      6. Exit maintenance.
To ensure that no incorrect transport configuration file is generated with a new setup or an enhancement of the transport domain and subsequent activation and distribution, change function module TRINT_PP_GET_DEFAULT_VALUES as described in the attachment or apply the respective Hot Package. (You should do this for all systems participating in the transport domain and not only in the transport domain controller <TDC_SID>.)
Best Regards
AK

Error during transport request import - how to get it's text at runtime?

Good day to you, Ladies and Gentlemen!
Would be glad if someone can give me an advice.
Suppose we are importing a transport request to a system. And an error occurred during import.
In my program I want to display why the transport failed. How can I get the error message text with description of what is wrong? The same we can see at the transport log?

Hi
If you mean reading the Transport Log of a request you can use this FM
data: lines type table of TRLOG.
CALL FUNCTION 'TR_READ_LOG'
EXPORTING
   IV_LOG_TYPE             = 'FILE'
   IV_LOGNAME_FILE         = '/usr/sap/trans_UE6/log/E7DG900147.UE6'
TABLES
    et_lines                = lines
EXCEPTIONS
   INVALID_INPUT           = 1
   ACCESS_ERROR            = 2
   OTHERS                  = 3
You just have to figure out which directory is you system using to store the Transport Logs. Also note that in this case UE6 it would be the logical name of your system and E7DG900147 the transport request number.

Transport of Query to Test System

Hi
All do you transport newly craeted query and its web template to Test system. I have created a query now will have to craete the transport request for the same and transport it to Test system.
Regards,
Rohini

Thanks Brat, Bhanu and Roberto
Bhanu i already have a development package created.
and i ahve already done with my query design.
Now how will have to transport to Test system?
Creating transport request now when iam done with query design will consider this new report in the request and move the report to QA?
Regards,
Rohini

How to cancel changes that were made via transport request importing?

Hi!
Could you please tell me whether it is possible to cancel changes that were made via importing of transport request into the system?
Thanks and Regards,
Siarhei

hi
the programs maitains the versions ...just check the version managemet..
regds

Adding transports to import queue after System Refresh

Hello All,
Every time we do system refresh from PRD to Sandbox as a part of post refresh activity we need to import all the transports which are in the import queue of PRD(which are not yet imported to PRD) to our Sandbox.
But its a tedious job, as in the import queue many old transports which are still not yet imported to PRD will b there.
So may b around 150+ transport requests in the import queue of PRD, which we need to add those manually from path
Extras---->other requests -
> Add. doing same for 150 times. cant even imagine dat work.
So my question is, Is there any way to get the replica of import queue of PRD to Sandbox.
Some where i read like transport buffer in the path /usr/sap/trans/buffer/<SID> of the system will have list of all transports in the import queue.
So can i copy dat file and replace SID with Sandbox SID and place it in the Sandbox under same path.
Please suggest or give me a correct solution.
Regards,
Ravi

Thanks a lot for your reply.
I had read about using script like tp addtobuffer inorder to add the transports to the import queue some time back.
But forwarding transports is a new method i got to know here which even looks easy too. It would be great if any 1 tell me how forwarding works.
Also it would b fine if who all uses this method of forwarding to add transports to import queue do reply about any problems faced while forwarding requests.
Bcoz in our landscape , transport route is as below
Dev to QA and Sandbox then from QA transports will move to Production.
So after refresh forwarding Transports from PRD to Sandbox, how does this work. Please share your suggestions.
Regards,
Ravi

Issues while transporting requests to an upgraded system

Hi all,
There is a development system which is upgraded.
prior to upgradation of this development system , we copied all the abap developments to a temporary system, where developments were done until development system is upgraded.
As of now , we are manually copying the changes done in temporary system to the upgraded development system,
     i.e for ex; Manually copying the code of a program in temporary system to upgraded development system
Instead of manual copying of the developements/changes from Temporary system to development system, can we move the requests directly from
temporary system to development system.
Please let me know ,what are the issues raised while moving requests ( of programs,tables,scripts,smartforms..... e.t.c ) from temporary system to development system
Thanks in advance.

There's a new 'check' that can be done when transporting CRs throughout your landscape. It is the unconditional mode "Ignore Invalid Component Version".
This feature (check the component version) was included with SAP_BASIS 702, so the tp checks the component version of the system where the transport was released (this information is included in the transport) and the component version of the system where the transport is going to be imported.
This component version check feature will check all the components version between source and target system. So before choosing the 'Ignore' option, please try to make sure that the software component version that the objects contained in the request belongs to, should be the same between the systems, to avoid any inconsistencies. It is recommended to transport request in systems which are on the same support level or use the same add-ons.
The component check is a hint that you will import a transport which come from a system which is different from the target system. It only checks the installed add-ons and support packages. This means if you have in the source system installed a add-on which is not present in the target system of the transport you should aware that you import no objects which depends on the add-on which is not present in the target system, the same point belongs also to different support package
releases. This option was implemented to reduce the risk of inconsistencies. If you import the transport please use transport option "ignore invalid component version".
This import option means that transport requests can be imported even if their component version does not match the current component version (including Support Package Level) of the system. This is the case if the component version of the system is either new (the Support Package Level
is higher than that of the export system) or too old (you first have to have imported the Support Packages before you can import the request). You should only use this option if you are sure that the content of the transport request is independent from the component version.
If it is required to avoid this check you could set transport parameter SP_TRANS_SYNC with value OFF and this check will be not performed from tp, but I would recommend to use import option "ignore invalid component version" before you would import the transport.
transport parameter SP_TRANS_SYNC = OFF.
Parameter SP_TRANS_SYNC is delivered ON by default.
This option will avoid the check of the component version.
Some notes regarding this feature:
1581638 - SAP component checks no longer working in TMS
1577714 - Transport requests in Check requirements phase
1650265 - TMS workflow: 'Ignore Invalid Component Version' missing
1742547   Information about component version check in TMS
1756116   TMS Component Check: Fix for excluded component logic

Transport Request import Error

Hello Experts,
When I import transport request SAP system from another SAP system then getting error as "Result of cross-total check indicates a damaged data file (9114)" with the return code 16. Please suggest any one what is problem and how to resolve it?
Thanks.

Hi,
You can generate a transport os copies for the sae request an release it to get a proper datafie and cofile.
Regards,
Nirmal.K

Transport request import

configuration was done in client 000 and transport request put in, would like to know how to import in QA system?
Thank you,
zack

Hi
Let me tell you all the three scenarios
1.
If you are on same system with different clients as 100(DEV) 200(QAS) and 300(PRD) then use SCC1 and import the request form the source client by giving the transport request number.
2.
If you are on the same client and want to set up the transport route fot the within your system then you need to use Extended transport control to set up the transport route within the system.
3.
If you are on different systems as DEV QAS and PRD then use tcode STMS_IMPORT to import the tranport requests and if this doesn't work then import the requests manually through OS
tp addtobuffer <Trnspt req num> <SID> <Client> pf=<path to parameterfile>
and then
import reqst manually
tp import <Trnspt req num> <SID> <Client> UXXX
Goodluck
Rakesh

Transport Request import to Test System

Similar Messages

Maybe you are looking for