Вы находитесь на странице: 1из 5

Users Created after AME.

B Do Not Have Proper Grants / Cannot Access AME Application After Applied AME B [ID 375119.1] Modified 07-MAR-2012 Type PROBLEM Status PUBLISHED In this Document Symptoms Cause Solution

Applies to:
Oracle Approvals Management - Version: 11.5.10.2 to 12.1.3 - Release: 11.5.10 to 12.1 Oracle Approvals Management - Version: 11.5.10.2 to 12.1.3 [Release: 11.5.10 to 12.1] Information in this document applies to any platform.

Symptoms
1. Instances where applied AME.B, for new users created with AME responsibilities, get the following message while clicking on any AME responsibility : "User has no functions available to this responsibility". or When attempting to access AME Seeded responsibility (AME Application Administrator) than approvals, the following error occurs: Content-type: text/html; charset=US-ASCII Location: http://erpapp1.hathway.com:8020/oa_servlets/oracle.apps.fnd.sso.AppsLogin?requestUrl=APPSHOMEP AGE&ca ncelUrl=http%3A%2F%2Ferpapp1.hathway.com%3A8020%2Foa_servlets%2Foracle.apps.fnd.sso.AppsL ogin&errTex t=Please%20contact%20the%20Web%20Master%20or%20System%20Administrator.%20ORA01403%3A%20no%20data%20 found%0AORA-06512%3A%20at%20%22APPS.AME_UI%22%2C%20line%20496%0AORA06512%3A%20at%20%22APPS.AME_RULE S_UI%22%2C%20line%206055%0AORA-01403%3A%20no%20data%20found%0A

2. When logging in as the user, and selecting the responsibilities, get the message: "There are no functions available for this responsibility" 3. Approvals Management Business Analyst Responsibility throws following Error: "There are no valid navigations for this responsibility." Cause: Application Object Library was unable to load the menu for the current responsibility.

4. When attempting to sign on using the new AME responsibility Approvals Management Administrator, the following error occurs.

## Detail 0 ## java.sql.SQLException: ORA-01722: invalid number.

Cause
Incorrect Setup to Access Approvals Management Responsibilities. From AME.B the responsibilities are Role based. Use the User Management responsibility to attach roles to the users. Existing employees that had these responsibilities had them automatically converted to roles when AME.B was applied and the 'Approvals Management Post Upgrade Process' concurrent process is run.

Solution
1) From the System Administrator Responsibility, run the concurrent program : "Approvals management Post Upgrade Process" . This Program will attach the new responsibilities to the existing AME Users. The migration is implemented as a concurrent program with Switches. To migrate users, pass 'MIGRATE_USERS' as parameter. To migrate item class usages, pass 'MIGRATE_ITEM_CLASS_USAGES' as parameter. To migrate BOTH pass 'MIGRATE_ALL' as parameter. Ensure that concurrent manager and workflow BES are up before running the program. Also, please ensure that the port is bounced once the Concurrent Program has been executed/run successfully 2) Do not assign these new responsibilities : Approvals Management Business Analyst Approvals Management Administrator directly to a user, this will not work. For the responsibilities to work, AME Roles need to be assigned to the user and data grant has to be given. This is documented in AME.B implementation Guide (Section on AME Roles and Responsibilities and point number 2 under the Section : Implementing Oracle Approvals Management). 3) Follow the steps below to grant AME Access to a User : AME has implemented Role Based Access Model (RBAC) AME.B onwards. The following information would help you in setting up AME in R12. a) AME has 5 seeded roles Approvals Management Administrator Approvals Management Analyst Approvals Management System Viewer Approvals Management System Administrator Approvals Management Process Owner The description of each of the roles can be found in AME.B implementation guide(ame.uk.oracle.com) b) AME can be accessed if sufficient functional grants are available. Each of the above 5 roles has specific set of functional

grants. By assigning the roles to user, the functional grants will be available to user and hence he can access those functions/pages. c) Role can be assigned to user as follows: Login as Administrator Select the responsibility "User Management" Select "Users" screen Search for the user to whom you wish to grant AME roles. In the results table, click on update icon. In the update user page, user details can be seen along with a list of roles available to user Click on "Assign Roles" Select roles from the resulting LOV and click on Apply. d) Each of the 5 seeded AME roles, when assigned to a user, result in "Indirect" assignment of AME responsibilities to the user. e) Now the functional access to user has been successfully setup. f) AME restricts access to "AME Transaction Types" using Data Security. To access AME and use it, user needs to select a transaction type. But the transaction types that the user can select in the AME Dashboard is restricted by data security. g) Access to AME transaction types to a user can be setup as follows: Login as Administrator Select Functional Administrator responsibility Select Grants Tab Click on Create Grant Select "Specific User" as grantee type Select the User as grantee key Select "AME Transaction Types" as object In the next page there will be 3 options for instance type: OPTION 1 All rows: This grants access to all AME Transaction Types to the User This is the most common option and will grant user access to all transaction types. OPTION 2 Instance: This grants access to the AME Transaction Type(1) 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 To get these parameter values, run the following SQL
select application_name, transaction_type_id, application_id from ame_calling_apps

Then use the following values


GRANT PARAMETER PARAMETER VALUE (FROM SQL ABOVE) ------------------- --------------------------------

FND_APPLICATION_ID APPLICATION_ID <== should be a -ve number TRANSACTION_TYPE_ID TRANSACTION_TYPE_ID

OPTION 3 Instance set: This grants access to AME Transaction Types(>=1) specified by the following parameters: * Use the seeded 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, select "AME Calling Applications" as the permission set 9) Review and Finish. NOTE: Please note that it is possible that AME screens fail to appear for the user even after doing the above setup. This can happen if the workflow event system is not properly setup. Please refer to Bug 4721521 for more information. 4) Finally ensure that, the property : jbo.jdbc_bytes_conversion = jbo should be removed or commented in $COMMON_TOP/java/oracle/jbo/server/jboserver.properties. Clear cache, bounce apache server. Retest the issue.

Related

Products

Oracle E-Business Suite > Human Capital Management > Human Resources > Oracle Approvals Management Oracle E-Business Suite > Human Capital Management > Human Resources > Oracle Approvals Management Keywords AME; AME_CALLING_APPS; AME_UI; APACHE; APACHE SERVER; APPLICATION OBJECT LIBRARY; APPROVAL; ASSIGN ROLES; BOUNCE; CONTENT; EMPLOYEE; FUNCTIONAL ADMINISTRATOR; GRANT ACCESS; HTTP; IMPLEMENTATION GUIDES; JAVA.SQL.SQLEXCEPTION; LIBRARY; MANAGEMENT SYSTEM; ORACLE APPROVALS MANAGEMENT; PARAMETER Errors ORA-1722; ORA-6512; ORA-1403 Back to top

Article Rating Rate this document Excellent Good Poor Did this document help you? Yes No Just browsing How easy was it to find this document? Very easy Somewhat easy Not easy Cancel

Comments

Provide feedback for this article. Please use 'Contact Us' for other feedback.

Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support.