Form Personalization: Restrict the Profile Options LoV on the form FNDPOMPV

Posted by in Oracle EBS
3 Comments

Purpose
The Purpose of this Form Personalization is to limit the access to the profile option settings restricting the LoV of the profile options displayed.

Description
The implementation of this Form Personalization is divided in 2 steps:
1. Restrict the Profile Options List of Values.
2. Hide and Disable the un-needed fields.

Form Personalization Definition
Responsibility: System Administrator
Navigate: Application -> Function
Define a new function that is a copy of the existing ‘Profile System Values Function (FND_FNDPOMPV). This new function will be called XX_FND_FNDSCAUS_MDM:

Once the function is created, it should be added to one of the existing responsibility.

Form Personalization – Main Screen
The standard form FNDPOMPV before the Form Personalization looks like this:

The form FNDPOMPV after the Form Personalization will look like this:

Restrict the Profile Options List of Values
Before to start with the Form Personalization, the following profile options should be set to the user making the Form Personalization:
o ‘FND: Diagnostics’ set to ‘Yes’
o ‘Hide Diagnostics menu entry’ set to ‘No’
o ‘Utilities:Diagnostics’ set to ‘Yes’

From the horizontal menu select: Help -> Diagnostics -> Custom Code -> Personalize

This step needs to be done to avoid querying profile options related the site level.

Value (to be customized)::
START_DATE_ACTIVE <= SYSDATE and NVL(END_DATE_ACTIVE,SYSDATE) >= SYSDATE and ( SITE_ENABLED_FLAG = 'Y' or APP_ENABLED_FLAG = 'Y' or RESP_ENABLED_FLAG = 'Y' or USER_ENABLED_FLAG = 'Y' or SERVER_ENABLED_FLAG = 'Y' or SERVERRESP_ENABLED_FLAG = 'Y' or ORG_ENABLED_FLAG = 'Y') and (USER_PROFILE_OPTION_NAME = 'HZ: Generate Party Number' or USER_PROFILE_OPTION_NAME = 'HZ: Generate Party Site Number' or USER_PROFILE_OPTION_NAME = 'HZ: Maintain Location History' or USER_PROFILE_OPTION_NAME = 'HZ: Allow Update to Standardized Address')

Hide the un-needed fields
After the restriction of the Profile Option LoV, it’s possible to disable the other fields that will not be needed.

If it helps leave your comment or feedback! Thank you!

# # #

3 thoughts

  1. hi,
    I have a requirement to make the field disable.Condition for making field disable is as follows.Let suppose if user creates an invoice with pay group and press ‘save’ button, but now he wanted to change the pay group.so he should be able to do it but only with one responsibility. For other responsibility he should not able to change it.Any suggestions….

  2. Hi,
    this is not really related the profile options form personalization :P
    but you can use the same approach.

    1. Create a new function as copy of the one who let the user creates an invoice with pay group
    2. Add this function to a new responsibility
    3. Enable Diagnostic and Start the personalization
    4. Select by Text the item you want to disable
    5. Set Properity Name: ENTERABLE and Value FALSE

    Hope it helps.
    BR
    Danilo

  3. Chris Nicklin

    November 21, 2013

    Many thanks Danilo, this was exactly what I was looking for – I was unaware you could restrict the LOV by using the DEFAULT_WHERE property – previously I’ve only restricted LOVs by creating a query using a built-in and then applying it to the LOV, the downside of which is that you have to be able to replicate the underlying LOV query, for which you need Forms Builder, which I don’t have.

Reply