Skip to Content

Differences in refresh of different abap systems

Hi Experts,

I wanted to know what are the differences in refresh of different abap systems with oracle as the database. Like, what processes are different in pre and post refresh tasks for BW, CRM, SRM, SCM, ECC etc.

Please advice.

Thanks,

Asad

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Posted on Jan 04, 2016 at 06:23 AM

    Hi Asad

    From what I understand the system copy is not really specific to the SRM or ECC box it is mostly based on your database , your netweaver component level and whether you have ABAP or JAVA stacks

    1. Check the kernel and patch levels

    2. Prepare both source and target systems

    3. Check no released jobs exists

    4. Specify a directory with sufficient disk space for the export dump on the host where you want to perform the export

    5. Generate DDL statment to migrate the non standard database objects .

    Refer more on the link below to help you find the right guide .

    SAP NetWeaver Guide Finder

    Also check this one for Netweaver version 7.4 and Oracle as the database

    https://websmp207.sap-ag.de/~sapidb/011000358700000887092012E

    Regards

    Vinita

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 13, 2016 at 05:11 AM

    Dear Asad,

    For different system, you need to refer to the corresponding installation for refresh.

    In SAP world, the refresh is called "system copy", generally the export (copy from source system) are the same, the import (copy to target system) needs to refer to the installation guide. The guide mentioned all the pre and post steps.

    So to perform the refresh, you need two guides, system copy guide, and installation guide. system copy guide is usually for all the netweaver based systems, but installation guide is for every product based on netweaver.

    Best regards,
    James

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 06, 2016 at 01:23 PM

    Hi asad,

    Common steps after refresh.

    1.Apply License.

    2.Suspend the BTC jobs.

    3.Change Logical system names-BDLS.

    4.Change RFC destinations.

    5.Configure TMS.

    6.Printer configuration SPAD.

    7.Clear queue in SMQ1 and SMQ2.

    8.Remove batch inputs in SM35

    9.Create Logon groups SMLG.

    10.Client configuration SCC4.

    11.Delete Source profiles.

    12.Configure operation modes.

    for further information go to SAP market place.

    Regards,

    Manoj.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 08, 2016 at 11:18 AM

    Hello Asad,

    Make it simple about the procedure as all the systems. while doing a system copy, then you must take all pre steps like RFC connection and integration important jobs etc... for example if your copying production to quality system then you must bring back the system as it is like befor with PRD data. after system copy your quality system will act as PRD. so mostly we will avoid mail triger job and suspend the BG job etc.. SO , we have to take care exa like BIW RSA1 or SRM catalogue etc.. Need to check from each module consultant BI,CRM,SRM or SCM... many integration will be there... it standard documents guide are available in service market place.

    Thanks,

    Brindavan M

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 24, 2016 at 08:27 AM

    Hi All,

    We are trying to arrive at all preventive steps we should take during DB refresh from Production ECC to Quality to avoid accidental communication from quality to any Production components. Request your inputs calling out if any additional things we need to take care as a post processing activity.

    Stop all jobs till all post processing activities are complete.

    Prevent mails going out of Quality - Disable SMTP Node.

    Prevent printing on Production Printers - import Non Prod printers before enabling Spool Work processes.

    Prevent outbound IDOCs- Import non Prod RFCs exported. anything else we can do here.

    Prevent any calls to Production environment Web Services - Identify end point configurations and reconfigure (any automatic approach ?)

    Consumer Proxies depend on Ports so if we manage RFCs they should be covered already. Any inputs here.

    Workflows - Any required steps ?

    Anything else I missed to callout ... Please callout.

    Thanks in advance

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.