SAP BW 3.5 Technical Upgrade

Hi All,
My client is currently on SAP BW 3.5 and they are using Business Objects WEBI and Xcelcius for their Presentation with Infoview. We are planning to upgrade to BI 7.x version. With the upgrade we have some queries which I would appreciate if somebody can revert back.
1. Is portal Necessary if we are using Business objects Infoview for presentation layer?
2. what is the roadmap for SAP Portal and BO Infoview ?
3. Should we go for SAP Portal and do the BO Infoview integration also during the upgrade?
4. What will be the final Presentation layer in future?
5. How does the licensing work if we have SAP BW Licenses, do we need to pay extra for sap portal licenses? do we need to pay for bo infoview licenses if we go for SSO between portal and INfoview as we have more sap bw licenses and less bo infoview licenses.
Rgds
Amit

Hi Manju,
Please check the below links:
Re: Migration from BI 3.5 to BI 7.3
Re: upgrade from sap bw 3.5 to 7.3
Alternatively, post your question in the SAP Business Explorer (BEx) forum to get better response on this.
Thanks,
Abhishek.

Similar Messages

SAP Technical Upgrade Testing

We are doing an upgrade from 4.6 C to ECC 6.0. My question is related to integration testing.
When we upgrade, do we need to compare the test execution results from both the systems i.e. 4.6C as well as ECC 6.0? Does it make any sense? As far as I know, we should only test the upgraded system during integration testing.
Awaiting your replies!

Hi,
You need to test the older version with Newer Upgrade as technical upgrade objective is
One to One Mapping of previous Business process with Upgraded version.
for e.g. Depreciation run for the Assets will give same result in the new upgraded version May be the Display and cosmetic changes are done to the new Program but the results should not differ.
As ECC6.0 has switch framework it may happen that some of the extension is active unknowingly which affects the business process
So it is always recommended to test the existing 4.6c Business process with ECC6.0 environment.
Thanks and Regards
Pushkar Joshi

Technical Upgrade from R/3 4.6 to ECC 6.0

Hi all i have a query regaring system upgrade:
Currently i have 2 systems R/3 4.6: Development(D1), Quality(Q1).
Now this systems needs to be upgraded to ECC 6.0.
First the D1 is going to be copied to a new development(D2).
Then D2 will be upgraded to ECC 6.0.
Here a unicode check and other required modification (code compatibility) to
all the customizing and workbench objects is to be done.
Now a copy of Q1 is to be done in new Quality(Q2).
My requirement is to determine all the transported requests from D1 to Q1 and
then transport the same from D2 to Q2 so that the unidcode complaint objects are transported and they overwrite in the new quality system.
Is this process feasible? If yes, How?
Please suggest.

Hi Himansu,
I am making the assumption that you will as the final step upgrade your production to ECC 6.0 and then transport the Unicode corrected ABAP's from your Q2 environment into Prod, and then D2 and Q2 will become your new production support path while D1 and Q1 is removed. Is this assumption correct?
If so, then the next assumption for your plan is your reason for doing this is to keep the production support path D1->Q1->P1 intact while you are performing the upgrade and Unicode program testing in D2 and Q2.
I am also assuming that you are not doing a unicode upgrade/conversion at the same time, you are just making the code Unicode compliant to prepare for a future Unicode upgrade.
If so your plan will work just fine. To say it a little differently, here are the steps
1. Copy D1 to D2
2. Upgrade D2 to ECC 6.0
3. Run UCCHECK to test your code for compliance and to identify objects that need remediation
4. Fix the code that need fixing, and put it in transports with Q2 as your target system
5. Copy Q1 to Q2
6. Upgrade Q2 to ECC 6.0
7. Transport the converted code from step #4 to Q2
8. Perform thorough acceptance testing of the converted code
Now you can plan for your production cutover. While the above steps occurred, you either had a freeze on any changes to the production landscape, or you manually captured changes that was done in D1 in D2. The upgrade project is complex in itself and will need significant user testing assuming that it is only a technical upgrade with no additional or modified functionality.
If your D2 and Q2 was kept in sync, you can now upgrade your P1 system to ECC 6.0 (no need to copy), and configure your transport routes so that D2 and Q2 are now the new production support systems, then you transport the items in step #4 above from Q2 to the upgraded P1.
Regards
John
[SAP Unicode|http://www.sapunicodeupgrade.com|SAP Unicode]

Technical upgrade from 4.6C MDMP system to ECC 6.0 using CU & UC approach

Hi SAP Experts,
We are embarking on a project for Technical upgrade from SAP R/3 4.6C MDMP system to ECC 6.0 using the CU & UC approach for our Asian operations (comprising of India, Japan, Taiwan & Singapore).
Please share with me the Best Practices you followed in your projects, checklists, DOs, DONTs, typical problems you encountered and the possible safeguards, any other useful information, etc.
Since very little information is available from Organizations who have used the CU & UC upgrade approach successfully, I am raising this in SDN to share your experiences during the Technical upgrade.
All useful information will be surely awarded with suitable points.
Looking for your invaluable inputs which will be a BIG help for our project.
Best regards,
Rajaram

Hello Rajaram!:
It's a very big project, that you have to do in a lot of steps........
If you want sent me a email with the problems and you want.
Regards,
Alfredo.

Issues during technical upgrade from version 4.6C to ECC 6.0

Dear All,
We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
Request to kindly suggest the alternative to carry out the same in ECC 6.0.
Thanks in advance.
Regards,
Dhawal

Hi Akshya,
Please find answers below.
1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
Yes you can.
If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
Yes you can activate it.
3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
After the upgrade and unicode conversion you can install the java stack.
Regards,
Ravi.

Issues during technical upgrade from 4.6c to ecc 6.0

Hi
We are doing a technical upgrade from 4.6C to ECC 6.0. Some transactions in QM module when tested in ECC 6.0 test client give a abap termination message (or dump) and certain transactions like qs42,46, qa18, qs34 etc do not get executed (error = no entry foound for......) and similarly in PP-PI module transactions like C203 have similar problems, even though master data does exist. What should I look for? Can somebody pl. give details on configuration checks and the OSS notes from a functional point of view for a technical upgrade?
For certain transactions I get the error message - "Central system of distribution SM-P06CLNT430_TRUSTED is unreachable RFC destination SM_P06CLNT430_Trusted does not exist" - what does this mean?
thanks
BE

Hi,
1. Have you done successfull installation from 4.6C to ECC 6.0 at the time of PrePare ans SAPUP?
2. Check SP' for QM and PP-PI modules from http://service.sap.com/sp-stacks.
3. Configure RFC connections correctly, SM_<SID>CLNT<No>_Trusted automatically created, not manually.
http://service.sap.com/notes --> search for RFC trusted connections for Ecc 6.0
http://service.sap.com/upgrade.
Regards,
Srini Nookala

Technical Upgrade from XI 3.0 to PI 7.1

Hi,
My client is going for Technical Upgrade from XI 3.0 to PI 7.1 not fresh installation. They are asking for How best we can achieve this. I have gone through Decision making document and upgrade document from SAP. Apart from which please provide me the valuable Inputs like what measures we need to take care before and after upgrade as an XI developer. In our project about 90% of interfaces are having java mapping. will there be any changes to be done after upgrade.
I already gone through below link
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8085e299-718c-2a10-de94-928f62b763ce
https://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/40a0868a-9d40-2b10-8cb4-8e0c53b56655&overridelayout=true
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40a0868a-9d40-2b10-8cb4-8e0c53b56655
Thanks in advance
Venkatesh

you can use this document as your base - http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8085e299-718c-2a10-de94-928f62b763ce?quicklink=index&overridelayout=true
do an upgrade from XI 3.0 to PI 7.1
java mappings will still continue to work.
But you might have to modify some graphical mapping, java proxies and modules if any

Technical upgrade from 4.6c to 6.0ecc with unicode conversion

Hi Experts,
Can you explain me technical upgrade from 4.6c to 6.0ecc with Unicode conversion.
if u got any notes pls send it to [email protected]
vijay

Check these links. Search SDN with Term "Upgradation" you will get lot of links
http://help.sap.com/saphelp_nw04/helpdata/en/16/4b3c88170e11d6999d00508b6b8b11/frameset.htm
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0f9f37c-be11-2a10-3baf-d5d7de5fb78d
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/system%2blandscape%2bconversion
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/project%2bplanning%2b-%2bmdmp%2bsystem
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/communication%2binterfaces
Message was edited by: Jason Lax (Removed link to deleted content)

Config. comparision for technical upgrade

Hi ,
We are upgrading from 4.6c to ECC 6.0 ,this is a technical upgrade .
Do we need to compare the config. of 4.6c to ecc 6.0 ?
If yes then how do we go about it ?

Dear kedar landge,
Hope this helps you.
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh

What production downtime should we expect during the technical upgrade?

Hi,
We are planning for a Upgrade from 4.7 to ECC 600, i need to know how can we able to calculate the downtime for the upgrade?
Thanks.

The production downtime is the period during the technical upgrade when the production system is out of service. The downtime period depends on various factors such as hardware power and size of the tables to be migrated, and is therefore contingent on each individual situation. SAP upgrade technology provides you with two strategy options: downtime-minimized strategy and
Resource-minimized strategy.
Characteristics of the downtime-minimized strategy:
Shorter production downtime
Parallel operation of production system and shadow system that enables the execution of as many upgrade tasks as possible during the uptime of the production system
Higher demand on system resources
Characteristics of the Resource-minimized strategy:
No parallel operation of production system and shadow system
Lower demand on system resources
Increased production downtime
SAP recommends that you perform the upgrade using the downtime-minimized strategy if a short production downtime is required.
For more details refer
http://service.sap.com/instguides
http://service.sap.com/erp
http://service.sap.com/erp-inst
Hope this will help you, do revert if you need further details.
Best Regards,
Sachin.

Technical upgrade to ERP2005 6.0 and CRM2007 with CUA on 640?

We are in the planning stages of a technical upgrade to ERP2005 6.0 and CRM2007. Our CUA system is not being considered for this upgrade; it's currently at kernel release 640, patch level 80, ABAP load 1521, CUA load 15.
I've searched all over for recommendations, and all I've found is this from the SAP Help pages: "Use the most up-to-date system in your system landscape as your central system (if possible with a release status of 4.6C or higher). In this way, the newest functions in CUA are available to you." In Frank's NetWeaver Identity Management 7.0 Technical Overview Presentation, he states "IdM will replace the CUA in the long run, however, SAP will continue to support CUA in its current functionality according to SAP maintenance rules."
Will we have a problem if our CUA system is at a lower release than the rest of our systems?
thanks,
Mary-Anne

possibly not. still i would test the scenario on a sandbox system which is already on ERP 6.0 and another one with CRM2007 on it. you could for that purpose simply add them to your ALE-scenario (BD64). after such a test you can be sure whether everything is still o.k.
that recommendation from SAP makes sense though: distributing from a system which is running on the latest software is preferable, since you would have a source which is likely to be more 'reliable' than the target.
why don't you upgrade your CUA central? what are the reasons for this?

Material Column Invisible in Purchase Order Screen after Technical Upgrade

Hi Freinds,
Subject: MEPO1211-EMATN field invisible in Purchase Order (ME21N)
We are doing an SAP Technical upgrade project from 4.6C to ECC6.0. The 4.6C developement box is upgraded to ECC6.0. I found that the Material Column is missing from the Purchase Order Item.
In the right side of item screen, we can see the configuration icon. I have checked that configuration icon - Administrator - MEPO1211-EMATN - field is enabled in the invisible column.
I tried all the possible ways to disable the tick mark. still problems persists.
please let me know how to disable the tick mark (MEPO1211-EMATN)
Thanks
Ashok

Hi Guys,
I found the Problem. Let me share with you all.
For the Purchase order document Type NB - i found the corresponding field selection NBF.
Then i went to NBF screen layout and enabled the material as optional entry.
I have opened the Purchase order screen (ME21N), material column is diplayed.
Thanks
Ashok

Technical Upgrade

Hi All,
I am new to upgradtion.I am upgrading from 4.6C to ECC6.0.
I am working in ABAP.I want the technical upgrade Procedure.LIke Basis people has done the every thing.They given me the system.What i need to do exactly.What is the procedure i have to follow.
If anybody has the documentation.By seeing that documentation i need to do Technical Upgrade.Please can anybody help me.Please this is very urgent.I will reward you more points.

Following are the activities carried out after Basis activities in a Technical Upgrade -
SPAU & SPDD
During an upgrade or the import of a Support Package, existing objects of the SAP standard are overwritten with the objects redelivered. To help the customer retain the objects modified in a previous release, SAP provides all modified objects which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of transactions SPAU and SPDD. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant supports this process of adopting customer modifications.
In the past, all objects modified by a customer and delivered again by SAP, an IBU or an SAP partner 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.
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
Catch up of Transports
There were some transports moved from DEV to PRD (4.6 c) after the development system was upgraded to ECC 6.0.
To keep both the development systems DEV 4.6c and D60 ECC 6.0 in Sync remediation of the respective objects was done. All the changes w.r.t the latest transport was incorporated in the new upgraded system D60 after comparison with DEV using the Remote Comparison functionality or the SE39 transaction.
DDCHECK
Table enhancement categories
OSS note Note 493387 - Potential effects of table- and structure - extensions
ABAP Fixing of the affected or Obsolete Function modules
Some tables are obsolete in ECC 6.0, moving the data from Obsolete tables to new tables
Some transactions are either changed or outdated or obsolete, or there are some screen changes; BDCs recorded for all such transactions should be re-recorded.
Please refer to the below WIKI page for details on upgrade -
https://wiki.sdn.sap.com/wiki/display/HOME/ERP2005+Upgrade
Hope this helps you.

Crm 5.0 to 7.0 technical upgrade

Hi,
We are performing a sap sap crm upgrade from 5.0 to 7.0(CIC & ICSS). Once the basis done with the technical upgrade of the crm system to 7.0), will the new system be up and running with the standard functionality of 7.0 without any customizing or configuration or is there anything that we need to configure to bring up the system on standard functionality?
If anyone has done similar upgrades, will appreciate your quick reply.
Sumit

Didnt get any answer, closing this thread

Grantor Managment solutions and BCS problem after technical upgrade.

Hello every one,
The current release SAP installation was upgraded to ECC 6.0; this was a technical upgrade and did not replace functionality such as "Former Budgeting" with the new BCS functionality. SAP developed the Grantor Management solution utilizing BCS. BCS utilizes a different table structure from the Former Budgeting functionality. The current tables do not contain the BCS reference points to each other which limits the implementation of Grantor Management in the same instance. There are no plans to upgrade to BCS functionality at this point in time.
what are my options? How can we work around this issue?
Regards
K

Hi,
Thanks for the resposnse.
But when i go through the OSS notes it is provided that there will be performance problem in executing the report.
How to get it solved?
Thanks,
Regards
M.A

SAP BW 3.5 Technical Upgrade

Similar Messages

Maybe you are looking for