In fresh R12 (12.1.3) implementation MO: Default Operating Unit profile option not working as expect
My customer did not set MO: Default Operating Unit profile option at both responsibility and user level. However, when they try to submit any concurrent program (for e.g. 'PRC: Distribute Labor Costs'); sometimes Operating Unit parameter defaults to one of the OUs.
Into 'PRC: Distribute Labor Costs' program - on the Request Tab - Operating Unit Mode is set to Single
Issue is not consistently reproducible. However, customer has definitely seen it happening without finding any cause for it and it happens for all concurrent programs, for all PA responsibilities.
Profile option value set against 'MO: Security Profile' does provide access to OU 'UK_Sita INK UK Ltd_2001_OU'. However, MO: Default Operating Unit is set to NULL. Therefore, expectation is that operating unit should never be defaulted, which is not consistently observed.