Reporting Basis Security

Any ideas on how to lock down a user to one or more Reporting Basis in FSM? We thought about using Actor Context, but we don't see a Key Field/Context Property specific to Reporting Basis. We also looked at Global Ledger Security Setup, but the closest option is Chart Account Security.

What we want to do is create a Reporting Basis that uses the same Reporting Chart as our main Reporting Basis, but limit it to only one company in the Company for Basis tab. Then individuals it is assigned to can run an Account Analysis using only the new Reporting Basis and be limited to entries out of only one company.

Find more posts tagged with

Comments

unknown

Hey Stace,

I'm not sure if this is what you are looking for but I was able to create a Context Property for ReportingBasis and assign a value to my actor. I then added the filter syntax shown below to the ReportingBasis selection list and it displayed only the ReportingBasis assigned to my Actor Context. I do not know how you would use this show multiple Reporting Bases but it will limit the Actor to viewing 1 Reporting Basis.

(ReportingBasis = actor.context.ReportingBasis)

If you would like to try this out you can use the steps below:

1) From the Administration Console role select Security > Context Property

2) From the Context Property Screen click the Add icon

3) In the Key Field field select ReportingBasis and click Save.

4) Navigate back to the Context Property of the Actor Context section and assign the ReportingBasis Context Property along with a Reporting Basis value to an Actor.

5) Add the syntax (ReportingBasis = actor.context.ReportingBasis) to the ReportingBasisList

Stace Webley

Thank you, John. That did work to filter the Reporting Basis list. There is still a backdoor for the user though because while it doesn't show it in the list if you type in a different reporting basis it accepts it and works. I thought by adding the actor context there would be a hard stop to keying it in as well. Do you know?

unknown

Since the Context Property for Reporting Basis is not part of the Dimensional Security I am guessing that there is not logic in the BusinessClass to reinforce security for the field. One thing you could try is to add an Exit Rule Configuration to the Add and Update actions for the AccountAnalysisSettings Business Class. An example of these configurations is shown below

Update is an ActionOverride

Exit Rules

constraint (ReportingBasis = actor.context.ReportingBasis)

"Reporting_Basis_Must_Be_<actor.context.ReportingBasis>"

Create is an ActionOverride

Exit Rules

constraint (ReportingBasis = actor.context.ReportingBasis)

"Reporting_Basis_Must_Be_<actor.context.ReportingBasis>"

Stace Webley

Thanks, @john.gallaher! We didn't use the actor context, but we used the exit rules for the create and update actions and hardcoded the values there for the actor. That got us what we needed.

Copyright © 2025 Infor. All rights reserved.