Skip to Content
0
Former Member
Dec 06, 2006 at 02:15 PM

Function API_SEMBPS_SETDATA: Avoiding locks with a reduced ITK_ROW table?

35 Views

Hi folks,

I need to process regularly a value update on the BPS-cube via the function API_SEMBPS_SETDATA. Therefore I'm using a special level with a matching layout and the 0-adhoc-package. The ABAP runs perfectly if no user plans parallel.

The used layout has e.g. the characteristics A, B and C. The values for B are e.g. T1 and T2. If a user plans he always only locks T1 or T2. The idea was that each dataset will be effected sometimes. On average this is would be okay.

Using the SETDATA function with the table ITK_ROW containing data with both values T1 and T2 an error is comprehensible. Therfore I split ITK_ROW to datasets with value T1 and datasets with value T2. With each part I tried the function call. But even if a user only locks e.g. T1 even the function call with ITK_ROW containing only T2 datasets results in an lock error.

Question: Is it possible to avoid a lock on a function call of API_SEMBPS_SETDATA with a reduced ITK_ROW? Or is only the layout and the package/level relevant?

If a reduced ITK_ROW is not supported/without effect for locks: How can I solve that lock issue? A package or level selection is not possible because I don't know the explicit values and count of values for characteristic B.

Thank you for your help.

Carsten