Page History
...
- Find the
CUSTOM.pll
andCUSTOM.plx
files, usually located in your Oracle Applications folder. - Back up the
CUSTOM.pll
andCUSTOM.plx
files. - Verify that no Oracle Applications user is currently logged on to the database or any other database using the
CUSTOM.pll
andCUSTOM.plx
files. Run the
%ORACLE_HOME%\bin\if60gen.exe
tool (sometimes calledifbld60.exe
).Info For Oracle Applications version R12 replace
f60gen
command withfrmcmp.exe
.- In the welcome wizard, select Open an existing form, followed by OK.
- Choose
CUSTOM.pll
and click Open. - Under PL/SQL Libraries > Custom > Program Units right-click on Package body and select the PL/SQL Editor.
- Find the EVENT procedure, locate the first BEGIN after the commented sample code, and insert the following code, starting with BEGIN.
Verify that the script was not inserted into commented sample code. You can easily mistake sample code for real code.
begin
if (event_name='WHEN-NEW-FORM-INSTANCE') then declare
cursor_name integer; rows_processed integer; del char(1) :=
substr(get_application_property(CURRENT_FORM),1,1);
begin
if (del != '/') then del := '\';
end if;
cursor_name := dbms_sql.open_cursor;
dbms_sql.parse(cursor_name,
'begin VERITAS_APPS_LOG( ''F'' , :username ,
:application , :form , NULL) ; end ;' ,1); dbms_sql.bind_variable(cursor_name,':username' , FND_PROFILE.VALUE('USERNAME')); dbms_sql.bind_variable(cursor_name,':application' ,
substr(get_application_property(CURRENT_FORM), instr(get_application_property(CURRENT_FORM),del
,
-1)+1, length(substr( get_application_property(CURRENT_FORM), instr(get_application_property(CURRENT_FORM), del,-1)+1))-4)); dbms_sql.bind_variable(cursor_name,':form' , Name_In('system.current_form'));
rows_processed := dbms_sql.execute(cursor_name);
dbms_sql.close_cursor(cursor_name);
exception
when others then begin dbms_sql.close_cursor(cursor_name); exception
when others then null;
end; end; end if;
exception
when others then null;
end; - Click File > Save.
- Run
%ORACLE_HOME%\bin\ifcmp60.exe
. - Fill in the following fields:
- File
CUSTOM.PLL
(that we changed before) - Userid APPS
- Password APPS password
- Database database name
- Module Type LIBRARY
- Module Access FILE
- File
- Click OK.
Anchor | ||||
---|---|---|---|---|
|
To have an Interpoint for Oracle Applications identify interactive forms in Oracle Applications 11.5 or higher, you must manually update the system profile of Oracle Applications with site-specific initialization code. As a result, Oracle Applications forwards the required information - the user, form, and application name for interactive work and the concurrent program and application name for batch work - to an Interpoint for Oracle Applications.
...
Info |
---|
In this query we expect to have Interpoints' code ( |
To find problematic profiles
...
- Log in to your Oracle database with the APPLSYS account.
- 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'); - Run the following command to correct the errors:
update FND_PROFILE_OPTION_VALUES set PROFILE_OPTION_VALUE =
'begin veritas_custom_profile; end;'
wherePROFILE_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;'
wherelast_update_date=to_date ('13-JUL-75', DD-MON-YY');
- Commit the changes.
...
IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal