Can you explain the Advantage and disadvantage of GL Segment Level security? I heard segment level security can require lots of maintenance. Which one is better : Data access sets or Segment value security rules? Thank you.
Data access sets restricts the access of ledgers and if your requirement is to restrict the access of GL Segment values, then you need to go for GL security rules
Hi. The Security Rules in Cloud works like in EBS for Company segment value? For example, there's a Primary Ledger with 40 Companies, a rule is defined for Company 01 and is applied to all responsibilities that works with Company 01 and avoid the user indicate a different value in Company segment. How does it should be defined in Cloud? Thanks in advance. Regards.
@@OracleEbizandFusionVideos Ok, thanks a lot. How a Security Rule can be defined for Company segment? The Ledger has 40 Companies. So an user can enter for any company, to avoid errors, the Company needs Security rules to ensure the correct accounting, it means, if the user enter a transaction for Company 04, and by error in the account combination types 08 in the Company segment, a warning message should indicate the error. Is it clear? Thanks a lot.
Does this work for Accounts payable roles? How can we restrict the access to the company values while creating Invoice. I would like to give access to only one company value. Is it possible? Please advise.
Unfortunately, its not possible to restrict... You can see the journal but you cannot see those journal lines which has GL segment values for which you do not have access as per the security rules
@@OracleEbizandFusionVideos Thanks for the reply. Can you please advice on any Alternate if any? My COA setup is 1 Business Unit and 45 Department. And we need restricted view access at Department level since we have customer data on DFF's on the receipt page.
Please see below my video on the difference between Cross Validation rules and security rules... This video is on ebs, but concept wise its same whether EBS or Fusion ua-cam.com/video/bV6KzddJSWI/v-deo.html
I think no separate video is required on Allow dynamic combination... If you check the checkbox of "Allow Dynamic combination" during Segment structure creation, segment combinations are dynamically created automatically
Thank you soo much for your detailed explanation.
You are welcome!
Thanks for such a informational class.
Glad it was helpful!
👍
Thanks
Thanks!
Welcome!
can you make some more vedios on AGIS and fusion tax,SLA...thnx again for doing vedios for us
Sure I will
Nice
Thanks
Can you explain the Advantage and disadvantage of GL Segment Level security? I heard segment level security can require lots of maintenance. Which one is better : Data access sets or Segment value security rules?
Thank you.
Data access sets restricts the access of ledgers and if your requirement is to restrict the access of GL Segment values, then you need to go for GL security rules
Will this help in restricting create accounting BU-wise? If we Have 2 BUs both have different balancing segments?
Yes
Could pls make video on Fusion Finance role matrix with privileges
Sure
Hi. The Security Rules in Cloud works like in EBS for Company segment value?
For example, there's a Primary Ledger with 40 Companies, a rule is defined for Company 01 and is applied to all responsibilities that works with Company 01 and avoid the user indicate a different value in Company segment. How does it should be defined in Cloud?
Thanks in advance.
Regards.
Sorry, your question is not clear.. Can you reconfirm your requirement from Cloud perspective
@@OracleEbizandFusionVideos Ok, thanks a lot. How a Security Rule can be defined for Company segment? The Ledger has 40 Companies. So an user can enter for any company, to avoid errors, the Company needs Security rules to ensure the correct accounting, it means, if the user enter a transaction for Company 04, and by error in the account combination types 08 in the Company segment, a warning message should indicate the error.
Is it clear?
Thanks a lot.
What is difference between security rule and cross validation rules
Refer the below where i explained the difference between Security rule and Cross validation rules:-
ua-cam.com/video/bV6KzddJSWI/v-deo.html
security rules is for restricting segment value set and cross validation is for restricting code combination.
Does this work for Accounts payable roles? How can we restrict the access to the company values while creating Invoice. I would like to give access to only one company value. Is it possible? Please advise.
Yes, you can follow the same steps for any role including Accounts Payable role
But here when u go to manage Journal, you can view other cost center journals. Can we restrict that as well?
Unfortunately, its not possible to restrict... You can see the journal but you cannot see those journal lines which has GL segment values for which you do not have access as per the security rules
@@OracleEbizandFusionVideos Thanks for the reply. Can you please advice on any Alternate if any? My COA setup is 1 Business Unit and 45 Department. And we need restricted view access at Department level since we have customer data on DFF's on the receipt page.
What is the difference between segment security and cvr
Please see below my video on the difference between Cross Validation rules and security rules... This video is on ebs, but concept wise its same whether EBS or Fusion
ua-cam.com/video/bV6KzddJSWI/v-deo.html
@@OracleEbizandFusionVideos thanks.. Please make video for allow dynamic combination
I think no separate video is required on Allow dynamic combination... If you check the checkbox of "Allow Dynamic combination" during Segment structure creation, segment combinations are dynamically created automatically
The screen display is very small. unable to see the application, properly
Thanks for your feedback. I tried to play this video on my laptop and i can see the entire application properly.