Impacts on ECC6 Functional Upgrade

We have just technical upgraded our SAP ERP 4.6 to ECC6 recently, we're soon going to perform the functional upgrade of the ECC6.
I would like to check if the ECC6 functional upgrade will have any impact to our existing BW 3.5 system?
Please advice, thanks.

i dont think, the new plugins will impact your BI system. if you go for the technical upgrade, this may break your source system connection and that time you have to do source system restrore connection.
Other than that, no major impacts would be happened in the BI system.

Similar Messages

New for ABAP in functional upgrade from 4.6c to ECC6.0

i want to know the enhancements, additions and changes in the technical side/ABAP , when moved from 4.6c to ECC6.0 in case of FUNCTIONAL UPGRADE only....
our compny has done FUNCTIONAL UPGRADE so far..whats new for technical ppl like us apart from changing bdcs, some missing functions, etc...
thanx,
Naveen Vishal

Hi
Technical upgrade is the fast upgrade without additional functionality but with minor user interface changes to ensure business continuity. In the past, all objects modified by a customer had to be manually re-modified during an upgrade. Now, modifications are either automatically adopted or the system provides you with an assistant for adjusting your modifications to the newly upgraded configuration using transactin SPAU and SPDD.
SPDD: This transaction allows you to adjust modifications to ABAP Dictionary objects during an upgarde.
Using this transaction we can adjust the Domains, Data Elements, Tables, Strcutures, Transparent tables, pooled and cluster tables including their technical settings, indexs of transparent tables. If you adjust data elements that have been changed with the Modification Assistant in an earlier release, the changes can be copied automatically.
Steps to run SPDD:
       1.      1) Start transaction SE03 as user DDIC and choose Administration ® Set system change option
       2.      2) Select Modifiable in the Global setting dialog box.
       3.      3) Choose Continue.
       4.      4) Choose Edit ® Select all.
       5.      5) Save your changes.
       6.      Then log on as a normal user, since user DDIC may not perform any repairs.
SPAU: This transaction allows you to adjust programs, function modules, screens, interfaces, documentation and text elements after an upgrade.
After you adjusted or edited an object, you can use User/Status function to modify the status of the object. Before doing this, you can also add other developers or testers that are allowed to edit the object and create a short note.
Steps to run SPAU:
1) Start transaction SE03 as user DDIC and choose Tools ® Administration ® Set system change option.
       2.      2) Select Modifiablein the Global setting dialog box.
       3.      3) Choose Continue.
       4.      4) Choose Edit ® Select all.
       5.      5) Save your entries.
       6.      Then log on as a normal user, since user DDIC may not perform any repairs.
Other important topics in Technical Upgrade:
Updaring the Development System: Perform the adjust int he development system using SPDD and SPAU transctions and assign to transport requests. The upgrade control program R3up exports the transport that you have marked in a later upgrade phase.
Upgrading the Production System: During this phase, the R3up upgrade control program checks whether there are any change requests registered for transport from the development system to the production system. If this is the case, R3up offers to import the transport automatically, instead of you carrying out adjustments with transactions SPDD/SPAU. If you choose this procedure, you still have the option of stopping SPDD/SPAU to check the changes accepted automatically before they are activated.
If you decide to import a transport automatically, a subsequent analysis checks whether there is an entry in the transport you specified for each modified object found in this SAP System. Only if this is the case is the transport marked as suitable.
If there are more modified objects in the production system than in the test system, they cannot be dealt with by the transport. This means that you have to adjust these objects.
If you had more modified objects in the test system than in the production system and these are also contained in the transport, you import these into the production system with the transport
regards
karthik
Reward points if useful

Functional upgrade from 4.6C to ECC6, changes in Controlling

Hi
We will be doing a functional upgrade from 4.6C to ECC6. I need to know what are the changes in Controlling on ECC6, with specific reference to the Aerospace and Defence Industry Solution. We have completed the technical upgrade.
Thanks
Henry Bekker
[email protected]

Hi
We will be doing a functional upgrade from 4.6C to ECC6. I need to know what are the changes in Controlling on ECC6, with specific reference to the Aerospace and Defence Industry Solution. We have completed the technical upgrade.
Thanks
Henry Bekker
[email protected]

What is the impact of R/3 upgradation from 4.7 to ECC 6 on BI

Dear all,
Can any one tell me what will be the impact of R/3 Upgradation on BI... as we are shortly going to upgrade our R/3 from 4.7 to ECC 6.
Do we need to take any precautions in R/3 and aswell as BI
Please give the information...points will be given
Regards
venu

Hi
Please Refer this as this vll give u the Pros and Cons for upgrade.
Refer
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B
This Wiki contains Rob Moore's ( BW Manager, Edwards Limited) teams experiences in upgrading Business Warehouse System from 3.0B to BW 7.0.
Contents
1 Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
2 Introduction
3 Overview & Scope
4 Drivers
5 Environment
6 Resource & Timescales
7 High Level Plan
8 Summary Task List
8.1 #Support Pack Hike
8.2 #Plug-in installation
8.3 #PREPARE process
8.4 #Dbase upgrades
8.5 #System Upgrade
9 Lessons Learnt
10 Issues & Fixes
10.1 Unfixed Issues
10.2 Fixed Issues
11 Regression Testing Process
11.1 Introduction
11.2 Set up
11.3 Actions
11.4 Security
12 Transport Freeze
13 Web Applications
13.1 Dashboards
13.2 Internet Graphics Server (IGS)
14 Detailed Task Lists
14.1 Support Pack Hike (detail)
14.2 Plug-in installation (detail)
14.3 Dbase upgrades (detail)
14.4 PREPARE Process (detail)
14.5 System Upgrade (detail)
Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
Introduction
This Wiki contains my teams experiences in upgrading our Business Warehouse System from 3.0B to BW 7.0.
Hopefully it will be useful to anyone else who's about to embark on this. If there's anything I've missed or got wrong, then please feel free to edit it or contact me and I'll try to explain.
Rob Moore - BW Manager, Edwards Limited.
Overview & Scope
This was to be a technical upgrade of BW only. The new BW 7.0 web functionality & tool suite which requires the Java stack rather than the ABAP stack was out of scope. We had heard that the latter was where most of the problems with the upgrade lay. Our plan is to wait for this part of BW 7.0 to become more stable. Also it has a big front end change and the business didn't have sufficient resource to cope with that much change management.
Drivers
3.0B at the end of its maintenance
Opportunities to do better reporting
Options to utilise BI Accelerator
Environment
Our R/3 system was at 4.6C and was not going to be upgraded. We have APO at version SCM4.0.
Our BW system is approximately 300 GB, with 125 global users. It was at version 3.0B SP 18
We have Development, Acceptance and Production environments.
Resource & Timescales
The Project ran for 3.5 months from Feb to May 2007. We used the following resources. The percentages are the approx. amount of their time spent on the project.
Project Manager * 1 70%
BW technical team * 3 50%
ABAP coder * 1 10%
SAP Systems Development expert * 1 20%
Basis * 1 25%
High Level Plan
These are the basic areas. We planned to complete this process for each environment in turn, learning our lessons at each stage and incorporating into revised plans for the next environment. However we did the Support Packs and Plug-Ins in quick succession on all environments to keep our full transport path open as long as possible.
Upgrade BW to the minimum support pack.
Install R/3 Plug-ins PI 2004.1
Run PREPARE on BW
Dbase upgrades (Database & SAP Kernel upgrade)
System Upgrade
Summary Task List
This list contains all the basic tasks that we performed. A more detailed check list is shown below for each of the headings.
#Support Pack Hike
We moved only to the minimum acceptable SP as this seemed most likely to avoid any problems with the 3.0B system prior to the upgrade.
Apply OSS 780710 & 485741
Run Baseline for Regression tests
Full Backup
Apply SP's (we were at SP18, going to SP20)
SPAU list review
Regression testing
#Plug-in installation
Apply SAP note 684844
Import and patch Basis plugin PI 2004.1
SPAU list review
#PREPARE process
BW Pre-Prepare tasks
BW - Inconsistent Data fix
Run PREPARE
Review of results
Any showstoppers from PREPARE?
#Dbase upgrades
Database Upgrade (FixPak)
SAP Kernel Upgrade
#System Upgrade
Reverse Transport of Queries
Reconnect DAB & SAB to AAE
Run Baseline for Regression tests
Full Backup
Run the Upgrade
SPAU list review
Regression testing
Lessons Learnt
Testing is all! We picked up on a lot of issues, but would have picked up more if we'd had a full copy of our production environment to test over.
Our approach of doing a full upgrade on each environment before moving to the next one paid dividends in giving us experience of issues and timescales.
Write everything down as you go, so that by the time you get to upgrading production you've got a complete list of what to do.
We succeeded because we had people on our team who had enough experience in Basis and BW to be able to troubleshoot issues and not just read the manual.
The SAP upgrade guide is pretty good, if you can understand what they're on about...
Remember the users! The fact that the loads have been successful doesn't count for anything unless the users can see the data in Excel! There's a tendency to get caught up in the technology and forget that it's all just a means to an end.
Issues & Fixes
I've listed the main issues that we encountered. I have not listed the various issues where Transfer rules became Inactive, DataSources needed replication or we had to reinstall some minor Business Content.
Unfixed Issues
We could not fix these issues, seems like SP 13 will help.
Cant delete individual request from ODS
After PREPARE had been run, if we had a load failure and needed to set an ODS request to Red and delete it, we found that we could not. We raised an OSS with SAP but although they tried hard we couldn't get round it. We reset the PREPARE and still the issue persisted. Ultimately we just lived with the problem for a week until we upgraded production.
Error when trying to save query to itself
Any query with a re-usable structure cannot be saved (more thsan once!)
OSS 975510 fixed the issue in Dev and Acc, but NOT in Production! SP 13 may solve this once it's released.
Warning message when running some queries post-upgrade
Time of calculation Before Aggregation is obsolete. Not a big issue so we haven't fixed this one yet!
Process Chain Scheduling Timing error
Process chains get scheduled for the NEXT day sometimes and has to be manually reset.
See OSS 1016317. Implement SP13 to fix this. We will live with it for now .
Fixed Issues
Duplicate Fiscal Period values in Query
If you open up a drop down box ("Select Filter Value") for Fiscal Year/Period to filter your query, you are presented with duplicate entries for Month & Year.
Due to Fiscal Year Period InfoObject taking data from Master Data not InfoProvider. Thus it picks up all available periods not just Z2.
Auto-Emails being delayed
Emails coming from BW from process chains are delayed 2 hours on BW before being released
Due to userids that send these emails (e.g. ALEREMOTE) being registered on a diffferent timeazone (i.e. CET) from the BW system (i.e. GMT)
Pgm_Not_Found short dump
Whenever a query is run via RRMX or RSRT
Call transaction RS_PERS_ACTIVATE to Activate History and Personalisation
Characteristics not found
When running a query the warning message Characteristic does not exist is displayed for the following: 0TCAACTVT, 0TCAIPROV, 0TCAVALID
We activated the three characteristics listed and the warnings stopped. NO need to make them authorisation-relevant at this stage.(also did 0TCAKYFNM)
System generated Z pgms have disappeared
Post-upgrade the system Z-pgms ceased to exist
Discovered in Development so we compared with pre-upgraded Production and then recreated them or copying them from production.
Conversion issues with some Infoobjects
Data fails to Activate in the ODS targets
For the InfoObjects in question, set the flag so as not to convert the Internal values for these infoobjects
InfoObject has Conversion routine that fails, causing load to fail
The routine prefixes numeric PO Numbers with 0s. SD loads were failing as it was not able to convert the numbers. Presumably the cause of the failure was the running of the Pre-Prepare RSMCNVEXIT pgm.
Check the Tick box in the Update rule to do the conversion prior to loading rather than the other way round.
Requests fail to Activate on numeric data
Request loads OK (different from above issue) but fails to Activate
Forced conversion within the update rules using Alpha routine. Deleted Request and reloaded from PSA.
Database views missing after pre-PREPARE work
Views got deleted from database, although not from data dictionary
Recreated the views in the database using SE14.
Workbook role assignations lost
We lost a few thousand workbook assignments when we transported the role they were attached to into Production
The workbooks did not exist in Development, thus they all went AWOL. We wrote an ABAP program to re-assign them in production
Regression Testing Process
Introduction
We were limited to what we could do here. We didn't have a sandbox environment available. Nor did we have the opportunity to have a replica of our production data to test with, due to lack of disk space in Acceptance and lack of sufficient Basis resource.
Set up
We manually replicated our production process chains into test. We didn't have any legacy InfoPackages to worry about. We asked our super-users for a list of their "Top 10" most important queries and did a reverse transport of the queries from Production back into test (as we do not generally have a dev/acc/prodn process for managing queries, and they are mostly created solely in prodn). We made sure every application was represented. In retrospect we should have done some Workbooks as well, although that didn't give us any problems.
Actions
Prior to the various changes we loaded data via the Process chains and ran the example queries to give ourselves a baseline of data to test against. After the change we ran the same queries again and compared the results against the baseline. We tried to keep R/3 test environments as static as possible during this, although it wasn't always the case & we often had to explain away small changes in the results. After upgrading BW Development we connected it to Acceptance R/3, so that we had pre-upgrade (BW Acceptance) and post-upgrade (BW Development) both taking data from the same place so we could compare and contrast results on both BW systems. We did the same thing once BW Acceptance had been upgrading by connecting it (carefully!) to Production R/3. To get round the lack of disk space we tested by Application and deleted the data once that Application had been signed off. Once we got to System test we involved super-users to sign off some of the testing.
Security
We chose to implement the new security schema rather than choosing the option to stick with old. For us, with a relatively small number of users we felt we could get away with this & if it all went wrong, just temporarily give users a higher level role than they needed. Our security roles are not complex: we have end user, power-user and InfoProvider roles for each BW application, together with some common default roles for all. In the event we simply modified the default "Reports" role that all our users are assigned, transported it and it all went smoothly. Apart from the fact that everyone's workbooks are assigned to this role and so we "lost" them all !
Transport Freeze
Once you've upgraded Development you've lost your transport path. We planned around this as best we could and when absolutely necessary, developed directly in Acceptance or Production, applying those changes back to Development once the project was complete. Depending on what other BW projects you have running this may or may not cause you pain!
Web Applications
Dashboards
We had various dashboards designed via Web Application Designer. All these continued to function on the upgraded system. However there were various formatting changes that occurred e.g. Bar graphs were changed to line graphs, text formats on axes changed etc. SAP provides an upgrade path for moving your Web applications by running various functions. However we took the view that we would simply re-format our dashboards manually, as we didn't have very many to do. Plus the external IGS (see below) powered all our environments and needs upgrading separately as part of the SAP method. Thus we couldn't have tested the SAP path in Development without risking Production. Sticking with manual mods was a lower risk approach for us. We did find we had to re-activate some templates from BC to get some of the reports to continue to work.
Internet Graphics Server (IGS)
We had an external IGS server with v3.0B. Post-upgrade the IGS becomes part of the internal architecture of BW and thge external server is redundant. We found no issues with this; after the upgrade BW simply stops using the external IGS and no separate config was needed.
Detailed Task Lists
Support Pack Hike (detail)
Apply OSS 780710 & 485741
Communicate outage to users
Warning msg on screen
Stop the jobs which extract data into delta queues
Clear the delta queues by loading into BW
Check RSA7 in PAE that delta queues are now empty
Run Baseline for Regression tests
Stop Delta queues
Lock Out users
Full Backup
Apply SP's
Upgrade the SAP kernel from 620 to 640
SPAU list review
Apply OSS Notes 768007 & 861890
Unlock Test users (inc. RFC id's on R/3)
Regression testing
Regression sign-off
Remove warning msg
Unlock users
User communication
Plug-in installation (detail)
Communicate outage to users
Warning msg on screen
Apply SAP note 684844
Lock out users
Full Backup
Empty CRM queues
Import and patch Basis plugin PI 2004.1
SPAU list review
Apply OSS 853130
Switch back on flag in TBE11 (app. BC-MID)
Remove warning msg
Unlock users
User communication
Dbase upgrades
Dbase upgrades (detail)
Communicate outage to users
Warning msg on screen
Run Baseline for Regression tests
Stop the Data extract jobs
Full Backup
Lock Out users
Apply FixPak13SAP to DB2 database
Upgrade the SAP kernel from 620 to 640
Apply OSS 725746 - prevents RSRV short dump
Unlock Test users (inc. RFC id's on R/3)
Regression testing
Regression sign-off
Remove warning msg
Unlock users
User communication
PREPARE Process (detail)
Pre-PREPARE Process
RSDG_ODSO_ACTIVATE
Repair Info objects and recreate the views
Communicate outage to users
Warning msg on screen
Run Baseline for Regression tests
Stop the Data extract jobs
Lock Out users
Full Backup
Run RSMDCNVEXIT Using BSSUPPORT ID
If there conversion process runs longer delay the regular backup
Re-run Baselines and sign off
If there conversion process Fails repeat the steps on Sunday after the regular backup
BW work
Back up customer-specific entries in EDIFCT (note 865142)
Activate all ODS objects
Execute report RSUPGRCHECK with flag "ODS objects" (note 861890)
Check Inconsistent InfoObjects - Upgr Guide 4.4; OSS 46272; Convert Data Classes of InfoCubes - Upgr Guide 4.3
Execute report SAP_FACTVIEWS_RECREATE (note 563201)
Make sure Delta queues are empty (RSA7)
Basis Work
Full Backup of BW
Lock users
Unlock id's RFC id's and designated test users
Confirm backup complete OK
Apply OSS 447341 Convert Inconsistent Characteristic Values - Upgr Guide 4.5
Confirm OK to PREPARE
Run PREPARE
Review of results
System Upgrade (detail)
Communicate outage to users
Process errors from PREPARE
Check disk space availability for PAB
Warning msg on screen
Reverse Transport Queries from PAB to SAB & DAB
Change BW to R/3 connection
Get backup put on hold, for Ops to release later
Ensure Saturday night backup is cancelled
Final run of PREPARE
Run Baseline for Regression tests
Clear Delta Queues
Delete Local Transports
Remove process chains from schedule
Lock Out users (with some exceptions)
Confirm to Ops and Angie that we're ready
Full Backup
Incremental backup of Unix files
UPGRADE "START"
Back up kernel
Unpack latest 700 kernel to upgrade directory
Check ids required for upgrade are unlocked
Check no outstanding updates
Turn off DB2 archiving
Open up the client for changes
Stop saposcol, & delete from exe directory
Run the Upgrade
Execute the saproot.sh script
Perform the database-specific actions
Perform follow-up activities for the SAP kernel
Reimport additional programs
Import Support Packages
Call transaction SGEN to generate ABAP loads
Transport Management System (TMS)
Handover to BW Team
SPAU list review
Apply OSS Notes from SPAU
Process Function Module XXL_FULL_API (part of SPAU)
Restore table EDIFCT (if required)
Transport Fixes from our BW Issue list
Convert the chart settings - manually
Perform activities in the Authorization Area
Activate hierarchy versions
Update the where-used list
Execute the conversion program for the product master
Transport New roles to PAB
Unlock selected users
Regression testing
Regression sign-off
Go / No Go decision
Restore if required
Remove warning msg
Tell Ops that the CR is now complete
Lock down PAB
Unlock users
User communication
Perform the follow-up activities for SAP Solution Manager
Reschedule background jobs
Reschedule weekly backup on Ctrl-M
Drinks all round.
Vendors mentioned: dBase
Hope this helps.

Impact of ECC 6 Upgrade on BI7.0

Hi Experts,
We are on BI 7.0 ( Netweaver 2004S ) and Source system is ECC5 . Our company is in the process of Technical Upgrade from ECC5 to ECC6 with unicode and Ehp4.
Current setup is
BI 7.0 SP 19 Non Unicode Oracle 10g
ECC 5 Non Unicode Oracle 10g
I would like to know the Impact of ECC6 upgrade on my BI system.
1) We have lot of customization in BI extractor .
2) Various Abap routines written for transformation . will there be any change for unicode.
3) Is there any impact on deltas or Do we need to reinitialise the deltas.
Thanks,

Re: ECC upgrade impact on BI
testing in BW for ECC upgrade
Re: ECC upgrade impact on BI
Go through these threads, sure it would help you.

Doubts in functional upgradation from 3.x to 7.0.

Hi All,
I have some doubts in functional upgradation from 3.x to 7.0.
After migration of Transfer rules, update rules ( between the ods & cube also) & datasource.
1). Cube & ods have filed which is added like enhanced field, do we have to do anything after migration for that filed.
2). Is the Z object also will get migrated automatically or not ( i have zfield in the datasource).
3). If i have a routines in the trans rules & update rules, what has to be done for these routines
4). How the custom reports, deliverd reports and workbooks will get migrated.
5). Macros in the web templets ( is the macros coding in the web templets also will get migrated auto matically r do we need to rewrite the coding).
6). Is the migration steps are same for the all SD, MM, FI datasources.

1. this should not be a problem
2. IO is not needed to be migrated, it is not changed so much between 3x. and 7.x
3. routines & update rules in the trans rules are migrated automatically, see
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/f00e2696d24c5fe10000000a155369/frameset.htm
https://wiki.sdn.sap.com/wiki/display/BI/Migrationof3.xobjectstoBI7.0
4. reports are to be migrated manually, see http://wiki.sdn.sap.com/wiki/display/BI/Migrationof3.xBExQueriestoBI7.0-Useful+Tips
5. see https://wiki.sdn.sap.com/wiki/display/BI/QueriesorWorkbooksMigration-ErrorsandFixes
6. in general yes.

ECC6.0 Upgrade and BW Extractors

Hi Experts,
We are doing a Source system upgrade from 4.6c to ECC6.0 just a Technical upgrade. Can you please let me know if we need to delete all the delta queues and re-initialize delta.
Following are the 4.6c Pre- Export Activities in relation BW.
1. Lock the users
2. Clear the entire delta queues in RSA7 (till we achieve - 0 records in BW) and make sure no outbound queues are empty in SMQ1
3. Delete Set -up table data.
4. Reshedule V3 Jobs
5. ReSchedule - BW process chains
After upgrading to ECC6.0
1. SM59 connections with new system.
2. Restore Source System connections in RSA1
3. Replicate DS and Activate Transfer Structure. (In relation to BW: we have done the technical upgrade from 3.x to BI7.0 (but the datasoucre and data flow are still 3.x).
After all Post processing of ECC6.0 Upgrade activities, the source system is only available to users for posting the transaction.
Please let me know if we need to delete all the delta queues and re - initialize delta.
1.We are not installing any new business content extractors from ECC6.0 - Just using same 4.6c extractors and structures.
2.And consider that no users post any transaction after clearing the delta queues in RSA7.
Appreciate your feedback,

Hello Subbu,
There is no need to reinitialize the extractors, the steps you mentioned in your original post are enough, the reason
for these steps is to make sure that there is no data left in sm13, lbwq, ras7, setup tables etc, you need to run the related infopackages twice on the BW side to clear the BW repeat part of the queue in RSA7, if you have a doubt that this was
not done you can goto rsa7, select the queue and on the next screen you can check if there is any data available in the
delta repeat part of the queue.
The reason for the step is that that the upgrade could potentially change an extract structure for a datasource and then if you
have data in the old format it may not be possible to upload it in the old format.
I repeat though there is NO need to delete the current entries in RSA7 and reinitialize.
Best Regards,
Des

ALV Layouts are missing in ECC6 after upgrade

Dear Friends,
we have an issue of missing ALV Layouts in ECC6 after upgrade of ECC6 from 4.7 version
For example, we have a custom table ZRCILOT, data displayed using tocde se16, but when we check layout are missing in ECC6 but the same exist in 4.7 version.
please check the attached screen-shots.
kindly suggest, is there any possibility to retrive it.
Thanks,
Munvar Basha.

Hello
Variants should be preserved by the upgrade...
You could export/import layout using the report from the here under note
Regards
551178 - FAQ ALV Layout
During the upgrade of or when importing Support Packages?
Answer: Layouts created by the customer are retained and you can continue to use them.
643330 - ALV layout: Importing and exporting layouts

Check List for Functional Upgrade from 4.7 to ECC 6.0

Hi Gurus,
Cany anybody tell me what is the check list for SAP SD Functional Upgrade from 4.7 to ECC 6.0.?
My Email : [email protected]
Points for sure for useful answer
Venkat
Edited by: Venkat Goteti on Feb 4, 2008 5:34 AM

If it is possible can you send me file to [email protected]

Functional Upgrade Assessment help required

Hi ,
Anyone can help me out in functional upgrade assessment process . What is the tool for it and what is alternative methods . This is required for 4.7 to ecc 6.00 .
Regards
RB

Hi,
Functional upgrade :
Is built on the technical upgrade, the functional upgrade provides in addition the opportunity to implement new functionalities in area like FI,HR,Logistics ..,this upgrade type also represents an opportunity to maximize the use of SAP standard functionalities by replacing custom modifications and consolidate instance or systems.
Regards,
Madhu

Upgrade from 4.6 to ECC 5.0 Functional Upgrade

HI Friends,
We are upgrading from 4.6 to ECC 5.0 Functional Upgrade, with New G/L Functionality, i would like to know what are the pre requistics for performing this upgrade and along with check list.
Thanks in Advance
Satish

Hi Satish,
Now i am sending some URL for Functional upgrade
May be those are all useful toyou
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/transactionsChangedinECC6.0
http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/
Regards
Surya

BI Sizing for Functional Upgrade

One query for which I could not get any clarification.
We are planning for a functional upgrade of BI 7.0 to new functionalities.
In the quicksizer table (say for cubes), do I need to inlude:
a) All the EXISTING cubes/ ODS, dimensions, chars and KF, OR
b) ONLY the NEW cubes/ ODS , dimensions, chars and KF, OR
c) All EXISTING + NEW Cubes
Though 'a' does not look like ok, but clarity between 'b' and 'c' is important, as there are 90 cubes, and 180 ODS in the system. Counting everything manually is a pain, and very time consuming. There is no report, could not find this in any data table either. Only option left is metadata repository (one by one objects), if needs option 'a' or 'c'.
Regards
Manish Madhav

Check following:
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=85000722
http://wiki.sdn.sap.com/wiki/display/BI/UpgradefromBW3.XtoBI7.0+%28SP13%29
Testing of SAP BW system after migration from OS Unix to windows
there are many more other here on SDN.
BR
m./

BI Functional Upgrade

Hi All,
Our project recently underwent BW 3.5 to BI 7 technical upgrade. Now we intend to go for the Functional upgrade.
Please suggest Action plan or procedure to carry out the Functional upgrade. We want to transform our current 3.5 objects to 7.0 instead of creating them newly in 7.0 environment.
Please help.Thanks.
Vivek

Hi Vivek,
Check here..
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60ecc07d-3a4b-2b10-ef83-c988e6ecabf6
http://gnanamax.com/Documents/BI%207.0%20Functional%20Upgrade%20-%20Migration%20points.pdf
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742
Thanks,
Vijay.

Impacted Object List - when upgrade

When a customer upgrade from E1 8.10 to E1 8.12, he should know the impact over his customization on standard objects. Where can he get the consolidated list of impacted objects by this upgrade?

Hi,
There is a guide (7MB) available on MetaLink3 that lists all changes to ALL objects. The one I came across is JD Edwards EnterpriseOne Programmer's Guide - Xe to 8.12
You can find them in:
Knowledge > Browse Home > JD Edwards EnterpriseOne > All Products Information > Documentation - Install & Updates > All Products > Implementation Guides & Updates > Browse Results
Good luck
Greg

What is a functional upgrade?

When I was doing upgrade, I just went thru the guide and notes available on SMP.
Now people are talking about functional upgrade and technical upgrade.
I am not sure what is a functional upgrade.
Thanks if you can help. Regards.

"Functional upgrade" is that what it means, upgrade functionality (in sense of new functionality for MM, SD etc.) vs. "technical upgrade" which is just an upgrade of the underlying technology without changing functionality.
Markus

Impacts on ECC6 Functional Upgrade

Similar Messages

Maybe you are looking for