AME Setup Responsibilities for Oracle CRMS (R12)

This is how to configure Approvals Management Engine (AME) access in Oracle R12 for CRMS environments using the Role-Based Access Model (RBAC), while keeping all sensitive details removed.

 

 Overview of AME in Oracle R12

Approvals Management Engine (AME) is used to define and manage approval workflows across Oracle applications.
From AME onwards, it follows a Role-Based Access Control (RBAC) model to manage user permissions.

 

Step 1: Seeded AME Roles

AME provides five seeded roles:

1. Approvals Management Administrator
2. Approvals Management Analyst
3. Approvals Management System Viewer
4. Approvals Management System Administrator
5. Approvals Management Process Owner

Each role contains a predefined aset of functional permissions.
Assigning these roles automatically provides access to relevant AME functions.

 

Step 2: Assign AME Roles to a User

Follow these steps to assign AME roles:

1. Log in with System Administrator access
2. Navigate to the User Management responsibility
3. Open Users screen
4. Search for the required user
5. Click Update
6. Select Assign Roles
7. Choose the required AME roles from the list
8. Click Apply

Important Note

When AME roles are assigned:

• Responsibilities are assigned indirectly
• Functional grants are automatically enabled
• User gains access to the AME dashboard and related pages

 

Step 3: Verify Functional Access

Once roles are assigned:

• User will have the required AME permissions
• AME dashboard and functions should be accessible
• If not visible, check workflow configuration

 

 Step 4: Grant Access to AME Transaction Types (Data Security)

AME restricts transaction access using data security.
Users must be granted access to specific transaction types.

Steps to Create a Grant

1. Log in with the Functional Administrator responsibility
2. Navigate to the Grants tab
3. Click Create Grant
4. Select Grantee Type: Specific User
5. Select the required user
6. Select Object: AME Transaction Types

Choose Instance Type

You will see three options:

1. All Rows

• Grants access to all AME transaction types

2. Instance

• Grants access to one specific transaction type
• Requires Application ID and Transaction Type ID

3. Instance Set

• Grants access to multiple transaction types
• Use seeded instance set: AME Transaction Type Instance Set
• Enter parameters as required

Next:

• Select permission set: AME Calling Applications
• Review and Finish

 

 Step 5: Validate Setup

After configuration:

 ✔ User roles assigned
✔ Functional grants enabled
✔ Transaction type access granted
✔ AME dashboard accessible

If AME screens still do not appear:

• Verify Workflow Event System configuration
• Ensure required services are active

 

Best Practices

• Assign only required AME roles (least-privilege access)
• Use Instance-level grants where possible
• Maintain audit/approval compliance
• Document all role assignments