Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Projects - EBS (MOSC)

OGA - implement in a separate business unit ?

May 13, 2014 5:28AM edited May 21, 2014 12:00PM in Projects - EBS (MOSC) 2 commentsAnswered

Hi

I noticed that some modules DO NOT WORK with OGA in the same operating unit: eg Project contracts, OTL, ...

Then it is recommended as an option to implement those modules in A SEPARATE BUSINESS UNIT.

Could please explain in detail what it does mean ? Implement in a different operating unit ? Impacts ? Impacts on interfaces ?...

Is it really a recommended approach ?

Thanks, you answer will be very much appreciated.

Norbert

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month