The transport request are pending in the import quene

Hi the transport request are released from the development system and are showing pending in the production system

Hi Shri,
According to your query you have only two system landscape. If this is true then before import transport to prd from dev to import in send box which is test client. If everything is ok then you can import this transport in prd server with stms tcode.
If you have any doubt pls mentioned here in details.
Regards,
Anil

Similar Messages

  • The transport request is running all the time, what is the problem

    I have a transport request which can transport from DEV to QAS successfully ,but failed when the request transport to PRD, I found the request running for several hours.   I do not know what the problem?    how can I check this problem?
    need your help                            thanks

    Hi
    The background job Rddimpdp is not scheduled in the system for client 000...And you want to investigate what happend to the job..
    The background job details are kept in table TBTCO..So if you goto SE16 and try to choose the fields which are of your interest..as it(this table)  has lot of fields. And in this we have fields like last run time,scheduled by,last job change time etc.So with the above information i hope you will be able to get the information you want.
    And if everything is fine ..the backgrouns job alone can vanish someone manually might have done done something ..and that can be found out by above investigation on the table.
    Hope this info helps...
    Regards
    Vani

  • 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

  • Re-transport the transport request in Quality 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

    No cross posting
    Read the "Rules of Engagement"
    Regards
    Juan

  • What does the return code 20 stands for in the Transport request log

    Hi,
    When we have retreived the Transport request log by using the Unix command, we have got return code 20.
    Please let us know what does the return code 20 stands for and under what scenerios I will get the return code 20.
    Thanks & Regards,
    Madhuri.

    chk the last return code in this link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/57/38e26c4eb711d182bf0000e829fbfe/content.htm

  • How delete the Transport request in Development system

    Hi Guys,
    I have created one Transport request and released (not moved to other system), now I don't want that request to transport to other systems.
    I need to delete the Transport request, could you please suggest how to delete the Transport request.
    Please provide the steps to delete the Transport request.
    Thanks,
    Gourisankar.

    hi Gaurishanker
    check this thread
    How to delete transport request if child request was released
    hope it helps you.
    thanks
    Sachin

  • To check the user who imported the Transport request.

    Hi,
    Can we know who imported the transport request. We are able to see the owner of the request . Is there any place where we can see the User who had imported the transport request.
    Thanks,
    Tanuj

    Hi,
    1. Goto to transaction STMS_IMPORT
    2. Menu, Goto--> Import History
    3. Menu, Edit-->Display More
    A column Name User will appear, giving user who carried the import.
    Award points if you like.
    Thanks
    Imtiaz

  • How to get the details of Transports which are yet to be imported

    Hi Experts,
    Kindly let me know how to get the Transport request details which were not yet imported.
    For example:
    We have two client in development system 300 and 400, The transports which are created in 300 and imported to 400 (in SCC1).
    I need to know the details of transport requests related to 300 which are yet be to moved to 400.
    Where can i get these details.
    Thanks,
    Narasimhan Krishna

    Narasimhan,
    Take a closer look at Yves KERVADEC's approach. The issue here is that typically SCC1 is used to move transports which have not yet been closed.  You can see the details of any transport via se01/se09/se10, whether open or closed, but my interpretation of your question is that the customer wants to know which transports have been imported into the unit test client (400) via SCC1, which transports have been brought in by the transport system (after they were closed), and which transports have not yet been sent to either the unit test or QA system (i.e. are still open).
    My guess is that you are trying to track down why things work in the unit test client and not in the QA client. That is actually a different question with a different approach, but if that's what you really want to answer, go ahead and ask that question in a separate thread and you'll get a ton of techniques.
    Back to the question you actually asked: By writing a query, you can get a list of transports which have been brought in to the unit test client via SCC1. You can also get this information from SCC1 --> Goto --> Log Display. Then click All Transport Requests and doubleclick on the client. This will give you the import log of your unit test client with date/time stamp. Analysis of that data indicates to me that perhaps you may want to look at CC0_RSCCPROT03_ALV, but I'm not an ABAPer so the previously mentioned tables are probably better.
    Anyway, once you have a list of transports which have been imported, you can subtract out the ones that have been closed and transported downstream (and back into the unit test client.. your transport path does re-import the final version of the transports into the unit test client... right?). You can get that information from another query or you can get the list from STMS as suggested by Aparajit Banik.Then you'll have a list of transports which have been imported into the unit test client via SCC1 but have not yet been released and made it downstream. This will give you a "hit list" of transports which might be causing a mismatch between your unit test and QAS clients. You would then inspect them more closely with SE09/SE10/SE01 (I prefer se01, but different folks prefer different version of the transaction).
    Again, there are better ways to deal with client mismatches, but I'm answering the question you asked in case I misunderstood the underlying subtext.
    I hope this helps!
    Best regards,
    --Tom

  • 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

  • The dependent requests are in different transport orders

    Hi,
    When i save a particular query, and then try to reopen it, i get an error saying "The dependent requests are in different transport orders".
    Because of this error, my query becomes uneditable.
    Could anyone help me out with this??
    Thanks.

    The best way to transport the query is to go to RSA1->Transport connection and collect all dependent objects like formula variables..calculated key figures..etc in the same transport.

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

  • How to send the transport request from one client to other client?

    Hello Friends,
    I have generated one transport request in one of the client in Development server.Now as it is  customizing request so unless and until i transport it to other client within the same server, Changes will not be visible in other clients.So how to transport this customizing request from one client to other client within the same server.
    Thanking you guys in advance.
    Regards,
    Jitendra

    Hi Jitendra,
    Release your Transport Request via SE10, then go to STMS & import the request first to your quality server, then to your production server.
    Apologies for the incorrect inputs, please use SCC1 as advised by other forum members
    Hope the above clarifies your query.
    Regards,
    Vivek
    Edited by: Vivek on Mar 16, 2009 1:05 PM

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

Maybe you are looking for