Lock entry created for items in comparison columns?

[Former Member]

Hi all,

I encountered a problem today in which I assumed the system would behave differently:

We have a planning level with positions 3,4,5,6 in the level restriction (example only!). In the layout we have fixed rows. They show position 1 and 2 as comparison columns, and 3,4,5,6 open for input. Now the system will create a lock entry also for positions 1 and 2.

Unfortunately this creates locking problems for us, as 1 and 2 will at the same time be updated in another layout.

Many thanks in advance for your assistance!

Regards,

Andreas

[Former Member · Accepted solution]

Thanks for the response. The thing about the UPC_DARK2 entry sounds very promising, however I have one question about it:

In the description to the SAP Note it says that there is a restriction "Reference data can be either in the rows or in the columns". Does this mean that the solution will not work if we have both a reference column and a few reference rows?

We are on SP17, so I cannot test this at the moment.

Thanks again for your great replies,

Andreas

[gregor_dieckmann · Accepted solution]

Hello Andreas,

yes, the solution only works if you have reference data either in rows or in columns. The key is that the system needs one characteristic to split the selection into two disjoint parts, one to be locked (and this part should be non-overlapping for different users) and one reference part (unlocked) that can be shared.

I think it should be possible to model the layout in such a way that you can use this new feature.

Regards,

Gregor

[Former Member · Accepted solution]

Unfortunately I think this will be difficult. We have two comparison columns (coming from a reference cube, which holds actuals), and two reference rows. I need to use the new feature for the reference rows. But I cannot do without the reference columns, as I need to point to the reference cube for the actuals data.

Regards,

Andreas

[gregor_dieckmann · Accepted solution]

Hello Andreas,

if you have a layout of the following type it should work:

Leadcolumn (characteristic M1)

1 reference, not in package

2 reference, not in package

3 in package, user specific

4 in package, user specific

.

and in data columns

Keyf1 Keyf1

Area 1 (plan) Area 2 (actuals)

the use note 555849 to make Area 2 a 'reference' area, the

package contains both Area 1 and Area 2 (i.e. no reference colum in terms of the new note). But with note 555849 no lock will be used for

Area 2 at all.

At run time the selection for Area 1 will be locked with

M1: 3, 4, ...

Keyfigure: Keyf1

So all users can share the reference data for charactristic values 1, 2.

Regards,

Gregor

[Former Member]

Hello Andreas,

Generally the locks are created based on the characteristic values being called for in the layout and not on the key figures.

Even though you have set the columns 1 & 2 as comparison, the characteristics being called are being used for columns 3 to 6.

Therefore if you are trying to open a different layout with the same characteristics and trying to update other key figures, the system would lock you out as there is conflict in the characteristic data being called.

Hope this helps.

Sunil

PS: Assigning points is a way of saying thanks

[Former Member]

Thanks Sunil,

I think the locks are more specific. If I look into UPC_ENQUEUE_READ, I see that the characteristic values 1,2,3,4,5,6 are locked. I expected 3,4,5,6 to be locked, as only those values are in the level restriction.

Regards,

Andreas

[former_member93896]

Hello Andreas,

planning layouts use only one database selection. It does not matter if columns or rows are marked as comparison. Everything in the layout will be locked.

Please see SAP note <a href="http://service.sap.com/_{form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=635244/">635244</a> and SAP note <a href="http://service.sap.com/}form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=555849/">555849</a>.

Regards,

Marc

SAP NetWeaver RIG

[gregor_dieckmann]

Hello Andreas,

just for you information in BW-BPS 3.50 SP18 there is a new switch available to split plan data from reference data also in manual planning, cf. note 953803 for details.

Regrads,

Gregor