What could be the cause?

BC Inc. added a new Operating Unit to its existing Multi-Org Access-enabled responsibility. When
users logged in using their existing responsibility, they could not see the new Operating Unit in the
list of values. What could be the cause?

BC Inc. added a new Operating Unit to its existing Multi-Org Access-enabled responsibility. When
users logged in using their existing responsibility, they could not see the new Operating Unit in the
list of values. What could be the cause?

A.
Security List Maintenance was not run.

B.
The Set MO: Operating Unit profile was not defined.

C.
The Set Multi-Org Preferences profile was not defined.

D.
The Set MO: Default Operating Unit profile was not defined.

E.
The Set MO: Security profile was not defined for the responsibility.

Explanation:



Leave a Reply 0

Your email address will not be published. Required fields are marked *