Page History

...

Correcting problematic profiles

When the Interpoint for Oracle Applications does not correlate some of its information with the Collector agent, the following scenario may be applicable:

The Interpoint for Oracle Applications collects some of its data from the Oracle Applications using the initialization of every form that is declared in the System Profile. The System Profile contains 4 profile levels, one for each level. Listed from the weakest to the strongest are: Site, Application, Responsibility, User. The Interpoints’ code is on the weakest link here, meaning, Site level. When you customize one or more profiles at a stronger level, the code that resides at Site level is hidden.

To find problematic profiles

1. Use the following query:
   select a.profile_option_value, DECODE(a.level_id, 10001, 'Site', 10002, 'Application', 10003, 'Responsibility', 10004, 'User', a.level_id)
as "System Profile Level", a.level_value, to_char (a.last_update_date, 'YYYY-MON-DD') LAST_UPDATE_DATE
from FND_PROFILE_OPTION_VALUES a, FND_PROFILE_OPTIONS b, fnd_profile_options_tl c
where
profile_option_id = b.profile_option_id and profile_option_name = c.profile_option_name and
user_profile_option_name = 'Initialization SQL Statement - Custom' order by a.LEVEL_ID;
2. Add the Interpoints’ code within the profile (By changing the relevant profile in Oracle Applications). I.e. verify that the profile_option_value looks like:
        begin veritas_custom_profile;
     <customer code goes here (or empty)>
     end;
   This query shows all relevant profiles affecting the code.

Correcting typing errors in the system profile

Typing errors in the system profile may prevent Oracle Applications forms from opening, including the system profile form. To validate that there is no other definition that overrides your profile definition and to correct any typing errors, you need to log in to the Oracle database externally using SQL*Plus.

To correct typing errors

1. Log in to your Oracle database with the APPLSYS account.
2. Run the following command to view erroneous text:
        Select * from FND_PROFILE_OPTION_VALUES where PROFILE_OPTION_VALUE like '%veritas%';
   You may search for any expression by replacing '%veritas%' in the where clause with the string you are looking for. For example, to search for the profiles that were entered on July 13, 1975, execute the following command:
        Select * from FND_PROFILE_OPTION_VALUES where last_update_date=to_date ('13-JUL-75', 'DD-MON-YY');
3. Run the following command to correct the errors:
        update FND_PROFILE_OPTION_VALUES set PROFILE_OPTION_VALUE ='begin veritas_custom_profile; end;'
     where PROFILE_OPTION_VALUE like '%veritas%';
   You may update any expression by replacing '%veritas%' in the where clause with the string you are looking for. For example, to update all profiles that were entered on July 13, 1975, execute the following command:
        update FND_PROFILE_OPTION_VALUES set PROFILE_OPTION_VALUE='begin veritas_custom_profile;end;'
     where last_update_date=to_date ('13-JUL-75', DD-MON-YY');
4. Commit the changes.