Missing transport requests

Hi Sap-experts!
in our system is a gap btw. transport request XZ1K900500 and XZ1K904000!
the requests seem to be deleted or number range was manipulated!
where can I find these missing records  ?
there's no track in table E070/1...
greetings
Andreras

ok Joe,
I've checked change documents to se16n - nothing
and analysed several tables in the same package as e070 - but find nothing!
here are some records  (with the gaps) from e070
TRKORR          AS4DATE
XZ1K900021      2010/01/12
XZ1K900022      2009/09/07
XZ1K900023      2009/07/21
XZ1K900024      2009/07/28
XZ1K928326      2010/01/20
XZ1K928332      2010/01/20
XZ1K928333      2010/01/20
XZ1K935163      2009/07/29
XZ1K935164      2010/01/05
XZ1K935165      2010/01/05
I don't understand the  interplay of the as4date??
it remains dubious.
thanks again all and have a nice weekend!
Andreas from germany
Edited by: Andreas Mann on Mar 26, 2010 3:09 PM

Similar Messages

  • Re: Transport Request Missing Very Urgent

    Hi Peers,
    One of my transport request is missing. I had configured in Dev client and the same configuration has been transported to Sandbox, because of Abap programs.
    All the configuration which is there in Dev has been copied to Sandbox & I am able to see all my config.
    Now in Testing also all my requests has been copied from Dev. But One particular request is missing and I dont remember the request name & number.
    I have checked in SE10 also but No Luck not found my request.
    Kindly requesting all of you to immediately give your valuable inputs.
    Regards
    Pavani

    Hi Ruchit,
    Thanks for the immediate response.
    I had gone to SE03 but not able to find out PGMID & Object type & name????
    I am a functional consultant so does not know about these terminology, can you tell me in detail vt needs to be done? My only worry is I had created some 1200 positions in that particular request. If I did not find out again I have to redo the same.
    Can you please kindly help me out what needs to be done?????????
    Regards
    Pavani

  • Transport Request number missing after Remote client copy

    Hi,
       I have done a remote client copy with SAP_ALL .but after completing client copy i can find transport request numbers are not showing (SE10,SE09) for all the functional consultants. Plese help me to solve this issue, suggest me any solution
    Thanks
    Jyothish

    >    I have done a remote client copy with SAP_ALL .but after completing client copy i can find transport request numbers are not showing (SE10,SE09) for all the functional consultants. Plese help me to solve this issue, suggest me any solution
    If you did client specific customzing in those they are of course not found.
    Markus

  • Datafile missing for a Transport Request

    Dear Sir,
    We created a Transport Request directly in our Quality Server and subsequently using SE10 we released the Transport Request also .   However we find that there is no Data File & CoFile are found on the Quality Server for this request .
    Due to this , we can not import the request in our production server also .
    Kindly help us pl .
    Rgds
    Sonia Agarwala

    Hello,
    First check the type of your transport request, probably it will be a "local transport" request.
    Local transport requests do not generate data and cofiles when they are released.
    Probably your current TMS setup does not allow you to release transports from the QA system.
    What you can always do is creating a transport of type : "Transport of copies" and manually add your objects you want to transport.
    Do not forget to fill in the "target" field in your transport, otherwise when you release it it will be again a local transport without data and cofile.
    [https://service.sap.com/sap/support/notes/28967|https://service.sap.com/sap/support/notes/28967]
    [Local Transport|Local Transport]
    I hope this can help you further.
    Best wishes.
    Wim Van den Wyngaert

  • Error while assigning objects to Transport Request

    Hi All,
    while  assigning a Transfromation to a Treq i am getting an error saying
    Object '7KU37C7IG3T7AQ5NHSLEZVC91' (ROUT) of type 'Routine' is not available in version 'A'
    Message no. RSO252
    Diagnosis
    You wanted to generate an object with the name '7KU37C7IG3T7AQ5NHSLEZVC91' (in transport request ROUT) of type 'Routine' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
    System Response
    The object was not taken into account in the next stage of processing.
    Kindly advice how to rectify this error

    Hi,
    You see the which infoobejct contains that routine and first collect that infoobejct and transport it then transport Transfromation. I hope you are missing some Routines while collecting the Transformations into request.
    See OSS Notes:
    Note 613581 - Transfer structure does not exist in version 'D'
    Note 508921 - P11:Content transfer:RSO 252 or RSO 296:InfoObject
    Note 1157873 - BI7.0(SP18) Message RSO 252 using transport connection
    Thanks
    Reddy

  • How to fill a transport request from SPRO

    How could I repeat transport of customizing already done and transported. I have feeling something is missing but I do not know exactly what.
    I know how to enter in a transport request content of tables(also customizing) but I am not sure this is the right way.
    I think it is possible from SPRO fill a transport request BUT HOW(without option u201Cautomatic  recordingu2026u201D in client setting u201Cscc4u201D transaction , as with this option I have to change customizing and change it back)
    Thx in advance

    You could
    - Merge the previous transport requests into a new one
    - Most of the Customizing transaction have an option to transport (e.g.: menu : Table view / transport)
    Regards

  • Transport Requests

    Hello Experts,
    I am facing couple of issues in transporting the requests from Dev to QA environment.
    Firstly when trying to replicate DS in QA, DS is replicated but it is in MOdified status (and Cannot activate because QA system is non modifiable status) . I just right click on the appln component & then replicated metadata .  Is ther any step I'm missing or can be taken so that DS can be activated ?
    Secondly when trying to move transport request for transformation between InfoSource & DS getting this error message "Message no. R7501"
    "Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)"
    Also along with this message also getting message :-
    Source RSDS ZQMNOTIFICATION_STATUS2 SD2CLNTXXX does not exist
    Above mentioned source SD2CLNTXXX is dev DS and transport req is only for transformation .
    I'm not able to understand why transformation req b/w IS & DS is including source system name.
    Please advice if anybody has faced this situation.
    Thanks,
    Murtuza.

    Firstly when trying to replicate DS in QA, DS is replicated but it is in MOdified status (and Cannot activate because QA system is non modifiable status) .
    I guess, this is due to different versions of support packs in DEV & QA.
    After replication of Datasource, now u have to transport the same datasource from BI Dev to BI QA. So, that it should overwrite the replicated one.
    Secondly when trying to move transport request for transformation between InfoSource & DS getting this error message "Message no. R7501"
    "Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)"
    Also along with this message also getting message :-
    Source RSDS ZQMNOTIFICATION_STATUS2 SD2CLNTXXX does not exist
    Above mentioned source SD2CLNTXXX is dev DS and transport req is only for transformation .
    I'm not able to understand why transformation req b/w IS & DS is including source system name.
    Since the datasource is not actively present in QA, thats why transportion of transformation throwing errors. to transport Transformation, Datasource & InfoSource must present in QA
    Now, in BI Dev u should collect Datasource, Infosource, transformation and transport them to QA.

  • Not able to import transport request in A66

    Hi Expert,
    I have done an amendment via t.code OBR3 in N66 so created a transport request. I went to SE01 to release the transport request and I saw the status is released and the is a warning message "Import steps not specific to transport request". I logged on to A66 and go to STMS_IMPORT but I could not find my transport request to import it into A66. Did I missed out anything? Have I done anything wrong?
    Kindly advise.. thanks

    hi
    sometime it happens recreate the transport request and try to re-import it may work.

  • Can't able to release transport request which has process chain information

    Hi Experts,
    Can any one come accross the similar issue? . If so I am eager to know the fix for it.
    I have collected my process chain in a transport request and when I am trying to release the same for import to another system, I get the following error message.
    Error Message: some object (start varient for process chain and DTP process) is missing in the transport request.
    BUT THE MENTIONED OBJECT IS COLLECTED AND I CAN SEE UNDER MY REQUEST.
    But still i get the error message. Not sure where the problem is.
    Hope there might be some solution to resolve the issue.
    Thanks and Regards,
    Saravanan.

    Hi All,
    I have tried all the options which you all suggested, but still i face the same issue.
    I tried collecting it through transport connection through RSA1.
    Right click on request/task.
    Please let me know any other solution to resolve.
    Are there any check will be happened at database or somewhere else when collecting  the transport?
    Thanks and Regards,
    Saravanan.

  • Problem in tables of transport request !!!!

    Hi all,
    When i doing the Charm Process....nd during that when the developer generates the transport request....at that time that tp request appears in table /tmwflow/trordhc but it does not appear in /tmwflow/track .... nd after releasing the subtasks and then finally the whole transport request....at that point also it does not appear in /tmwflow/track ..... after this when the basis person pass that transport request to quality....then the /tmwflow/track shows 1 record for that transport request.....so finally after the whole flow /tmwflow/track will show 2 records for that transport request i.e 1 of quality and 1 of production....logically 'dev' record should also be there.....what i am noticing is after few hours like 2 or 3 hours that development record started appearing in table /tmwflow/track .... so is it a problem in configuration of solution manager or this sudden appearance of dev record is ok....coz ive to build a report in which it displays the tracking of tp requests....
    Any suggestions would be helpful...
    Regards,
    Deadlocks

    Hey deadlocks,
    many ChaRM tables are updated as Fernando said when cmssyscol job finished.
    I guess those 2/3 hours correspond to the time u waited before the job runned. The transaction solar_eval and a couple of others allow u updating data as well.
    U have to know that this job may sometimes/quite often give unsupected/missing data; and also delayed. The best you can do is simply read the tr log using a function modul and interpretate info concerning the transport requests
        CALL FUNCTION 'TRINT_TDR_USER_COMMAND'
          EXPORTING
            iv_object  = lv_object
            iv_type    = ls_sel_node-type
            iv_command = lv_command
          IMPORTING
            ev_exit    = pv_exit.
    LV_OBJECT                                             SLMK900004
    LS_SEL_NODE-TYPE                                     REQU
    LV_COMMAND                                             TAST
    for example.
    You can debug log reading in SE01 and put a watchpoint on instruction 'CALL FUNCTION'. It is the second one.
    This will display log on screen
    Good luck
    Khalil

  • Import and Export transport requests on Netweaver 2004s Sp11 Sneak Preview

    Hi Experts,
    I have configured the transportation system <STMS> in order to import and export transport requests on the NSP system. The configuration is working properly as files can be imported and exported out of the C:\sapmnt\trans directory. (configuration distributed by STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration, Folder SAPMNT shared).
    The problem I'm facing with the import of some example transports is given by the hanging import queues. In phase 'Import ABAP Dictionary Objects' I have the following message for almost all objects -> '... was not imported in this step'.
    I tried to solve this issue by running SE38->RDDNEWPP with DDIC user to schedule job RDDIMPDP for TP imports. I also made the config in TP_DOMAIN_NSP.PFL with SYSTEM_PF = C:\SAP\NSP\SYS\profile\DEFAULT.PFL.
    The error is still in logfile SLOG0732.NSP
    ERROR:       The following call returned with exit code 7:
    ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=NSP
    and logfile dev_evt
    ERROR ***: MsSndTypeOnce, rc = -20
    ERROR ***: Event raise failed
    With the exports there is a similar issue in the EXPORT phase, given the note
    0 entries from WDY_APPLICATIONT exported.
    Batch process is available (parameter rdisp/wp_no_btc = 1)
    Profile has been activated by rz10->utilities->import profile->ofactive servers.
    Any ideas what still can be wrong? Does the import export and DDIC activation really work with the sneak preview?
    Thanks
    Christoph

    Hi Peter
    First of all thanks for your advice.
    I did No. 1. 2. 3. steps.
    Step 4. reacts with the folowing error message.
    Transport control program tp ended with error code 02008.
    Errors: error in transportprofile (param missing, unknown).
    My  license expires in four days. I tried to extend it via http://www.sap.com/minisap
    1. System-ID *   
    2. Hardware-Schlüssel (HWID) *   ?
    3.Systemnummer  ?
    What is to be entered in 1 and 2.
    Where should I look for HWID and Sysnr ?
    Thanks a lot again for your help
    With regards
    Fisseha

  • Query Transport Request

    HI,
    I have created transport request for Bex Query. First time I created transport request , I collected all query and query elements apart from this two more additional components added to transport request ( No transport request open on that
    query, Only display mode. I have created TP request for change mode)
    "BW: LOIO Class Metadata and BW: PHIO Class Metadata ."
    Next time i have tried with all grouping options in transport request, I have not seen
    "BW: LOIO Class Metadata and BW: PHIO Class Metadata .".
    anybody has idea why these "BW: LOIO Class Metadata and BW: PHIO Class Metadata ." components added transport request.
    Please let me know if you have nay idea on this one.

    Hi,
    - Check in SE09/se10 for creating requests.
    For collecting objects you have go Transport connection without missing the objects.
    SE03 for checking the Request objects.
    Go to transport connection in RSA1 Select u r Data target or report what ever it may be in development sys & select only necessary objectsu2026 click on transport optionu2026u2026it will ask the transport request create new req. go to SE-9 release the objectu2026go to STMS import u2026RELEASE The objects in quality sysu2026same procedure to production sys.
    Thanks
    sudhakar.

  • R/3 Transport requests

    HI,
      i raised a transport request for install & activate data source in R/3.I released the request in development system,But it is not showing in the transport queue
    stms_import
    What am i missing.....what is the tcode for transport queue.
    Thanks

    there is a possibility if there is filter in the list you see in stms_import transaction.click on the filter icon and view if there is any userid specifically given..
    But there shouldnt be any problem in transport if it is in se09..ask your basis to import to QA..and check if they have the transport path setup form dev to QA properly then it should not be problem in transport..

  • 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

  • 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

Maybe you are looking for