ETL Should be in BI 7.0 or BW 3.5

[Former Member]

Hi Gurus,

Our project is in its budding stage. Given that BI 7.0 having transformation involved in the ETL process and all the business content is in B.W 3.5 i.e transfer rules and update rules.

In what direction should we go for Master Data and Transaction Data.

For Master Data

Should we migrate all the data sources for Texts and Attributes to 7.0 transformations. In that case didn't we lose the functionality , coding delivered by the business content.

Please explain for each case individually 1) Texts 2) Attributes.

Think about the Major master data like G/L accounts, company code, customer, vendor etc,,,

[dennis_scoville4 · Accepted solution]

I would go BI 7.0 because it will give you much more flexibility, especially in the area of the transformation of data.

[Former Member · Accepted solution]

Please address the issues in going for 7.0, think about Whole data warehouse including core financial areas like G/L , and logistics,,

[former_member184494 · Accepted solution]

Kumar,

There is not binary solution to your question. Ideally implement business content - stabilize it and then migrate the same bit by bit into 7.0 - if you want to install the content - migrate the same and then go live - you are looking at a long time.

Also once you have Bi content in place - you will anyway need to enhance it and the best thing about this approach is that the time to customer is reduced instead of telling the end users that it is going to take X months more because we want to do it in 7.0 ( and for the end user - 3.x and 7.0 are just numbers ..)

[Former Member · Accepted solution]

we asked ourselves the same question for our current project.

We decided to use business content as-is whichmeans some 7.0 BC and a lot of 3.x BC.

Why? It is stable and working fine.

After migrating, which is a lot of work anyhow, we would also have to more testing.

Added value? Zero. When a particular BC object has to be enhance we will probably migrate it.

New things to be built will use the 7.0 possibilities.

Marco

[Former Member · Accepted solution]

Hi Marco,

I m lucky to get response from who were in same boat. Your replies are very valuable to our project.

What you guys did when you are implementing first time.

Your BC is in 3.5 and at that time If you got any enhancements in cubes, you need to change your ETL.

Did you implemented BC having additional enhancements in 3.5 or 7.0.

[former_member184494 · Accepted solution]

Unless you have a compelling case to migrate BC to 7.0 my advice would be to not do it - basically because :

1. SAP is going to deliver it someday

2. When SAP delivers it - we take no responsibility for the code!!! ( this is the best part )

3. The major initiative to migrate the same should be driven from a business perspective rather than " We HAVE to be on 7.0 )..

my 0.02

[former_member184494 · Accepted solution]

One more thing is that SAP also delivers enhancements to Business content all the time which means that when the 7.0 version does finally come out - it looks nowwhere near to the version you have live and you cannot just reinstall the new version.

What you guys did when you are implementing first time -

From what I have seen / done :

We did a 3.x implementation - enhanced the same to meet business requirements and once the dust settles - migrate the same at leisure since it involves understanding the code SAP has delivered - esp for Finance... and then migrating the same to OO for the routines... and Inventory code is nasty in migratig with a lot of inline code saying explicitly not to touch the code!!! - I would not touch the code before I know that the existing 3.x version is live and being used rather than try biting off too much and delaying the go-live.

Sorry for multiple posts : I just came off a discussion on the same and hence sharing my thoughts - can't tell you where the discussion went though...!!!

Edited by: Arun Varadarajan on Jun 5, 2009 2:21 AM

[Former Member · Accepted solution]

Arun, i do agree with you.

So far we had no need to change BC; we Are busy realisation for two weeks now.

I know we will have to do some enhancements in PM and in PS in a few days/weeks time.

As said strategy is if something has to be done in real logic to infoproviders we'll probably choose migrating.

But it is to be considered.

[Former Member · Accepted solution]

Thanks you very much guys ,, That clears my doubts for now.

[former_member184494]

7.0 ETL is better than 3.x IMHO but then most of your business content is not yet available in 7.0 versions meaning that Business content for FI etc are still in 3.x formats...

You can migrate the same to 7.0 but then would involve a l;ot of effort in temr sof converting the code etc... which would go back to effort etc...??

You can migrate the same using the available tools but then not all of them can be migrated smoothly and also the datasource has to be in 7.0 version for you to proceed...

Edited by: Arun Varadarajan on Jun 4, 2009 10:36 PM

[Former Member]

Is there a lot of code conversions involved in moving 3.5 ETL process to 7.0 transformations at Master Data front, for attributes especially.