Showing posts with label 11i-Issue. Show all posts
Showing posts with label 11i-Issue. Show all posts

Monday, September 24, 2007

Further Person Information not Displaying on People | Enter And Maintain Form

Oracle Human Resources - Version: 11.5.10
Issue with Perwshrg.fmb , further person information DDF

Problem:
further person information DFF modifications means display different information are not displaying under the Employment Tab of the People Form.This is restricted functionality.

Solution :
Further person Information flexfield is not a Descriptive Flexifield it's a Developer Descriptive Flexifield. This is a restricted functionality.

Developer Descriptive flexfields are reserved for Development & should not be modified.You can see this flexfield information for 'US' legislation's , in PUI on person form, inthe 'Empolyment' tab,All fields with in this tab belongs to this flexifield.

By
Srinivas Ramineni
Oracle APPS DBA

Provide Access to "AME Tranaction Types" to a user

Hi,
This is Srinivas Ramineni.

These steps flourishes the way to "How to Provide Access to "AME Tranaction Types" to a user

1) AME restricts access to "AME Transaction Types" using Data Security. To access AME and useit,the user needs to select a transaction type. But the transaction types that the user can select inthe AME Dashboard is restricted by data security.

2) 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:
1. All rows: This grants access to all AME Transaction Types to the User
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
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.

In the next page, select "AME Calling Applications" as the permission set
· 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.


If u have any doubts please feel free to contact.

Sunday, September 23, 2007

OPM Profile issue

Hi
Greetings
there is no LOV values like YES or No
there is only options like below

GMF:Use OPM Revenue Account for AR Update
Default : 1
Options :
0 =No
1 = Yes
Description : User OPM Revenue Account.
Recommended Change Levels : Site Level

there is no need to create LOV for profiles .
Default it is "1 " means " yes"
if u want to change it to "NO" use "0"

if u have any doubts feel free to contact.
---Srinivas Ramineni
Oracle APPS DBA

Saturday, September 22, 2007

OPM Profile Option



We are implementing OPM Module. I have one small problem in OPM Profile options.


In Profile Option name GMF: User OPM Revenue Account for AR Update Profile option does not have any list of values.
Actually as per the User guide it should have Yes or No values. Could you please anyone suggest how do we create the LOV for that profile option?


Narendra
Nairobi (Kenya)