This content has been marked as final. Show 7 replies
Markus,1 person found this helpful
I think you are making it more complex than needed.
Why not just alter the users security class to a lower level than the security class assigned to the export?
You can review the user class in the User Maintenance and the export security in the Object Maintenance.
thanks for your quick response.
The problem I have is that this needs to be dependend on another setting.
What I'm basically trying to achieve is the following:
I have some kind of two phases closing process:
In the first phase all users are allowed to load data into HFM.
In the second phase all changes to the data need to be authorized by HQ.
So the only persons to load data into HFM should be from HQ. If HQ rejects the
changes the entities are required to undo the changes in the source system and resubmit the data.
I hope this clarifies the reasons behind my question a little bit better.
Thanks in advance,
How is FDM supposed to know if it is phase 1 or phase 2?
What distinquishes the data inside of FDM?
I use a setting from a DB table which I evaluate within the Event-Scripts in FDM.
So in the EventScripts I can know, based on the evaluation of the DB table, if I'm in Phase I or II.
Based on that knowledge it should be possible to stop the users from exporting.
Can you think of any way on how to achieve that? Maybe even something else but EventScripts?
I think I will do it in a way you suggested above,
but with dynamically updating the permissions of Export in Object Maintenance.
Thanks for your input!
Maybe a helpful suggestion: to prevent certain users to export we are going to use the financial controls (in Metadata>Locations). there you can for instance assign submitters to specific locations, will this help solve your issue?
unfortunatley that's not what I wanted to do.
I already solved my problem like described in the post above.