cancel
Showing results for 
Search instead for 
Did you mean: 

Right approach to move from BW 7.0 SP27 to BW 7.5 SP3 with existing 3.x dataflows on a non-HANA DB

Former Member
0 Kudos

What would be the right approach to move from BW 7.0  SP27 to BW 7.5 SP3 with existing 3.x data-flows?

When we did a direct upgrade of sandbox from BW 7.0 SP27 to BW7.5 SP3 we have several deactivated / missing transfer rules for 3.x data-flows - especially on the master data dataflows. However someome 3.x dataflows did get activated and working right-away- especially transaction dataflows.

Is upgrading directly from 7.0 SP27 to 7.5 SP3 the right approach or is there a necessity to go via a intermediate 7.0 to 7.3 to 7.5 approach?

Is there a necessity to migrate 3.x dataflows first or at all? For that do we need to be atleast on 7.0 SP32 to get the 'migrate dataflow' option.

Is the SAP_BW_BEFORE_UPGRADE task list using tcode STC01 - a necessity before the upgrade? For that do we need to be atleast on SP31 or implement SAP Note 1734333 before the upgrade?

Being a non-HANA DB and having a lot of 'classic modelling objects' and no SAP 'HANA modelling objects' is it still ok to move to 7.5 SP3 or there is a necessity to convert the modelling objects?

Is it a necessity to go to BW 7.5 to get the Netweaver 7.4 basis component to be at par with rest of the latest versions of ECC, CRM EP Netweaver components?

Thanks in advance for your time BW professionals.

Regards,

Mahesh.N

Accepted Solutions (1)

Accepted Solutions (1)

john_hawk
Active Contributor
0 Kudos

Hi Mahesh,

I'd say that you need to plan on SOMETHING being deactivated or requiring correction post upgrade - this  is normal.

If you have been doing your development in Dev, it should be easy to collect the post-upgrade activations or corrections in a transport, so they may be applied automatically post-upgrade in QA and Production.

Don't forget to mark your question as answered!

Good luck,

John Hawk

Former Member
0 Kudos

Yes, John- that is exactly what we had planned on doing as a work around. But it is good to get a confirmation on this.

Answers (1)

Answers (1)

john_hawk
Active Contributor
0 Kudos

Mahesh,

Generally speaking, the 3.x dataflows work just fine after the upgrade without migrating to 7.x.

Consider ABAP OO. ABAP changed along way to be object oriented. If your update rules are ABAP heavy, test thoroughly. My rule during upgrades is that if i have to touch a 3.x data flow, it is simpler to migrate it to 7.x and make repair in 7.x.

No, you don't need to modify your InfoProviders either. They should work correctly, if not optimally, post-upgrade. It is perfectly acceptable to "clean as you go" , modifying objects as changing business requirements or performance tuning requires you to touch the object.

No, you don't need to execute SAP_BW_BEFORE_UPGRADE before upgrading. However, the upgrade will take longer if you haven't done your housekeeping.

To find out compatible versions, check the Product Availability Matrix

https://apps.support.sap.com/sap/support/pam 

Check your upgrade to fine out the best path. If the upgrade guide allows as direct upgrade, use it.

Good luck,

John Hawk

Former Member
0 Kudos

Thank you for your reply John.

We thought the same way too especially after looking at 2296693 - SAP BW Upgrade Path Finder.

However we did get several 3.x objects deactivated or the transfer rules missing entirely after the upgrade.

That's the reason I was looking at some procedure or steps that SAP has recommended for a 7.0 upgrade to 7.5 upgrade.

Regards,

Mahesh.N

832-253-6264