SAP ECC upgrade - Impact to GRC

Hi Forum guru's,
We have a client that is currently using all 4 components of GRC AC Version 5.3 running on ERP 4.7.  The client will be upgrading shortly to ECC6 and I would like to ascertain some important tasks required from a GRC functional point of view and the components that will be the most impacted.
1) New connectors will be created for each component. 
2) RA&R: Re-upload of auth objects and full re-generation of rules.
3) ERM: New connectors to be added to the current landscapes and roles uploaded.
4) SPM: Component to be fully re-configured on the new system
5) CUP: Existing workflows will apply as they do not use the "system" as the initiators.
Is there any other important steps from a functional point of view that I am missing?. Please advise.
Rgds,
Prevo

Hello Prevo,
1) New connectors will be created for each component.
-> Not required. Existing Connectors created in each of the component of GRC for 4.7 system will work. Just need little modifications.
2) RA&R: Re-upload of auth objects and full re-generation of rules.
->  Right.
3) ERM: New connectors to be added to the current landscapes and roles uploaded.
-> No new connectors required and can use the existing connector after little modification.
4) SPM: Component to be fully re-configured on the new system.
-> Upgrade of RTA component will upgrade the SPM component as well.
5) CUP: Existing workflows will apply as they do not use the "system" as the initiators.
-> right.
To enable AC5.3 to be used with ECC system, you will need to install the RTA of 5.3 for ECC 6.0 system. You can download this RTA from the SAP service market place and then install them. This will ugprade your existing RTA component installed for SAP 4.7 to RTA for ECC6.0.
You can follow instructions on Upgrade guide for more information about the upgrade. Also, there are SAP Notes available which you can use.
Regards, Varun

Similar Messages

  • ECC upgrade impact on data archival

    Friends,
    We are working on the data archival SAP version 4.7, parallely ECC upgrades activities are going on.  We are working on the archive tools like transactions SARA, SARI etc as part of archiving.  Not sure on what changes to the features will be available in the ECC6.0 version and its impact on already archived files.  Can somebody give some inputs/direction?
    thanks
    Nalinikanth.

    Hi,
    Retrieval of Archived data
    1. SAP system support to retrieve data archived from 4.7 system by ECC system. There is no negative impact in retrieving archived data of deferent version in ECC system.
    Advice to take back ups of Field catalog, Archive infostructure in case it is Custom or any additional field added to standard structure.
    2. Some changes in Archive index is there in ECC system -
    In ECC system, if you want to retrieve archived data from FB03 then activate and fill the Archive infostructure, Archive build index will not work.
    This method remains same for Material document and other documents
    In ECC system SAP recommends to use Archive system instead of building archive index table such as ARIX_BKPF...
    Archive Program
    1. All the BC sets to upgrade archiving process are been implemented in ECC system, so you can see some changes in the Write program, Delete program.. or for some archiving object you may also see addition of preprocessing program..
    For example: MM_EKKO in initial released 4.7 version didn't had preprocessing job, Write job variant had option of company code to archive purchase order. Later BC set was released with upgraded programs with Preprocessing program and in Write variant with selection of Purchase organization instead of Company code.
    If you have already implemented latest release of BC sets then in ECC 6.0 will not have any changes otherwise some minor changes you can see.
    Please specify which archiving object with program you are concern with.
    Store Function
    1. In ECC system, SAP has filled up a long standing gap of storing archived data of different company code in separate content repository. This is very much useful when you want to store the archived data of different organization units in different storage repository. This also easy to get rid of data that has completed total retention period from the storage system.
    Remain other functionality remains the same. Please let me know if you have any concern about archiving object that you are using.
    -Thanks,
    Ajay

  • ECC upgrade impact on BI

    Hi Gurus,
    We are currently on BI7 but the R/3 version is 4.7. The R/3 is going to be upgraded to ECC6 shortly. I know this is going to have an impact on BI7 since some of the tables & fields are going to be standard, which might have been customized earlier. Can u give suggestions on the impact on BI and what care needs to be taken from a BI perspective during the ECC upgrade. Also, any doc or pointers which talks about such impact on BI. Points will be awarded accordingly. Thanks for the help in advance.
    Ud

    Hi,
    the following are the activities that I can think of Pre- and Post ECC Upgrade on the BI box.
    Pre-Upgrade
    - ensure that the Delta queue is cleared in RSA7
    - check the PI in ECC6.0
    - stop all loads from BW
    Post-upgrade
    - run Init w/o Data Transfer for deltas
    - check extraction for full & delta loads
    - replicate all data sources in ECC
    - activate all rules thru programs
    Other than this, is there any other activity a BW consultant has to do. Also, would it make any difference to our upgrade approach if the BW system is BW3.5 or BI7? our system is on BI7 currently.
    Additionally, what SAP Notes will have to be applied pre and Post ECC upgrade.
    Would the ECC upgrade have any impact on BI Unicode conversion?
    Also, I am still worried about the change to Data Sources post-upgrade to ECC as we have a lot of customization. how do i find out which fields in the Data Sources have been standardized in ECC?
    Reponses highly appreciated and points duly awarded.
    Uday

  • ECC Upgrade impact on BDC's

    Hi All,
    My question is regarding transaction level changes resulting dfrom ECC upgrade.
    We are upgrading ECC 4.7 to ECC6.0. There are certain BDC's already working in 4.7 and I need know the transction level changes so as to see impact on BDC pragrams.
    I have already tried using SPAU and SPDD for modifications.
    Is this kind of information maintained on help or service-marketplace portals? I checked but could not get the information.
    Thanks and Regds,
    Gaurav

    Hi Gautham,
    The table u suggested gives details on trasnaction names.
    Also the link you have given is about the various issues related to BDC in upgradation process.
    My question is different as to find out the changed at transaction level like ...field changes.... mandatory.....sequesce of fields....
    is this kind of incormation maintained in any help or service marketplace folders....
    I have already tried SPAU and SPDD but don't want to do that for number of transactions.
    Regds,
    Gaurav

  • SAP ECC upgrade from EHP6 to EHP7

    Is  GTS upgrade from NW 7.2 to GTS  7.3  to be mandated as ECC is getting upgraded from  ECC 6.0 EHP6 to  EHP 7 .  Why?

    Hi John,
    Your statement looks a bit misaligned.. There is no GTS 7.3 version, the SAP Netweaver 7.3* application server on which SLL_LEG GTS component sits.
    The underlying Netweaver AS versions between ECC and GTS systems can be different BUT what needs to be the same is the GTS plugin component in ECC and GTS components in GTS system itself, as best practice they should also be on the same support pack level.
    If the ECC upgrade from ehp6 to ehp7 requires you to upgrade SLL_PI gts plugin component in ECC, then in this case you should upgrade SLL_LEG component in GTS system to the same version.
    I personaly dont think its required, but check Service markeplace for, PAM Product-availability-matrix and other ehp 7 requirements..
    Hope this helps,
    Branio

  • SAP ECC Upgrade : Userexit or Related Enhancement been Overwriten

    Hi All,
    Is that anyone get explanation from SAP why during ECC upgrade most of the enhancement been overwritten and need to re-do.
    Thank in advance on your knowledge sharing.
    Trevor Wong.

    Ok. There might be need to do "adjustmens" in case of upgrade conflict, or just simple confirmations of code enhancements in transactions SPAU + SPAU_ENH.
    I think you should find all missing code enhancements there, waiting for adjustment.

  • SAP HR ECC upgrade

    Hi,
    Could someone tell me what will be the role of SAP HR abap developer in SAP ECC upgrade.
    Specially Payroll programming.
    and after the upgrade  is done what kind of development support is required.
    Many thanks
    Swetha

    Hi Swetha,
    ABAPer needs to check all of the user exits and BADIs implemented before in order to check whether any changes need to be done.
    Additionally, if there had been any repairs in the system, these need to be reimplemented after upgrade.
    For further reference please check the following links:
    Re: what are abaper tasks during upgrade to ECC 6.0?
    http://www.sapdev.co.uk/upgrade/ug_tasks.htm
    Regards,
    Dilek

  • Sold-to's missing link to ship-to's - SAP ECC -to CRM data load

    I have recently extended my middleware between my CRM 2007 and SAP ECC systems.  I have adjusted the CRM middleware filters to include a newly created Sales Org that was created in our ECC system.  I'm loading the data from SAP to CRM and the accounts are coming across for this new Sales org however they all seem to be assigned to the Sold to Role and none of the accounts are assigned to Ship to, Bill to or payer roles.  This is despite the fact that PIDE is maintained correctly in SAP ECC. My middleware objects also seem to be fine.  All my other sales orgs worked perfectly in the past. 
    What objects (business, customizing and condition) do i need to need to run to get these relationships into CRM from SAP.
    The main one that I have run is CUSTOMER_MAIN and CUSTOMER_REL
    Any ideas as to what the problem might be?
    Thanks in advance
    eddie

    This issue defintely relates back to our SAP ECC Upgrade
    It looks to me like that any NEW accounts created in SAP (post our SAP ECC Upgrade from SAP 4.7)  and loaded into CRM do not include the relevant account relationships
    That is to say that if an account in SAP say 100001 has 4 sold tos 100002 - 100005, 1 payer 100006 and 1 bill to 100006 then that same account will not have any relationships.  The 7 accounts will be created in CRM but there will be no relationships between them.  All the historical data is fine, any master data that was created prior to the SAP upgrade is unaffected - the relationships exist.  Even if this master data was loaded into CRM after the upgrade.  The issue is with master data created in SAP after the ECC upgrade and when this loaded into CRM the problem is evident. 
    This never came to light during a recent business unit rollout as their master data was created in SAP before the ECC upgrade and came across to CRM without issue.  We only have seen this issue as we are now dealing with a new business unit that has had all its master data created on SAP post the SAP ECC upgrade.  Its this master data that is affected in CRM in terms of missing relationships.
    Any advice would be greatly appreciated.  Has anyone seen this issue before
    Thanks
    Eddie

  • Upgrade of Sourcesystem SAP EHP3 SAP ECC 6.0 to SAP EHP4 SAP ECC 6.0

    Hi,
    I noticed there is a lot of questions on the testing procedures for BI side when Upgrading the source system from R/3 to ECC 6.0. But noticed there aren't many posts on when doing Ehancement Packs. But I believe the process would be more or less the same?
    My project is doing an Upgrade of SAP EHP3 SAP ECC 6.0 Stack03 to SAP EHP4 SAP ECC 6.0 Stack07. BI Side is also upgraded, but I am more interested in the impact of the Upgrade's Source System (ECC) on BI.
    I believe the amount of impact is less as compared to an upgrade from R/3 to ECC, but there still should be impact to BI somehow.
    Basically, from what I have researched, there correct procedure is as below:
    Pre-Upgrade
    1 - Lock users in ECC
    2 - ensure that the Delta queue is cleared in RSA7
    3 - check the PI in ECC6.0 ( What is PI???)
    3 - stop all loads from BW
    Post-upgrade
    1 - Check Source System connections
    2 - replicate all data sources in ECC (when I do a check connection in RSA1 I get the message "No metadata upload since upgrade" which I believe is due to this step not done yet? Is it ok to replicate all datasources??)
    3 - activate all rules thru program (RS_TRANSTRU_ACTIVATE_ALL. Is it ok to activate all transfer strucs?)
    4 - run Init w/o Data Transfer for deltas
    5- run and then check extraction for full & delta loads
    Appreciate if I could your expert inputs on the procedures above? Maybe a more detailed step by step procedure or comments are most welcomed.
    Thanks.

    Additional information:
    I start the upgrade from SAP ECC 6.0 with a dual stack.
    SAP advised me to download the following file to start the upgrade
    SAPehpi_68-10005800.SAR from the SMP
    Download path: Browse our Download Catalog-->  Additional Components --> Upgrade tools --> SAP EHPI Installer --> SAP EHP Installer 7.00.
    Start the upgrade without the jce_policy_zip extension. This was written in note 1302772 .
    Have more luck with it.

  • ITS is not working after the Upgrade to SAP ECC 6.0

    Hi Folks
    ITS is not working as it supposed to be after upgrading to SAP ECC 6.0
    When I try to connect thru ITS i m getting HTTP 404 and HTTP 500 Errors
    Can some one throw some ideas.
    But web AS is running perfectly alright.
    Thanks
    Jay

    Hi Priya,
    You need to Implement the following SNOTE's for these changes.
    Union Budget 2015: As per Finance Bill 2015, the Government has implemented amendments to existing sections and introduced new sections in the Income Tax Act. Changes have been made in the following topics:
    Tax Surcharge Rate
    Increase in Conveyance Allowance
    Section 80
    Sukanya Samriddhi Scheme: The Government has launched this new deposit scheme for the minor girl child. This is a savings scheme that can be opened by the natural (biological) or legal guardian of a girl child aged below 10 years. Related Notes:
    2139208 - Union Budget Changes – 2015
    2138605 - Sec80C: Sukanya Samriddhi Scheme
    Upcoming Developments:
    PF Admin Charges Revision
    Professional Tax for Mizoram & Nagaland states
    Average Rate of Tax
    Regards,
    Venkat Polisetty

  • SAP R/3 System analysis before upgrade 4.6C -- SAP ECC 6.0

    Hello!
    Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
    The following functions should be included in this program:
    - detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
    - comparison against a SAP ERP 6.0 reference system
    - extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
    - syntax analysis of program code with respect of adjustement need
    - quality control of own development
    - control of amount of transports within different company areas
    - control of user information, such a user type, logon date, etc.
    - basic control, whether a sufficient authorization concept is available
    - Identification of objects that should be considered for the archiving in oder to decrease the db-size
    My question are:
    - which tasks can be convered with SAP standard transactions what are the names of the transactions?
    - which effort do I investigate for these tasks?
    Thank you very much!
    regards

    Dear Thom,
    To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
    http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
    http://service.sap.com/releasenotes and  http://service.sap.com/upgrade  for functional changes.
    Need to consider the following things:
    For Reports…it’s custom developed program …so unless there is any kind of change in requirement from the client regarding the layout…nothing needs to be changed…I think it will work fine in ECC 6.0 to…except few things may needs to be changed..so you need to discuss whether they want the reorts as it is right now…or want to change the layout (adding some new info/fields etc) of any report…so u need to modify the program for those…and estimate accordingly…for a medium complexity’s Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing)…so to modify it will be less than that (depending upon the scope of changes)
    Now say for Batch Inputs(interface/Data Migration) using BDC…you need to see how many BDCs are there…again if the field lengths and layouts are not changing…then no need to change anything (except the main thing…..you need to change the obsolete function modules…there are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0…there are some new with enhanced functionality so you need to modify the BDCs…and many cases it happens that the whole transaction screen changes for process…in that case better to develop new BDCs…so you have to consider those parameter…look into and estimate accordingly…modifying a BDC should not take more than 1 PD…
    Now say for Forms…there was no Smart form in 4.6C…form printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart form…in that case…it’s complete new dev…so estimate accordingly…a medium complexity’s form should take 8 PD (FRSTDSCoding+Unit Testing)…you can take it as 10 PD too…even if client wants to keep it is as it was in older version…you have to redevelop the layout in ECC 6.0 again…as form printer is even client dependent…maximum you can copy the program associated with that form in the new version too…and your effort will be saved…again you have to consider if clients wants to change the layout too…
    Now for enhancement…so in that case u need to see individual cases…for a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)…
    One more important thing is that the Unicode Compatibility…this needs to be done….needs to change the code (variable name) accordingly….also Version management tool is used for the standard programs…
    Also pls find the following forums:
    Re: Data Migration from 4.6C to ECC 6.0
    List of transations supported in SAP 4.6c and not in ECC6.0
    Re: Upgradation from 4.6C to ECC  6.0
    Re: what's the advantage to upgrade 4.6c to ECC5.0...
    RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
    Upgrade batch inputs from 4.6C to mySAP ERP 2005
    /thread/317225 [original link is broken]
    Upgrade from SAP R/3 to ECC 6.0
    Hope it will help you.
    Thanks,
    Atin
    <b><b>Reward points if it helps.</b></b>

  • Error while upgrading SAP R/3 Enterprise 4.7 to SAP ECC 5.0

    Dear SAP,
    We are on the process of upgrading SAP R/3 Enterprise 4.7 with Ext:110 to SAP ECC 5.0.But during the VERSCHK_INI phase an error is been thrown showing that
    "The start release configuration :
    SAP_ABA  :620
    SAP_APPL :470
    SAP_BASIS :620
    SAP_HR:470.....is not supported "
    At this stage we decided to continue with this by ignoring the VERSCHK_INI phase,but it gave us a warning that to continue with the next phase(TOOLVERSIOn_INI phase) we require a password.
    we searched in several documents even in the documents along with the cd but was not able to find a password for this or a solution for the error in phase VERSCHK_INI.
    I request team SAP to help us in this regard.Expecting your reply ASAP.
    Thanks and  Regards
    Anantha Raman E.

    Were you able to find a resolution to this problem. We are also having a similar problem in our prepare phase and cannot find anything to help us as yet.
    Thanks,
    Barry Keating

  • Impact of SAP ECC 6.0 in BI 7.0

    Hi all,
    can any one know what type of impact of SAP ECC 6.0 on BI 7.0. if ECC 6.0 as source system for BI?
    kindly provide more info on it
    thanks

    if SAP ECC 6.0 as source system for BW, what is the pre-requisites for BW system has to be required to extract data, and any service pack has to be apply for BW system for adaptability towards ECC 6.0 and also impact of ECC 6.0 towards BW system?

  • Error in PHASE PREP_EXTRACT/PREIMP: Upgrade SAP R/3 4.7 to SAP ECC 6.0 EHP4

    Hello,
    I'm currently in upgrading a SAP R/3 4.7 system to a SAP ECC 6.0 EHP4.
    Therefore I followed the Upgrade Guide from marketplace - installation- and upgrade guides - SAP ERP - SAP ERP 6.0 - SAP Enhancement Package 4 for SAP ERP 6.0 - Upgrade Guide SAP ERP including EHP4 SR1 - Unix on MaxDB.
    I downloaded media from marketplace/swdc - Installations and Upgrades - SAP Application Components - SAP ERP - SAP ERP ENHANCE PACKAGE - EHP4 FOR SAP ERP 6.0 / NW7.01 - Upgrade.
    I'm starting upgrade with upgrade master DVD 51036889_1 and      51036889_2.
    Now upgrade breaks down in phase PREP_EXTRACT/PREIMP with error:
    Severe error(s) occured in phase PREP_EXTRACT/PREIMP!
    Last error code set: Single errors (code <= 8) found in logfile 'PREIMP.ELG'
    PREIMP.ELG says:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    R3trans preimport and RETURN CODE in R710VPE.REX
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
    Kernel is stored in /usr/sap/REX/SYS/exe/run and database is ADA (maxdb).
    File R710VPE.REX says:
    4 EPU201XBEGIN OF SECTION BEING ANALYZED
    4 ETW000 R3trans version 6.13 (release 640 - 17.02.10 - 13:07:00).
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 07.03.2011 - 15:28:36
    4 ETW000 control file: /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
    4 ETW000 > import
    4 ETW000 > file='/usr/sap/REX/upg/abap/bin/R710VPE.SAP'
    4 ETW000 > safeandslow=yes
    4 ETW000 > buffersync =yes
    4 ETW000 > commit     =1048576
    4 ETW000 > importtruncated =yes
    4 ETW000 R3trans was called as follows: R3trans -w /usr/sap/REX/upg/abap/tmp/R710VPE.REX -u 1 /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
    4 ETW000 active unconditional modes: 1
    2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
    4 EPU202XEND OF SECTION BEING ANALYZED
    Can anybody help me out here?
    Regards,
    Julia

    Hello,
    I run 'R3trans -x' command, but there was no problem - connection to database was working.
    Problem was following:
    Before starting the sdt service on host, I set environment variables JAVA_HOME and LD_LIBRARY_PATH for sidadm. That's not neccessary and that was the problem. Without setting these variables it is working now.
    Thanks,
    Julia

  • Upgrade from SAP R/3 4.7 to SAP ECC 6.0 with PSCD and TFA

    Hello!
    I have to upgrade an SAP R/3 4.7 to SAP ECC 6.0.
    We have SAP FI/CO, PSM, IM, FI-AA, PS, with PSCD (FI-CA) as well the special taxes component TFA.
    Is there some special procedures for the the Upgrade with this components (PSCD and TFA)?
    Is there some documentation for the special Uograde procedure as well the normal procedure?
    We use Windows with Oracle.
    Can some one

    PSCD is in ERP a Business function set - see 957295 - PSCD: Renaming PUBLIC_SERVICES business function set, the upgrade should automatically take care that activation.
    Is TFA the tax extension for Ireland? If yes, then the same should be true here.
    Markus

Maybe you are looking for