BW 3.5 to BI 7.0 Upgrade - ABAP OO migration

[Former Member]

We have written all our ABAP routines, update rules, etc in regular ABAP in BW 3.5.

Do we need to migrate all the regular ABAP to ABAP Object Oriented in BI 7.0 ?

Or will the regular ABAP still work in BI 7.0.

Does the new BI 7.0 functionality require ABAP OO ?

Thanks

[Former Member]

Hi,

and in addition:

it pretty much depends on your coding. At least you need to do something about the structures used. ABAP OO isn't that different from what you call regular abap. You have some statements which aren't allowed in the oo-context anymore. But lot of them are obsolete anyway and shouldn't be used in regular abap since a long time like the tables statement or internal tables with header lines....

regards

Siggi

[Former Member]

If you upgrade from 3.x to 7.0,

update rules etc will still work. The same for the routines in the update rules, transfer rules.

However, if you are going to migrate update rules to transformations, routines will have to be written in ABAP OO.

This sounds heavier than it is, really.

Also, you can let the system do the migration itself.

The ABAP code will be rewritten automatically.

This only works in easy setups. Advanced ABAP code, you have to rewrite manually.

There are other programming rules in ABAP OO.

You can do a search on the forums, and also here:

http://help.sap.com/saphelp_nw70/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm

[Former Member]

As explained well above - if you are doing a PURE technical upgrade then OO doesn't matter

It's only in a functional upgrade where you convert update rules to transformations etc that you have to use OO

The cmod etc is still old style ABAP based (although with a slightly tighter checking that 3.5 - ie you can't use bad coding in select options any more - ie EQ on a interval)