Export/Import and Client Copy

Hi All,
Could you please help me with what are the major differences between Export/Import...client copy...and a System Refresh.How they differ from each other.
Regards
Rajesh

Hello Rajesh ,
I have capture some data from SAP Help :
Local Copy: Copying Clients Within a System:
You can improve the performance of the client copy by, for example, by excluding tables or packages, with Edit -> Expert Settings.
You can exclude tables from the client copy, for example if they are not relevant for the target client, in the Tables tab
Copying Clients Between Systems (Remote Copy):
The same product is installed, with the same release, in both systems
The client copier can copy a client into another system. The systems can be on different platforms. You can change the client number.
When you copy a client from one system to another, the data is transferred directly via the RFC interface - there is no intermediate storage on hard disk.
Transporting Clients Between Systems ;Client export (SCC8):
The client copier can copy a client into another system, which can be on a different platform. You can change the client number.
You are no longer required to transport clients before you can copy them between systems. You can make a remote copy instead.
Up to three transport requests are created, depending on the selected copy profile and the existing data.
The transport request for texts is e.g. only created if the source client contains customer texts.
<sid>KO<no>  cross-client data
<sid>KT<no>  client-specific data
<sid>KX<no>  texts and forms
The data export is performed automatically asynchronously. The output of the export includes the names of the transport requests that are to be imported.
Import transport requests into the target client (STMS)
Choose one of the transport requests of the client transport in the Transport Management System (TMS). The other transport requests belonging to this client transport are then automatically added in the correct order.
Import these transport requests into the target client.
client import postprocessing (SCC7)
You need to perform postprocessing activities to adapt the runtime environment to the current state of the data.
Copy by Transport Request :
This function transports customizing changes that have been recorded in a transport request between two clients in a system.
You can choose whether you only copy the object list of the request or also the object lists of unreleased tasks in the request.
Entries in the target client are overwritten or deleted according to the key entries in the transport request.
Choose Administration -> System administration -> Administration -> Client admin. ->Special Functions -> Copy Transport Request.
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/69/c24c0f4ba111d189750000e8322d00/frameset.htm">For more info Click here</a>
Regards ,
Santosh Karadkar

Similar Messages

  • Difference between client Export/Import and a system refresh

    Hi Experts,
    I would like to know the diffrence between client Export/Import and System refresh.
    Actually i have done client export from our production system and imported it into our quality system, I have asked our functional consultants whether the production data is now available in Quality. They replied me saying whole data of production system is available in Quality system as off date i have copied the export.
    The size of the export was around 8GB, How can this have all the data of Production system which is around 600 GB.
    In this way what is the use of System refresh which is done by database level ( changing the cntrl file etc... ), As i am getting all the data by doing Client Export/Import.
    Thanks & Regards,
    Injamuri

    Hi,
    What is system refresh when and why it is done?
    The system refersh is nothing but the deletion of the client and replacing the data from other client. For example : you have clients 100, 200 and 300. Suppose when you want to refresh the client 100 you remove the client 100 and replace it with 200 0r 300 as per your reqiurement.
    Mostly the refresh of clients will be happen at the time of development stage.
    System Refresh is a simplified term to Client Copy. Client Copy means copying the production client on to the quality to test the real data. As recommend by SAP this need to carried out every 3 months.
    The process to carry out the same is as follows:
    1. Create a client on quality system using txn scc4
    2. Create a RFC between Production system and Quality System (need to create on quality system)
    3. Login to the newly created client using sap* and pass as a password
    4. Txn sccl to start the client copy.
    You can test the client copy by selecting the test run option. (test run will estimate the time taken for the activity).
    Anil

  • Doubt in  export, import and table para when creating Function Module

    Dear fellow ABAPers,
    I have a doubt in defining export, import and table parameter while creating a function module.
    I am calling a function module inside a user exit. Now in the user exit the SAP fills an internal table called i_lfa1 with all the data user has eneterd.
    Now I want to pass this whole internal table to function module and the perform some checks on the values of internal table.
    After that function module fills an error structure with values depending on some check.
    1)
    How do I pass this internal table to function module ? 
    When I am creating function module in se37 where do I define this iternal table type ? Is it in Import or Table parameter during function module creation?
    2)
    Where do I define error structure type (which is returned by function module to main program)? Is it in Export or table parameter during function module creation?
    Please clear my doubt..
    Relevant points will be awarded.
    Regards,
    Tushar.

    Hi Tushar,
    1. How do I pass this internal table to function module ?
       I assume u are creating your own Y/Z FM.
       Pass it thru TABLES parameter.
    2. When I am creating function module in se37 where do I define this iternal table type
       Define this in TABLES interface.
       What Type ?
       THE SAME TYPE WHICH HAS BEEN DEFINED
        WHILE PASSING IN THE USER-EXIT FUNCTION MODULE.
       IF U SEE THE FM OF THE USER-EXIT,
       U WILL COME TO KNOW.
    3.
    Where do I define error structure type (which is returned by function module to main program)? Is it in Export or table parameter during function module creation?
    Define it in TABLES interace. (not in export, import)
      (Since what u are going to return is an internal table)
      U can take for eg. BDCMSGCOLL.
      OR u can create your own Y/Z structure
    for the same purpose.
      (or u can use the structure type T100)
    I hope it helps.
    Regards,
    Amit M.

  • Audit Issue in QA after system restore and client copy

    Hi Experts,
    We have an audit issue and need your advise on that.
    Our QA system was audited and auditors were looking for the approval tickets on which a user was created. I found that several users that were not created in QA and do not even exist in QA have their change logs in QA showing that user was created.
    I researched it and found the steps that Basis and DBA's do when creating a new QA client.
    1. Basis export user master and authorizations using SAP_USER profile from the target QA environment.
    2. Then DBA's restore the QA Environment from the Production Backup.
    3. Basis import back the preserved User master and roles using SAP_USER profile.
    But when reading about this profile, I came to understand that change documents ( USH* ) tables are not exported and imported back. So that is why we have change logs in our QA from Production system.
    So my question is how to solve this issue, where Auditors look at the change documents in QA and ask for the documentation though in reality these change documents are coming from Production. Should we ask for DBA team to truncate USH tables or is there a client copy profile that saves the change logs that we can export and import back.

    Hi,
    as you know the USH* tables belong to delivery class L. The tables in this class are never copied during client copy but you don't do client copy. Idea of deleting records from L tables after backup restore does not sound good because you will loose all data. As a workaround you could backup content of tables with delivery class L, export users SAP_USER, restore production backup, import users and import backup for tables with delivery class L. There is around 5000 L tables in ECC. Another approach could be to restore production on different box and do proper client copy to QA system.
    Cheers

  • Export-Import and Naming convention question

    All,
    Newbie here. Have a question related to the naming convention for SAP R/3 system and XI manual export/import process. We are currently in the development environment where our R/3 systems are named as D55CLNT400, D56CLNT300 etc (first 3 characters are the system id, and last 3 are the client number.) This is per the XI best practices convention.
    The question i have is - if we name the technical system as above - and export the configuration objects from the Dev to Test environment - where the R/3 systems are named as T55CLNT400, T56CLNT300 (similar naming structure). Does it mean that we need to manually change almost all of the items in the Test environment on the configuration side (like business sytem name, interface determination, receiver determination etc)
    Is this the correct way or are we missing something??? I would have preferred a way - where we needed to only update the communication channel parameters.
    Thanks.
    Message was edited by:
            thezone

    In the SLD, create three Business System Groups: DEV, QAS and PRD.
    In each of these groups, you must have the relevant application servers (in your case, R/3s) and one integration server (XI).
    Then, for each Business System in Group DEV, define a transport target in QAS group.
    In your case, the transport landscape should be like this:
    D55CLNT400 -> T55CLNT400
    D56CLNT300 -> T56CLNT300
    XI_DEV -> XI_QAS
    Do the same for the QAS group (defining transport targets in PRD group). Observe that you need to have the same number of Business Systems in each group for this to work properly.
    Now, when you transport your configuration objects from XI_DEV to XI_QAS, all the Business Systems in DEV landscape will be replaced for the equivalent ones in QAS landscape.
    More info: http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/a21e3e0987760be10000000a114084/frameset.htm
    Regards,
    Henrique.

  • Oracle export/import and indexing

    Hello All,
    I am a newbie in oracle filed and trying to understand export/import funtionality and indexing related to it. May be it's silly but I don't get any other way to understand it.
    Below are the topics I tried to understand-
    1) I export one Db and trying to import that in another database server. I used sysdba username to import. A new table space will get created or how the data will store in database what would be the effect in indexing with this export and import.
    2) If i import one more db on the same database server using sysdba username then also how indexing will behave?
    Please help me to understand
    Thanks
    Sayan
    Edited by: Sayan_Roy on Sep 26, 2011 11:41 PM

    Indexes are tied to tables. The default behaviour, in the absence of you specifying any directives, is that Oracle runs
    CREATE TABLE
    INSERT INTO table
    CREATE INDEX
    So, the Indexes are created after each of the corresponding tables.
    Do NOT ever attempt to export/import objects owned by SYSDBA. You should be creating a separate schema to hold all your objects (Tables, Indexes, Views, Procedures, Functions etc). That separate schema can be exported and imported into another database. If you have multiple such schemas, a Full Export Import will copy all the schemas.
    If a schema preexists in the target database, the import will error when attempting to CREATE TABLE --- unless you specify directives to handle this.
    Please read the documentation on Export and Import for the version that you are testing.
    Hemant K Chitale

  • Logical System and Client copy

    Hi Gurus ,
                 I just now finished ECC 6.0 successfully , I want to take the client copy . But i hacve one doubt , In client creation one TAB logical system is there , Kindly advice me how to create Logical system and steps .
    Regards
    Selvan

    Hi Manjula ,
                  Below i mentioned the full detail about the error .
        RFC destination for client copy in systems with Financials Basis     (FINBASIS) component.    
    The system could not find any suitable RFC destination for processing     for client 000.     This note also appears if an RFC destination was found but this does not     work.     o   RFC destination: FINBTR@ID3CLNT000     o   Error text: Error during the retrieval of the logon data     Proceed as follows to eliminate this error:    
    1.  Start the wizard to create a new RFC connection     or perform the following steps manually:     1.  Create an RFC destination with the target ZK>source client of client         copy (in this case 000).   
    2.  Check whether the RFC destination works in transaction SM59.         To avoid errors when assigning the password or the authorizations of         the RFC user, use the authorization test Test -> Authorization.   
    3.  Enter the RFC destination:         -   Transaction: FINB_TR_DEST (Destinations for Transport Methods of             the Financials Basis)         -   Client: 000    
    4.  Start the client copy again.
    Kindly advice me
    selvan

  • Post-install of SSM 4.0 and client-copy

    We finished the installation of Sol. Man. 4.0 on a linux/oracle platform.  At what point in the post install do we do the client copy of client 000 for data and client 001 for users to a new client? Before, during or after all the img config in 000?
    thanks in advance,
    Steven McElwee, Duke University
    PS- Sap's install docs for SolMan 4.0 leaves much to be desired ...

    Well, we had a chicken-and-egg issue here. Let me explain. By default, the SSM 4.0 SR2 install is at SP9, which gave it a somewhat simpler IMG. However, we gave in to the temptation of installing SP11 since this SPs were obtainable without Maintenance Optimizer, which gave us a more complicated IMG which includes, at some point, the client copy as mentioned above. We went through most of the IMG resulting from SP11 until we had Maintenance Optimizer working and then downloaded SP12.
    I am in the process of installing the ABAP SP12 packages now and plan tomorrow to deploy the JAVA SP12 .SCA files. The IMG looks better and less confusing at SP12 than at SP11 or SP9. I think this calls for another IMG pass.
    The $100 question - which parts of the IMG need to be done in client 000 and which to do in our client 100 (copied from client 000 after SP11 was applied). We are really confused on this point. If anyone can shed some light on this, i would very much appreciate it.
    Sincerely,
    Steven McElwee, Duke University

  • Procedure to know client size, and client copy.

    Dear Experts,
                        I am new to client copy process.Please help me in some of my queries.The client which i want to copy is a customizing client (120) in development server.And new client to be created is also on development server itself.
    1). How can I know the exact size of the client which i want to copy?
    2). Will all the customizing done on the (120) client be copied to the new client created .
    3). Will all the profiles and parameters be copied as the source client?
    4). And Detailed process from client creation to client copy.
    Please help me .
    Thanks in Advance
    Regards
    Akif

    Dear Umesh,
                       As you told to add the space i did that .And started the client copy but it ended with 4 following errors:-
    Table/Object
    Component
    Error
    AGR_HIER
    BC-SEC-USR-PFC
    Write Error (See System Log)
    DSYS_PHCONT_E_CD
    PY-XX
    Write Error (See System Log)
    SOES
    BC-SRV-GBT
    Write Error (See System Log)
    ZFX_BCBNR
    DDIC Error        (See SE14)
      Please suggest what should be done of this errors.
    And thx for ur total support.
    Regards
    Akif
    <u></u><u></u>

  • Installation number and client copy

    Hi Gurus,
    Is client copy possible between two systems which has got two different installation numbers?
    This is a very basic question I know, but i don't see any other source of information. Even the client copy pre-requisites doesn't tell anything about installation number. Hence could anybody who has already experimented tell me about this.
    Thanks and Warm Regards
    Syam

    This question was answered by Gopalan Narayanan. Thanks Gopal
    Client copy between different installation number systems is possible.

  • Extraction failing after source system and client copy

    Hi all,
    We refreshed our source QA system with a copy of production.  And basically tried to "restore" the connection from our BW QA system.  Some of the datasources can be extracted from BW, others fail with an error of "No transfer structure is available for InfoSource 0COSTCENTER_ATTR in the source system".
    Trying to do the same thing with RSA3 in the source system, works fine.
    The strange thing is it works for some objects but not others.
    here's what we did:
    1. System copy from R3 Prod to R3 QA
    2. Client copy with R3 QA client 300 -> 200
    3. Restore connectivity in BW QA to the R3 QA system (Using RSA1 -> Source  System -> Restore)
    4. Now some objects can be extracted in BW, others fail as I mentioned above.
    I have regenerated the transfer structures in BW and R3. 
    All of these objects that don't work seem to work in RSA3 on the R3 system but not in RSA1 on BW.
    All the SAP documentation is geared to copying the R3 source system and then restoring connectivity between BW and R3.  I don't think any of it involves copying the client in the R3 source system - which might be causing our problems.
    We are using an SAP delivered PDF and note 886102 mainly for direction.
    SAP PDF is "How to... System Copy in SAP Business Intelligence System Landscapes".
    Does anyone have any ideas?
    Thanks,
    Kevin

    Hi,
    can you isolate somehow the kind of DataSource which works and those who don't?
    Master data / transactional or client dependent and not, delta or full....
    To which R/3 client is your BW connected? when you succeed loading the data, is it coming from the right client?
    RSA3: do you run it specifying your BW client in the target sys field? does it make a difference if yes or if not?
    Are your RFC connections and partner profiles all right?
    Check some IDOCs sent by BW received in R/3 and vice-versa (RSSEND, RSINFO, RSRQST..). Load a hierarchy (via IDOC)... verify that your IDOC have the correct partner settings....
    let us know
    Olivier.
    Message was edited by:
            Olivier Cora

  • ASD Export/Import and the Anti-Marshal (kind of like a supervillain)

    Just tried to export a single resource action and import it back into the same environment with a new "prefix" and I get the following errors on validation....  same goes for importing it into another environment.  (which we will call "new environment"... where the Resource Action doesn't exist)  The workflow that the RA points to exists in the current environment because there is an RA that already points to that workflow.  In the new environment, the workflow exists due to a successful vRO sync.  (we can then build a successful form against the workflow in the new environment.)
    It seems like it is complaining about the Resource Type, but none of those were selected for export.. so one would expect that they wouldn't be imported.
    Anybody try out the export/import functionality in ASD and have it be successful?
    When we build a form in our Lab environment, we have to completely rebuild it in two other environments.  Though building forms in ASD is exceedingly fun and intuitive, we would really like to have a working export/import capability!

    It throws same error for exporting/importing ASD blueprints( Nothing else was selected to export like actions etc). In this case ASD blueprint exists in the destination.  Sean, did you make any progress?
    Failed on Can not unmarshal entity:resource-mappings of type: com.vmware.vcac.designer.rest.stubs.CsResourceType
    Warning
    RHEL
    Service Blueprint
    blueprint.name.duplication
    Info
    RHEL
    Service Blueprint
    blueprint.validation.success
    Error
    Can not unmarshal entity:resource-operations
    Resource Action
    resourceoperation.unmarshal.exception
    Error
    Can not unmarshal entity:resource-types
    Custom Resource/Mapping
    resourcetype.unmarshal.exception
    Error
    Can not unmarshal entity:resource-mappings
    Custom Resource/Mapping
    resourcetype.unmarshal.exception

  • Personas - Export / Import and missing icons

    Morning all.
    Have many of you used the import  / export feature to move flavours between clients? I have used it successfully in the past but the now have an issue.
    I have 4 flavours and a bunch of media files, many of which are shared amongst the flavours. When I export them the export is missing quite a few of the media files.
    Has anyone else experienced this issue?
    thanks,
    Neil

    further testing has revealed that it's files of type 'icon' only that don't get exported, the 'pic' file types export fine.
    Can anyone confirm the behaviour on their system please?

  • Export, Import and Table declaration in custom function module

    I am creating a custom function module. Parameters needed are export internal table and one data field from the internal table.
    What do i need to fill for 'associated type' for these export parameters since size of the internal table and type for the data field from the internal table vary.

    Hello Albert
    If the function module need not be RFC-enabled then you have many ways to define such dynamic parameters, e.g.:
    FUNCTION ZUS_SDN_DYNAMIC_PARAMS.
    *"*"Local Interface:
    *"  EXPORTING
    *"     REFERENCE(ET_ITAB) TYPE  TABLE
    *"     REFERENCE(ET_ITAB_1) TYPE  ANY
    *"     REFERENCE(ET_ITAB_2)
    *"     REFERENCE(ED_DATA) TYPE  CLIKE
    *"     REFERENCE(ED_DATA_1) TYPE  ANY
    *"     REFERENCE(ED_DATA_2)
    ENDFUNCTION.
    See also: How to return back a structure of dynamic tables in a Function Module
    Regards
      Uwe

  • Client Copy error during client export / RX file is not getting

    Hi Experts,
    During the client export process of client copy in order to created two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
    In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
    Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
    Regards,
    Haris

    Hi Experts,
    During the client export process of client copy in order to create two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
    In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
    Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
    Regards,
    Haris

Maybe you are looking for