Transport table ?

Hi,
I have one question on transporting a table.
I need to transport with data from dev to qa system.
The problem here is , in dev the table got created in table space ts01 but this tablespace does not exists in QA system (in QA this table needs to goto tablespace ts02).
How do i transport this table?
Thanks
Ram

Hello Rama,
My suggestion is based on my observations with in my system landscape.
I checked for the tablespaces of  couple of tables in my landscape.
In my developement system  they were created on tablespace: PSAP<sid> while in QAS also they were present  on table space PSAP<sid> but obviously both table spaces are different since <sid> of both the systems is different.
Now I checked the transport requests that were responsible for movement of table (structure/definition) from development to quality. I found that the imports happened successfully and without any errors. Also the transport or transport logs had no reference to table space That is why I think no issue should occur in you case also.
Have you faced any error or is just a precautionary measure that you are taking?
Regards.
Ruchit.

Similar Messages

  • How can I save the first dept. for an employee in a transport table?

    Hi All,
    I have created a table to store the transports to an employee from department to another department.
    the first department number to every employee is stored at the parent table called employees.
    when I insert a new record to the transports table (which is the child for the parent employees) for an employee and the manager agrees for this transport the original value of department number in employees table will be changed to the new one. I done this process through a db trigger on the transport table.
    Now the problem is that the original value of the first department number will be lost cause of the db trigger that changes this value after manager agreement!
    I looked to solve the problem by adding a new column in employees table to save the first dept. no. for each employee only if Count of records = 1 for that employee like this:
    -- Before Update DB Trigger on Transports Table:
    DECLARE
    pragma autonomous_transaction;
    N NUMBER;
    BEGIN
    SELECT count(EMP_SID) -- emp-sid is the FK referenced from employeess.emp_sid
    INTO N
    FROM TRANSPORT_TRANS
    where emp_sid=:NEW.EMP_SID
    GROUP BY EMP_SID;
         IF :NEW.AGREE_FLG = 1 AND N = 1 THEN -- If the manager agrees and this record is the first one for that employee
         UPDATE EMPLOYEESS E
         SET E.FST_AD=E.ADMINISTRATION_SID, -- E.ADMINISTRATION_SID has the oroginal value for admin no. and FST_AD is the new column to save the first value
                E.FST_HE=E.HEADQUARTERS_SID,
                E.ADMINISTRATION_SID = :OLD.ADMIN_SID, -- changing the value with then new one added on the table
                E.HEADQUARTERS_SID = :OLD.HEAD_SID
               WHERE E.EMP_SID = :OLD.EMP_SID;
         ELSIF :NEW.AGREE_FLG = 1 AND N != 1 THEN -- if the manager agrees but the record is not the first record for that employee
         UPDATE EMPLOYEESS E
            SET   E.ADMINISTRATION_SID = :OLD.ADMIN_SID, -- only change the original  values
                     E.HEADQUARTERS_SID = :OLD.HEAD_SID
                     WHERE E.EMP_SID = :OLD.EMP_SID;
         END IF;
    END;But the form gives me this error if I deleted (pragma autonomous_transaction;) st. :
    ORA-04091: table transports is mutating, trigger/function may not see it
    But when I keep it, the form gives me this error:
    ORA-06519: active autonomous transaction detected and rolled back
    Edited by: Dev. Musbah on Aug 18, 2009 2:09 AM

    Dev. Musbah,
    First make sure that the insert statement executes. And check whether other error messages are getting. Currently you are checking only NO_DATA_FOUND. so change the exception part with
    EXCEPTION
         WHEN NO_DATA_FOUND THEN NULL;
         WHEN OTHERS THEN MESSAGE('Some Error Occured');Regards,
    Manu.
    If this answer is helpful or correct, please mark it. Thanks.

  • Transporting table entry with primary key 120 char

    Hi all,
    I have 2 separate questions which I feel are closely related.
    In the url:
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb6e446011d189700000e8322d00/content.htm
    It says:....
    <i>If the key length is greater than 120, there are restrictions when transporting table entries. The key can only be specified up to a maximum of 120 places in a transport. If the key is larger than 120, table entries must be transported generically.</i>
    <b>How do I transport the table entries "generically" for such a table?</b>
    To further illustrate my actual problem:
    My problem in the real world lies with the MIMETYPES table, maintained in trx SMW0.
    I select the mime types row by row and do a <u>Table Entry > Transport Entries,</u> but get an error that says
    <i>"Key entry for table MIMETYPES may only be generic"</i>.
    As a result it fails to attach to my transport.
    (Note: the primary key of MIMETYPES is 128 chars long)
    The Diagnosis long text says "<i>The key is longer than allowed by the Change and Transport System (120 characters</i>)."
    The Procedure says:
    <i>1.  Make sure that you only specify the character fields before the    
        first non-character key field. You must enter the key with a generic
        ending. Enter the generic symbol directly after the specified part 
        of the key.                                                                               
    2.  You must enter the generic symbol at the latest in the 120th       
        character of the key.                                              </i>
    <b>What is this generic symbol that i need to insert at the 120th position??</b>
    Message was edited by:
            Kevin Wong
    Message was edited by:
            Kevin Wong
    Message was edited by:
            Kevin Wong

    Thanks Nick!
    So the mysterious "generic character" is actually the asterisk (*). It works.
    Strange tho as the error long text says to insert the "generic character" at the 120th character position of the key, but I found that altho I can save it, the transport still fails with the same error.
    I tried placing the * right after the key value e.g.
    KEY123*
    and it worked.
    Thanks again!

  • Transport table+data one server to another server

    Hi expert,
    i have 2 servers DEV1 & DEV 2 with ecc 6.0 oracle 10g.
    Both server have same patch level and same version of OS,DB & Patch.
    in DEV1 have a table which consist  54500 rows i want move to this table and data in DEV2 server.
    Please suggest How can i do this if i create a transport or copies request it move only structure not data.
    Regards,

    Hi,
    It is possible through SAP by creating transport request.
    See the below link for how to:
    Transporting Table entries from one server to another
    [http://****************/Tips/Basis/Transport/TableEntries.htm|http://****************/Tips/Basis/Transport/TableEntries.htm]
    Regards.
    Rajesh Narkhede

  • Transport Table with Data from Development to Quality

    Hi
    Requirement:
    Transporting Table with Values from Development to Quality System.
    I have a Z* - table, appended one field at the end.
    I need to transport data along with the table structure from Development System to Quality System.
    In Development System, I have assigned the Transport request in Client 100(We can't add data to the table in this client).
    What needs to be done to migrate the new table structure with Values.
    Thanks in Advance
    Regards,
    Baburaj
    NOTE: the requirement is to transport table and table entries through a transport request.
    There should not be any manual update for the table in the target System (Quality System).

    Check the delivery class assigned to the table. Please see the documentation
    Delivery class
        The delivery class controls the transport of table data when installing
        or upgrading, in a client copy and when transporting between customer
        systems. The delivery class is also used in the extended table
        maintenance.
        There are the following delivery classes:
        o   A: Application table (master and transaction data).
        o   C: Customer table, data is maintained by the customer only.
        o   L: Table for storing temporary data.
        o   G: Customer table, SAP may insert new data records, but may not
            overwrite or delete existing data records. The customer namespace
            must be defined in table TRESC. (Use Report RDDKOR54 here).
        o   E: System table with its own namespaces for customer entries. The
    customer namespace must be defined in table TRESC. (Use Report
    RDDKOR54 here.)
    S: System table, data changes have the same status as program
    changes.
    W: System table (e.g. table of the development environment) whose
    data is transported with its own transport objects (e.g. R3TR PROG,
    R3TR TABL, etc.).
    or during client copy
    the data of client-specific tables is copied.
    Classes C, G, E, S: The data records of the table are copied to the
    target client.
    Classes W, L: The data records of the table are not copied to the
    target client.
    Class A: Data records are only copied to the target client if
    explicitly requested (parameter option). Normally it does not make
    sense to transport such data, but is supported to permit you to copy
    an entire client environment.
    or during installation, upgrade and language import
    behavior differs here for client-specific and cross-client tables.
    nt-specific tables
    Classes A and C: Data is only imported into client 000. Existing
    data records are overwritten.
    Classes E, S and W: Data is imported into all clients. Existing data
    records are overwritten.
    Class G: Existing data records are overwritten in client 000. In all
    other clients, new data records are inserted, but existing data
    records are not overwritten.
    Class L: No data is imported.
    Cross-client tables
    o   Classes A, L and C: No data is imported.
    o   Classes E, S, and W: Data is imported. Exisitng data records with
         the same key are overwritten.
    o   Classe G: Data records that do not exist are inserted, but existing
         data records are not overwritten.
    ehavior during transport between customer systems
    Data records of tables of delivery class L are not imported into the
    target system. Data records of tables of delivery classes A, C, E, G, S
    and W are imported into the target system (this is done for the target
    client specified in the transport for client-specific tables).
    se of the delivery class in the extended table maintenance
    The delivery class is also analyzed in the extended table maintenance
    (SM30). The maintenance interface generated for a table makes the
    following checks:
    o   You cannot transport the entered data with the transport link of the
        generated maintenance interface for tables of delivery classes W and
        L.
    o   When you enter data, there is a check if this data violates the
        namespace defined for the table in table TRESC. If the data violates
        the namespace, the input is rejected.
    Thanks,

  • Object extraction to transport table is not complete.

    I had applied the patch for BUG 2472140 and BUG 2451096 and exported the transport set with a one page group. I downloaded the Windows NT Command Utility and I saved it as export.cmd
    When I run the script with the Export mode set I get an error:
    C:\>export.cmd -mode export -s portal -p portal1 -c iasdb -pu orcladmin -pp sszp
    ortal1 -company OKSystem -d c:\test.dmp -automatic_merge -check_mode
    Mode Selected is EXPORT
    Error: Object extraction to transport table is not complete.
    Please try again later.
    Export/Import aborted.
    I have waited for 2 days, but it doesn't help. I tried the same with application and it worked fine.
    Thanks for help.
    Martin Rosol

    This could have happen when the background job in the Job_Queue is still waiting to get executed completely. You could do the following...
    1. Login to SQL*Plus as Portal Owner.
    2. Execute the following SQL statements...
    select export_id,name,status from wwutl_export_import$;
    (This will list you all the transport sets available ; Identify your transport set here)
    delete from wwutl_export_import$ where export_id = '(Export Id you found out just now)';
    3. Then Export the Pagegroup again to create a new transport set.
    4. Download the script and run it after the status of the transport_set becomes 'EXTRACT_COMPLETE'
    Thanks,
    Arun

  • Transport table and table entries

    Hi,
    I need to create a table and table entries, here I need to transport table and its entries to another system,
    what steps i need to follow for this?
    Please help me

    Entries
    Create entries by Se11-> utilities-> table content -> create entries
    For Transport
    Go to SE10.
    Click on the 'Create' icon.
    Select 'Workbench Request'(assuming your table is not customizing table).
    Enter description and click 'Save'.
    Put cursor on the task (lower number of the two) and in menu, 'Request/task>Change Type>Development/correction'.
    With cursor on the task(lower number), click 'Object List' icon on the toolbar.
    Once in, you need to toggle to 'Change' mode using the pencil icon.
    Then click on 'New Entries'. Now add the R3TR, TABU, <ZTAB> in the first row.
    Again in the menu, select 'Extras>Change object function>Key according to key list'.
    Now go to the menu, 'Goto-->Key list'. In the subsequent screen, click on 'Insert line' icon(with a + sign).
    Click on 'Key fields' button and it will now allow you to enter the values for each key field.
    Regards
    Shashi

  • What are non-transportable tables

    What are non-transportable tables?
    I am under the impression that any non-transportable object is a "local object".
    Am I right?
    Thanks,
    Raghu.

    Hi,
    Yes you are right. All the object created under $TMP package are non- transportable.
    We cannot transport these objects.
    There will not be any thing like Non transportable tables.
    Regards,
    Venkatesh.

  • Transport Table Maintainance

    Hi,
    I am currently working on merging two SAP systems. I was wondering what the best way is to transport table maintainance?
    Thank you.
    /Elvez

    Hi Elvez,
    This is very easy..
    You will need to transport the function group of the table maintenance in a transport.
    There are two ways:
    1) You can transport the database table and this function group together and there will be no problem.
    2) If you are transporting the function group in a separate transport, make sure that the transport for the database table is already moved.
    Thanks and Best Regards,
    Vikas Bittera.
    **Points for useful answers**

  • Transport table settings of standard transaction (Exemple CS02)

    Hello,
    Do you know how to transport tables setting ?
    Especially system variants which are visible to all users in the current client (although user-defined
    variants, where they exist, override system variants). They can be edited using the 'Administrator' function.
    Best regards,
    MV

    Hi,
    Running RPULCP00
    The simplest way is to go into the table through SM31
    Then in your top row of buttons there should be one called 'utilities' from here select 'adjust',
    Then select the client that you want to compare/copy from (you need to have an RFC destination set up).
    This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories:
    ML Differences, logon client entry
    MR Differences, comparison client entry
    L Entry only exists in logon client
    R Entry only exists in comparison client
    Identical entries
    (M) Differences only in hidden fields
    You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table.
    That should do the job. 
    Program variants
    If you have several program variants in a development system that you want to transport, use the following method to transport them:
    Execute program RSTRANSP (via se38) and inform the program and/or variant names (you can transport variant of several programs in one shot).
    Regards
    Sreedhar Reddy

  • How I could transport table entries from table NRIV

    Does anyone knows how I could transport table entries from table NRIV.
    I can mark them in se16 but the "table entries"->"transport" is grey. What shouuld be done.
    Is there another way to transport NRIV entries.
    Thank you in advance

    Hi,
    Goto SE01 -> Create Transport Request.
    Assign the Workbench request/Project.
    Single click the TR. Click on the DISPLAY OBJECT LIST or Press SHIFT + F11.
    Click on CHANGE -> Insert.
    PgmID Obj Object name
    R3TR TABU NRIV
    CLick Extras -> Change Object Function -> All entries.
    Save.
    Release the Tr.
    Best regards,
    Prashant

  • BI Transport Tables

    BI Experts,
    WE have an existing customized abap program that primarily analyzes any transport/object conflicts with standard SAP code within TADIR / E070. Are the transport tables and process primarily the same within ECC (R3) and BI?
    Right now the code only functions within R/3, but we would like the same analysis tool to work on BI. So from Development, QA, to PRD, I would want to have the same functionality before transporting beyond Development.
    Regards,
    Ajloren

    Find tables - > SE16 - E0* - F4
    E070                           Change & Transport System: Header of Reque
    E070A                          Change & Transport System: Attributes of a
    E070C                          CTS: Source/Target Client of Requests/Task
    E070CREATE                     Change & Transport System: Creation Date o
    E070CTV                        Shared access to e070, e07t, and e070c
    E070DEP                        Change & Transport System: Dependencies of
    E070L                          CTS: Index for Assigning Numbers to Reques
    E070M                          CTS: Target Package/Layer for Requests
    E070TC                         Help Table for E070 for Client-Specific Im
    E070USE                        Use of Current Requests by Users
    E070V                          TMS WBO: E070 with Texts (E07T) and Source
    E071                           Change & Transport System: Object Entries
    E071C                          Change & Transport System: Client-Specific
    E071E                          Lang. Transport: Positive List for Generic
    E071K                          Change & Transport System: Key Entries of
    E071KF                         Change & Transport System: Nametab Info. o
    E071KFINI                      Change & Transport System: Nametab Info. o
    E071S                          System-Specific Import Status of Objects
    E071V                          View on objects in orders E070+E071
    E07T                           Change & Transport System: Short Texts for

  • Transporting table contents

    Hi ,
         I have created a master data table and i need to transport its contents ( the table is already in quality ) from devlopment to quality server but it is not at all asking for a request.Please help me out

    Hi Arvind,
    Probably your table is not marked as Transportable table.
    Go to table Maintanance and see if Standard recording routine us checked.
    You may also want to build the transport manually, Follow below steps:
    1) Go to SE01.
    2) Click on the 'Create' icon.
    3) Select 'Workbench Request'(assuming your table is not customizing table).
    4) Enter description and click 'Save'.
    5) Put cursor on the task (lower number of the two) and in menu, 'Request/task-->
    Change Type-->Development/correction'.
    6) With cursor on the task(lower number), click 'Object List' icon on the toolbar.
    7) Once in, you need to toggle to 'Change' mode using the pencil icon.
    Then click on 'New Entries'. Now add the R3TR, TABU, <ZTAB> in the first row.
    Again in the menu, select 'Extras-->Change object function-->Key according to key list'.
    8) Now go to the menu, 'Goto-->Key list'. In the subsequent screen, click on 'Insert line' icon
    (with a + sign).
    9) Click on 'Key fields' button and it will now allow you to enter the values for each key field.
    Regards
    Shital

  • Transport Table K9RPEF1000006  from Production Server to Quality Server

    Dear Friends,
         I am performing client export/import activity and I have exported the Production Client with SAP Profile SAP_CUSX but when we checked log then It shows the table K9RPEF1000006 is available on production server but not available in quality server.So I have two queries ,( i) how can we create tranport request for this sap standard table (ii) How can we transport/move table from production client to quality client.
    Regards,
    Adya

    Hi Adya,
    You will need to create a transport manually using SE03 or SE09 ...
    R3TR TABL will transport technical settings for the table.
    R3TR TABU will transport table contents.
    Best regards,
    Derrick Hurley
    Development Workbench

  • Error while transporting table entries to QA

    Hi All,
    I am working on system 4.6C i have a ztale with 3 key fields.
    I have added entries in table sucessfully.
    While imprting to Quality system.
    key field1   2183
    Key field2  A
    Key field3  CHF
    It returns an return code with message called 'key of table Ztest (6102183      ACHF) only valid up to offset 13. It's better to skip it.
    It has only enter when i enter values in 3 key fields. If i left key field2 as empty for those entries the values are impoerted to quality suceesfully.
    Can anybody please let me know what would be the problem.
    Thanks,

    YOu can try transporting the entries using generic keys.

  • Transporting table entries present in standard SAP R/3 table u201CTMCEXCFZu201D.

    Hi All,
    We have a requirement where in we need to capture a table entry in transport request in R/3.
    The table "TMCEXCFZ" is a standard SAP R/3 table.
    The" transport entries" option under the "table entry" in menu bar is disabled in our case.
    Is there an alternative way to capture the table entries in the transport request?
    Thanks for your help in advance.
    Thanks and Regards
    Arun Ail

    Hi Arun
    Try to go to object changeability in the table....assign the table in a package.....then try to save this...it should ask for a transport...
    Hope this helps
    Cheers
    Chanda

Maybe you are looking for