Transports backup during system refresh

I have a requirement to take the backup of transports from QA system which are not yet imported into PRD as QA is getting refreshed.  After refresh, I would like to add these transports into queue and import them in sequence.
Now I can get the list of transports not imported into PRD from "transports waiting to be imported" from PRD system.  But I am unable to get in which sequence should these be imported into QA.  Last time I did but it went in the wrong order and programs got overwritten in QA as I tried to do it by the time/date sequence.
I wish to know if anyone following the better procedure to take the transports backup in QA during the refresh process.

Hi Sameer,
2 things: Either these TRws are being imported for the first time, OR, you are concerned about the repeat import.
1.
Usually, the order of import is the same as order of release of the TR from development. However, there may be exceptions in some cases.
But why are you being worried about the order of the transports? The developers should have a look at the list and tell you the order in which they are to be imported. See, only they would know which request contains which versions of the objects and only they can tell you what goes in and in what order.
Being from Basis (I hope you are from basis only) you have no way of knowing the correct sequence in such a case. Basis never decides order of TRs.
2.
But, if you mean these were imported once in Q but after refresh you want the same order, then you should have gone to the transport history for the system in STMS and from there, you should have seen and saved the order of the original imports.
Regards,
Shitij

Similar Messages

  • How to save SM59 RFC entries during system refreshes

    Hello,
    I will be refreshing our NW04 ERP and SRM QA systems.   Our platform is Oracle/Unix.
    My question is how to export the SM59 RFC entries before the refresh, so I can reimport them after the refresh.   I have done this successfully in R/3 4.6c, but cannot get it to work in NW04.
    During the last refresh, I manually created transports and added the three standard objects, but after reimporting the transport in the newly refreshed system, I found that the RFC's were not restored.
    Any help would be greatly appreciated!
    Thank You,
    Joyce

    Hello Joyce,
    I've created an RFC destination in a NW04 system while making a SQL trace.
    It did
    a DELETE in table RSECACTB
    an UPDATE in table RFCDES
    an UPDATE in table RSECTAB
    an INSERT in table RFCDES
    an UPDATE in table ATAB
    an INSERT in table RFCATTRIB
    a  DELETE in RSECTAB
    an INSERT in RSECTAB
    an INSERT in RSESCACTB
    an INSERT in ATAB
    I think that the data model is much more complicated in NW04 than in R/3 4.6 and creating manually a transport is a challenge that I would not try !
    Regards,
    Olivier

  • Changing OPS$ passwd during system refresh

    Hi All,
    i have to do system Refresh/system copy ,i m using oracle 10g database.
    while studying the docs and sap notes,i found that after database is backed from source system and restored in target system
    .It is also required to change some passwords for OPS$ or SAP<Schema> user in table "sapuser" at OS level.
    I am totally unaware of any such activity.can someone help me in this regard,as what are the post steps after DB is restored in target system and to how to perform them.
    We are using brtools here.
    Also what is the command line for restroring DB while system copy.
    Regards,
    Vishesh S

    *Hi,*
    *1.*
    *can someone help me in this regard,as what are the post steps after DB is restored in target system and to how to perform them.*
    After doing DB restore, one has to
    a. Apply the Control files of source system database
    b. Perform DB recovery by applying available offline redo log files (based on Complete DB recovery or Point-in-time DB recovery).
    c. Then after successful DB recovery, one has to OPEN the database with RESETLOGS options.
    d. Upon successful Database instance startup, Start Target SAP system
    *2.*
    *what is the command line for restroring DB while system copy.*
    brrestore -b logfilename -m full
    e.g. brrestore -b bcnmhluz.aft -m full
    *3.*
    a) Logon using the OPS$ user ("connect /@<sid>") to determine the
    sapr3 password that is stored in the database table SAPUSER.
    Now i have no idea,that how to check the password,as i logged in using "connect /",it just got connected.
    But how will i know that what password has been set.
    In OPS$ connection mechanism, only the existence of ops$<sid>adm user requires. Under <sid>adm OS user if you execute "connect /" in SQLPLUS, then it will get connected with Database through ops$<sid>adm database user, without asking for password.
    During OPS$ connection mechanism, the SAP work processes get connected to Database using this OPS$ user. Then as a next step,  the password of Schema user (SAPSR3 or SAP<SID>) is read from the SAPUSER table from database, and then with that password od schema owner , the R/3 work processes actually get connected with Database Instance schema. So the SAPSR3 password should be same at Oracle DDIC and SAPUSER table levels.
    If you do not know the password of SAPSR3 or SAP<SID> database users, you can change them with br*tools or by the execution of the following brconnect command.
    brconnect -f chpass -o [sapr3 | sap<sid> | sap<xyz> | sapsr3] -p <new_password>
    (Refer SAP Notes 562863, 361641 as reference)
    *4.*
    *after doing a system copy/refresh, what changes i have to perform in OPS$ user.*
    If your getting with OPS$ user issue while SAP startup or R3trans -d execution, then you can refer SAP note 40024 or do the following .
    a.
    Check weather the correct OPS$<SID>ADM user exists at DB level or not ?
    SELECT * FROM DBA_USERS;
    b. If the required OPS$ user does not exist in Target DB....
    CREATE USER "OPS$<SID>ADM" DEFAULT TABLESPACE <user_tsp>  TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;
    c. Grant roles/previleges to OPS$ user
    grant sapdba to ops$<SID>ADM;
    d. check the existence of SAPUSER table and the owner of SAPUSER table in target DB
    SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'SAPUSER';
    e. If the owner of SAPUSER table is not OPS$<SID>ADM, then u need to drop it and recreate it in Database.
    -- DROP TABLE "<owner>".SAPUSER;
    -- CREATE TABLE "OPS$<SID>ADM".SAPUSER  (USERID VARCHAR2(256), PASSWD VARCHAR2(256));
    --INSERT INTO "OPS$<sid>ADM".SAPUSER VALUES ('<sapowner>', '<password>');
    f.
    Execute R3trans -d under <sid>adm OS level user and verify its return code. Also check trans.log file
    5.
    what is the middle step between db recovery and starting the system.
    middle steps can be
    a.  to OPEN Database with RESETLOGS or NORESETLOGS option and restart the DB instance.
    b. create OPS$ Database user according to new SID and new <SID>ADM OS user
    I hope the above information will be helpful to provide you possible understanding.
    Regards,
    Bhavik G. Shroff

  • Transports Issue after system Refresh

    Hi All,
    Recently we performed a system refresh from our Production to Development system. It is SAP ERP 6.0 ehp5 system. The refresh was successful however we are seeing issues related to STMS.
    1. In our development system we are unable to use SCC1 to move transport from one client to another. The following is the dump.
    Category               ABAP Programming Error
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_SDB_ORA_PROGRAM_ERROR
    ABAP Program           CL_SDB_ORA_UPDATE_STATS=======CP
    Application Component  BC-DB-ORA-CCM
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 24 of the (include) program
    "CL_SQL_STATEMENT==============CM008".
    The cause of the exception was:
    ORA-20003: Specified bug number (16470836) does not exist#ORA-06512: at
    "SYS.DBMS_STATS", line 23922#ORA-06512: at "SYS.DBMS_STATS", line
    23973#ORA-06512: at line 1
    2. We are not able to see the sub request record for the transports is missing in E070 table for the TRs which were created before refresh.
    Please provide your inputs and help us to resolve these issues.
    Thanks!

    Hi
    Why do you mean by "system refresh from our Production to Development system"
    DB copy or client copy ?
    Based on the problem you have it must have been a DB copy.
    As you might know this is not recommended by SAP, you should at least have exported the object versions as stated in the here under note.
    I hope your TMS domain controller was the production system...
    It is normal that you did loose data in the CTS tables as you overwrite all CTS tables with the data from production, thus orders created in DEV that were not released should have been erased.
    I'm afraid your problem could be tougher than a simple Oracle error...
    For the Oracle error could you try launching system statistic and see if you get the same error
    brconnect -u / -c -f stats -t system_stats
    Why did you perform that refresh, client copy could have been a safer alternative.
    Regards
    130906 - How can versions be transported?
    You want to copy the versions of the repository objects from one R/3 system into another, for example because you are planning to copy your production system to your development system.
    Such a procedure does not correspond to the strategy recommended by SAP, to always retain the development system.

  • Rebuilding Domain controller & Transport Routes after system refresh

    I have refreshed Dev from Prdn, now my domain controller only shows single system
    I have documentation but, it is confusing to me how to have QAS and Prdn join the domain controller again and show the domain as a three tier system
    When I log into QAS and Prdn I still see the old 3 tier system including the domain and the other systems.
    Please advise
    maria
    Edited by: Maria Graziano on Mar 27, 2008 3:53 PM

    You don't perform backup of domain controller.
    You only designate in STMS one of servers as "Backup Domain Controller"
    when Primary  controller fails than "Backup domain Controller" takes his role and becomes a primary.
    So action to refresh domain controller is:
    1. Designate one of servers as backup domain controller
    2. Backup transport directory if it is on refreshed server (just in case)
    3. Switch backup controller to become primary
    4. Refresh primary system
    5. Join refreshed system to domain
    6. Switch back primary function to refreshed server
    Regards,
    Wojtek

  • DTP transport error after system refresh

    Hi Experts,
        The scenario is that Dsystem has already refreshed data from Psystem,and then error occured when transport DTP from D to Q system.
        As per the threads before, i know that we can trace  DTP technical name in table RSBKDTP.
        That i show the detail as the field from RSBKDTP in the below,
    Before refresh,
    System        DTP technical name     DTP original technical name  
    P                  DTP2                            DTP0
    Q                  DTP1                           DTP0
    D                  DTP0                            DTP0           
    After refresh P to D,
    System        DTP technical name     DTP original technical name  
    P                  DTP2                            DTP0
    Q                  DTP1                           DTP0
    D                  DTP2                         DTP0   
    Then the transport error from D to Q caused by that the two name underlined is not corresponding.
    Could anybody give me advice to solve the problem, if not ,i could only creat a new DTP in D.
    I am currently trying to find an solution and I will share if I find. Thanks.
    Edited by: rurupolo on Jul 15, 2010 5:20 PM

    Hi Friend,
    Just activate the DTP2 in D again and transport to Q.  It should work.
    Regards
    Hemant Khemani

  • System Refresh Precautions?

    Hi,
    During system refresh, are all types of data - master data, transaction data as well as <b>customising data</b> get refreshed from prouduction environment?
    Could you please suggest what is best way to get back project specific new customising data on a refreshed environment? Is there some sap recommended best practice on this.
    regards,
    Karthik

    Hi Please go through. This will give you exhaustive information. After refresh we used this to get back the required system specific customizations.
         Refresh from PR1 to QA1
    1.     Before the copy 
    &#61558;     Note down customer key, Installation number and license key - Done
    •     LICENSE system: QA1
    •     Customer key: L1985917776
    •     Expiration_date: 99991231
    •     Installation no: 0020065063
    •     Key: GKRZ25H353129JYX8HCJRS13
    •     Productid: R3_ORA             
    license useable ***
    (directory: \usr\sap\QA1\SYS\exe\run)
    (run command: saplicense – show)
    Team Involved: SAPDBA
    &#61558;     Download RFC tables  - To be done
    Tables rfcattrib, rfcdes and rfcdoc have been exported using sapdba on QA1 and the corresponding files are kept in a new temporary directory: /oracle/QA1/rfc_dest. After the system copy, these files have to be moved from /oracle/QA1/rfc_dest to /oracle/QA1/sapreorg and then the tables can be imported into QA1, to revert back to the RFC destination information as it is now.
    Steps : 1)login with oraqa1
               2) type sapdba
               3) select e - Export/import
    Perform this step two days before the scheduled refresh.
    Team Involved: SAPDBA
    &#61558;     Backup user master records in QA1 - To be done
    Procedure : login to QA1 400.
    Execute Transaction code: SCC8 (CLIENT EXPORT)
    Selected profile: SAP_USER
    Target system: QA1/DV1(safety backup)
    Perform this step two days before the scheduled refresh.
    Team Involved: SAPDBA
    &#61558;     Compare filesystem spaces -  Done
    Team Involved: SAPDBA
    &#61558;     Compare transports To be done
    Team Involved: SAPDBA
    &#61558;     OPERATION MODES(RZ04) Done
    Existing QA1 operation modes.
    Team Involved: SAPDBA
    &#61558;     Successful backup of PR1 To be done
    A successful offline backup has been scheduled on *** and that backup will be restored on to QA1 by the Unix team.
    Team Involved: USTO
    &#61558;     System messages/E-mails To be done
    SM02- CREATE A TEST MESSAGE IN PR1
    Two days before the scheduled refresh perform this step.
    Team Involved: SAPDBA
    &#61558;     Delete the existing datafiles on QA1  To be done
    Login as qa1adm and execute stopsap
    Login as oraqa1 and execute:
    lsnrctl stop
    rm –rf sapdata?/*
    Team Involved: SAPDBA
    2.     The copy To be done
    Copy all the datafiles from /oracle/PR1/sapdata? To /oracle/QA1/sapdata?
    Owner, group and permissions of the new files/directories to be maintained as before
    Copy Command: rcp –p  /oracle/PR1/sapdata*   Sierra: /oracle/QA1/sapdata*
    (NOTE: If errors occur when restoring/copying the sapdata on the target system, the complete restore/copying has to be repeated.)
    Team Involved: UNIX FOF/USTO
    3.     After the copy To be done
    &#61558;     Creating the control file on PR1 – To be Done
    Login as pr1adm and execute the following in svrmgrl
    connect internal
    alter database backup controlfile to trace;
    exit
    FILE created under the following Location: \ORACLE\PR1\saptrace\usertrace\ <pr1_ora_xxxx>.trc chose the latest run
    ftp the file onto desktop
    Team Involved: SAPDBA
    &#61558;     Edit the control file – To be done
    Here is the edited control file:
    Team Involved: SAPDBA
    &#61558;     Creating the control file on QA1  -  To be done
    Login as oraqa1 ftp the file to /oracle/QA1 and execute the following in svrmgrl
    connect internal
    @control.sql
    alter database open resetlogs;
    lsnrctl start
    exit
    Login as qa1adm and execute startsap
    Team Involved: SAPDBA
    &#61558;     Post system copy activities
    •     License installation  - to be done
    Login with user qa1adm
    Goto /usr/sap/QA1/SYS/exe/run  
    command: saplicense –install
    •     Installation check (Transaction SICK)
    •     SE06 > Database Copy or Migration > Post Installation Processing
    •     Delete entries from tables: DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA, MONI, PAHI, OSMON, DBSNP, SDBAH, SDBAD, SDBAP, SDBAR, DDLOG, TPFET, TLOCK and TPFHT
    •     Initial SAP consistency check (Transaction SM28)
    •     Database consistency check (Transaction DB02)
    •     Server check (Transaction SM51)
    •     TMS configuration
          Logon to the SAP R/3 System and goto TCODE SE06. Select "Database Copy or Migration" and execute "Post Installation Processing".
          Delete old TMS configuration and make new configuration for TMS via STMS TCODE.
    •     Logical system set-up and BDLS
    Delete logical system for client 400 after system refresh and create new logicalsystem and assigned to client 400.
    After refresh: LOGSYS400(logical system for client 400)
    Delete this logical system and create new logical system
    New logical system: QA1CLNT400 (logical system same before refresh in QA1)
    •     ITS and Bugseye settings
    •     RFC destinations as per Appendix (import the exported tables and then delete the temporary directory /oracle/QA1/rfc_dest)
    •     Logon load balancing(Transaction SMLG)
    •     Instance profiles
    Import profiles from active servers using RZ10
    Save and Activate instance profile. And restart the sap services.
    •     CCMS configuration
    •     Housekeeping jobs
         Background jobs(daily jobs)
    •     Application jobs
    •     Printer/spool/TemSe set-up
    •     User administration
        The transports are imported implicitly in post processing with transaction     
    SCC7.                                                                    
    •     Transport sequence number set-up
    •     Mass transport and Support package/patch application.
    Re-import transports to QA1 from DV1 which are not available in PR1.
    •     Manual configuration
    •     Create the rest of the clients:
    o     400     UAT/OAT Live Copy
    New client 340 to be created with the following settings.
    Source client: 400
    Target client :340
    Profile: SAP_UCSV
    COPY MODE: local copy
    Team Involved: SAPDBA

  • System Refresh: Abap+Java stack

    Have a few questions about CRM refresh I'm working on. Done many refreshes over the years and the new process has me shaking my head in disbelief.
    Performed a normal system refresh, by restoring online backup of production system onto mirror system. The mirror system exactly matches my production sytem (Oracle 10g, SuSE Linux 64 bit, UNICODE). 
    Now my system is running from Abap stack perspective, however Java components fail to load.
    Now from reading the documentation (System Copy for SAP, Based on SAP Netweaver 2004s Abap+Java) it appears that I have to use sapinst and no longer use online database backups for system refreshes.
    Is this the case? Has the investment my organization made into online backups now worthless?
    Is there a way to take the java schema in this online copied database and bring it online after converting it to work on the mirror landscape?
    Or should I throw out our system methodology and start new

    Thank you for the reply.
    Reading SAP's documentation seems to imply that I need to extract out the java schema from my production source and then re-install on my QA target to make a refresh of the java stack possible.
    However, if I have a complete copy of my source system database working on the target, why is the extract necessary?
    At least, I should be able to extract out the contents from the source as if it was the target, thereby eliminating any sort of production outages (we have many constraints about shutting down production from fuctional perspective).
    I'll do some research around the other tools mentioned to see if they can lend a hand fixing the issue,

  • Export partner profiles and SM59 Entries before system refresh

    Hello All,
    How to Export partner profiles and SM59 Entries before system refresh in Netweaver
    thanks
    Shyam

    In  SDN search  with name RFC export ..you will get so many answers ..
    Once again please find the below prcoess for RFC export/import during system refresh.
    RFC Export --
    go to trans dir.. and then create .ctl file as below
    #cd /usr/sap/trans/bin
    #vi export_rfc_<sid>_<date>.ctl
    #Please create the data file as u201Cexport_<SID>_rfc_<Date>.datu201D
    Export
    Client=<XXX>
    file '/usr/sap/trans/data/export_<SID>_rfc_<Date>.datu2019
    delete from rfcattrib
    select * from rfcattrib
    delete from rfcdes
    select * from rfcdes
    delete from rfcdoc
    select * from rfcdoc
    delete from rzllitab
    select * from rzllitab
    delete from ZTCA_USER_LANG
    select * from ZTCA_USER_LANG
    delete from rfcsysacl
    select * from rfcsysacl
    delete from rzllitab
    select * from rzllitab
    #After that excute export command as below.
    R3trans u2013w <export_rfc_<targetSID>_date.log> export_rfc_<targetSID>_date.ctl>
    (Format is: R3trans u2013w <logfile> <controlfile>)
    Export is finished....
    Import
    Example:
    #cd /usr/sap/trans/bin
    #vi import_rfc_pta_11042004.ctl
    #Please enter the exported RFC data file in the import control as follows:
    import
    file '/usr/sap/trans/data/export_pta_rfc_11042004.dat'
    (Enter the file name, which is created during the export process)
    Regards,
    Srinivas Chapa.

  • Lost Transport Import History after the system refresh

    Hi,
    We forgot to take the backup of the TPALOG table before the system refresh. We refreshed our testing system from production system. Right now we donu2019t have the old import history for the testing system. We played with TPALOG table and TPALOGHDR to synchronize TPALOG table with ALOG*  files. But we are not able to do that. I remember we had synchronized the TPALOG table with ALOG* files in the past. Please advise for any function/program to achieve this. Thanks.
    Thanks.
    Raj.

    Hello Raj,
    The mechanism behind the import history is that STMS will look in table TPALOGHDR to check if the time frame for which the import history is called, is between STARTTIME and ENDTIME.
    If it is, it will use the entries in table TPALOG.
    If not, it will read the ALOGxxxx files on /usr/sap/trans/log and update table TPALOG.
    Modifying the ENDTIME in TPALOGHDR will force reading the ALOG files again and will update the internal table TPALOG. In most cases,using the first date you find in the ALOG file that covers the missing transport.
    To reduce the possibility of competing accesses to the action log you can select a system-specific name. For this purpose, set the tp parameter ALLLOG in the STMS transport tool as global and with value:
    ALLLOG = ALOG$(syear)$(yweek).$(system)
    This will create system dependant ALOG files like, ALOG0318.D01
    It should be noted that : The import history in TMS is only available for periods after the last copy of a system. The reason for this is, that TMS needs some information about the ALOG files which are stored
    in the database. During a database copy, this information is destroyed and there is no possibility to restore this data.
    Best Regards
    Niraj

  • System refresh backup

    Hi All,
    I am doing System Refresh, could you please suggest me how can I take the backup of printers, RFCu2019s and Logical systems
    Previously I used to note RFCu2019s but in this Landscape we have many RFC, printers and logical systems are different  from production
    Could please suggest me how can I take the backup

    Hi,
    You can Transport all spool Devices from Tx-code SPAD but need to re-configure at the target level.
    1. Go to SPAD --> Select Configuration --> Output Devices
    2. In the list of Out put Devices screen select "Edit" --> Transport --> Transport all
    It will display a pop-up window "Device definitions must be processed later in the target system". you can proceed but below procedure has to performed in the target system.
    Procedure
    In the target system, you must adapt the spool servers for each device transported. This is because the system name is used in the instance names and it differs in the target system from the name of the current system. Logical instance names are an exception; they are defined identically in both systems.
    When selecting the new spool servers, ensure the host spool device names configured on the respective host are valid (access method L).
    If you are using destination hosts (access method U or S), you must ensure that they can be accessed by the new host. Otherwise the configured device cannot be activated. If the host name of the destination host is defined differently here, you must also adapt the entry in the device definition.
    Note: To assign a new spool server, choose menu options "Utilities" -> "For output devices" -> "Assign server".
    I am not sure about the other two if found any, i will definetly share.
    --Kishore

  • False backup / archive alerts after system refresh

    We have implemented CCMS on our systems. We recently refreshed our QTS system with a backup of production (PTD). CCMS is now sending alerts for backups and archives. It tells us that the backup and archive did never run.
    I checked DB12 and found that there is no data in DB12. This is probably due to the system refresh.
    Is there any extra post refresh step that we can do to prevent these false alerts (other than running a full online backup as post refresh step)? Is it possible to export the backup information (tables used by DB12) as pre refresh step and re-import them after the refresh?

    Kevin DK wrote:
    Will it create issues if we do not delete tables SDBAH and SDBAD during the refresh?
    No. BTW, tables are not to be deleted, just the table 'entries'.
    Thanks

  • Backup of background jobs after system refresh

    Hi All,
    I want to know that during the system refresh how can we take the backup of the background jobs which are in "Released" state so that we can schedule them the same way after the refresh is done. Presently we are taking the screen shot of "start condition" and "step" of each and every job and then using those screenshots we are scheduling them again after the refresh is completed. It would be really helpful and time saving for us if we come to know the tables where this information is stored and also if there is any other easier way for this.
    Regards,
    Lovneesh

    Hello,
    Check the below thread. It mentions all the tables that contain batch job information.
    https://scn.sap.com/thread/1709175
    " Check below mentioned tables
    BTCCTL,
    BTCDELAY
    BTCEVTJOB
    BTCH1000
    BTCH1010
    TBTCO
    TBTCP
    These have all the information you need regarding background jobs, you may export these tables at the source and import them "
    Check and provide feedback.
    Regards,
    Mudasir

  • Adding transports to import queue after System Refresh

    Hello All,
    Every time we do system refresh from PRD to Sandbox as a part of post refresh activity we need to import all the transports which are in the import queue of PRD(which are not yet imported to PRD) to our Sandbox.
    But its a tedious job, as in the import queue many old transports which are still not yet imported to PRD will b there.
    So may b around 150+ transport requests in the import queue of PRD, which we need to add those manually from path
    Extras---->other requests -
    > Add. doing same for 150 times. cant even imagine dat work.
    So my question is, Is there any way to get the replica of import queue of PRD to Sandbox.
    Some where i read like transport buffer in the path  /usr/sap/trans/buffer/<SID> of the system will have list of all transports in the import queue.
    So can i copy dat file and replace SID with Sandbox SID and place it in the Sandbox under same path.
    Please suggest or give me a correct solution.
    Regards,
    Ravi

    Thanks a lot for your reply.
    I had read about using script like tp addtobuffer inorder to add the transports to the import queue some time back.
    But forwarding transports is a new method i got to know here which even looks easy too. It would be great if any 1 tell me how forwarding works.
    Also it would b fine if who all uses this method of forwarding to add transports to import queue do reply about any  problems faced while forwarding requests.
    Bcoz in our landscape , transport route is as below
    Dev to QA and Sandbox then from QA transports will move to Production.
    So after refresh forwarding Transports from PRD to Sandbox, how does this work. Please share your suggestions.
    Regards,
    Ravi

  • Preserving SOA Logical Ports and Trust Relationships during DB Refresh

    Hi,
    I have been searching for this for a while and have not had any luck so far. I thought maybe the vast experience in this community might be able to help me.
    I am trying to preserve the SOA Logical Ports and the SMT1 Trust relationships of the target server during  DB Refresh. Is there a list of tables that we could export (Much like exporting/transporting RFC Destination)?
    Regards
    Shantanu

    Hi
    Check the here under tables if they fits to your needs
    Regards
    SRT_LP                       Logical Ports
    SRT_LP_FEAT            Logical Port Feature
    SRT_LP_OP_FEAT     Logical Port Feature (Operation-Dependent)
    SRT_LP_SXI_ADDR   Logical Ports: XI Addressing
    RSECACTB                 Table for ABAP Access Authorization for Secure Memory
    RSECTAB                    Secure Memory: Memory for Encrypted Data
    RFCTRUST                 List of existing trusting systems
    RFCSYSACL               List of permitted trusted systems for the current system

Maybe you are looking for