Oracle iStore - Hide Tax Exemption

Oracle iStore determines whether to display the tax exempt part of the customer UI in the checkout billing pages based on the Oracle Receivables (AR) settings for Tax Exemptions at Customer level.

Release 11i

To disable the Customer Exemptions flag

Responsibility: Receivables Manager
Navigation: Setup > System > System Options
Go to the Tax Defaults and Rules Tab
Uncheck the "Use Customer Exemptions" field

Release 12

E-Biz Tax Module > Defaults and Controls > Select Operating Unit and Application Receivables > Application Tax Options
Uncheck the Allow overide and entry of Customer exemptions.

To Create / Modify a JSP Page in Oracle iStore

To Create / Modify a JSP Page in Oracle Apps

Link : http://www.mediafire.com/view/?nu6x6p0s3n7nmi2

Clearing JSP cache in R12 (s_jsp_main_mode)

There is a change in the default behaviour of handling JSP cache in R12 as opposed to 11i. Remember, JSPs were handled by Apache Jserv engine in 11i and is being handled by OC4J (10.1.3 AS) in R12.

In 11i, when we clear cache ($COMMON_TOP/_pages) and try to access JSP pages, it gets automatically recompiled. However, thisis not the case in R12 by default.So, in an R12 instance, if you clear _pages and restart apache,you will only get a blank screen since AppsLocalLogin.jsp wouldn’t get compiled by default. You will not even see a new _pages directory.To overcome this, as per Oracle, whenever JSP cache is cleared, we have to run“ojspcompile.pl” to recompile ALL jsp pages in the Application. This will take roughly around 15 to 20 mts. However, in the real world (atleast in the pre-production stage) this is not affordable.

The solution to this is to change the XML file parameter s_jsp_main_mode to a value of “recompile” from the default value of “justrun” and run autoconfig. JSP pages will be recompiled automatically after this change.

Where is OA_HTML defined in R12

OA_HTML is defined in $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config/oc4j.properties

Steps to compile JSP pages in Oracle Apps

Note: - If you are working on any other development Instance. Please confirm from DBA where is your Application server is Installed.

For the CDEV (Development Instance), Application server is installed on CCDEV08.

1)    FTP the JSP file from the server to your local Machine.

Note:- You should Always take the latest file to modify the file. If you are not sure, the file in the CDEV is the latest one then, please take the file from the PVCS.



Note: - FTP the file in the ASCII mode.

Following is the path where you have all the JSP files. (Opened Application).

cd $OA_HTML

Note: - We have to register the JSP page.





2) Make the changes to the JSP file.























3) Delete the JAVA and CLASS files of the JSP file you have modified now.



Note: - JAVA and CLASS files of the JSP file would start with underscore ( _ ) and file name with the extension of .java or .class

Following is the path where you can find all the CLASS and JAVA files.

cd $COMMON_TOP/_pages/_oa__html














4) After Modification, move the file from your local machine to your server.




Note: - FTP the file in the ASCII mode.

Following is the path where you have all the JSP files. (Application).

cd $OA_HTML

Note: - When you try to open the page from any Responsibility in the Application. New JAVA and CLASS files would be created.











5) Bounce back the Apache Server.







Note: - Login into your server with your UserID and then login with Super Userid.

            For the CDEV Instance, Super User ID is aplcdv

The following commands are run after login with Super User “aplcdv” to bounce back the Apache server.

    cd $IAS_HOME/Apache/Apache/bin
    apachectl graceful

**Note: - Bounce backing the Apache Server would affect other actives running on the server. So, please inform your DBA before you bounce back the Apache server.



You will see the Restarted Message after running the file successfully.

Steps to compile JSP pages in iStore

Note: - If you are working on any other development Instance. Please confirm from DBA where is your Application server is Installed.

For the CDEV (Development Instance), Application server is installed on CCDEV08.

1)      FTP the JSP file from the server to your local Machine.

Note:- You should Always take the latest file to modify the file. If you are not sure, the file in the CDEV is the latest one then, please take the file from the PVCS.



Note: - FTP the file in the ASCII mode.

Following is the path where you have all the JSP files. (SAW or I-store module related).

cd $XXCOFI_TOP/comn/XXCOFIhtml











2) Make the changes to the JSP file.






















3) Delete the JAVA and CLASS files of the JSP file you have modified now.



Note: - JAVA and CLASS files of the JSP file would start with underscore ( _ ) and file name with the extension of .java or .class

Following is the path where you can find all the CLASS and JAVA files.

cd $COMMON_TOP/_pages/_xxcofihtml














4) After Modification, move the file from your local machine to your server.




Note: - FTP the file in the ASCII mode.

Following is the path where you have all the JSP files. (SAW or I-store module related).

cd $XXCOFI_TOP/comn/XXCOFIhtml

Note: - When you try to open the page from SAW or I-Store Module. New JAVA and CLASS files would be created.














5) Bounce back the Apache Server.





Note: - Login into your server with your UserID and then login with Super Userid.

            For the CDEV Instance, Super User ID is aplcdv

The following commands are run after login with Super User “aplcdv” to bounce back the Apache server.

Ø      cd $IAS_HOME/Apache/Apache/bin

Ø      apachectl graceful

**Note: - Bounce backing the Apache Server would affect other actives running on the server. So, please inform your DBA before you bounce back the Apache server.



You will see the Restarted Message after running the file successfully.

Create or Modify the JSP page in Application

1) Create the JSP file (new JSP) or for the modification, FTP the file from server to your local machine.
2) Make the changes to the file and FTP back to the server.
3) Delete the old CLASS and JAVA files of the JSP from the server.
4) Bounce Back the Apache Server
Note: - Server path where you have to FTP the JSP file and delete the JAVA and CLASS files of specific JSP file.

(cd $OA_HTML)

Note: - Server path from where you have to delete appropriate java and class files).

(cd $COMMON_TOP/_pages/_oa__html)

5) If you are creating the new JSP file, then you have to register it in the application. If it is new JSP file, then following steps would be a applicable.
i) Create Form
ii) Create Function
iii) Attach it to MENU

Create or Modify the JSP page in SAW (I-Store Module).

1) Create the JSP file (new JSP) or for the modification, FTP the file from server to your local machine.
2) Make the changes to the file and FTP back to the server.
3) Delete the old CLASS and JAVA files of the JSP from the server.
4) Bounce Back the Apache Server
Note: - Server path where you have to FTP the JSP file and delete the JAVA and CLASS files of specific JSP file.
(cd $XXCOFI_TOP/comn/XXCOFIhtml )

Note: - Server path from where you have to delete appropriate java and class files).
(cd $COMMON_TOP/_pages/_xxcofihtml)