Sep 13, 2012 -- 12:02PM, joergboeke wrote:

Sep 13, 2012 -- 11:57AM, ZAYNASHEV Tim wrote:

Hello gurus!

Regarding Slide 6. Optimize Data Layout Within DB

Any feature to perform repartitioning automatically when the number of max.partions in years reached? Wish to avoid manual maintenance at all.

Regards
Tim

Hi Tim

repartitioning is currently just a manual matter.

What I normally do is partitioning for the next 10 years.

Yes you're right to say whats about the year 11 after the partitioning is outdated.

An idea which comes to my mind is to create a report or extractor view ( for being used in a virtual InfoCube) to spot the partitioning information stored within BW Cube information table ( just send me an email and I can forward the details about the whereabout of such information, I need to check my internal docu)

By using a BW query on this cube you could do some exception reportinh sending you an info when cubes might be outdated

I hope that answers your question

Thanks Joerg. That's enough for a moment.

Sep 13, 2012 -- 12:04PM, M.S. Hein wrote:

Hie Joerg & Raymond.

I have a question. We are hearing some confusion about the authorizations in 7.3. What do you see as benefits of changes to authorizations in the new release?

Thanks.

I am not sure about the " confusion" what exactely you mean.

What is important between upgrading from 3.5 to /.3 and from 7.x to 7.3 is the following.

While running BW 7.x you can decide whether to use the old authorization (RSSM approach) or the new analysis authorization. YOu could even switch for and back.

So plenty of time to test the new concept.

When upgarding from 3.x to 7.3 you NEED TO USE the new analysis authorization concept.

That means you should be aware how to implement and use the new concept.

I often see customers still using old authorization variables in 7.x that have no real use anymore instead of using the new world in apropper way.

I recommend to investigate or tarin yourself with the new authorizations ( maybe on a sandbaox system, or use an experienced consultatnt.

The timeline after upgrading from 3.x to 7.3 is a bit shorter in terms of authorizations

Hopefully this is your expected answer

Hi,

I'm coming back on the delta queues with the five steps you recommended

After step 1 , stop the updater process in R/3 , all data change in R/3 are lost ?

I'm not to understand what is exactly the updater : do you speak about program to transfer data from outbound queues to delta queues ?

where do you see the biggest challenges in BW 7.3 upgrades in general? Can you share your thoughts/experiences on pitfalls and solutions?

Sep 13, 2012 -- 12:27PM, BridgetKotelly wrote:

where do you see the biggest challenges in BW 7.3 upgrades in general? Can you share your thoughts on pitfalls and solutions?

The biggest challanges from the historic point of view were

Authorizations ( #1) because a lot of customers did not think about the loss of the old authorization concept and werent prepared well.

The preparation steps prior to upgrade (#2)

( housekeeping and cleaning of the systems in terms of obslete data and open tarnsports)

A buch of errors ( SAP program features ;)  )that occurred during the early stages of BW7.3 ( its better with the actual version)

The wrong ideas and understandings of fisrt updrading to 7.0 than to 7.3 instead of directly going to 7.3

I have some Problems and its solution noted down and I can share those information with the paticipants.

I will send te list to Kristine and Bridget and they can forward it by tomorrow.

Joerg