FRM-92101 Error

FRM-92101 Error

Error: "FRM-92101 , found the following error in FormsGroup.0.stdout - Forms session <84> aborted: unable to communicate with runtime process."

Modified

serverURL=/forms/formservlet

to

serverURL=/forms/formservlet?ifip=100.100.100.100

But this cannot be used as a permanent fix, because after this change all the connections coming to forms will treated as if they are coming from the IP address 100.100.100.100.

Also the logfiles and the tracefiles will have the client ip address as 100.100.100.100 irrespective of the actual client ip address

So current workaround can be used as temporary fix until the issue is permenantly fixed by applying the required patch.

"

MWA - Cannot establish telnet session to MWA server

MWA - Cannot establish telnet session to MWA server

Check if you are able to telnet to the box from your local machine command prompt

Example :

From local machine CMD prompt

C:\telnet test.oracle.com 30000

If you are not able to ping ,that means MWA server is down.

You have to check for all telnet ports where MWA server is running.

For MWA and Dispatchher Port informatiom :

=========================================

cd $MWA_TOP/secure

file " mwa.cfg "

grep for : "mwa.TelnetPortNumber" and "mwa.Dispatcher"

eg :

mwa.TelnetPortNumber=30000,30002,30004

mwa.Dispatcher=test.oracle.com:30030

From SSH in the box ,check if the ports are listening

Example :

$ netstat -an|grep 30000

The log details are available in nohup.out file

Start MWA server

=================

MWA start/stop scripts are available in $MWA_TOP/bin directory

Start the MWA server with the following commands:

cd $MWA_TOP/bin

$nohup ./mwactl.sh start 30000 1> nohup.out 2>&1 &

$nohup ./mwactl.sh start 30002 1> nohup.out 2>&1 &

$nohup ./mwactl.sh start 30004 1> nohup.out 2>&1 &

$nohup ./mwactl.sh start_dispatcher 1> nohup.out 2>&1 &

Execute all the four commands above.

Sysadmin User Responsibilities Missing

ISSUE: Sysadmin User Responsibilities Missing

In Oracle Applications, when logging as sysadmin - all the Sysadmin User Responsibilities Missing.

To fix this issue please perform the below.

1.) Execute following select :

SELECT *

FROM Fnd_Responsibility_vl

WHERE Application_Id = 1

AND Responsibility_Name = 'System Administrator'

AND Start_Date <= Sysdate

AND ( End_Date is NULL OR End_Date > Sysdate );

2.) Execute following select :

SELECT count(*) FROM Fnd_User_Resp_Groups;

3.a) Create the Backup table :

CREATE TABLE wf_role_hierarchies_copy AS SELECT * FROM wf_role_hierarchies;

3.b) truncate the existing table:

TRUNCATE TABLE applsys.wf_role_hierarchies;

3.c)sqlplus apps/xxxx @$FND_TOP/patch/115/sql/affurgol.sql FORCE

3.d) Insert the data into the new created table :

INSERT INTO wf_role_hierarchies SELECT * FROM wf_role_hierarchies_copy;

4.) Verify the output of the following SQL statement at this point :

SELECT count(*) FROM Fnd_User_Resp_Groups;

Pasta to PDF printing Setup

Pasta to PDF printing Setup

Pasta Introduction:

------------------

Pasta technology provides nultilingual support in Oracle E-business Suite particularly In printing (Pasta),viewing a report on-line (Vpasta) and generating bitmap reports ( IX Library).Pasta works on UTF8 and other character sets as well which Oracle Supports.

Pasta is part of E-business Suite’s Application object Library (FND).Pasta enables Multi-lingual handling by taking advantage of PostScript language. Pasta converts an input content from text format to PostScript format to add the multi-lingual support. During the PostScript conversion, Pasta includes all the necessary information in addition to the language handling such as paper size, font size and so on. After converting the input, Pasta sends the content to preprocess command if it is set in the preprocess option in the Pasta configuration file before printing. The content is then sent to the printer command that is specified in the printCommand option in the configuration file. ( pasta.cfg)

Prerequisites:

-------------

Printer should be setup at the operating system level .Use lpstat -a commandand check if the printer is configured as OS level.

Configuration:

--------------

Pasta patch 3325651 is provided as standard AD patch of Oracle Applications and it needs to be applied on the concurrent processing node.

Setting up your system to use Pasta is much simpler than the standard Oracle Applications printer setup procedure. The Printer Type, Printer Driver, and SRW driver files are provided. The only setup required to begin printing is the registration of the printer with Oracle E–Business Suite.

Pasta comes with default Printer type:

Responsibility: System Administrator Menu Path: Install->Printer->Type

--PASTA Universal Printer Type. We can use the same printer type or configure a new printer type.

Associate the printer type with different printers as required.

Responsibility: System Administrator Menu Path: Install->Printer->Register

Pasta configuration files are located in $FND_TOP/resource directory.

Pasta looks for files pasta_.cfg file in the above directory. If the file is not present it will look for the file pasta.cfg

You can change the file that is defined as the default configuration file for Pasta by using the -F command line parameter.

For example, suppose you create a PCL print specific configuration file named pcl.cfg. Set the FNDPSTAX command line option as follows: -Fpcl.cfg

Pasta will look for pcl_.cfg first, and if it is not found, Pasta will use pcl.cfg as the default.

These files must be placed under the $FND_TOP/resource directory.

The -F command line parameter can be set in the Arguments field ofthe Printer Drivers window.

Pasta_pdf.cfg is the file used by pasta to print pdf converted to postscript By 3rd party utility.The driver name is PASTA_PDF.

Ex:

In pasta_pd.cfg : preprocess=pdf2ps {infile} {outfile}.

The configuration file Pasta.cfg file governs many printing options.The file

is a simple ASCII text file.

Some important options :

1.OutputFormat = ps/text ( ps stands for printers which support postscript format and text stands for printers which doesnt support post script Format)

2.Preprocess =

3.Printcommand = lp (Print command for unix platform)

4.Pagewidth

5.pageheight .

There are lot of other options which can be configured like fontname, font size.Please Refer to PASTA3.pdf file uploaded for details.

With reference to the work related to ohsconfig team , we receive tars related to Pasta configuration , troubleshooting, changing parameters in pasta configuration files(pasta.cfg ..etc).

For most of the changes made to configuration files it is necessary to bounce concurrent manager for changes to take effect.

Oracle Apps - Printer Setup

Oracle Apps - Printer Setup

Fnd the below steps which will help to setup printer in Oracle Applications

A)Prerequisites:

- Printers should be first defined at Unix OS level by customers

Please check the status of printer at unix level by using the following command

lpstat -a

B)Configure Printer in Oracle Applications

The following is the order of Printer setup in Oracle Applications:

Define Driver

Define Style

Define Printer Type

Register the Printer

1) Define the printer driver, Install > Printer > Driver

Login to application using System Administrator or Application Administrator resp

Define the printer driver, Install > Printer > Driver

Please provide the below values (depending upon your configuration) to set up.

Enter the Driver Name : LANDWIDEHPLJ4SI

Enter the User Driver Name: LANDWIDE for Printer HPLJ4SI

Description: Give some desc appropiate

SRW Driver: HPW

SRW drivers are read by Oracle reports when a report is run and insert control characters which tell the destination printer on where to insert the page breaks and font to be used etc.. SRW driver is used when output file is sent to the printer

SRW driver files on unix are located in $FND_TOP/reports. In the above example, file name would be HPW.prt

Platform: Not required

Arguments: Printer Driver pass the following arguments to program

Name of the destination printer

Number of Copies to print

Banner of the title page

Filename

Initialization and Reset strings: Instructs printer on printing characteristics are needed for the document to be printed. Printer vendor provides these details

2) Define the printer style , Install > Printer > Style

Login to application using System Administrator or Application Administrator resp

Define the printer style , Install > Printer > Style

Please provide the below values (depending upon your configuration) to set up.

Style Name : HPW

Seq: Enter unique sequence number

User Style: LANDWIDE - HPLJ4

SRW Driver: HPW , this should match with driver define page

Layout:Columns,Rows and Orinetation: Columns and Rows inserted here override the height and width defined in SRW driver file

3)Define the printer type, Install > Printer > Type

Login to application using System Administrator or Application Administrator resp

Define the printer type, Install > Printer > Type

Please provide the below values (depending upon your configuration) to set up.

Type: HPLJ4SI

Style: Style name

Driver Name: Driver name

4)Register a new printer , Navigation Path is Install > Printer > Register

Login to application using System Administrator or Application Administrator resp

Define the printer type, Install > Printer > Type

Please provide the below values (depending upon your configuration) to set up.

Printer : Printer Name

Type: Type defined earlier

Description : Useful description

Some important tables related with printing are:

-----------------------------------------------

FND_PRINTER

FND_PRINTER_INFORMATION

FND_PRINTER_STYLES

FND_PRINTER_DRIVERS

NOTE: Please note any changes to Printer Type, Style and Driver needs bouncing of concurrent manager for the changes to take effect.