Transport Request Between Server

Dear All,
I did request from One client to Other client in Same Server. Its working fine.
But I don't know, How to transport Request between One server ( QTY ) to Another Server ( DEV ).
Let me know.
Edited by: thomas_raja on May 30, 2011 4:08 PM

DEV --> QAS is a straight way which will be done by your BASIS team.
If you have different requirement than this, also contact them.
Regards,
Nick Loy

Similar Messages

Transport Request Between Server QAS --- DEV

Dear All,
I have 60 Request in mine QAS Server. I set STMS Path to QAS & DEV Server,
After that i do the Remote Client copy from QAS ( 200 Client ) to DEV ( 400 Client ). Its successfully completed.
In QAS ( 200 Client ) - See the All request through SE01.
But I check the DEV ( 400 Client ) through SE01 . It didn't display thel request.
where can i get the Request Numbers in my DEV Server?

Yes correct.
All datas were moved in my DEV server ( 400 Client ). Functional Team members also checked with details.
All company code & datas moved in Properly.
But I want to know What are the Request is there in DEV Server ( 400 Client ) by userwise.
I check with transaction SE01, its only workbench request is there.
So Please advice me

Transport Request - QA Server

Hi,
I couldnt understand why Log files are not created for a Request in QA - Quality server.
In SE09 there are 4 types of Request Types exists - how to know which one to choose while creating a new Request.
I appreciate ur time.
Regards
Krithika

> Hi Sanjay,
> Thanx
> 1)In Dev - Server i can goto SE09 and be able to
> o view the Logs by choosing on the Request no and
> clicking the Transport Logs button , but in QAS it is
> not possible to view Logs for any Request numbers.
<b> see my other response</b>
> 2) say for ex i want to create a transport request
> t - for transporting Variants / Table contents
> ......
> Which request type i should choose - customising /
> workbench/..., will it vary according to the
> transporting object?
Typically you will not go to SE09 to create a request unless you know exactly what you are doing. When you change any object, system will recognize whether it is a transportable object and if so, it will prompt you to create or choose an existing transport request number. System will also know what type of transport request it needs to create. But just for your understanding, you will create a customizing request if your changes are related to tables that are customizing tables(it is an attribute of the table). You will create a workbench request for all those objects that you work on using the workbench tools(including programs, tables, screens, status etc)
Srinivas

Export and Import transport request between different version?

Hi,
I have tried to Export the transport requests from ECC5 to ECC6 via STMS .Its not throughing any error but no Master datas are transported. Anyone have idea about that?

Hello,
From my experience SAP didn't recomneded transporting from 46C -> ECC5.
The structure of tables and objects are a little bit different between different
releases.
Dimitry

How to download transport request to server on a HANA system?

On a non-HANA system I am used to downloading transport requests to the server by following these instructions:
scn.sap.com/docs/DOC-45570
On the HANA system the directories 'cofiles' and 'data' are empty and I have not been able to locate the transport files (K-files) in any other directory.
Also the transactions CG3Y and CG3Z dont exist etc.
Anybody know how to go about this on a HANA system?

Solved by installing a transport route

Download transport requests from server to GUI

Hi All,
Is there any FM or report that could download a released request (or a copy) on GUI.
Any help is appreciated.
KS

Here is a program that I just whipped up. It does pull the files from the application to the presentation, but I don't know if the files are not corrupted. You will have to test them out.
report zrich_0001.
parameters: data type localfile
           default '/usr/sap/trans/data/R903289.TST'.
parameters: co   type localfile
           default '/usr/sap/trans/cofiles/K903289.TST'.
data: begin of idata occurs 0,
      rec type string,
      end of idata.
data: xdata type string.
data: begin of ico occurs 0,
      rec type string,
      end of ico.
data: xco type string.
data: stripped type rlgrap-filename.
data: file_path type rlgrap-filename.
data: fe_path type string.
start-of-selection.
* Download Data Files
open dataset data for input in text mode.
if sy-subrc = 0.
    do.
      read dataset data into xdata.
      if sy-subrc <> 0.
        exit.
      endif.
      idata-rec = xdata.
      append idata.
    enddo.
endif.
call function 'SO_SPLIT_FILE_AND_PATH'
       exporting
            full_name     = data
       importing
            stripped_name = stripped
            file_path     = file_path.
concatenate 'C:' stripped into fe_path.
call function 'GUI_DOWNLOAD'
       exporting
            filename = fe_path
       tables
            data_tab = idata
       exceptions
            others   = 22.
* Download Co Files
open dataset co for input in text mode.
if sy-subrc = 0.
    do.
      read dataset co into xco.
      if sy-subrc <> 0.
        exit.
      endif.
      ico-rec = xco.
      append ico.
    enddo.
endif.
call function 'SO_SPLIT_FILE_AND_PATH'
       exporting
            full_name     = co
       importing
            stripped_name = stripped
            file_path     = file_path.
concatenate 'C:' stripped into fe_path.
call function 'GUI_DOWNLOAD'
       exporting
            filename = fe_path
       tables
            data_tab = ico
       exceptions
            others   = 22.
Regards,
Rich Heilman

Whats the diff between copying a Transport request and Importing a request?

Hi gurus,
Can some one explain me the difference between copying a transport request between clients and importing transport request between clients? say for eg: difference between copying a transport request containing a datasource being copied from client 100 to client 200 and importing the same request from client 100 to client 200?... When do we follow such scenario's?
thanks.
kishore

Hi Kishore,
A request copy applies only for customizing (client dependent) objects.
A request tracks object modifications since its last transport. if the object is created in source system and included in a transport request, when it is transported to another system, it will create the object in target system. Then if you modify the object, it will include modifications since last transport.
As i said, a request copy is only valid for customizing objects. This is entries in tables, you will see that you have two kind of requests, customizing and workbench. Workbench objects are client independent, so request copy doesn't applies.
it's very important to keep the order of requests when you transport and also not to delete requests in any system.
Hope this helps (and hope it is clear, if you have any doubt, just ask!).
Regards,
Diego

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

Change of Source client in transport request

Hi Gurus,
I want to change source client of transport request
Since I want to transport request between clients of same server.
I did it using scc1
But when I want to make any changes to form which was included in that request it is saying
Request/task DEVK***** has invalid source client XXX
I am trying this in YYY client
Please provide solution
Thanks in advance for your efforts

Yogesh,
Does both the clients allow development in the server? Generally it should not be the case.
Does the client still exists in the server?
Here is a thread with replies for such an error message.
Re: regarding Client change for transport request
Check it,it may give you some lead.
K.Kiran.

How to download a transport request?

Hi Seniors,
Is there any facilities in SAP to download a whole transport request from one server to a local file, n then upload it to another server, keeping in mind servers r not interconnected?
thnks
Sameer

Hello Sameer, Bernardo and Diana
On standard R/3 systems I use transaction CG3Y and CG3Z for downloading and uploading the files (cofile and data file) of RELEASED transport requests.
When these transactions are not available I try to use fm EPS_FTP_PUT (or EPS_FTP_GET) to copy the files onto another R/3 system where I can download them as described above.
What is the problem with releasing the requests? Is it the fact that the request is no longer changeable or that it might automatically added to the target system's import queue.
I usually recycle my transport requests between DEV and TEST system. What does this mean? When I do rapid prototyping I may change the same program objects 10, 20, 30 times. I release the request in DEV, import it into TEST and then open the SAME request again in the DEV system. This is done by a simple report which updates E070-TRSTATUS (change from 'R' to 'D').
When I am ready with prototyping then I import the latest export version of the same request into the PROD system. Now I create a new request for follow-ups.
How to avoid the adding to the import queue of the target system I really do not know.
Regards
Uwe

Difference between CTS and Transport request

Hi,
i need to know what is the Difference between CTS and Transport request.
kindly expecting replies

CTS (Change & Transport System)
The CTS is a tool that helps you to organize development projects in the ABAP workbench & in customizing and then transport the changes between the SAP Systems & clients in your system landscape.
This docuentation provides you with an overviewof how to manage changes with the CTS & essential information on setting up your system & client lanscape & deciding on a transport strategy. Read & follow the documentation when planning ur development project.
For practical information on working with the Change & Transport system, see Change & transport Organizer & Transport Management System.
Transport Request
Transport Request is a Request number where the developments are given logical storage number which in turn help in transporting the developments to one system / server to other server.
T.Code SE09 & SE10 are used to Transport the request..
Click the Display button.
The list of Workbench ( Workbench request )Customizing ( Customizing request) are shown.
Reward Points if useful.

How to set at the server level to log transport request in SAP ME

Hi:
when I do configuration in SAP ME, can I set at the system level to log for transport request ?
so I can use transport request for other client or server.

Hi!
There is no "transport request" in SAP ME, however, there is Configuration Data Transfer Export/Import activity which can export the data to ZIP file at the source site and then import that file at the destination site.
CDT activity can utilize CTS+ as a transport channel but I would suggest ZIP file instead because the file can be edited manually in case of any issue or if you want to remove some data.
For details, please consult this How-To Guide.
Regards,
Sergiy

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

Transport request from one server to another

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

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

To revert back a transport request from prd to dev server

hi experts
    how to revert back a transport request from prd server to
    dev server?
    a transport request has been wrongly transported
    and it has make major changes in production server,
   now we want to revert back that request , we know the   request no.
regards
pankaj

All you have to do is create an order of transport type "Transport of copies" in PRO.
I give you the steps to follow:
1. Go to SE01 and create a new order (remember the type "Transport of copies").
2. Enter the data of the order of transport that is going to come back.
3. Enter the target, here is where you asign the target system to carry the request.
4. Now just add the number of request to the new request you just created.
5. Finally released the request from this transaction.
6. Check on the queue of transport in DES, the request must appear there.
I hope you serve =)

Transport Request Between Server

Similar Messages

Maybe you are looking for