When this checkbox is checked, in any transaction screen, if user try to enter a new GL Code combination which does not exists in GL_Code_combinations, it will be created automatically behind the scenes... If this checkbox is unchecked, then its the responsibility of GL maintenance team to manully create all the required code combinations
Hi Arvind, I liked the way you have explained the various Oracle financial process in a simple, lucid and detailed manner in all your videos. I have been watching your videos since last few days. Can you please upload some videos on Oracle cash management as well. It will be really helpful. Thanks !
Security rule will restrict the dropdown... Cross validation rules will restrict the data entry even though a specific value is available in dropdown... Both will work together
Hi Arvind If we need to restrict different combination of COA segments by responsibility, it may not be possible I guess since cross-validation rules are COA specific? May be we should opt for a Forms personalization in such cases? Thanks!
Yes, Cross Validation rules are COA specific. If you need to see different COA segments by different responsibility, then the GL: Data Access set profile option assigned to the resp should derive the ledger and hence it should appropriate COA segments under that resp. I believe no form personalization may be required in such cases
Will this Cross-Validation Rule works for sub-ledger also, for Example if we add this code combination to AP distribution then will it give the same error message?
Yes. As mentioned in my video, Cross Validation are COA specific and they work across the instance and across all modules. So, you will get same kind of error message when you try to use the account code combination (which violates Cross Validation rule) in any subledger as well
@@shankark206 Unfortunately CVR rule works only on new code combinations and not on existing code combinations. If there are code combinations which violate CVR rules, then you need to manually disable those code combinations
Helo sir.. I am a follower of you sir and your knowledge levels on Oracle are really very good and it helps me learn a lot...Thank you and keep helping us.. In this case, Should we mandatorily use include rule before using exculde? Can't we use exclude alone for the required ones.
Hi sir....at 4:09 in key flexfield screen allow dynamic inserts is enabled...What is it's significance can you brief
When this checkbox is checked, in any transaction screen, if user try to enter a new GL Code combination which does not exists in GL_Code_combinations, it will be created automatically behind the scenes... If this checkbox is unchecked, then its the responsibility of GL maintenance team to manully create all the required code combinations
In Fusion, how can we EXPORT cross validation rules that are in the system
is it possible to disable the COA segments …. when business client was to go frm 8 segment COA to 6 segments? (that while reducing it)???
That's not recommended... instead default value to say 000 for those segments which are not required and leave these segments enabled
Hi Arvind,
I liked the way you have explained the various Oracle financial process in a simple, lucid and detailed manner in all your videos. I have been watching your videos since last few days. Can you please upload some videos on Oracle cash management as well. It will be really helpful. Thanks !
Sure. Please stay tuned to my channel
As requested, please see below video on Oracle Cash Management:-
ua-cam.com/video/lO3l7ZTGcwg/v-deo.html
All the videos are good, but the volume/voice is very low for all the videos.. its almost 60% of volume if we compare with other videos.
Thanks Vangam for the feedback... I will ensure that volume will be high for all my future videos
i have one question can you explain
in my system i have both security rule and cross validation rule.which will work first?
Security rule will restrict the dropdown... Cross validation rules will restrict the data entry even though a specific value is available in dropdown... Both will work together
thank you
You're welcome
Hi Arvind
If we need to restrict different combination of COA segments by responsibility, it may not be possible I guess since cross-validation rules are COA specific? May be we should opt for a Forms personalization in such cases? Thanks!
Yes, Cross Validation rules are COA specific. If you need to see different COA segments by different responsibility, then the GL: Data Access set profile option assigned to the resp should derive the ledger and hence it should appropriate COA segments under that resp. I believe no form personalization may be required in such cases
Thanks you
Welcome
super explanation
Glad you liked it
Will this Cross-Validation Rule works for sub-ledger also, for Example if we add this code combination to AP distribution then will it give the same error message?
Yes. As mentioned in my video, Cross Validation are COA specific and they work across the instance and across all modules. So, you will get same kind of error message when you try to use the account code combination (which violates Cross Validation rule) in any subledger as well
@@OracleEbizandFusionVideos how to enable CVR to existing code combinations to prevent users to post to particular LE?
@@shankark206 Unfortunately CVR rule works only on new code combinations and not on existing code combinations. If there are code combinations which violate CVR rules, then you need to manually disable those code combinations
@@OracleEbizandFusionVideos thanks. would it be better to Disable, End-date or disable allow posting or one better than the other?
@@shankark206 End dating would be the best option
Helo sir..
I am a follower of you sir and your knowledge levels on Oracle are really very good and it helps me learn a lot...Thank you and keep helping us..
In this case, Should we mandatorily use include rule before using exculde? Can't we use exclude alone for the required ones.
Thanks for your feedback....No... Exclude alone will not work... You need to include everything and then exclude what you do not need....
Thanks a lot ......
You are welcome
Thanks a lot!!!!
Thanks