Quantcast
Viewing all articles
Browse latest Browse all 1545

Work status rule violation

Hi,

 

we have just migrated from BPC 7.0 to 10.0 and in the intercompany matching model now users get the error message that their currency translation job fails due to 'Work status rule violation'. In the past we did not have problems with these security and access settings.

 

Each user group can read&write only to their own entity, but can read all data, in order to see the matching figures from the sister companies.

Work status is set as following for data manager:

Unlocked - All

Submitted company - Mgr

Submitted group - Mgr

Approved group - Locked

 

Does this mean now in BPC 10.0 that, if any of the other entities has locked its data already, that another entity cannot run the fx translation properly anymore?

In the currency translation package, we have set the option to 'Yes', when asked whether to check for work status settings before running the package.

 

Would it now be better to set the 'Submitted company' setting in the work status options to 'All'. Or rather create a new 'Submitted intercompany' work status? Or would it not matter, if the users would check the box 'No' in the data package?

 

Or is this a totally other problem at all?

 

Thanks,

Melanie


Viewing all articles
Browse latest Browse all 1545

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>