Problem with Work Status!!

[Former Member]

Hi Experts,

We are using BPC 7.5 M, SQL Server 2008, I am facing a problem related to work status as there is a template and when we submit the values through template it shows the error:

ExecuteBaseLogic::some records are rejected by work status

Please guide on this.

Thanks & Regards,

Rohit

[Former Member]

Hi,

We have faced this kind of problem with one of customers. With thorough analysis, we realized that the logic was posting values to the previous periods, whereas the previous periods were already locked.

It might be a similar situation. You need to revisit the default logic.

Hope this helps.

[Former Member]

Hi Nilanjan,

Thanks for your reply, you are right that the logic is posting values to the previous periods, whereas the previous periods are locked but this same behavior is working fine in BPC 5.1 and we are seeing this error now when we upgraded to BPC 7.5.

In which version you have seen this error and any update that something has got changed with Work Status in BPC 7.5.

Thanks & Regards,

Rohit

[former_member186498]

Hello Rohit,

maybe you used '*ignore_status' statement before in your default logic.

Best regards

Roberto

[Former Member]

Hello Roberto,

No I have not used Ignore Status in logic before and nothing got changed in logic as it only got migrated from 5.1 to 7.5, whats a use of "*Ignore status"

Thanks & Regards,

Rohit

[former_member186498]

Hello Rohit,

"*Ignore status" should permit to post datas on locked periods.

Best regards

Roberto

[Former Member]

Hello Roberto,

I got your point but I haven't used "*Ignore status" in 5.1 and I am not getting why same logic is not working in 7.5 and giving this WORK STATUS error.

Thanks & Regards,

Rohit

[Former Member]

Hi Roberto,

I have searched BPC Help but didn't found anything like "ignore status" and also tried writing "ignore status" in script logic but got error saying invalid syntax didn't found "*ignore status" instruction.

Please update.

Thanks & Regards,

Rohit

[former_member186498]

Hello Rohit,

sorry I forgot "_" the instruction is

*IGNORE_STATUS.

Best regards

Roberto

[Former Member]

Hi,

There have been few changes in the design in the 2 versions, so it wont be fair to compare them. If they would have been same, why would anyone start using 7.5, if they already have everything in 5.1.

Secondly, the way the script is behaving, is ideal and realistic. You wouldn't want the script to update any historical values if they are locked, would you?

[Former Member]

Hi Nilanjan,

You are perfectly right but is there a way to confirm that in 5.1 script was allowed to post changes even if workstatus was locked, my question is are these changes documented somewhere.

Thanks for your reply.

Thanks & Regards,

Rohit

[Former Member]

Hi,

I am not very sure. You might want to take a look at the release notes of all the releases (all SPs) starting from 7.0. I am not sure in which release this was introduced.

[Former Member]

Hi Nilanjan,

I unterstand that you are not sure of the documentation of this Work Status behavior but are you sure that in BPC 5.1 when default logic called via template then it does not check for Work Status.

Please Update.

Thanks & Regards,

Rohit

[Former Member]

Hi Rohit,

I really dont remember how it was in 5.1; since it has been quite a long time, I have used it. If you have the access to 5.1, can you check that and let us know.

Coming back to your issue, you can definitely use *IGNORE_STATUS as suggested by another expert, earlier. However, I dont think that is a good option. I am sure the customer wouldnt want to overwrite the data in the historical periods. So, my suggestion would be to re visit the script, and adjust it so that it doesnt post any values in the previous periods.

Hope this helps.

[former_member186498]

Hi Rohit,

I changed BPC from 5.1 sp10 and to 7.5 sp3 last december and I don't must change the script logic, the behaviour doesn't change.

I suggest you *IGNORE_STATUS because you said that before you will post data in the previous period, but I confirm that normally if you lock a period that is because you don't want that any input schedule, package, etc change this data, in this case is better you see again the script logic.

Best regards

Roberto

[Former Member]

Hi Roberto,

Thanks for your reply, I am sure that in BPC 5.1 when default logic is called via template and if there are any rec statement in logic posting value to lock region then it allows to do so. This is happening and I can show this.

Thanks & Regards,

Rohit

[Former Member]

Hi Rohit,

If thats true, then the security in 5.1 was not that strong (which is a known fact). The security in 7.5 is more strong and integrated, and definitely, you wouldnt want the logic to post the values to the previous periods. My suggestion would be to revisit the logic and make the necessary amendments. I wouldnt suggest you to use *IGNORE_STATUS, as it is not a good option.

Hope this helps.

[former_member186498]

Hello Rohit,

the message was generated by the default logic.

Some data that you try to send are in a locked period.

Best regards

Roberto