Changeing the Transport request Attributes?

Hi Guys,
Can anybody tell me how to Change the Transport request Text , means while creating a Request u will enter the Description for Each request.Can anybody tell me how to change that description?
Very Urgent.
Thanks,
Gopi.

HI,
You cannot change the text of a request if you are not the owner of that request..first change the owner of the request to your id and change the text.
Thanks
mahesh

Similar Messages

Changing the Transport Request of an Object(Report)

Hi,
By mistake I have saved one of my Custom Transaction Code( of a custom Report) under wrong Ttransport Request Number.
Could you please let me know the procedure to change the Transport Request number of any object like Report, TCode etc.
Regards,
Nitin

Hello,
Delete that perticular object from the request.
And save that object again , so , system will ask you for the request again.
Regards,
Naimesh

To change the Transport request nUmber

Hi
i have created some programs with diffrent request numbers
and task numbers
now i need to change the descriptions , requst numbers for the same programs
how to change that
Thanks in advance

Hi Sri,
if the request is not released just double click on the request and click on change button (pencil icon) click on Properties tab and you can change the description there, just save it and you are good to go.
Hope it helps
Gothrought the following links,
Changing description of a Transport object
Regards,
Harish

To change the Transport Request Number Range.

<b>Hi Experts,</b>
My customer needs a typical solution.
He wants SAP to create the Future Transport Requests starting from 10000. ( Ten thousand)
now the sequential order is 321
that is <SID><K9>00321. From now on the new transport request should start from 10000
i.e.
<SID><K9>100000
<SID><K9>100001
<SID><K9>100002
etc.
Is it possible. ?
Thanks for your help.
Best Regards,
Raghunahth L

Hi
Check the report RSWBO301 and check its documentation..
Press "I" button in the selection screen to get the documentation..
I believe this might solve your problem...
Program documentation
Short text
Number Assignment for Requests: Find Free Interval
Description
This report program searches for a free interval for numbering requests.
    If the search is successful, you can save the interval. The request
    numbers are then taken from this interval.
Requirement
For customers the number range interval includes the follwing areas:
o   900000-999999 (just numerals)
o   9A0000-9ZZZZZ for ASCII character set or
        9AAAAA-9Z9999 for EBSDIC character set.
You only need to execute this program if you have come to the end of the
     number range interval, but there are still large gaps in the range that
     you want to use up.
Example
         Why you might get into this situation:
         The customer has the R/3 System C11. The last number assigned is
         C11K900115. The customer now imports transport request C11K9ZZZZA
         from an external R/3 System C11 into the customer system C11. The
         next request created in this system will have the number C11K9ZZZZB
                                                                                Procedure
Proceed as follows:
1. Execute this program in transaction SE38.
2. Enter the interval limit, for example 5000. You can change this
         limit at any time.
3. Choose Execute.
         If you entered an interval limit of 5000, the report searches for a
         free interval with a size of 5000.
4. If the search was successful, you can save this interval. If not,
          repeat the search with a smaller interval.
Thanks,
Naren
Thanks,
Naren

Change the transport request number

HI All,
One of my program in porduction we done few modifications to that program one month back that is still in QAS,again we done few more modifications to the same program so now I have 2 request numbers due to few problem here my client don't want to move to PRD the TR number that I created one month back he is asking me to create new TR number,but my problem is after that TR I already created one more TR that is also in QAS,if I create again a TR is it will have modifications that I done in two earlier requests,any one please suggest me.
Thanks and regds,
Sree.

Hi Sree,
If i am not wrong, you are having below doubt :
1. You have done some modification which u transported to quality. Transport No A.
2. You have done some new changes which u record into another transport request. Transport No B.
If its a workbench request, then no need to worry, you can transport request no B only to PROD.
But if its a customize request, the u have to include Transport A contents to Transport B.
Thanks
Piyush

How to change the transport request of a NOTE without undoing the note

When we applied the OSS NOTE we put it in a transport request. How can we move the objects into another transport request? Since this is a REPAIR type, SAP does not allow manual copy of the entries. I don't want to include the objects of this transport into another one, Is there any other way?

1. Create a new transport request in SE01
2. Select the request and click on "Include Objects: button.
3. Select "Freely Selected Objects: option from the pop-up windoe
4. Select "Selected Objects" option
Now you see three rows without any PGMID selected.
5. Check the checkbox corresponds to the row and enter the value OBJ & OBJNAME (Textbox without any label). (This valued can be retrieved from your previous request).
6. Delete the same object from your previous request.
7. Click on "execute" button.
8. Click on "Save In request" button.

Released the Transport Request which is in Local Change Request

Hi,
Actually without knowing I have released transport requests which are under Local Change Request.Due to this they are not available for importing in Quality system.My Package is also there in one of those Requests.Now please guide me how to recover these requests.
Regards
Karthik

Hello Karthik
The easiest way should be to copy the object list of your local request to a new (transportable) workbench request.
However, the system might tell you that your objects can only be put into a local request.
In this case you need to find out why your objects are not (yet) transportable.
Usually there are two reasons for local request:
1.) The request does not have a target system -> check the request header and enter the correct target system (if possible)
2.) Your package has an inappropriate transport layer assigned -> change the transport layer
Regards
Uwe

How to find the transport request which was released to Quality

Hi Friends,
Could anyone please let me know, how to find the transport request that was already released from Development to Quality?
there was some change in customization took place. I could find the user (through change log) who made these changes, however I could not find the transport request number he has already released. I did give his user name in SE10 and checked the released checkbox and did click transports to see them, however I found nothing. A message got displayed on the screen: Cross-system information for user xxx. I can't ask the Basis people about it, as its not yet been trasnported to Productive.
Is this the correct way to see the transport request number? Is there any other way to find the number. I can give the tentative dates when the change was released.
This post might already posted before, I did some search, could not find the exact info what I am looking for. Would appreaciate if anyone could give the step by step method to find it.
Thanks in advance.
BR,
Sats.

Ram,
let me tell you the the situation in a better way.
When I see se10 with my user id I could see all the transport requests that I have released. However, now when I enter my colleague user id who did these changes (he is on vacation, otherwise I could simply ask him the transport number), nothing is shown on the page. in simple words the page is completely blank. Initially I thought it is because of some authorizations, but I can get the transport request numbers that are released by another user.
the info what I have right now are:
1. I knew the user name who did these chages
2. I knew the date when it was changed.
I just need the Transport Request number I mean which starts with DEVXXXXXXX.
As per your solution --> If you have any idea when the reques was relase you can select the request and click on goto-transport logs. This way you can find out the request. --> I knew the date when it was released, but didnt understand, the bold and underlined sentense in your answer.. select on which request? as I said, the page was blank after I enter his user id and activate it.. May be I did not understnd your solution properly. Could you please simplify it.
Thanks a bunch in advance
Sats.

Program to Track the Transport Request

Hi Experts,
I got a requirement to write a program which can track and compare the Transport Request between the servers(Development ,Test and Production) .
If in case is there any descrepancy between the versions (In the server) it should throw an error saying that particular thing is missing or not synchronized.
For ex: If the program which is in Development server has some structure dependent to the code which is address to single TR.
where as same version of the program in Test don't have structure ,it has to throw an mismatch error.
If you guys have any clue on this please throw some light.
Higher points will be rewarded for every useful inputs.
Thanks in Advance,
Dharani

Hi Dharani,
Some sample Code. This I got debugging the SAP Standard.
TYPE-POOLS: strhi.
Data varaints for remote compare
INCLUDE rvscdcom.
INCLUDE rsvcutct.                      "Utilities, Constants, Types
INCLUDE rsvcvcct.                      "General Constants Types
INCLUDE rsvcvdct.                      "VRSD Constants Types
INCLUDE rsvctrct.                      "Tables for transports details
INCLUDE rsvcditd.
INCLUDE ole2incl.
DATA: application TYPE ole2_object.
DATA: remote_info_line LIKE abaptext-line,
      remote_info_line_a LIKE vrsinfolna,
      remote_info_line_b LIKE vrsinfolnb,
      remote_versno     LIKE vrsd-versno,
      remote_objname    LIKE vrsd-objname,
      remote_objtype    LIKE vrsd-objtype,
      remote_system     LIKE tadir-srcsystem,
      returncode        LIKE sy-subrc.
DATA: srcsys            LIKE tadir-srcsystem,
      author            LIKE tadir-author,
      mslang            LIKE tadir-masterlang,
      devcla            LIKE tadir-devclass,
      notfnd            LIKE bool.
INCLUDE rsvceudb.
INCLUDE rsvcvdtd.                      "VRSD Constants Types
INCLUDE rsvctrtd.                      "Tables for transports details
INCLUDE rsvctrfo.                      "Interface for transport details
INCLUDE rsvcrmck.                      "Remote Access Utilities: Checks
    PERFORM get_rfc_destination   USING    srcsys
                                  CHANGING w_destination1.
    SELECT SINGLE objname objtype korrnum FROM vrsd
           INTO CORRESPONDING FIELDS OF it_transports
           WHERE objname = it_abap_hdr-obj_name
          AND   objtype = it_abap_hdr-object
           AND   versno = '00000'.
   it_transports-trkorr = it_transports-korrnum.
Open tranport number with object name
    SELECT SINGLE trkorr pgmid object obj_name FROM e071
           INTO CORRESPONDING FIELDS OF it_transports
          WHERE trkorr   = it_transports-trkorr
          WHERE trkorr   NE 'SW3_P00001'
           WHERE pgmid    EQ it_abap_hdr-pgmid
           AND   object   EQ it_abap_hdr-object
           AND   obj_name EQ it_abap_hdr-name
           AND   lockflag EQ 'X'.
Open tranport number with object name
    SELECT SINGLE as4user as4date FROM e070
           INTO CORRESPONDING FIELDS OF it_transports
           WHERE trkorr   = it_transports-trkorr.
Remote compare
    IF p_rcomp = 'X'.
      CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
        EXPORTING
          text = 'Remote Comparison started'.
      IF w_destination1 NE space.
        PERFORM remote_compare USING w_destination1.
        IF it_transports-korrnum EQ it_transports-trkorr.
          it_abap_hdr-in_qa = 'Same version'.
        ELSEIF it_transports-korrnum IS INITIAL.
          it_abap_hdr-in_qa = 'Not found'.
        ELSE.
          it_abap_hdr-in_qa = 'Not Same version'.
        ENDIF.
        MODIFY it_abap_hdr.
      ENDIF.
FORM get_rfc_destination USING    pi_orgsys
                         CHANGING po_destination.
Baustein zur Auswahl von R/3-Destinationen.
FUNKTION(EN):
ruft einen FB, der den Anwender eine Destination für den
Aufruf der Versionsverwaltung als REMOTE-Function-Call
auswählen läßt.
Parameter:
PI_ORGSYS LIKE TADIR-SRCSYSTEM
PO_DESTINATION LIKE RFCDES-DESTINATION
DATA: dest_note(60).                 " für STRA Baustein
IF pi_orgsys = space.
    po_destination = space.
    dest_note = space.
ELSE.
    IF pi_orgsys <> sy-sysid.
      po_destination = pi_orgsys.
    ENDIF.
    CONCATENATE
      'Note: The original system of the object is the system'(l11)
      pi_orgsys INTO dest_note SEPARATED BY space.
    CONCATENATE dest_note '.' INTO dest_note.
ENDIF.
CALL FUNCTION 'SVRS_GET_RFC_DESTINATION'
    EXPORTING
      p_text         = dest_note
    IMPORTING
      remote_dest    = po_destination
    EXCEPTIONS
      no_destination = 1
      OTHERS         = 2.
IF sy-subrc <> 0.
Falls keine Destination ausgewählt wurde:
    po_destination = space.
ENDIF.
ENDFORM.                    "get_rfc_destination
INCLUDE LSVRLF07                                                   *
FORM get_version_list_remote USING pi_objtype pi_objname
                             CHANGING po_no_entry.
DATA: old_state LIKE bool.
REFRESH: vrs_dir_vrs, logvers_dir.
PERFORM check_vc_state_remote CHANGING old_state.
IF old_state = true.
    PERFORM get_old_fashioned_versdir USING pi_objtype pi_objname
                                      CHANGING po_no_entry.
ELSE.
    CALL FUNCTION 'SVRS_GET_VERSION_DIRECTORY_46'
      EXPORTING
        destination            = dir_destination
        objname                = pi_objname
        objtype                = pi_objtype
      TABLES
        version_list           = vrs_dir_vrs
        lversno_list           = logvers_dir
      EXCEPTIONS
        no_entry               = 1
        system_failure         = 2
        communication_failure_ = 3.
    CASE sy-subrc.
      WHEN 0.
        po_no_entry = false.
      WHEN 1.
        po_no_entry = true.
      WHEN 2.
       'Fehler im Zielsytem'.
       MESSAGE W123.
       LEAVE.
      WHEN 3.
       'Keine Verbindung zum Zielsystem'.
       MESSAGE W124.
       LEAVE.
    ENDCASE.
ENDIF.
ENDFORM.                    "get_version_list_remote
      FORM CHECK_VC_STATE_REMOTE                                    *
FORM check_vc_state_remote CHANGING po_old_state.
DATA: head_entry LIKE vrsd.
PERFORM get_vrsd_entry_remote
          USING head_type head_objname head_versno
          CHANGING head_entry po_old_state.
ENDFORM.                    "check_vc_state_remote
      FORM GET_VRSD_ENTRY_REMOTE                                    *
FORM get_vrsd_entry_remote USING pi_objtype pi_objname pi_versno
                           CHANGING vrsd_entry po_no_entry.
CALL FUNCTION 'GET_VRSD_ENTRY_46'
    EXPORTING
      destination           = dir_destination
      objname               = pi_objname
      objtype               = pi_objtype
      versno                = pi_versno
    IMPORTING
      vrsd_entry            = vrsd_entry
    EXCEPTIONS
      no_entry_found        = 1
      system_failure        = 2
      communication_failure = 3.
CASE sy-subrc.
    WHEN 0.
      po_no_entry = false.
    WHEN 1.
      po_no_entry = true.
    WHEN 2.
     'Fehler im Zielsytem'.
     MESSAGE W123.
     LEAVE.
    WHEN 3.
      'Keine Verbindung zum Zielsystem'.
     MESSAGE W124.
     LEAVE.
ENDCASE.
ENDFORM.                    "get_vrsd_entry_remote
      FORM GET_OLD_FASHIONED_VERSDIR                                *
--> PI_OBJTYPE                                                    *
--> PI_OBJNAME                                                    *
--> PO_NO_ENTRY                                                   *
FORM get_old_fashioned_versdir USING pi_objtype pi_objname
                               CHANGING po_no_entry.
DATA: vrsd_entry LIKE vrsd.
DATA: object_not_found LIKE bool.
PERFORM get_vrsd_entry_remote
          USING pi_objtype pi_objname null_versno
          CHANGING buffer0 po_no_entry.
IF po_no_entry = false.
    CALL FUNCTION 'GET_VERSION_LIST_46'
      EXPORTING
        destination           = dir_destination
        objname               = pi_objname
        objtype               = pi_objtype
      TABLES
        version_list          = vrs_dir_vrs
      EXCEPTIONS
        system_failure        = 1
        communication_failure = 2.
    CASE sy-subrc.
      WHEN 1.
       'Fehler im Zielsytem'.
       MESSAGE W123.
       LEAVE.
      WHEN 2.
       'Keine Verbindung zum Zielsystem'.
       MESSAGE W124.
       LEAVE.
    ENDCASE.
    SORT vrs_dir_vrs DESCENDING BY versno.
    LOOP AT vrs_dir_vrs.
      logvers_dir-versno = vrs_dir_vrs-versno.
      APPEND logvers_dir.
    ENDLOOP.
    READ TABLE vrs_dir_vrs INDEX 1.
    IF vrs_dir_vrs-versmode = impt_mode.
     Es gibt einen offenen Import, setze Flag zurück:
      vrs_dir_vrs-versmode = corr_mode.
    ENDIF.
    vrs_dir_vrs-versno = 0.
    MODIFY vrs_dir_vrs INDEX 1.
ENDIF.
vrsd_entry = buffer0.
PERFORM add_active_version_remote
          CHANGING vrsd_entry object_not_found.
IF object_not_found = false.
    po_no_entry = false.
ENDIF.
Möglicherweise gibt es eine überarbeitete Version.
PERFORM add_modif_version_remote
          CHANGING vrsd_entry object_not_found.
IF object_not_found = false.
    po_no_entry = false.
ENDIF.
ENDFORM.                    "get_old_fashioned_versdir
      FORM ADD_ACTIVE_VERSION_REMOTE                                *
--> VRSD_INFO                                                     *
--> PO_NOT_FOUND                                                  *
FORM add_active_version_remote CHANGING vrsd_info STRUCTURE vrsd
                                        po_not_found.
DATA: object_not_found LIKE vrsd-versmode.
DATA: nplus1           LIKE vrsd-versno.
DATA: retcode          LIKE bool.
CALL FUNCTION 'FIND_OBJECT_40'
    EXPORTING
      destination           = dir_destination
      objname               = vrsd_info-objname
      objtype               = vrsd_info-objtype
    IMPORTING
      object_not_found      = object_not_found
    EXCEPTIONS
      system_failure        = 1
      communication_failure = 2.
CASE sy-subrc.
    WHEN 1.
       'Fehler im Zielsytem'.
     MESSAGE W123.
     LEAVE.
    WHEN 2.
       'Keine Verbindung zum Zielsystem'.
     MESSAGE W124.
     LEAVE.
ENDCASE.                             " SY-SUBRC.
IF object_not_found = space.
    po_not_found = false.
ELSE.
    po_not_found = true.
ENDIF.
CLEAR: vrsd_info-korrnum, vrsd_info-author,
         vrsd_info-datum,   vrsd_info-zeit.
IF po_not_found = false.
    IF vrsd_info-versmode = impt_mode.
    Es gibt einen offenen Import, und einen Satz n+1 der
    uns verschwiegen wurde. Er beschreibt die aktive Version
      nplus1 = vrsd_info-lastversno + 1.
      PERFORM get_vrsd_entry_remote
              USING vrsd_info-objtype vrsd_info-objname nplus1
              CHANGING vrsd_info retcode.
    ELSE.
      PERFORM get_korrinfo_remote CHANGING vrsd_info.
    ENDIF.
    MOVE-CORRESPONDING vrsd_info TO vrs_dir_vrs.
    vrs_dir_vrs-versno    = null_versno.
    logvers_dir-versno    = acti_versno.
    INSERT vrs_dir_vrs INDEX 1.
    INSERT logvers_dir INDEX 1.
ENDIF.
ENDFORM.                    "add_active_version_remote
      FORM ADD_MODIF_VERSION_REMOTE                                 *
FORM add_modif_version_remote CHANGING vrsd_info STRUCTURE vrsd
                                       po_not_found.
DATA: mod_dd_exists LIKE vrsd-versmode.
CALL FUNCTION 'TEST_MOD_DD_40'
    EXPORTING
      destination           = dir_destination
      objname               = vrsd_info-objname
      objtype               = vrsd_info-objtype
    IMPORTING
      mod_dd_exists         = mod_dd_exists
    EXCEPTIONS
      system_failure        = 1
      communication_failure = 2.
CASE sy-subrc.
    WHEN 1.
      'Fehler im Zielsytem'.
     MESSAGE W123.
     LEAVE.
    WHEN 2.
      'Keine Verbindung zum Zielsystem'.
     MESSAGE W124.
     LEAVE.
ENDCASE.
IF mod_dd_exists <> space.
    po_not_found = false.
    PERFORM get_korrinfo_remote CHANGING vrsd_info.
    MOVE-CORRESPONDING vrsd_info TO vrs_dir_vrs.
    vrs_dir_vrs-versno    = modi_versno.
    logvers_dir-versno    = modi_versno.
    INSERT vrs_dir_vrs INDEX 1.
    INSERT logvers_dir INDEX 1.
ELSE.
    po_not_found = true.
ENDIF.
ENDFORM.                    "add_modif_version_remote
      FORM GET_KORRINFO_REMOTE                                      *
FORM get_korrinfo_remote CHANGING vrsd_info STRUCTURE vrsd.
CALL FUNCTION 'GET_KORRNUM_AUTHOR_DATUM_40'
    EXPORTING
      destination           = dir_destination
      objname               = vrsd_info-objname
      objtype               = vrsd_info-objtype
    IMPORTING
      author                = vrsd_info-author
      datum                 = vrsd_info-datum
      korrnum               = vrsd_info-korrnum
      zeit                  = vrsd_info-zeit
    EXCEPTIONS
      system_failure        = 1
      communication_failure = 2.
CASE sy-subrc.
    WHEN 1.
      'Fehler im Zielsytem'.
     MESSAGE W123.
     LEAVE.
    WHEN 2.
      'Keine Verbindung zum Zielsystem'.
     MESSAGE W124.
     LEAVE.
ENDCASE.
IF vrsd_info-korrnum <> space.
    Korrektur ist offen, Zeitstempel korrigieren:
    vrsd_info-datum = sy-datum.
    vrsd_info-zeit = sy-uzeit.
ENDIF.
ENDFORM.                    "get_korrinfo_remote

Import back the transport request to Development Server

Hi All,
I need to import back the Transport request which is in Quality Server to Development Server.
For ex: DEV900764 from Quality to Development Server.
But the same(DEV900764 ) transport request is available in Development also.
How to overwrite the transport request which in Development server ?
I deleted the request in se01, stms in DEV server.
Once i updated the copy of Quality to Development in co-file,data file in OS level. But still it show the old one(DEV copy) while importing thro' stms in development server.
How to solve this ?
actually i need the data of quality transport request

Hi Milan,
Even though you have deleted the request in Development system and later copy the co-file and data file from Quality to Development it will be the same. What is the reason of transporting from Quality to Development.
Normally requests will move from Development to Quality and to production as you already know. Once the request is released from development and transported to next systems that request will have same data in the request what it was at the time it was released and whenever you re-transport that request it will have same changes.
Why you want to do from Quality to development. If you find any differences in the changes of quality and development then some one might have done the chages directly in quailty with client being opened. If it is the same case then you need to take care of the system and avoid any direct changes. If as per my assumption if really there is any difference then make the necessary changes directly in development instead of wanting to transport from Quality.
Transporting from Quality to development is not good practise.....
Regards,
Sharath

To delete the transport request.

when i'm trying to delete the transport request by using se09, it responses with " Request/task BWDK916118 cannot be deleted because it contains locked objects." That request is created by me. It showing same name but it will not allow me to delete. Please help to delete how to delete that request.
Thanks
Satish

Hi..
Basically you are getting this messge because first you have to delete all the objects of the underlying sub requests and then the subrequests ......then finally the actual request.................
Secondly, it is better to unlock all the objects first so that you can delete all the objects at a time..............because if you have to delete all the objects one by one.....and if each requests contains 100s objects then it is very tedious to delete all the objects one by one...
Go to SE03 --> There you will get the options "Unlock Objects (Expert Tool) " --> Click over there --> give the subrequest nos and unlock it....
Then go to SE01 --> Click on "Objects" tab --> You will get the change button --> click on it --> Select All and Delete at a time...
Regards,
Debjani..

How to find the transport request........

Hi,
For particular info object I want to see the transport request
by which it has been locked.
Is there any way to find the transport request by giving the
object name ? (Not by SE10 , where we already knows the trnsport request)
Thanks,
Jeetu

Hi,
I will add one more option.............
In RSA1, goto Transport Connection. There Select your info object, drag and put on right side. Here you can see all the details (Last Changed by, Transport No, Package Name, etc......)
Hope this helps...........
Vivek

Function Module not being displayed in the Transport Request

Hi,
I Created a FM "RH_ACTIVATE_WFOBJECT_AFTER_IMP" in my SAP System. After I created due to problem in editing I have deleted the FM and also deleted it from the request.
I have re created the function module and if I see the object directory entry I find the following
Identical request locks
Request User Task/request Object
**** ***** R3TR FUGR RHWS
In the request I cannot find the function module but only the function group. Please help me to get my function module visible in the transport request.

Hi ,
When your creating the FM for first timw with new FGRP then no need to worry .
You can see only the FGRP in the transport request number and when you move this transport request to further systems your FM automatically transport with the FGRP.
Next time when your creating a new FM under the FGRP which is already moved to production you can see only your FM name under the transport request.
When you go to FGRP main program by follwing the path
FGRP -> Disply FGRP in SE37 you can see the main program of the FGRP there if you see one include with TOP and XX .
double click on the XX Include.
there you can see allthe FM under that FGRP.
Thanks
Naresh

How to Trace all the Transport Requests on a machine ?

Hi,
I am need of a procedure to find out all the transport requests (Workbench or Cusomizing) created on a particular Computer based on its IP address or the Host name ...
Or In other words....
If there are multiple users(>20) using the same Development USER ID and PASSWORD (Say SAPDEV)... How can I track which person has created a particular request based upon the person's PC IP address or Hostname ?
Thanks in Advance...
Regards,
Mohammed Anwar...

Congratulations to tell on a public SAP forum that you don't pay the SAP developpers licenses !
That is very smart and will surely please a lot the SAP Company !

How to delete the entries from the transport request

i need to delete the entries programatically from the transport request for all the entries which is exists in the package for the tables e070 and e071.

Hi,
I think you need to have authorization for that thru auth group SA.
One more thing is where ever its created like source client only you can do if u have authorization.
Regds
Sivaparvathi
Please reward points if helpful...

Changeing the Transport request Attributes?

Similar Messages

Maybe you are looking for