Printer and Pasta configuration on Oracle Applications

Setting up printer in Linux OS (Remote printer configuration)

- Run printtool as root

Illustration I: Printtool Command in Linux

Click new from the popup

Adding a New Print Queue
Here I gave name as HPLaser2105 and short description as HPLaserJet printer in Abdulla Machine (Just to identify)

Defining a Print Queue
You select queue type from the drop-down combo box (Networked Windows (SMB))

Select Queue Type
You click specify from the window.
Select Windows SMB

Here is the configuration window

Configuration - Printer residing Machine
It is finished with configuring. (It will be like (specified))
Configuration - Note the word (Specified)
Next Select printer model, Here I selected PCL6/PCL XL Printer
Note for PCL from Provider

Next Test Print from the printer (It should be printed!) else review the steps.
Test Page Print

After configuration the printer configuration will be like this.
Finish Printer Configuration

You should share, and make the printer as default by clicking edit.

Now the Applications Configuration:

Login as sysadmin and navigate to system administrator then Install:Printer
Then navigate to Driver. Here I created HPLASER2105 (Printer type)
Selected SRW driver as L
Driver method as command and driver method parameters as Spool File
Arguments as
: lp –c –d$PROFILES$.PRINTER –n$PROFILES$.CONC_COPIES –t"$PROFILES$.TITLE" $PROFILES$.FILENAME
To test the argument, please run this command in os command

$lp –c –d -n1 –t"Print Test"

Here I used (example)
lp –c –dHPlaser2105 –n1 –t"Print Test" sqlnet.log

Command Line : Printer command for Linux (telnet)

The printer should work. This is the command we are going to pass as argument in Oracle Apps

Define Printer Driver from SYSADMIN -> Install Print. Provide SRW Driver as L for Landscape
You next navigate to

Install printer -> style
You query for Landscape with SRW driver as L

Look for SRW Driver L for Landscape

Then move to Printer Types
Here you have to define a new type called Hplaser2105 and description as PCL

Create a new Printer TYPE
You select as HPPD, HPW, LANDSCAPE, LANDWIDE,PORTRAIT, PORTRAITLASERCHECK, RL1PAPER styles and correspondence driver files with HPLJ4.

Now. You register the printer
Install:Printer-> Register

Registering Printer
Here I have defined the printer as HPLASER2105, Selected type as HPLASER2105 and Description as Windows Remote Printer Configuration.

Set Profile option for Printer at site level – Most important.

That’s all, we completed. Now
1. Bounce the concurrent Service. It is most important. Whenever, you are doing modification with printer, you should do bouncing the concurrent service.

2. Now run a concurrent request to print a report

3. Here Selected Active users

Print Test with any report (Here I used Active Users)
Click Options.
There you select copies as 1.

Then submit with OK
Now, the concurrent manager should complete with status completed normal. Review the log file.
If any thing happened in middle, please review the steps. Thats All.. Finished Printer configuration in Oracle Applications.

Installing PASTA (FNDPSTAX)
Pasta is Oracle Application utility to convert text report files to Post Script so that these can be printed by PostScript Printers. Executable name for Pasta is FNDPSTAX. For various printing options via Pasta, you can use pasta configuration file called as pasta.cfg

The pasta.cfg is there in $FND_TOP/resource.

Copy the Pasta.cfg to Pasta_(Your printername).cfg. (Oracle recommends to copy the name to your printer name) PASTA makes it easy to customize your printing configuration very easy. So use the OS Printer name to define the Pasta.
1. Replace printer_name parameter in pasta.cfg as one with your OS printer name. Here my printer name is HPlaser2105
The command lp –c –d{printername} should print with command line.
Please check before you make changes with your pasta.cfg.
Screen Shot.

Save and exit.
Login to Oracle Apps as System admin
Navigation Path: Install -> Printer ->Driver -> create a driver, PASTA_PORTRAIT. There will be default PASTA-DRIVERS in built with Oracle Apps, We can use them.
For Portrait -> use SRW driver as P
For LANDSCAPE -> use SRW driver as L
For LANDWIDE -> use SRW driver as LW
You please check the Spool File and program name as FNDPSTAX.
Next:
Install -> Printer -> Type
Here I have created PASTA_POSTSCRIPT_HPLASER2105 with all the drivers.
Then you register.
Install -> Printer -> Register.
Save and Exit.

Restart your concurrent Manager (Important)

Check with Active Reports
You please note, the language I selected As Arabic and PASTA as the printer. Submit the request, It should completed normal. In case any problem in the middle, then review the steps.

Cheers!!!

Enable Event level Trace in Oracle Applications

We need to generate the trace for some application user (either Apps 11i or E-business suite R12). In this case when a user connects to an application its very difficult to track the session.

For this reason we have a profile option, which can be set to generate trace file for any event we want within the application.

Follow the below steps for enabling the event level tracing within an application.

1) Login to application and go to “System Administrator” responsibility.

2) Navigate to “Profile -> System”

3) In the user field, enter the name of user you want to enable tracing for. This will be your application user.

4) On the profile search screen search for “Initialization SQL Statement - Custom” profile.

5) When the profile is shown you can set the value as

begin

fnd_ctl.fnd_sess_ctl(”,”,’TRUE’,'TRUE’,'LOG’,'ALTER SESSION SET EVENTS=”10046 TRACE NAME CONTEXT FOREVER, LEVEL 12” tracefile_identifier=”AppsTrace_10046”’); end;

All the quotes are single quote here. You can just copy and paste the profile value.

6) DO NOT SAVE THE PROFILE

7) In another browser window, login as the user you are going to trace and prepare to reproduce the problem

8 ) Once you are ready to reproduce the problem, go back to the Applications Forms and Save the profile change

9) Reproduce the problem

10) Back in the Applications form, set profile to null so it does not trace anymore and Save the change

11) The trace will be located in the user_dump_dest. The trace can be identified using the trace identifier we have set - “AppsTrace_10046″. If you have set some different identifier, then you can search using that key word.

Custom Top in Oracle Application - Creation & Registering

CUSTOM TOP (Registering Custom Application)
Balaji R S

These are all the steps to register a custom top and custom application with Oracle Apps
Create xxncm as custom top, user, schema, application name....

Steps:
Created the directory structure for your custom application files under $APPL_TOP/xxncm
cd $APPL_TOP
mkdir xxncm
mkdir xxncm/11.5.0
mkdir xxncm/11.5.0/admin
mkdir xxncm/11.5.0/admin/sql
mkdir xxncm/11.5.0/admin/odf
mkdir xxncm/11.5.0/sql
mkdir xxncm/11.5.0/bin
mkdir xxncm/11.5.0/reports
mkdir xxncm/11.5.0/reports/US
mkdir xxncm/11.5.0/forms
mkdir xxncm/11.5.0/forms/US
mkdir xxncm/11.5.0/$APPLLIB
mkdir xxncm/11.5.0/$APPLOUT
mkdir xxncm /11.5.0/$APPLLOG

Added entry XXNCM_TOP=/apps/oracle/visappl/xxncm in Enviornment file.

export XXNCM_TOP
You can source all the environment files before proceeding.

Create new tablespace for database objects

create tablespace xxncm datafile '/apps/oracle/visdata/xxncm.dbf' size 10M;

Create schema

SQL> create user xxncm identified by xxncm default tablespace xxncm
temporary tablespace temp quota unlimited on xxncm quota unlimited on temp;

SQL> grant connect, resource to xxncm;

Register your Oracle Schema

Login to Applications with System Administrator responsibility
Navigate to
Application–>Register

Application = Custom Application

Short Name = xxncm

Basepath = xxncm_TOP

Description = Custom Application

Register Oracle User

Naviate to
Security–>Oracle–>Register

Database User Name = XXNCM

Password = XXNCM

Privilege = Enabled

Install Group = 0

Description = Custom

Upgrade JInitiator

Upgrading Jinitiator in Oracle 11i
Balaji R S [11/09/2008]

Oracle JInitiator is basically available on two streams of JDK for Oracle Applications 11i customers. One stream is based on Jinitiator version 1.1.8.X version and another stream is based on 1.3.1.X version. As JDK 1.1.8 has long been desupported by Sun, Oracle will continue to provide critical updates to Jinitiator 1.1.8 through the desupport date for Release 11.0; Oracle strongly recommends that Oracle Applications 11i customers move to the latest certified version of JInitiator 1.3.1.x. In some cases, migration to JInitiator 1.3.1.x requires additional technology upgrades.

Many a times you might face a situation where you need to upgrade your Jinitiator version to the latest version available. Also some times users are unable to open the forms. When they click on forms, system constantly ask for jinitiator upgrade, and even after upgrading the Jinititator system keeps on asking to install the same version again and again. This happens because of fundamental reason — Your client system is not having correct version of Jinitiator then your application is at currently. Example the situation might be that your client PC is having a Jinitiator version of 1.3.1.18 where as your application expects a Jinitiator version of 1.3.1.25. In that case when you click on the forms window it will automatically ask you for installation of required Jinitiator version. But note that installation of required Jinitiator version is only one time job. Next time click on forms should open the forms window correctly.

Reason for asking to install Jinitiator repeatedly is that if your application system is not having a correct version of Jinitiator then it will prompt to install the highest available version with it. If this version happens to be lower version then the required then it will repeatedly as you to install the same Jinitiator version again and again.

This problem has two solutions. First solution is to download the correct version of Jinitiator
manually and install in your client PC.

Another solution is to upgrade your Jinitiator version in application system. This will put the correct Jinit exe in your application which will be downloaded and installed first time when you click on forms. With proceeding clicks it will open up the forms correctly. This post explains about upgrading Jinitiator version of your application system.

For more details, please refer to metalink note ID 124606.1.

Upgrading JInitiator for application system
For upgrading JInitiator version of your application, you need to apply 2 patches as given below depending on your Jinitiator current version.
JInitiator Version JInitiator Patch Interop Patch
1.3.1.29 6350285 6169479
1.1.8.27 6612584 6615232

In the JInitiator patch (6350285 or 6612584) , there will be jinit*.exe. You can extract this exe file by unzipping the patch.
Once the exe file is extracted, place the exe file at $COMMON_TOP/util/jinitiator/ directory.
This is the place from where the jinitiator will be downloaded in your local client PC. After placing the exe, apply the interop patch for the respective version using the following steps.
1) Apply the patch driver in the interop patch using AutoPatch.
2) Run the jinit.sh script from the
//fnd/patch/115/bin/ directory, against the web node
of your middle tie.
The usage of the script is
jinit.sh
Example: jinit.sh 13129
(If you are upgrading to 1.3.1.29 version).
The script will return the appropriate file, or prompt you for the following values:
Location of APPSORA.env file (This is located in APPL_TOP) Location of Context File (echo $CONTEXT_FILE will give the location of context file) Password for the APPS User in the database This will make the necessary changes to the application system and JInitiator version is now upgraded. You can bounce the services now and access the application. This will download the correct latest JInitiator version that you have upgraded to your local PC and it will install. You will be able to access the forms as well correctly.
You can verify the JInitiator version that you have upgraded by enabling the Jinitiator’s console as per the steps given in metalink note ID 124606.1.
References:
Metalink note ID 124606.1