Scribd Logo
Upload

Welcome to Scribd!

  • 130 views

    System Refresh

    Uploaded by

    Dhanam Jay
    1. To prepare for a client copy in SAP, you need to determine the size of the source client, adjust file systems to fit the client size, and choose whether to do a remote copy or export/import. 2. When doing an export/import, use R3trans to speed up copying of clustered tables, and refer to release notes for improving performance on cluster tables. 3. A system refresh involves deleting an existing client and replacing it with data from another client, usually done during development to test with real data. It is recommended to refresh production clients onto quality systems every 3 months.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd

    System Refresh

    Uploaded by

    Dhanam Jay
    130 views1 page
    1. To prepare for a client copy in SAP, you need to determine the size of the source client, adjust file systems to fit the client size, and choose whether to do a remote copy or export/import. 2. When doing an export/import, use R3trans to speed up copying of clustered tables, and refer to release notes for improving performance on cluster tables. 3. A system refresh involves deleting an existing client and replacing it with data from another client, usually done during development to test with real data. It is recommended to refresh production clients onto quality systems every 3 months.

    Original Description:

    ggg

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    1. To prepare for a client copy in SAP, you need to determine the size of the source client, adjust file systems to fit the client size, and choose whether to do a remote copy or export/import. 2. When doing an export/import, use R3trans to speed up copying of clustered tables, and refer to release notes for improving performance on cluster tables. 3. A system refresh involves deleting an existing client and replacing it with data from another client, usually done during development to test with real data. It is recommended to refresh production clients onto quality systems every 3 months.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    130 views1 page

    System Refresh

    Uploaded by

    Dhanam Jay
    1. To prepare for a client copy in SAP, you need to determine the size of the source client, adjust file systems to fit the client size, and choose whether to do a remote copy or export/import. 2. When doing an export/import, use R3trans to speed up copying of clustered tables, and refer to release notes for improving performance on cluster tables. 3. A system refresh involves deleting an existing client and replacing it with data from another client, usually done during development to test with real data. It is recommended to refresh production clients onto quality systems every 3 months.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 1

    SAP Basis Notes: SAP Client Copy / System Refresh http://sapbasisnotes.blogspot.com/2007/11/sap-clien...

    Before doing a client copy, you need to prepare the following :-

    1. Find the source client space with the client size custom program which can be
    implemented using the rel. note:
    Find the space of the client - '0118823'. This will give you the size of the source client.

    2. If your are on Unix OS, adjust all the file systems according to PRD file system to fit
    the PRD client in DEV
    client based on space requirements also.

    3. You can do the client copy by remote or export/import client.


    Remote method is not preferred if you are doing a large client copy.
    Do a client export/import.

    4. To speed up the export/import, use R3trans export/import for the clustered tables.
    Please find the rel. notes related to performance improvements for cluster tables in OSS.

    5. Do import and post processing.


    Note: Export may take 10 to 20 hr. for 50gb of data
    import may take 4 days and post import will take 8 to 15 hr. for 50gb of data. And it all
    depends on
    your system performance.

    Please refer OSS rel. notes for the few RZ10 parameters which needs to be set for cluster
    tables to speed up the process.

    Note :-

    If it is a fresh installation, do this --

    1. SCC4 --> Create client no. and fill other details.


    2. Logon to the newly created client with SAP* and PASS as password.
    3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client .
    4. Preferably do a test run initially to check if it can go well.
    5. As a care check space in databases.

    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).

    1 of 1 Friday 08 October 2010 03:06 PM

    You might also like