How to compare the transports requests in the same system

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

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

Similar Messages

  • Can give me the details how to release the transport request to the qa

    can give me the details how to release the transport request to the quality server pr production server
    thanks

    Hi,
    Use transaction SE09. Here select "modifiable" .Then click -Display.
    Now you get a list of all requests which can be released.
    Locate your request number and drill down. Release the sub-request first and then the main request by selecting and using the "transport" icon.
    Muraleedharan.R
    091 9880028904

  • How to delete unreleased transport request where the objects are locked

    Hi Experts,
      I was created a transport request, but I am facing some probelms with taht request, now I want to delete transport request. I tried to delete them in SE10, I am getting message that the objects are locked. Please tell me how to delete unreleased transport requests where the objects belong to this transport request are locked.

    Hi,
    First go to transaction se03 Choose "Unlock Objects (Expert Tool)" option under "Requests/Tasks" and unlock your task,
    Than go to se10 and delete what you want.
    I hope it helps.
    Bulent

  • 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

  • Transport request for the deleted dso

    Hi,
    i had deleted the dso in development and not captured the transport request. now how can i generate the transport request for the deleted dso to move for production.
    Regards
    Ram
    Edited by: ramsapconsultant on Mar 9, 2011 7:40 AM

    Hi Ram,
    you can try creating DSO with same name in Dev system. Capture it in transport req.
    Now delete that DSO and capture it in deletion Transport Request.
    I am not 100% sure if this will work but you can give it a try.
    Regards,
    Hardik

  • How to find Particular Transport Request.

    Hi All Experts,
    Can anybody please tell, how to find previous transport request for the scenario like mentioned below.
    If I have created some objects and transported to quality system from dev system.
    Now, i need to do some changes in those objects and retransport those changes, with original object.
    So in the request for changes to existing objects if I need to include the request from which the object was transported before, how can i find that old request.
    Your help will be surely rewarded.
    Regards
    Vinay

    Hi,
    in SE01 you can display your requests.
    Alternatively you can use SE03 / Search for Objects in Requests/Tasks, enter your user ID in the Owner, select relevant status, mark the first empty checkbox in the selection of objects, enter the object type (e.g. IOBJ for infoobjects, CUBE for ICube...) and enter its name in the input box; execute
    this will show all your requests packed with the selected objects...
    hope this helps...
    Olivier.

  • 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 Transport Request?

    Hi all,
       I want to delete the Transoport Request from Production Box( we have 2 request number... one child another one parent). I released the Child Request. Now i want to delete that request. we don't have setup in our production Box i think(in order to release that we don't have setup in Production Box).
    Any Idea? I know how to delete that Transport Request. If i try to release that i'm getting TP(Transport Profile error) <b>with return Code 12</b>. it suppose to handle by Basis. My basis consultant is not aware of how to work on this?
    Regards,
    Nagesh Ganisetti.

    I am not sure I understand.
    You release the request in the system you created, not in another system (in your case production). It will then go to the import queue of the target system.
    Transports will be configured in all the systems in your landscape (including production).
    Just by releasing a request, it will not go to the target (unless it is configured so, not likely if the target is production), someone has to import it into the target. I assume you do not want this request to go to target. In this case, release it, then go to STMS, import queue, and delete it from there.
    Added -
    I now see that the request is in production.
    Igore the above in that case.
    If you are not able to release it, let it be. If you are doing an upgrade/support pack, you will need to release it.
    When you try to delete, what message do you get?
    Message was edited by: Ajay Das

  • How to find out the transport request that a report is locked to?

    Hello Experts,
    I have to transport a report to production system.
    The report has already been assigned to a transport request.
    How do I find as to which transport request is the particular report assigned to.
    Any place where I can check for the locks on a report ?
    Any advice is very much helpful...

    Hello Venkat,
    Thanks for the prompt reply.
    Actually i had tried it. but unfortunately, NO request number is shown. The Only nessage i'm getting is
    " Source systems can not be transported."
    The report is opening in RRMX in change mode.
    This implies 2 things,
    1. The report is already assigned to a transport request. OR
    2. Its assigned to $temp.
    But if the report is stored as $temp, while tranporting in transport connection, it should ask for a transport request and also ask for the development class. Which is not happening
    Any other places to look for ?????

  • How to track the transport request number for the Role/Composit Role

    Hi,
    How to track the transport request number for the Role/Composit Role.
    Thanks,
    Ravi

    Use transaction SE03 Transport Organizer Tools
    Execute "Search for Objects in Requests/Tasks" with objects of types:
    R3TR     ACGR     Role
    R3TR     ACGT     Role - User assignment
    Regards

  • 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.

  • How to include the transport request

    Hi Experts,
    i am asked to create a copy of cube  and asked to  .Include the Transport request in request DEVK9795967
    Please explain how to do it,
    Thanks in Advance
    Nitya

    Hi,
    You can create the copy of Infocube and Include the transport requst. Follow bellow steps;
    1. Goto RSA1> Select Info Area> Select Create the Infocube> Give the Technical/Discreption and Select the Copy of the Cube> Save and Activate.
    2. At acitvation time the system asked the request.
    Select the Own request from Pop Up> Select your created request> Select Continue.
    It wil include the your created request.
    Regards.

  • How to find the Transport request for table entry

    Hi ,
    There was certain entry made in the SAP std table and which got transported to subsequent system. I want to find the Transport Request Number which was containign that table entry and which gor transported.
    Please suggest how can I find that transport number.
    Thanks
    Saurabh

    Hi,
    Yes we can get , Basis team will help.
    B'coz i had same requirement my basis got the TR for me.
    Take their help.
    He said u can like this.
    SE11 - > Table Display - > Table Entry in Menu Bar - > Transport Entries.
    Rhea.

  • How to get the transport request for a particular standard text?

    Hi,
    i want to know, how we get the transport request which associated for standard text.
    Please note already the standard text is assigned to the TR using RSTXTRAN program.
    i have a std text. i want to find the related TR for that!
    rds,
    Siva.

    Refer the link. It might tellsa about attaching to transport request but using the way you can find also -
    Re: How To Transport STANDARD TEXTS??
    Regards,
    Amit
    Reward all helpful replies

  • How could we delete transport request and task(the released one)

    Hello
    We have a released transport task(not request). Transport request is not released.
    How could we delete transport request and task(the released one). Namely we would not like to transport it to production

    Hi, never delete directly in table.
    There are more tables which depends each other...
    Here, you can find nice example how to do it: Help on ABAP: Few Tips for Transport Request Manipulation
    Using program: RDDIT076 and changing status.

Maybe you are looking for