To implement AME, you need to carry out the following steps:

1. Install the application.

   AME's installation routines and administration features determine which applications can use AME. Installation and administration are typically jobs for a technical specialist. Installation is generally done only once, and administrative tasks (using AME's Administrator Dashboard) are usually only necessary to enable a new application to use AME, or to access or clear a transaction's error log.

2. Set up AME security by completing the following:

   • Attach the predefined roles to a user or group of users.

     AME uses the Role Based Access Model (RBAC) to provide users access to AME functions. This access model has the following predefined roles:

     Role	Description
     Approvals Management Administrator	Role inherits Process Owner role and System Administrator role. User with this role can create action types and modify default configuration variables.
     Approvals Management Business Analyst	Role provides full access to Business Analyst dashboard pages. Role does not provide access to default configuration variables and create Action Types.
     Approvals Management System Viewer	Role provides view only access to Administrator dashboard pages.
     Approvals Management System Administrator	Role enables users to create, update, or delete transaction types. Users can access exception logs and configuration variables. This role inherits the System Viewer role.
     Approvals Management Process Owner	Role provides view access to all Business Analyst Dashboard view pages.

     The Approvals Management Administrator role inherits all the other roles. Based on your business requirements, you can assign specific roles to users in your enterprise.

     Each of the predefined roles has a specific set of functional grants. The grants provide users access to AME. To enable functional grants, you must assign roles to users using the User Management page. For information about accessing User Management page, see: Oracle E-Business Suite Security Guide.

     Set up user access as follows:

     1. Login as Administrator.

     2. Select the User Management responsibility.

     3. Select the Users page.

     4. Search for the user to whom you wish to grant AME roles.

     5. In the results table, click Update. In the Update User page, you can view user details along with a list of roles available to the user.

     6. Click Assign Roles.

     7. Select the roles from the resulting list and click Apply.

     When you assign any of the five predefined roles to a user, you are indirectly assigning AME responsibilities to the user.

     Note: You can create custom roles to meet your requirements. See: Oracle E-Business Suite Security Guide . For information about permission sets for roles, see: AME Roles and Responsibilities.

   • Grant data access to users.

     As AME restricts access to transaction types using Data Security, you grant users access to the transaction types using the Grants page. Set up user access as follows:

     1. Login as Administrator.

     2. Select the Functional Administrator responsibility.

     3. Select the Grants tab.

     4. Click Create Grant.

     5. Select Specific User as grantee type.

     6. Select the user as grantee key.

     7. Select AME Transaction Types as object:

        1. All rows: This grants access to all AME Transaction Types to the User

        2. Instance: This grants access to a specific AME Transaction Type specified by the following parameters: FND_APPLICATION_ID => Application ID of the application to which the transaction type belongs TRANSACTION_TYPE_ID => Unique identifier of the AME Transaction type within application

        3. Instance set: This grants access to one or more AME Transaction Types specified by the following parameters:

           • Use the predefined instance set AME Transaction Type Instance Set.

           • In the next page, select FND_APPLICATION_ID as Parameter1 and a wild card search string for TRANSACTION_TYPE_ID as Parameter2.

     8. In the next page there will be three options for instance type: select AME Calling Applications as the permission set.

     9. Review and Finish.

     For more information, see: Oracle E-Business Suite Security Guide.

   Note: If you are an existing customer, then you must ensure your existing users have the Approvals Management Business Analyst and Approvals Management Administrator responsibilities. You must run the Approvals Management Post Upgrade Process to migrate existing users to the new responsibilities. See: Running the Approvals Management Post Upgrade Process

3. Set the user profile - AME:Installed

   This user profile is predefined by AME and is available for integrating applications such as Internet Expenses, iProcurement, to make use of. It is set at the application level and can be used by that application to determine if AME is installed and if so what action to take. In some instances this determination is used to decide if AME should be used for the approval process of that application, this is not always the case however. Please review the specific documentation of the integrating application to determine if that application uses this user profile.

4. Configure transaction types.

   An application administrator should review AME's configuration-variable values as soon as AME is installed and its security has been set up. AME has the following kinds of configuration variables:

   • Single-Valued Configuration Variables

     AME's configuration variable distributedEnvironment has a single value for the entire application. This variable describe various aspects of AME's computing environment. You must set its value for AME to function properly.

   • Transaction-Type-Specific Variables

     Other AME configuration variables can have a default value, as well as a value for each transaction type. These variables are:

     • adminApprover

     • allowAllApproverTypes

     • allowAllItemClassRules

     • allowFyiNotifications

     • currencyConversionWindow

     • forwardingBehaviors

     • productionFunctionality

     • purgeFrequency

     • repeatedApprovers

     • rulePriorityModes

     These variables determine many aspects of how AME generates a transaction type's approval processes and are similar to the mandatory attributes. The difference is, their values are always constant for all transactions in the transaction type. Ensure you are satisfied with these variables' default values before using AME.