Take backup of transport request to a cd

Hello All
How can we take the backup of transport requests for eg Program name is ZQAS_XXX_XXX and transport request SIDK902343. Please let me know the step by step process to take the backup of the transport request to a CD.
Is it just by coping the corresponding files with same name as transport request in /usr/sap/trans/data and /usr/sap/trans/cofiles ?
Please let me know the step by step process.

Thank you very much reyes
So I will copy the corresponding datafile and cofile of the transport request from /usr/sap/trans/cofile and /usr/sap/trans/data and copy that to a cd. I hope this will be enough to take the backup from source system.
And for uploading that transport request to target system, I will do as you said.
Thank you for the help .

Similar Messages

Transport request's

hi Frds,
plz light on the transport request purpose, importance and procedures in sap implementations, if any doc available with screen shots plz mail to [email protected]
thanks in advance and good day guys
thanks
mohan.m

Dear Mohan.M,
For more information about the SAP Change and Transport System (CTS), visit the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm
Transport Request is generated in following scenarios:
1. Customizing Request - When doing or changing some customization.
2. WorkBench Request - When configuration is cross-client. Eg Generating new Table, making changes in access sequence, Abap development, etc.
Transport request is not generated for Master Data. For eg: Customer Master, Material Master, price master, etc.
Benefit of Transport Request:
SAP Landscape normally has 3- Tier system:
Development Server - Where customization takes place. Transport request is generated at this level & then first transported to Quality server for testing whether it meets the requirement or not. Once the requirement is met in Quality server then Request is transported from Development Server to Production Server (Actual / Live System)
Quality Server - Mainly useful for testing.
Production Server Actual / Live server, where the real transactions are created & posted.
Procedure to Release & Transport Request:
1. In development server, go to T.Code: SE10 & select the check box Modifiable & enter
2. In the next screen, you will see list of transport request created.
Note: Transport request consist of main request along with sub request. These sub request hold the object to be transported.
3. Expand the main request & you will be able to view the sub requests attached to main request.
4. First release the sub requests.
Note: To release the request, select the request ni & click on release request individually (Do not select release all request)
5. Next release main request.
6. Once the request is released sucessfully, imform the basis person to import the request to QA server.
or
If the authority is with you, through T.Code: STMS, select development server --> select request no & release to QA server. Here when it pops up client no, user id & password, maintain it of QA server & release the request to QA server.
Hope this will help.
Regards,
Naveen.

CHaRM-Handling old transport request before CHARM was activated.

Hi All,
Recently i just activated CHARM in solman-SM1 for new a project implementation. This CHARM was setup in in such a way that it tie to one of the local IMG project EPROJ in developmemnt-DEV. Now i have one concern and that is those transport requests where created before i activated CHARM.
These old transport requests were crerated directly in DEV without project assigned. Therefore, we tried to assign IMG project EPROJ (the same IMG project setup in CHARM) into those old transport request manually.
Problem : When i tried to perform released step in CHARM tasklist it says that "No transport request found"
Question : How do i make CHARM to pickup those old transport requests?
Really appreciate your feedback as there are a lots of old transport request which needed.
Thank you.

Hi,
If you use Change Request Management, you should always use Change Request Management means to create transport requests; that is, create transport requests in a change transaction or in the task list.
Manually registered transport requests can be assigned to a task list only, not to a change transaction. If you use change transactions ,,,,the system does not take into account transport requests that you added manually.
This note is what you want
Note 1150426 - Registering transport requests in ChaRM
Hope it solve ur problem completely.
Regards
Prakhar

Merging of Transport Request

Hi Experts,
What are the disadvantages of merging a Transport Request into other?
regards.

Dear Kevin,
If you use Change Request Management, you should always use Change Request Management means to create transport requests; that is, create transport requests in a change transaction or in the task list.
Manually registered transport requests can be assigned to a task list only, not to a change transaction. If you use change transactions (reg. corection, urgnt corection), the system does not take into account transport requests that you added manually. Taht is the mani disadvantage.
You can find further details about how to register transport requests created outside ChaRM in following note:
1150426 - Registering transport requests in ChaRM
Kind regards,
Marta

Releasing transport requests with job roles take forever after upgrading to Netweaver 7

Dear experts,
Some time ago we've out SAP ECC 5 system to ECC 6. Since then, it takes a very long time to release transport requests containing job roles.
For example, a request containing 154 job roles (1 template and 153 derived roles) took 4 hours to release in our DEV system. Before the upgrade this only took a couple of minutes.
Afterwards, the import in our QAS and PRD system don't take longer than normal.
Apparently this time is taken by the Export phase:
Checks at Operating System Level
17.04.2014 09:50:03
(0) Successfully Completed
Pre-Export Methods
17.04.2014 09:50:37
(0) Successfully Completed
Export
17.04.2014 13:51:02
(0) Successfully Completed
Does anyone know what causes this and how to solve?
Kind regards,
Nicolas

Hello Nicolas,
What I understood from your description is that ,it takes very long time to release the job. Once it is released, execution does not take much time.
To me it seems to be background job/work process issue. Maybe all the background work process are busy to execute current jobs and no free work process available for the jobs which are in the queue. In that case, if possible try to increase number of bg work processes.
Check for any performance issues during that period. Check if there is any locking issue and jobs are stuck because of that.
Hope this helps to investigate the issue
Regards,
Archana

ChaRM Reporting - Transport Request, Tak and Owner columns not filled

I am using ChaRM reporting functionalities (/TMWFLOW/REPORTING transaction). When I select "display header, project, task list and transport", transport request, task and owner columns are not filled with values.
What is the problem?
Thanks
Antonello

Hi,
1. Is it configurd for ChaRM functionality in your systme landscape.
2. If not, please do the ChaRM configuration using by tcode SPRO.
Regards,
Srini Nookala

Best approach for backup and transport (NW BPC 7.5)

Hi,
we are currently in a situation, where we have developed a prototype in a Q (quality) envoirnment. This has been a standalone system sofar.
Now we have a Development->Quality->Production envoirnment - and I want to move my prototype from the Quality system to my Development system.
I'm thing about the "UJT_BACKUP_RESTORE_UI" program. I will not copy masterdata and transactional data.
My question is now. Is it possible to backup my Appset prototype in Quality and restore it under a new Appset Name in development, and then put in it a transport request ?
Or would I have problems with technical names for cubes and dimensions ?
What is the best approach ?
Thank you,
Joergen
Edited by: jdalby on Jun 14, 2011 9:49 PM

Hi,
First of all, you should have posted your question in the BPC for NW forum.
Coming back to your question, you can try the transaction UJBR. You can take the backup of metadata / masterdata / transaction data or any combination of those.
I wont suggest you to change the name of the backup files. Instead, you can create a copy of the appset and then take the backup and restore it in DEV.
Hope this helps.

We want to take backup of ( RFC ,Printer, ALE setup) Tables

Hi All,
We want to take backup of ( RFC ,Printer, ALE setup) Tables before refresh. Could you please suggest me how we can find the related tables to export RFC etc..

Hi Manohar,
You can use below methods..
RFC connections
For releases < 6.10 SE01 -> create -> workbench req (next popup screen Fill in the BOX Target, write same SID as you are logged on to -> delete task created. Request/Task -> object list -> display object list -> change -> new entries -> r3tr tabu rfcdes -> enter -> extras -> change object function -> entire table -> save.
Release transport, check transport log, number of exported entries should be the same as rows in table.
FOR CLARITY:
SE01
Create (paper icon)
Tick workbench request
OK
Add description, project id (if listed) and sid (use log if not available) and save
Highlight unclassified transport
Delete (dustbin icon) and confirm
Double click on transport (lowest level)
Change to update (pencil icon)
Add entries u2013 PRO = r3tr / OBJ = tabu / OBJECT NAME = rfcdes
Enter
Click on key in next column
Reply yes to save changes and close the warning box
Update (pencil icon)
Add an *
Save
Similarly ::::::::::
Table TBDLS (logical names)
Table IACORDES & IACORSITE (logical names)
Printer definitions make transport
SPAD -> Output devices -> Update -> Edit -> Transport -> Transport All
User masters (if required) make transports
SCC8 u2013> Selected profile: SAP_USER and target system
Save batch task info from tables TBTCO & TBTCP in SE16
thanks
ashish

How to find multiple transport requests for one object

Hi all,
Is there any function module which will fetches multiple transport requests ( if created ) for one object.I tried almost all the function modules , but i didn't got the solution.
I need to develop a report ,   which will takes a single Task number as input and gets the Request number from table E070.
Based on that Request Number i will fetch remaining Task numbers under it.
Then for all the Tasks Numbers, i am fetching their objects by using table E071.
I need to list out whether any of these objects are in multiple Transport Requests. Once i got all the Transport Request numbers i need to release the Request based on their Transport Request sequence.
I tried the following FM's , but not able to get the solution.
SVRS_DISPLAY_VERSION_LIST
SVRS_GET_VERSION_DIRECTORY_46
SVRS_GATHER_REQUEST_FRAGS
Thanks..

Hello
I have tried with below code
DATA list_tab TYPE TABLE OF abaplist.
SUBMIT RSWBO040 USING SELECTION-SET 'TEST'
                EXPORTING LIST TO MEMORY
               AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
   TABLES
     listobject = list_tab
   EXCEPTIONS
     not_found = 1
     OTHERS           = 2.
IF sy-subrc = 0.
   CALL FUNCTION 'WRITE_LIST'
     TABLES
       listobject = list_tab.
ENDIF.
break-point.
Submitting the program(RSWBO040) of SE03 transaction a will result in 'CNTL_ERROR' dump.
Please try some other options
Thanks

Error while collecting the process chain in a transport request

Hi Gurus,
I am getting an error while collecting my process chain in a tranpsort request.I have to transport the request from DEV to QA system.
When in RSA1--->transport connection i drag & drop the chain from left to right side pane then the Error occurs.
1.Object 'REQUDELZPAK_48RZW8GZX87CNEH7S897TFQSD' (RSPV) of type 'Process Variants' is not available in version 'A'
Sap help given
You wanted to generate an object with the name 'ZPAK_48RZW8GZX87CNEH7S897TFQSD' (in transport request RSPT) of type 'Process Chain Starter' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
2.Object 'ZPAK_48RZW8GZX87CNEH7S897TFQSD' (RSPT) of type 'Process Chain Starter' is not available in version 'A'
Sap help given
You wanted to generate an object with the name 'REQUDEL ZPAK_48RZW8GZX87CNEH7S897TFQSD' (in transport request RSPV) of type 'Process Variants' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
From one of the threads:
(https://forums.sdn.sap.com/click.jspasearchID=10081153&messageID=4623856)
i though it was the problem of patch level sap note(966131).
Accordingly i tried collecting process chain in the request where the patch level is high(24).But same error is seen.
I have activated chain again & then tried collecting the request i the process chain.But did not solve the error.
I have to collect Process chain in a transport request.Can you help me out to solve the problem?
Thanks in advance!
Regards,
Pallavi

Hi,
take a look:
Data Warehousing
"Errors occurred during post-handling RS_AFTER_IMPORT for MPRO L "
Errors occurred during post-handling RS_AFTER_IMPORT for ROUT L
Try to set the Process Chain Start to Immediate(background jobs) in the schedule, because this will trigger the process chain once tranported and may cause similar errors.
Regards
Andreas

Releasing transport request taking long time

Hi All,
I am releasing transport request in SE09, for releasing child request it was taking long time and for parent request taking much more long time.
In SM50, i didn't find any processes running.
Can anyone tell me the solution.
Thanks & Regards
Uday

Hi Uday,
>> I am releasing transport request in SE09, for releasing child request it was taking long time and for parent request taking much more long time.
You didn't note what release your are running on, but you can check the note 1541334 - Database connect takes two minutes
>> In SM50, i didn't find any processes running.
It is normal, because the system exports the transport request by "tp" command at the OS level, after TMS complete its job on a DIALOG wp.
Best regards,
Orkun Gedik

Transport request coming at the time of creating doc type

Dear all;
Here is a serious problem ,I am currently working in development server ,I was trying to create a new purchase order document type from Standard PO document type .after copid the NB i have done the required change ,but at the time of saving no transport request is cominmg it is direcly saving by the system.I have checked in IDES there it is coming fine.Whatmay be the problem?It is serious problem ,because I canot check in sand box due to I am unable to **** it to Sandbox .Please suggest.
Thanking you;
Joydeep Mukherjee

Hi,
Use T.code:SCC4, check whether development client setting done for not generating transport request!
Here,select your development client and double click; system will take to new screen
Now check u201Cchanges and transport for client specificsu201D Tab and select u201Cautomatic recording of changesu201D and save.
Better consult your Basis Consultant for above.
Regardsm
Biju K

Importing transport request bypassing quality system

HI,
I have a transport request in DEV BW system which is released. For some reason my Quality BW system is down so I cannot import the request in Quality BW system.
Usually we release the request from DEV , say request number DBIK1234, then import that request in quality system. After that we import the same request DBIK1234 into Production.
But for some reason quality system is down, so can we import the request bypassing the quality and directly into Production BW system??
Regards,
Rahul S

Hi Rahul,
Directly Transporting to PRD from DEV is not considered a "Best Practice"
and is therefore not encouraged. You should import into QAS first then the
Request is available in the PRD import buffer, and you can bypass the
recommended testing process if you really want to. However it is still
possible to import directly into PRD by manually adding the Transport
Request to the import Buffer.
We can also configure our TMS to add released TR's to Quality and PRD importing at the same time.
Better if you go through Transport Management System Documentations before you take decision.
Hope this answers your question.
Regards
Ramesh V

How to release a transport request with warnings using a function module?

Hi,
I want to release a transport request(which has some warnings) using some function module .
The warnign that i get when i try to release the Transport Request manually is "not all objects could be locked..."
Which function module can I use so i can release such a transport request?
I am currently using TR_RELEASE_REQUEST but I am unable to release the TR, it throws an exception.
Also i wouls assume that the function module mentioned would take care of releasing all the unreleased task
under the request.
Regards,
Bikash.

Hello Bikash
As an alternative (to cope with the warnings) you may use TRINT_RELEASE_REQUEST.
However, since this fm offers only a single task/request as IMPORTING parameter you need to take care about unreleased tasks yourself. Looking at SE09/SE10 even there you do not have the option the release a request including all its tasks.
Regards
Uwe

ABAP Query Transport request related

Hi,
I have created a Abap query,
1) User group
2)Infoset
3) Query
But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
Development
Please suggest, is this std behaviour or is anything missed
Rgds,
Jai

Thanks to all,
I just created TR with new package for user group and included ifoset and query in the same TR
and imported, issue is resolved
But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
Short text
SAP Query: Transport tool
Description
The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
General information
Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
In both cases, you have to perform similar actions.
The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
Transport action EXPO (exports)
If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
The import options, each of which has an abbreviated syntax,
are as follows:
REPLACE or R
MERGE    or M
GROUP=ug or G=ug    (ug = name of a user group)
UNASSIGN or U
If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
This transport type allows you to transport a modified InfoSet and all the associated queries.
For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
Transporting a user group
Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
Entering a new member in a user group in the target client is possible only if a user master record exists.
In the target client, the assignment of InfoSets to this user group remains.
Transporting an InfoSet
Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
Transporting a query
Transporting a query means only the query itself is transported.
Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
Transport action IMPO (imports)
If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
Transport action SHOW (display)
All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
Transport action DELE (delete)
All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
regards,
Jai

Take backup of transport request to a cd

Similar Messages

Maybe you are looking for