SAC (with the BPC-Live connection) uses functionality of BW Integrated Planning (BW-IP), and IP has a strict locking system that prevents one planning session overwriting data of another planning session while that is not yet finished. These sessions are not only related to a UserID. One user can have different sessions open and then also the first session will lock the second. (Try running transaction RSRT in two SAP-GUIs and open the same input ready query --> The second query will only open in read-only mode.)
In one SAC Story a user operates in one session, so you can have a query and a Planning Sequence running on the same data. But if one user opens two stories based on the same BW-data, or the same Story in two browsers, then the second will always lock the first.
This "Only one at a time" is a fundamental principle of BW-IP that cannot be changed. (Ok, technically you can switch off the locking of data, but this is meant to be used only in sandbox systems and during conceptual testing. Never ever in a productive system! Data could get completely destroyed.)
So one planning session first has to save the data. Then a second planning session can start modifying this data.
However, you can enable parallel working in different sessions as far as possible by setting the "lock relevancy" for characteristics.
For more information you can refer to Lock Concept and Lock Management documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.