Cross validation rule once created would immediately take affect with all the responsibilities that are using the accounting structure(chart of accounts) for which the rule is defined.
Cross Validation Rule that define valid combinations of segment values a user can enter in an account.
Cross-validation rules restrict users from entering invalid combinations of account segment values.
Cross validation rules prohibit invalid account combinations being created thus they are applicable to a combination of segment values. Cross validation rule once created would immediately take affect with all the responsibilities that are using the accounting structure(chart of accounts) for which the rule is defined.
Cross Validation rules restrict the user from entering invalid key-flex field segment value
combinations while data entry. E.g. you may set up a cross validation rule that disallows using department segments with balance sheet accounts.
Cross Validation Rule applies on Segment values.
Cross validation rules prohibit invalid account combinations
Cross validation rule once created would immediately take affect with all the responsibilities
Security rules applies at Value Set level while Cross Validation Rule applies on Segment values
Security Rule determines the accounting transaction user can view at different levels of hierarchy, such as at Site Level -->Application Level --> Responsibility Level --> User level.
Security rules are segment specific and enforce predefined restrictions of a particular segment. After defining a security rule for the security rule to take affect it should be assigned to a responsibility.
Security rules applies at Value Set level while Cross Validation Rule applies on Segment values.
Security Rules that allows restriction on segment values or ranges of segment values for a specific user responsibility
Security rules applies at Value Set level while SR restrict user define segment values
security rule to take affect it should be assigned to a responsibility
Cross Validation Rule that define valid combinations of segment values a user can enter in an account.
Cross-validation rules restrict users from entering invalid combinations of account segment values.
Cross validation rules prohibit invalid account combinations being created thus they are applicable to a combination of segment values. Cross validation rule once created would immediately take affect with all the responsibilities that are using the accounting structure(chart of accounts) for which the rule is defined.
Cross Validation rules restrict the user from entering invalid key-flex field segment value
combinations while data entry. E.g. you may set up a cross validation rule that disallows using department segments with balance sheet accounts.
Cross Validation Rule applies on Segment values.
Cross validation rules prohibit invalid account combinations
Cross validation rule once created would immediately take affect with all the responsibilities
Security rules applies at Value Set level while Cross Validation Rule applies on Segment values
Security Rule determines the accounting transaction user can view at different levels of hierarchy, such as at Site Level -->Application Level --> Responsibility Level --> User level.
Security rules are segment specific and enforce predefined restrictions of a particular segment. After defining a security rule for the security rule to take affect it should be assigned to a responsibility.
Security rules applies at Value Set level while Cross Validation Rule applies on Segment values.
Security Rules that allows restriction on segment values or ranges of segment values for a specific user responsibility
Security rules applies at Value Set level while SR restrict user define segment values
security rule to take affect it should be assigned to a responsibility
No comments:
Post a Comment