lock BPC application while data loads

[Former Member]

Dear Experts,

Is any of you aware of a solution that coud lock BPC application from logging on while data are loading, i.e. while a process chain is runnig? BPC NW 10.0 verison.

Thanks,

Ralitsa

[Former Member · Accepted solution]

Hi Ralitsa,

Regarding restricting logins application when its offline check your task profiles,

This should not be assigned to users if you want to avoid fresh logins.

But need to check about already logged users as pointed by Vadim. Need to check how to kick them out.

Or you can check application status and task profile roles in your writeback BADI (if you already implemented) for user and reject records directly when user is not authorized to use application offline and application status is offline.

Regards,

Prashant

[Former Member]

Hi Ralitsa,

Can you please clarify what is the business reason behind this requirement? This looks like Embedded feature where you have to change cube to load mode and nobody can plan at that time. Many customers prefer BPC standard approach when users don't have to wait for load to be finished.

I saw 2 cases when similar requirement was brought in.

In the first case, design was made in such a way that users planed on same data that was being loaded. This was just a wrong design and after those two data regions were separated requirement went away.

In the second case, users didn't want to see loaded data until it's verified by Administrator. We made that data invisible until Admin run a Process Chain when it becomes visible.

Problem with you requirement is with users that are already in the system. Should load wait for them to finish their work? You can't kick them out in the middle of what they are doing.

Regards,

Gersh

[gajendra_moond]

I think Locks in SM12 or RS12 can be deleted for logged in users to ensure that even if the data is submitted, it is not saved.

[Former Member]

Dear Gersh,

You are correct about the design. We have many other issues due to that. Redesign proposal is submitted and we are hoping that there would be budget for it next year.

I discussed the issue of already logged on users with the business on Friday. They want that people who are already logged on to be kicked off the system or if we switch the environment offline while they are logged on, when they try to save, not to be able to save. The business decided to go with this approach because at this time there should be no one in the system anyway and users are trained that they should not use the system between certain time range.

Now we have to find out how to change Environment status to offline from the process chain.

[Former Member]

Dear Ralitsa,

That's why consultants are on the project to prevent business from making dangerous decisions:).

Decision your business made can have bad consequences. If you would be able to implement it can you imagine what happens if you kick out a user in a middle of writing data back - unbalanced amounts, damaged Dimensions, etc. And if you think that it's not very probably imagine a long running script that does some data posting can be cancelled in a middle. How much effort it would be to bring the system back to a workable condition.

How about converting cube to Load Mode and load data using BW tools?

Regards,

Gersh

[gajendra_moond]

Hi Ralista

How about kicking out the logged in users and then lock them before loading and then unlock them after loading the data? I understand that it will lock users for everything else. Check this thread:

You can create a custom program as suggested and call that in the process chain to lock and unlock. This might not be the most desired way but it is one of the ways.

[former_member186338]

And what about already connected users?

Vadim

[Former Member]

Hi Vladim,

Yes, this is one scenario which we realized too. We are thinking of saving last refresh date and time and compare to parameter that is modified at start of PC and end.... something of this type... not very clear of the exact solution to this scenario...still analyzing different options for overall solution....

but any suggestions or concerns are most welcome! Thank you for commenting.

[former_member186338]

Please read note http://service.sap.com/sap/support/notes/2037826

It will prevent posting during offline.

And search for other offline related notes.

Vadim

[Former Member]

Hi Ralitsa,

You can try creating program around CL_UJA_APPSET->SET_APPSET_STATUS which update application status to online or offline. Then you can use it as process chain variant while executing processes chain. Call that variant once at the beginning of process chain making application offline and then at the end bringing it online again.

Thanks

Best Regards,

Prashant Vankudre

[Former Member]

Hi Prashant,

We have already tried this option and users were still able to log on and save data. See attached screenshots