Documente Academic
Documente Profesional
Documente Cultură
You all know by now that Multi Org model in Oracle Release 12 will be changing. They call it Multi Org Access Control. I
would like to explain to you the reasons behind this change, and how this will impact you. I will also explain to you how
this will not impact you at all [if you don't wish to use MOAC- Multi Org Access Control]
For those that are not familiar with pre-Release12 multiorg model, you must read Link Basics Of Multi Org. That link
explains how the current multi-org model feature works, i.e. prior to Release 12.
Does this mean the payables clerk responsibility will have access to all the operating units?
This is possible now in R12 if that's what your business needs. You can assign a node of organization hierarchy or a list
of operating units to your responsibility. Effectively, you are now able to assign multiple operating units to a single
responsibility. This is made possible either through Organization Hierarchy or by an Organization List.
This sounds very much like HR Security Profiles as we saw in link Oracle HRMS Security Profiles ?
True, in fact Oracle Release12 multi-org model uses Security profiles (so I am told). Read this linked article above to get
your concepts on HRMS security profile clear.
Does this mean, a security profile will be attached to responsibility as profile option?
Correct.
What if I don't wish to implement this enhanced feature? Will this break my existing multi org setup?
Oracle is great when it comes to upgrades. Unless you implement security profile feature, your multi-org will keep
working as pre R12.
Coming back to payables clerk, while keying in the invoice, how will they attach specific invoice they key that invoice
against a specific
operating unit?
By entering value in the operating unit field in the screen. Prior to Release12, this was a hidden column. But now all
screens that use security profile multi-org will have an enter-able field.