Unlocking with API_SEMBPS_REFRESH and API_SEMBPS_POST

[Former Member]

I have two doubts.

When I'm running with an exit the function API_SEMBPS_REFRESH it's unlocking some entries that I see in SM12 but not all. Anyone can give me a possible cause.

Secondly is a doubt about API_SEMBPS_POST. Is this function supposed to store data in the cube? In my case it's not storing anything. Any clues.

Regards. Points always awarded.

[Former Member · Accepted solution]

<FONT FACE = "Tahoma", Font Color = "Blue">

Hi<br>

API_SEMBPS_REFRESH should release lock entries <b>for that particular User and for that particular session</b>. Please pay attention to User ID and Session when you check the lock entries. It is possible that this API is releasing the locks as expected, however there might be some step in your planning sequence etc which immediately creates lock entries again. <br><br>

API_SEMBPS_POST should save data or in other words transfer data records from SEM Buffer to your InfoCube. Does the SAVE button on your web interface save data? This API is as good as that SAVE button.

<br><br>

Hope it helps.<br>

Cheers Abhijit</FONT><FONT FACE = "Verdana", Font Color = "Red">

• Way of saying 'Thanks' in SDN is by assigning Reward Points generously

</FONT>

[Former Member · Accepted solution]

Thanks for your reply.

API_SEMBPS_POST works perfectly. It was just me that didn't test it right at first.

I'm however still having problems with API_SEMBPS_REFRESH. When debugging I see that there is a point when the function unlocks everything. But at the end the system locks again the planning area where the exit function is being ran. In all, I can unlock entries but automatically new locks are created again..even for a planning area that contains a non transactional cube. So the exit can not be executed twice because the second user gets a lock. Any ideas.

Thanks again.

Alberto

[Former Member]

<FONT FACE = "Tahoma", Font Color = "Blue">

Hi<br>

Please check OSS Note - 441384 (Planning Functions: Release Memory). It is possible that this API is not working correctly for you because of Program Error.<br>

<br><br>

Hope it helps.<br>

Cheers Abhijit</FONT><FONT FACE = "Verdana", Font Color = "Red">

• Please assign Reward Points if I deserve them in your opinion

</FONT>

[Former Member]

No. the API is working perfectly. But I believe that appart from releasing all the locked data the function also locks the data where the exit function is running. I would like to verify this with anyone which is familiar with this API_SEMBPS_REFRESH function.

Thanks,

AS

[Former Member]

<FONT FACE = "Tahoma", Font Color = "Blue">

Hi<br>

What selections you are making in the Planning Level where you have this EXIT Function to release locks? This Exit Function is a last step of your Sequence or there are some steps after this?

<br>Ideally, I would expect you to make same selections for which you expect the lock entries to be released.

<br><br>

Hope it helps.<br>

Cheers Abhijit</FONT><FONT FACE = "Verdana", Font Color = "Red">

• Please assign Reward Points if I deserve them in your opinion

</FONT>

[Former Member]

I'm executing the refresh function as a single function in a multiplanning area. I believe that a function always locks data. I'm able to unlock everything i want but at the end the function locks something. I believe that any function will lock the data over where it's running.

I have the oppinion that API_SEMBPS_REFRESH is able to unlock the data locked but also creates its own locks.

Regards,

AS