Transport request question

Dear ABAP'ers,
I've got a question ...
... how can I check if a program for example is assigned to any transport request?
I will be thankful for a small tip.
Regards. P.

Hi,
You can check it in table E071.
Give OBJ_NAME as your program name
Thanks

Similar Messages

How to collect the deleted query in a transport request.

Hi Friends,
I have created a query and transported it to the Quality, the data content is all ok, except that i have not used the Project Naming conventions. Now i have a defect against my name for this. I have to copy the same query with the correct Naming convention and transport it.
My question is after copying the query with correct name i have to delete the old query (if not there would be 2 versions of the same query). How do i collect the deleted image of the query in a transport and send it to quality?.
I tried deleting a test query from Bex Designer, but this does not ask me for a transport. should i use RSZDELETE?. Not sure if it asks for a transport request when i delete the query.
Can someone pls tell me how to go about this?.
Thanks in advance.
BN

Hi BN,
I do agree that deleting directly in Quality and Prod is not good way and not recommeded.
I have not tried and deleted.But if the system is configured in such a way that if it doesnt ask for a request
then i feel you have no option.
If any object is deleted then you must have the deletion image collected into request at the same point when you are deleting.Because later when we go to transport connection we wont find the object itself.
What i think from your point as you said you have done earlier is you must have any open request regrding this query and when this query is deleted , the deletion image is also included in the same request.
So go to se03 and give your deleted query name and check all the requests.
Check in the requests when the deletion image is captured or not. we might be knowing that this is cpatured.
Regards
vamsi
Edited by: vamsi talluri on Nov 9, 2010 9:14 PM

How to move a transport request from one client to the other

Hi,
I created a new transport request with a lot of elements (and also some modifications), but I made it in the "wrong" client on the system. Now I have the question if there is any possibility to change the client-relation of a transport request via SE01 (or similar transaction). Copy and Paste of the element list isn't the optimal way, because there are also table contents in the transport request.
Can you give me a hint?
Thank you
Kind regards
Markus

Yes you can change the traget client.
Check the TR properties and set the taget client .

Import steps not specific to Transport Request

Hi all,
I need to move 5 Released Transport Request as "Local Change Requests" to another SAP installation.
I followed two guides to do this:
SAP BASIS / ABAP - How to Export and Import an External Change Request - YouTube
How to copy Repository Objects between non-connected SAP systems - ABAP Development - SCN Wiki
However I have problems creating the Change Request that contains all my requests: if I generate it as Local Change Request it is not available on cofiles and data folders.
So I created a new Virtual System called M02 and I created a standard consolidation transport link between my original system M01 and the virtual system M02.
Then I created a new TRANSPORT OF COPIES Transport Request and I selected as target system M02. All objects are correctly added to the new request and the validation is correctly performed.
However when I release the request on the SOURCE server I get the following error:
M01#######            My Request Name
M01        System M01
             Checks at Operating System Level         05.03.2014 16:48:34    (0) Successfully Completed
             Pre-Export Methods                       05.03.2014 16:48:37    (0) Successfully Completed
             Export                                   05.03.2014 16:48:47    (0) Successfully Completed
      Import steps not specific to transport request
M02        Virtual System
             Selection for Import                     05.03.2014 16:48:47    (0) Successfully Completed
      Import steps not specific to transport request
"Import steps not specific to transport request" expanded as:
Feedback after export or import 05.03.2014 16:48:48    (0) Successfully Completed
I get this message even if I generate the new Change Request from a single Change Request (the first one that we released).
The cofiles and data files are correctly generated, however the IMPORT on the TARGET server returns an error (invalid data package)
My question is: is the "Import steps not specific to transport request" message correct, or should I modify something? Why am I getting this message?
Thank you

Hi Chinna,
Its a warning message you can ignore that... if you want to see what exactly the reason for warning in SE09 --> select the released request --> click the Transport Log Ikon --> select the warning message and click the spects Ikon --> go on expanding you can find the warnings of Objects in Yellow...
Hope this helps,
Sudhakar.

CHaRM-Is that possible to create multiple Transport Request in UC

HI Gurus,
Quick question on ur.gent correction using Solution Manager CHaRM in EHP1. Is it possible to create multiple transport request(TR) for single ur.gent correction (UC). DO NOT confuse with transport task.
For example, after I created transport request and developer start working and release the task, realised to add another transport request for same UC. When I tried, it did not create any TR but checked the message found that
Schedule Manager: Monitor
Job Status: Processing completed, but with warnings
Program Name: /TMWFLOW/SCMA_TRORDER_CREATE
Action to be checked: Ur.gent Correction: Create Transport Request
There is already an open request, XXXXXXXXXX, for this project
So only way I can do that I released the TR and able to create another TR.
May be wondering why I need to create another TR, why not create TASK and work on that.
But this is the requirement at our company.
I will appreciate the effort and time to provide me the solution of this.
Thanks
Ava

Hi Ragu,
That's really quick turn around. Unfortunately not able to found whatever you mentioned in your message. Here is detail,
I navigate to Actions - Depending on Status, found the entry as
Trans. Type     StatProf         UserStatus     Seq     Action in SAP Change Manager
SDHF             SDHFHEAD   E0002            10       CREATE_HF
SDHF             SDHFHEAD   E0002            20       CREATE_REQ
SDHF             SDHFHEAD   E0002            30       SAVE_PARTNER
SDHF             SDHFHEAD   E0002            40       SET BO LINKS
Where SDHF - Ur.gent Correction
           E0002 - In Development
           CREATE_HF -        Create an Instance in SAP Change Manager
           CREATE_REQ -     Create Transport Request with Task
           SAVE_PARTNER - Save Partners in Respective Partner Roles
           SET BO LINKS -     Sets Links to Business Objects
I don't see any OPEN_TR.
Any other place need to make change.
Thanks
Ava

Merging Java Transport request with Abap Transport Request in Charm

Hello All,
We have activated the Change request Management in Solution Manager. Therefore transport request of type workbench and customising can be created when you choose action 'Create Transport Request'.
However we have some SAP systems that have CTS+ integrated which allows to generate transport request number and attach objects in PI Integration Directory - java transports.
Question is - Is there a way we can integrate the java transports generated in these SAP systems with Solution Manager CHarm and transport creation.
Or can we assign the java transports to charm in any way.
We are basically looking for how when users create Charm, the abap and java transports relating to the charm are generated and created only from Solution Manager manager or how these two transports can be linked together in Solution Manager.
Thanking you in advance for your help.
Tolly

Hello Friends
I have read the links and followed the instructions and tried to create object
TABLENAME R3TR TABU and tried to save it.
I keep getting a warning message
Note: ZTABLE1 is an application table
Object TABU ZTABLE1 has object function "k", but no key.
(I don't know what key to enter. I tried the Key field name, but it said 'Enter Numeric values only').
If I ignore and save and try to create transport request and then import it on a different server, again only table structure is getting transported and not the contents/data of the table.
I would appreciate if some one can please let me konw what I am doing wrong.
Thanks
Ram
Edited by: Ram Prasad on Jun 2, 2009 3:38 PM
Edited by: Ram Prasad on Jun 2, 2009 3:40 PM

Create transport request based on SDMI transaction type

Hello,
a customer of mine intends to use transaction type SDMI in a kind of unusual way. He only creates SDMIs without creating projects, cycles or change requests in ChaRM. He uses a customized copy of the normal correction to track his changes and now needs to activate the functionality to create transport requests as an auditor requirement.
As I'm not proficient in ChaRM, I would like to know if that is at all possible.
Assuming it is possible, what would be the preferences to use action "Create Transport Request" regarding IBase etc.?
Assuming it is not possible, what would be necessary as a minimum to establish the link to the respective system in which the transport request should be created to get that action working, a maintenance cycle? How is the maintenance cycle linked to the ticket?
That are a lot of questions, and it would be highly appreciated if somebody could lighten up the fog there for me.
Thank you in advance!
Kind regards,
Emanuel

Hi,
1) Do I need to perform any steps in the task list before ChaRM can be used?
No once task list is in active state and sdmn is created for ur project u can start using charms
2) How is the maintenance cycle ticket (SDMN) linked to the change requests? Is this linkage done in the SDCR ticket via the maintenance project in the "Customer fields", where solution, maintenance project etc. can be assigned? Or is this implicitly done by the chosen IBase?
Yes everything is dependent on IBASE and logical component.
Check this links
https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
Check SMP/SDN
https://websmp208.sap-ag.de/changecontrol
Resources on CTS+ [original link is broken]
Hope it solves ur queries
Regards
Prakhar

Transport request for BW queries and roles.

Hi All,
we need to craete 20 bw queries on 4 multiproviders. We need to save 18 queries as workbooks in one role and the other 2 queries in other role. Both the roles and queries does not exist and will be created in Developement environment.
We just want to know how we can transport them in the quality environment. What is the right method to transport them.
Can we transport all the object queries, workbooks and roles in number of transport requests so that if few queries or workbooks needs any changes then we do not have to transport all objects just the request which includes the changed objects.
Thanks & Kind Regards,
Hardeep

Thanks a lot for all of you for your quick response. But i still have questions.
If we create one transport for roles and one transport for each query then we will be having 21 transport requests. But the transport request on same multiprovider can lock the clacuated key figures and restricted key figures, if they are present in more than one query, it means they will be present in more than one transport requests, so they can be locked and trasport request will be failed.
If i just create one transport request for all the objects roles, quaries & workbooks it will not loack any object, and transport request will not fail. But i have to transport all the objects again if i need to change one of the queries.
Please let me know if there is a method that i can divide my queries as per multiprovider and can create transport requests as per multiprovider so that we can not lock calculated keyfigures and restricted key figures. Is workbooks can be published in the role in the same transport request. If it is and if in more than one transport request we are publishing the different workbooks to the same role, will it lock the role.

Re-transport the transport request to NQA server after system refresh

Hi
Users are moving the transport requests in NQA (quality server) using STMS tcode and Basis team is moving the trasnport requests using TP command in operating system level.
There are some transport requests that are released and are moved only to NQA server but not in Production server.
After the NQA refresh from Production server, we need to re-create the trasnport route for NQA server
in NQA using SE06 and STMS.
Now users want to re-transport the requests again in NQA server that was moved to NQA before the system copy but they are not able to make it. In the transport queue, users are able to see their transport requests but they are not able to re-transport.
When basis team try to move the same transport requests using TP command in operating system level, it failed with error:
- "Transport request is not in buffer".
- x2n0v2:nqaadm 14> transport250_NQAu126 908807
/usr/sap/trans/NDV/cofiles/K908807.NDV
is this the correct cofile ?y
cofile is K908807.NDV
source system is NDV
transport type is K
transport name is NDVK908807
Renamed to K908807.NDV.INTRANSIT on dbcindv
Datafile copied to dbcinqa
Cofile copied to dbcinqa
-rw-rw-r--   1 nqaadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NQA/data/R908807.NDV
-rw-rw-r--   1 ndvadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NDV/data/R908807.NDV
-rw-rw-r--   1 nqaadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NQA/cofiles/K908807.NDV
-rw-rw-r--   1 ndvadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NDV/cofiles/K908807.NDV.INTRANSIT
Please compare the files before proceeding
Do you wish to continue the import?y
tp addtobuffer NDVK908807 NQA pf=TP_DOMAIN_NDV.PFL
This is tp version 305.13.25 (release 46D) for ANY database
Addtobuffer failed for NDVK908807.
Cofile not existent or corrupted (datafile exists).
If source system is available you may try to reconstruct
the cofile using the command "createinfo".
We used the following method to re-transport the requests to NQA server:
"STMS --> Request -->Delete (the request number)" method delete the transport request from transport queue and from the cofiles/data directory of the operating system and then " STMS --> extra-> other request-> add" allow us to put the transport request back to transport queue in NQA server. Once the transport requests are in queue, we can re-transport all of them one by one or in group.
Question: Is it the right way to re-transport the request in NQA (first delete if from transport queue and then add and then re-import in NQA server).
Id there is any other way to re-transport the requests, pls suggest us.
Thanks
Amar

Amar,
Depending on how many tarnsports you have and also if this is one time, what you can do is ask Basis guys to write a small script which adds to the buffer to your NQA system.
Steps:
1) under /usr/sap/trans/buffer rename the NQA buffer file.
2) create a new empty file NQA (make sure permissions are identical)
3) Provide the list of transports and ask Basis team to put it in a file at Unix level
4) Run a script which will add to the buffer from the source file.
5) From STMS refresh the NQA queue and you should see all the transports ready for import.
Hope this helps.
Thanks,
Naveed
Edited by: Naveed Qureshi on Dec 4, 2008 8:52 AM

How to delete objects in transport request

Hi,
I have several different questions in Transport requests and need advice:
1. I need to transport an Infoobject and I chose only necessary objects in grouping and I don't see any app components in the request before created, but in SE01, under the request id I see app components and infoareas listed. A bunch of them, which I don't need to transport. Why this happens?
2. I want to know if there is a way to delete all the app comps in one shot from the request before it is released?
Thanks.

U might have selected 'Collect automatically"
I suggest u, to delete complete request ( first unlock it in SE03... then delete it from SE09)
Recollect that InfoObject in a new request, by selecting only necessary object & Collect manually
In this way u will have less confusion

Transport request for ABAP OO Class

Hi,
I have created a class with multiple methods and saved into one TR. Now under the TR contains task and under the task contains
->Class (ABAP Objects)
    ZCL_VRL_ZCFA_CLASS =>This is normal and fine.
Now I have created new class with 3 methods but the methods are recorded separately and the class name recorded separately, please find the below details.
SD1K977104(Main TR)
SD1K977105(Task)
->Method (ABAP Objects)
    ZCL_BASECLASS             CHECK_CONTRACT_MCON_ACON
    ZCL_BASECLASS             CHECK_CONTRACT_QUOTATION
    ZCL_BASECLASS             CHECK_CREATION_DATE
->Class (ABAP Objects)
    ZCL_BASECLASS
The separate recording will be happen when the TR is transported earlier, whenever creating new class this separate(class and methods) recording should not happen.
While transporting into Quality the first method trying to activate but the second method(which is called in 1st method) doesnt exist at this time. Anyhow the class(Object) getting transported and activated and working as expected but transport error log appearing in SE09/SE10.
" Ended with return code: ===> 8 <==="
My question is why the class name and method name recorded separately.
I appreciate your quick reply.
Regards,
Vadamalai A.

Please find the log.
Log file:                /usr/sap/trans/R3/log/SX1K997477.SX2
           Generation of programs and screens
           Transport request___: SX1K997477
           System______________: SX1
           tp path             : tp
           Version and Release: 340.16.41 640
           Generation of programs and screens for transport request SX1K997477
           Only generates programs with LOAD versions
           Start on 20.05.14 at 23:28:38
           Generation of the transported programs
           Generation of the users of the transported Includes
           Program ZCL_VRL_BASECLASS=============CP, Include ZCL_VRL_BASECLASS=============CM00L: Syntax error in line 000001
           Method 'MCON_FUTURE_DELETE_OPTI' is not declared or inherited in class 'ZCL_VRL_BASECLASS' -
           Ended on 20.05.14 at 23:28:42
           No. of programs /Min/Avg/Max (sec): 7   0 1 1
           Generation of programs and screens
           End date and time : 20140520232842
           Ended with return code: ===> 8 <===

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

The correct way to delete old transport request record ?

Dear all,
We want to delete old transport request record before 2008 (two years before) of our system.
We learn that we should delete the records in the below two path:
/usr/sap/trans/data
/usr/sap/trans/cofiles
Our target is that we will not see the old record after deleting in our PRD system.
Normally, we see the transport request record in system by this way:
STMS --> import overview --> PRD --> Import Queue system PRD --> Import history
Our question is do we need to restart our system after delete the record to refresh the Import history?
We have not delete the record now.
Any experienced or expert, please kindly give advice.
Regards,
Allen

Hello Allen,
there are some notes and documentations for this process. Deleting the files from /cofiles and /data will not erase the request from the import history, as you already know.
You should follow note #41732 to have the requests/data completely deleted from your system. There is a lot of complementary reading in notes #7224, #556734, #189841, etc.
Note that you can remove the request from the import queue, import history, data and cofiles subdirectory, but still have it on the <SID> buffer (located in /usr/sap/trans/buffer/<SID>). If this happens to you, please save a copy of the buffer file <SID>, then create a new, blank file named <SID> at a time when the import queue is empty (VERY IMPORTANT). Or, alternatively, please excute the tp cleanbuffer FIL command (which will erase the requests that are not found in /data and /cofiles directories).
--> Please test this first on a test system, not directly on a productive environment.
This should be enough to delete old transport requests on your system.
Best regards,
Tomas Black

How to assign transport request for Dynamic selection in SE36

Hi Friends,
Please guide me how to transport or assign a request for the changes made in BRF selecion view.
I have assigned and added BKPF-XREF1_HD field for FB03 transaction. Its working fine as per user requirement.
I am facing probelm to assing a transport request for that. I didn't find any transport menu in se36.
So please provide me how to assign a TR which need to import into Production client.
If I have to assign or create a program (standard), then please provide me the program name.
Please reply.
Thanks & Regards
Sankar.
Edited by: sankar babu on Jul 29, 2010 12:27 PM

Moderator message - Cross post locked
Total Questions: 283 (131 unresolved)
Please also close your old posts and assign po1nts to helpful answers.
Rob
Edited by: Rob Burbank on Jul 29, 2010 9:50 AM

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

Transport request question

Similar Messages

Maybe you are looking for