Validation on Transport Request Description

I want to put some validation on the transport request description.
Please let me know the procedure.

When you want to use existing transports to configure your process rather than re-keying in the configuration. However, I cannot imagine why you would want to detail your configuration this way.
Maybe when you want to provide a level of confusion as to how the system was configured? It's sort of similar to when you put a BC Set on the Config tab. Without a document telling you what the BC Set is doing it kind of makes it hard to see the big picture.

Similar Messages

How can i change transport request description

I need to change transport request description for one table
Note:
Considering this post as Basic and Locking it for futher postings.
Answer: Double click on the Request and using the change option, change it's Description
Edited by: Vijay Babu Dudla on Jun 29, 2009 7:02 AM

Hi,
I know I am a little to late to the party! But for all those who are going to search for this in the future there is a very good blog...i am posting the link below...
Basically run the program RDDIT076...
http://scn.sap.com/community/abap/blog/2015/03/12/program-to-change-transport-request-description-after-release
Regards,
Divaker

How to change Transport Request Description in SAP

Hi experts,
I want to change Transport request description, please suggest me whether its is possible or not. else i have to delete the same request and re-create as per my requirement.
Thank in advance..
looking forward for expert comments...
With Best Regards,
Bharat B

Hi Bharat ,
You can chnage the description of the transport request if thesame is not moved from Development --> to Quality .
Use T Code SE09/SE01 and select the required transport request no and Double click on the same .
Then click on Change Icon and properties Tab . Here you can change the description of the Transport request.
Thanks and regards
Veera

Rename of Transport Request Name

Hi Friends,
How do we can rename Transport request description in BID system?
Can we rename the same Transport request description in BIQ system(Once it is imported from BID system) ?
Thanks in Advance...

Hi ,
Regarding your query for renaming the transport, the transport request can be renamed only when it is in Development system and once it is released or being imported into the Quality system it cannot be renamed.
As suggested above, go to SE09, double click -> go to edit mode and chance the anme under properties tab.
Hope it helps,
Neha.

Transport request table

Hi all,
can u please let me know which table holds the transport request descriptions and stuff.
thanks,
Kiran.

Hi kiran,
1. the following tales :
<b>CTS : Header/Request Table     E070</b>
CTS : Client Source/Target     E070C
CTS : Last Number Of Request     E070L
<b>CTS : Object Entries     E071</b>
CTS : Texts     E07T
2. The bold ones are the important tables.
regards,
amit m.

Validations transport request

Hi All
I have created a validation, but I didn't got the transport request no.
Please let me know how to transfer the transport the validation or how to create the transport reqest for my validation.
Best regards
Madhavi

Hi
Keep the cursor on validation you created (Not on step ,validation may have number of steps ex:-step 001 ,step 002 etc..) and from the menu select Validation-> Transport. Select all the check boxes and execute.Then it will prompt for new Request creation.
After creating the Request go to SE09 to move the same to Quality server.Once it is moved to Quality Run the program RGUGBR00 to generate the ABAP Code for validation in Quality.The same need to be done in Production also.
Also i can say you , we can generate a transport request no. for the validation only but not for step.
So the same transport number will be valid for all the steps in the validation.
Hence we cant create a transport request no. for a step.
Regards
Venkat
Edited by: Venkat Dara on Dec 3, 2008 5:39 PM

Modify description of transport request

Is it still possible to change the description of a transport request once it is released?

Hi
there is an workaround available
This is at DB level
Change the entry in E070 table
update e070 set TRSTATUS='D' where TRKORR='REQUESTNO";
Then in SE01/SE10 its shown as modifiable
then Changet the description and Save it
and Release it.
The data/cofiles will be overwritten
this can be done on original system (i.e in which the request was created)
Hope this helps
Ravinder

How to change description of released transport request

Hi experts,
The transport requests tasks and are released and owner of TR also released, now need to modify description.
Is their any possible way to do it, because transport is not moved out of the system.
Thanks,
Pavan

Hi
There is one way to achieve this.But this s not advisable.
1.) Got o FM 'TRINT_CHECK_REQUEST_CHANGEABLE'
At the line number 111 IF is_request_header-trstatus CA sctsc_states_released, put the break point.
1.) Double click the released request which you want to change the description.
2.) your EDIT option will be disabled. Just type '/h' in the tcpode area and press enter, your debugging will switched on.
3.) Then Press ENTER again, it will open the debugger screen, in the variable change the SY_UCOMM field to 'WB_DISP_EDIT_TOGGLE' . Then press F8.
4.) your control will be in the FM 'TRINT_CHECK_REQUEST_CHANGEABLE' line number 111. Try to skip this IF condition by using debug technique.
5,) Now you can change the description.Now you cant save this as Save button is disabled.Just press back button, you will get the message for save the changes.Just save it. Done.
Thanks and Regards,
Senthil Kumar Anantham.

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.

Error when importing a Transport request in CHARM???

Hi all,
when i am trying to import a transport a request( thru CHARM) , its throwing an error " No valid system specified (Q11)" and "Import error: Check TMS Alert Viewer in target system"
Note::I was able to create a Transport request , release it but facing problem while importing to quality system.development system is ECC5.0 and quality is ECC6.0
rgds,
Anand

HI abhi,
i havecreated the domain link, my ECC5.0 and ECC6.0 are in one domain of which ECC5.0 is domain controller,now i configured Solution manager as new domain controller and created a link between these two domains...
now my queries are:
1.is it enuf if i create a link between or even shud i create som transport routes between the newly added system from other domain and the existing domain
2.i am not able to see the STMS configuration in solution manager system.ie in my ECC5.0 system( domain ctrller)if i goto STMS->Overview menu-> transport routes i see the configuration, which i cannot see by logging into solution manager and wentto STMS->Overview menu-> transport routes i dont see
rgds,
Anand

Enforcing free text in Transport request

Hello Experts,
I would like to inquire if there is a possible way to restrict or control the Short description of transport request? We have a naming convention but users are not adharing to standard standard name convension. Standard naming convention is a necessity so that we can identify quickly the ones that needs to be transported, or the ones that needs to be deleted during clean up activities. This should be strictly followed by users, instructors, trainees and developers. This naming convention needs to be strictly followed by developers to avoid their asset objects to be deleted in the system.
For example, Our Standard name convension is <string><md><c><9999999>FREETEXT
String = 2 char alpha numberic charactor
MD = Module
C = One charactor
9999999 = Incident or CR number
Then free text
we want to restrict this. so if the end-user named the TR with anything else that does not follow the naming convention we have established, the end-user should encounter an error stating the he/she must change the name of the TR and follow our naming convention before he/she could proceed.
Looking for good solution which can be easily implemented.
regards
Kishore

Hi,
Double click the request and change. There is a documentation tab. Enter the text there and save.
Pranav

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 request from one server to another

Hi All, We have two servers AB1 and AB2. We would like to transport request from client 101 (AB1) to client 110(AB2). How do i make transport route between these two servers. Thanks, Sam

Hi Sam,
You need to configure Transport Management System between these two system by following Configuring TMS - Software Logistics - SAP Library and by considering below detailed steps:
1. After SAP Gui installed. (Development system is always domain controller.)
2. Logon to Client :000User: DDIC.Pwd: ******
3. Put a T-code (se06) in the command field
4. Click standard installation and click post installation (yes)
5. Put a T-code (STMS) in the command field and give a description then save it.
6. Click System overview push botten, click extras option from the menu and click Distribute and activate configuration. (Yes)
7. Back to the stms main screen and click Transport routes from the push botten
8. Click Configuration button from the Menu.
9. Click Distribute and activate from the configuration menu.
10. Now your sap system is activate in domain controller.
11. Now logon to QAS system.
12. Client: 000User: DDICPwd: ****
13. Put a T-code (se06). In the command field.
14. Click standard installation and click post installation (yes)
15. Put a T-code (STMS) in the command field.
16. Click other Configuration push butten in the bottom of appear screen.
17. Give information about development system.
18. Then save it. OK
19. Now QAS is waiting for include domain controller.
20. Logon to Development system.
21. Click system overview push butten.
22. Click sap system from the menu.
23. Select the QAS systems.
24. Click Approve butten from the sap system menu.
25. Now QAS is member system of domain Controller. (Development system)
26. Suppose if you want configuring Production also, following the same step in the QAS.
Also you can follow links SAP Basis Tutorials/ Training: Transport Management System ( TMS ) Configuration In SAP Step By Step With Snap Shots
Hope this will help you.
Regards,
Gaurav

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

How to transport requests from development to production server

hi gurus
i am new to SDN
can u pls give me detailed information how to transport requests from development server to production server?if possible give me screen shot documents
regards
surya

Hi
Transporting
There are help pages that discuss creation of transports.
In simple terms, you: create a transport package
add objects to the package export the package, plus optionally any related objects to a predefined folder/directory on the portal server into a file with an extension of .EPA copy the .EPA file to the import folder of your QA system and import it test the contents on the QA system copy the .EPA file to the import folder of your production system and import it Create a transport package file
Here is the step by step procedure to create a transport package:
For Export
1. Go to system administration, and click on transport?export.
2. In the middle pane, select the folder you want to export and right click on the Transport Package. 3. Fill in the General Properties i.e the name of the package, id and description. 4. And say finish and open the object for editing.
5. When the object has been opened then right click on the object you want to transport, and say "Add object to the Transport Package".
6. Check the checkbox of the item u have added and see the properties if it has been added properly. 7. Now click on the save button.
8. After the object is saved, click on the export button. 9. U will have an option to select where to store the .epa file which will be generated. U can overwrite an existing one by selecting the browse button, or store it with the generated name in the location it automatically generates. 10. Now Click on the Start Export button.
11. once the export is completed, it shows a report on how much time is taken to generate the .epa file. 12. Here there is an option for downloading the .epa file. Click on the link and download the file. This file is ready to be uploaded into any other EP Server.
For Import:
Pre-requisites: You have to copy the .epa file created while export into the local drive. Optionally, you have to manually copy the .epa file generated in the export function into the Import directory of the server ie. chooseFollow the steps below for importing a certain file. 1. Go to System Administration in the portal, and click on Transport?Import. 2. For the source of the package, Click on the radio button Server for the .epa file you have copied lately. Else, click on the radio button on client if you are operating in the client and select the .epa file you have stored on the local drive. 3. Now select the file from the browse option and click on Upload.
4. Now click on the import button. 5. Once the import process is finished, the report is shown. In the whole process, the par files are not included in the .epa files. For the par files to be included into the .epa files then we have to change the pcdStartup.properties file in the server. The property to be changed is Pcd.TransportApplication.Export.ExcludeObjectTypesAfterRuleProcessing: Keep this property's value as empty for enabling the par files to be uploaded into the .epa. You can check for this property in the portal in the following -System Administration-Support-Portal Content Directory-PCD Configuration.

Validation on Transport Request Description

Similar Messages

Maybe you are looking for