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.

Design Tools & Output Technologies - JDE1 (MOSC)

Business Unit Security - Workflow process

Jun 5, 2020 11:12AM edited Jul 18, 2020 5:12AM in Design Tools & Output Technologies - JDE1 (MOSC) 2 commentsAnswered

Hello,

Has anyone had experience with user business unit security as it relates to the workflow process? I'm on 9.0.

Scenario #1:

- 'G' is the general business unit and all employees have access to this.

- The user has BU security ranges AA-AA and G-G and their address book record is in business unit 'AA';

- The approver has BU security ranges AA-AA, G-G and BB-BB and their address book record is in business unit 'BB'.

- When the user submits a credit limit change request, it immediately errors and ends.

The logs showed that the workflow process seems to be looking at the approver's BU security.

1

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