Transport Request Tracking

Hi,
Good morning all,
here i hava one requirement regarding transport request .
How to know request target when we released it .
I.e when we released the request , it should be transport either testing , quality or
production . or both .
where should sap maintaining these details .
is there any data base table ? .please help me .
In the table E070 it is maintainig some details .
The table contains only one target details .
if a particular request is transported to more than one server ,
still the table contains only about one server .
where can i get the remaning details .
my requirement is shown below .
requestno   shorttext reldate                 qualit prod
xxxk9008767  abc       27.01.08              Y     Y
xxxk9008768  abd       26.01.08              Y     N
xxxk9008769  fgh       25.01.08               N     N
if the request is transported to quality
i have to show Y  in the quality column
if trasnported to production also then Y in the
prod column .
but in the tabel E070-TARSYSTEM contains only one
target details .
i have checked for so many requests .
in the table E070 it is not showing the requests
are transported to both servers .
but in SE09 transaction it showing as
the particular request is successfully transported to
both systems .
please help me ,
Thanks in advance .
regards ,
Srinvias

Hi Srinivas,
Am not a 100% sure however how I think it works is
When you view the transport details in Development server in E070, the  E070-TARSYSTEM  for the request will point to QA server.
Then when the request is transported to QA, the same transport entry in E070 would be updated with  E070-TARSYSTEM  as Production server.
Can you check this and confirm.
Cheers.

Similar Messages

  • Transport Requests Tracking

    Dear Gurus,
    When I copy PRD to DEV this process is overwriting the transport request history.
    Is there any way I can prevent this from being overwritten?
    Any help is appreeciated.
    Regards,
    Rachel

    Hi Rachel,
    Is not a good practice to copy production into development. By doing that you won't only overwrite TMS but also version management.
    Can you describe your scenario?
    Regards
    Juan

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

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

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

  • 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 track Transport request released

    hi Experts,
    How to track Transport request released from one development system (D01)to another
    development (D02).
    is there any way we get know .
    Amit

    Hi,
           From SE09 & SE10 you track the transport requests, and even you can find the transport request details from the following database tables.
    E070                             Change & Transport System: Header of Requests/Tasks
    E070A                            Change & Transport System: Attributes of a Request
    E070CREATE                       Change & Transport System: Creation Date of Request
    E070DEP                          Change & Transport System: Dependencies of Requests
    E071                             Change & Transport System: Object Entries of Requests/Tasks
    E071C                            Change & Transport System: Client-Specific Lock Flag
    E071E                            Lang. Transport: Positive List for Generic Object Selection
    E071K                            Change & Transport System: Key Entries of Requests/Tasks
    E071KC                           Change & Transport System: Key Entries of Requests/Tasks
    E071KF                           Change & Transport System: Nametab Info. on (CHAR)Key Fields
    E071KFINI                        Change & Transport System: Nametab Info. on (CHAR)Key Fields
    E071K_30                         Change & Transport System: Key Entries of Requests/Tasks
    E07T                             Change & Transport System: Short Texts for Requests/Tasks

  • Tracking of transport request

    Hi all,
    I need to know whether there is any table wherein i can see whether the particular transport request has been successfully transported to the quality or not...
    Or any RFC's for the same..
    Please let me know...thanks for your help in advance.
    Regards,
    Rohan.

    Take a look at FM [TR_READ_GLOBAL_INFO_OF_REQUEST|http://forums.sdn.sap.com/search.jspa?threadID=&q=TR_READ_GLOBAL_INFO_OF_REQUEST&objID=c42&dateRange=all&numResults=30&rankBy=10001]
    Little sample (may help)
        CALL FUNCTION 'TR_READ_GLOBAL_INFO_OF_REQUEST'
             EXPORTING
                  iv_trkorr = p_record-trkorr
             IMPORTING
                  es_cofile = es_cofile.
        LOOP AT es_cofile-systems INTO system.
          LOOP AT system-steps INTO step.
            " Here system-rc has the result code
            LOOP AT step-actions INTO action.
            ENDLOOP.
          ENDLOOP.
        ENDLOOP.
    Regards,
    Raymond

  • Log for Addition/Deletion of object in a Transport Request

    Dear Friends,
    Recently I had a issue where I tried deleting an object from a transport request and I got the message that object is deleted successfully.
    But when the transport was imported then it failed with Sy-subrc 8 because of the same object in transport.  The reason for the same could be :
    1.) Either the object was not deleted from the transport request.
    2.) Or Some one else added the same object again in the request.
    I want to read the log of this transport in such a way that I see when a object has been added/deleted from a transport request along with SAP User ID of the person doing it.
    Is this possible ? If so kindly share the steps with me.
    Thanks a Lot for your kind help!!! This is very important for me....
    Regards,
    Lalit

    Hello Lalit
    I hope nothing of that sort is available as the transport requests will again have tasks under them.
    The changes done to  the task will have to be tracked in that case but SAP doesn't have that task change logging as far as I know.
    All E0* tables relates to transports and objects under these transports none of them have logs on this nor even any transactions which allow user to edit the transport object.
    You get an action log which provides who created it and who releaed them.
    But if you configure CharM on Solution manager I hope you can track each changes.
    Regards
    Vivek

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

  • Create transport request based on SDMI transaction type

    Hello,
    a customer of mine intends to use transaction type SDMI in a kind of unusual way. He only creates SDMIs without creating projects, cycles or change requests in ChaRM. He uses a customized copy of the normal correction to track his changes and now needs to activate the functionality to create transport requests as an auditor requirement.
    As I'm not proficient in ChaRM, I would like to know if that is at all possible.
    Assuming it is possible, what would be the preferences to use action "Create Transport Request" regarding IBase etc.?
    Assuming it is not possible, what would be necessary as a minimum to establish the link to the respective system in which the transport request should be created to get that action working, a maintenance cycle? How is the maintenance cycle linked to the ticket?
    That are a lot of questions, and it would be highly appreciated if somebody could lighten up the fog there for me.
    Thank you in advance!
    Kind regards,
    Emanuel

    Hi,
    1) Do I need to perform any steps in the task list before ChaRM can be used?
    No once task list is in active state and sdmn is created for ur project u can start using charms
    2) How is the maintenance cycle ticket (SDMN) linked to the change requests? Is this linkage done in the SDCR ticket via the maintenance project in the "Customer fields", where solution, maintenance project etc. can be assigned? Or is this implicitly done by the chosen IBase?
    Yes everything is dependent on IBASE and logical component.
    Check this links
    https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
    Check SMP/SDN
    https://websmp208.sap-ag.de/changecontrol
    Resources on CTS+ [original link is broken]
    Hope it solves ur queries
    Regards
    Prakhar

  • 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

  • Package objects and transport request

    Hi Gurus,
    How to find out the transport request which are generated by an object created?
    I have a package(ex:xyz) which has got an object (abc).Now i need to find the transport request which are related to this object abc?
    Please tell me the procdure or the Tcode to out the same.
    Regards,
    Prasad

    hi,
    SE09 is the transaction code for workbench organiser.Workbench organiser is the set of utilities for development change management.All Development changes are tracked via Workbench organiser.
    SE10 is for Customosing organiser.Customising organiser is the set of tools for customising change management.All customizing changes are tracked via customising organiser.
    thnks,
    raji.

  • How to reverse Transport requests from sand box to development client

    Dear all,
    I am doing some testing on Sand box, I made some transport requests from development to sandbox, which effected some settings in sandbox.
    Now I want to reverse those transport request from sand box to development, unfortunately I didn't make any note of transport requests which I transported from Development to Sandbox.
    Please educate me how to reverse transport requests from sand box to development.
    your suggestions are highly appreciated
    thank you
    Venu Gopal

    There is no reverse, you have to create a new transport with the original settings.
    Programs keep track of their versions and are easier to pull a previous version, configuration can be tougher, open all the folders in SE10 to see if you can determine the configuration changes.

  • 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

  • Transport request for function group

    Hi All,
            I have developed a function module in a function group say 'zdeep'.  I have moved the transport request for newly developed function module to production. But there Iam unable to run the function module. 
    Should we transport the function group also to production?
    If so, how can we get the transport request number for the function group?
    I have tried in se80. but there iam not able to track the request no for the function group.
    please help me
    regards
    Murali Krishna .T

    yes i think if u r doing any chnages in func group then it also has to be moved to Reflect chnages..also some proper order is to be maintained while moving TR
    http://wiki.sdn.sap.com/wiki/display/Snippets/Atoolrelatedtotrackingoftransport+request
    check this link
    Edited by: npathak on Aug 14, 2010 8:47 AM

  • 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

Maybe you are looking for

  • BADI for storage location restriction in IW32

    Dear All, I am working on one scenario in this user has to get the error message :- 1. Whenever he doesn't enter the Storage Location in Component Tab (in IW32) and also he should not be able to save the Maintenance Order. 2. There is ZTABLE (ZTPM058

  • DVD's no longer play in 10.4.11

    Both older and newer studio movies no longer play on my MacBook Pro after the last software update and can't figure out why. Thx for any tips.

  • WIFI cannot connect with TouchPad

    I just purchased a new HP TouchPad.  I am trying to connect to my WIFI.  Without security, the TouchPad connects just fine.   When I enable security on the wireless router, the TouchPad shows the watches cheap network is locked, or secured.  When I t

  • Can't transfer videos to itunes??

    hey all i just wanted to know if there was a way (if its legal) to transfer videos to itunes that you didnt buy off itunes...like i have dvds of some of my fav movies that i would like to put on my touch without having to buy them in itunes...is ther

  • Where are the toolbar icons located on a mac

    I want to find out where the toolbar icons are found in the OSX. The ones that  I am refereing to are those found in finder windows at the top, that show things like the quickview icon etc. I want to be able to make my own for scripts that I want to