Components comparison between IFS Applications 2004 AND Applications 7

Foundation1 Component	Applications 2004	Applications 7	Sales Part
IFS Base Server(FNDBAS)	3.1.0	4.0.0	Foundation1 Runtime
IFS Extended Server(FNDEXT)	3.0.0		Foundation1 Runtime
IFS Web Client(FNDWEB)	3.6.0	3.7.0	IFS Web Client Runtime
IFS Data Migration (FNDMIG)	1.0.0	1.1.0	IFS Data Migration
IFS Mobile Client Framework(FNDMOB)	1.0.0	1.1.0	IFS Mobile Client Runtime
RegNet(RegNet)	4.2.3
RegTime(RegTim)	2.2.2
Application Services(APPSRV)	3.4.0	3.5.0	Foundation1 Runtime
Application Services Web(APPSRW)	2.2.0	2.3.0	IFS Web Client Runtime
IFS Administration(FNDADM)		1.0.0	Foundation1 Runtime
IFS Development Tools(FNDDEV)		1.0.0	IFS Foundation1 Development
IFS Terms(Terms)		1.0.0	Foundation1 Runtime

Performance Analyzer Set up for IFS devtool.exe

Prerequisites:
1.Required oracle Sqlplus 8.0 or higher.
2.Required oracle files:
Oracle_Home\rdbms\admin\profload.sql
Oracle_Home\rdbms\admin\proftab.sql
3.Required IFS Foundation files:
F1_Home\Utilities\DbagrantProfiler.sql
F1_Home\Utilities\Performance.apy

Step by Step for Installation :
(examples with win2oo3 server in oracle9.27 and IFS2004-Flux)
1.startup by command mode C:\
2.C:\sqlplus /nolog
3.SQL>connect sys/manager@lgprog as sysdba
connected.
4.SQL>@C:\oracle\ora92\rdbms\admin\profload.sql

5.SQL>@C:\oracle\ora92\rdbms\admin\proftab.sql

6.SQL>@D:\IFS2004_SP5\Utilities\DbagrantProfiler.sql

7.6.SQL>@D:\IFS2004_SP5\Utilities\Performance.apy

8.Open Analyze - Overview in folder Performance Analyzer by executing devtool.exe.

The Internal Logic for Refresh of Security cache

Refreshing the security cache after changing the security settings is very important.
Both security windows Security Permissions and Grant Administration
include the possibility to refresh the cache.

The operation of refreshing the security cache consists of the following steps:

1. Remove method restriction entries in table SECURITY_SYS_TAB where no grants
   for the corresponding package are found in USER_TAB_PRIVS_MADE.
   
   
2. Copy package and view grants from USER_TAB_PRIVS_MADE to SECURITY_SYS_PRIVS_TAB.
   
   
3. Synchronize the contents of FND_USER_ROLE_TAB and SYS.DBA_ROLE_PRIVS (upgrade issue).
   
   
4. Update the table SECURITY_SYS_RPRIVS_COPY_TAB according to SYS.DBA_ROLE_PRIVS and FND_USER_ROLE_TAB to be used
   for performance boost of the next step.
   
   
5. Update the expanded role lists in tables FND_USER_ROLE_RUNTIME_TAB
   and SECURITY_SYS_ROLE_PRIVS_TAB
   by using non-expanded role relations in SYS.DBA_ROLE_PRIVS.
   (above is a example of IFS-2001 etc)
   

Shared Pool Administration IN Admin.exe

1.before Shared Pool administration functionality in IFS/Deployment Administrator can be used, Oracle package DBMS_Shared_Pool has to be installed in the database. This is normal done by executing the files: rdbms/admin/dbmspool.sql and prvtpool.plb as user SYS.
2.
The Shared Pool Administrator can be used to pin Oracle packages in the shared pool preventing them from being swapped out by Oracle.
There are two possible reasons for keeping a package permanently in the shared area:

• a package is large, so there is a risk that it won't fit back if it gets swapped out
  
  
• a package is often executed and swapping it out will increase the overhead

To be kept in the database, the package has to be loaded in the shared area.
The administrator window shows all the packages presently loaded,
so there is little point in running it unless the database has been running for a while.
Through the pop-up menu the packages can be sorted according to size or number of executions.
A Kept package will reside permanently in the shared pool until the Oracle restarts.
If the same packages are to be kept in the shared pool even after a restart,
a script that will load and pin those packages can be created from this tool.
This script should be run immediately after a database restart.

3.path:Installation/SQL File Executor
select pool, name,round(bytes/1024/1024) as mb from v$sgastat order by pool,mb desc

pool name mb
java pool free memory 32
shared pool free memory 332
shared pool sql area 6
shared pool miscellaneous 6
shared pool library cache 5
shared pool PL/SQL MPCODE 3
shared pool 1M buffer 2
shared pool PL/SQL DIANA 2
shared pool dictionary cache 2
shared pool KGLS heap 2
shared pool KQR M PO 1
shared pool message pool freequeue 1
shared pool KSXR receive buffers 1
shared pool KSXR pending messages que 1
shared pool event statistics per sess 1

4. init.ora
....
#######################
# Pools
#######################
java_pool_size =33554432
ared_pool_size =367001600

Custom RMB on Quick Report Results with parameters

Here is an example of one parameters
(Testing result is quite good in IFS2004 Flux !)

step by step as below:

1.create a sql expression on quick report as below:

SELECT a.Contract ,a.Part_No,
IFSAPP.INVENTORY_PART_API.GET_DESCRIPTION(a.contract, a.part_no)"PART_DESC",
round(a.Latest_Purchase_Price,4) "Latest_Purchase_Price",
round(a.Average_Purchase_Price,4)"Average_Purchase_Price"
,b.inventory_value "inventory_value"
from IFSAPP.INVENTORY_PART_CONFIG a,IFSAPP.INVENTORY_PART_UNIT_COST b
where a.part_no like '&PART_NO'
and a.contract=b.contract and a.part_no = b.part_no
and (a.Latest_Purchase_Price >0 or a.Average_Purchase_Price >0)
order by a.contract,a.part_no

2.let QUICK_REPORT_ID is 30

(SELECT QUICK_REPORT_ID,DESCRIPTION
from QUICK_REPORT)

3.In Custom Menu:(new)
--Action Type:SAL code
--window:tbwPurchaseOrderLine

--parameter:
InfoService.QuickReportStart(SalNumberToStrX(30,0) II
'@PART_NO=' IItbwPurchaseOrderLine.colPartNo II'^')

4.Testing okay in IFS2004 Flux

To enable PDF Print use teh following steps (provided by gojose)

1. Printserver.ifm. Set $PDF_DIR and changethe value of $PDF_ACTIVE to TRUE.
2. IFS Admin, Configuration.
Set "Print Server archiving setup" to "DEFAULT OFF".
Set "Path to Pdf-Archive directory" to "PDF_DIR".
3. ASPConfig.ifm -$PDF_ARCHIVE_PATH=PDF_DIR
4. Test

All IFS applications supports Command Line Parameters

All applications created with the IFS/Client framework supports a number of optional command line parameters. These parameters may be specified when starting an application.

Command-line parameters can be specified in three different ways:

• Start the application from a command prompt (using the start command) and specify parameters
• Start the application with the run command in the start menu and specify parameters
• Create a shortcut and specify the application with all parameters in the target field.

All parameters have the general form =. If multiple parameters are specified they should be separated with a space character.

Example:
c:\>start D:\IFS2004_SP5_runtime\Admin.exe DATABASE=LGPROD USER=IFSAPP PASSWORD=IFSAPP