Category Archives: Windows - Page 19

Project Rollup Patches Not Completing On DB Tier

Posted by on April 20, 2007 No comments

Problem: When applying Project Costing rollup patches to DB tier, the following errors are returned:

adlibout: error: cannot get table of contents in library file for product pa

File name is f:/oracle/prodappl/pa/11.5.0/lib/past.lib

Solution: mspdb60.dll not in the path.

Another issue was encountered on the system, which the application modules were relinked. While relinking, the message ‘gnumake: Error 128’ appeared. Metalink Doc ID 123595.1 and 142390.1 indicated that the mspdb60.dll file was not in the path (on the DB tier). After modifying the path, the relink completed successfully.

The Project Costing rollup patches were then reapplied, on both tiers, and all patches went through successfully. Relinking appears to be part of the patching process for the Project Costing rollup patches.

Configuring Expediting Report To Copy To Network Share

Posted by on February 12, 2007 No comments

This documentation shows how to configure Oracle Applications to automatically copy the expediting report to a remote network share for use by SharePoint.

To copy the expediting report, a virtual printer was set up. When the expediting report was sent to this virtual printer, the output file (in HTML format) was copied to a remote network share. A link was set up in SharePoint to point to this file.

Setting up virtual printer

Step 1:        To set up a new printer in Oracle Applications, select the System Administrator responsibility. The custom Printer Style and Printer Driver must be set up first. Navigate to Install > Printer > Style.

Step 2:        Click the New button to enter a new style.

Step 3:        Enter the following information in the Print Styles form:

Style Name: copy_expediting_report

Seq: 87

User Style:   copy_expediting_report

SRW Driver: L

Columns: 132

Rows: 66

Step 4:        After entering the information, click the Save button.

Step 5:        Next, navigate to Install > Printer > Driver . Set up the printer driver as shown below:

Driver Name: copy_expediting_report

User Driver:   copy_expediting_report

SRW Driver: L

In the Arguments field, enter the following command (one line):

cmd /c “copy /Y $PROFILES$.FILENAME \ppnets01Expediting_ReportPPGPL_EXPEDITE.html”

Save the changes.

Step 6:        Navigate to Install > Printer > Types to enter a new printer type. Type Ctrl+F11, then use the Up and Down arrow keys to locate the HPLJ4SI printer type.

Under Printer Drivers, click any row under Style, and then click New. A new row appears. Enter the names of the custom style and driver created in the previous steps. Then click Save.

Step 7:        Finally, navigate to Install > Printer > Register to register the new printer.

Type Ctrl+F11 to list the printers currently registered. Click New to enter a new printer. Type the name of the printer, the printer type (HPLJ4SI) and a description. Click Save to save the changes.

Updating Concurrent Program to Use Virtual Printer

Step 1:        Modify the concurrent program setup for the expediting report to point to the new printer. Navigate to Concurrent > Program > Define.

Type F11, enter USER_EXPEDITE in the Program field, and then type Ctrl+F11. Under Output, change the values for Style and Printer to those specified in the previous section. Ensure that Format is set to HTML.

Setting Up New Responsibility

In order for the report to be copied, it must be printed to the virtual printer with one copy, and not the default of zero copies. In order to automatically copy the file, the report must be set to print one copy by default.

The default number of report copies is set as a system profile value, and can be set at the application, responsibility or user levels. Once set, all reports under that level will print the specified number of copies by default.

Because all reports under the specified application, responsibility or user will be affected by changing the number of default report copies, a new responsibility was created and the report registered under this responsibility, so that the number of copies could be specified for the responsibility.

Step 1:        Navigate to Security > Responsibility > Request. Click New and enter the following information. Click in the Name field to enter the report and application name. Then click Save.

Step 2:        Navigate to Security > Responsibility > Define. Enter the following information. This will attach a basic menu to the responsibility created above. Under Effective Dates, change the From field to 01-JAN-1951.

Step 3:        Next, add the responsibility to a user. Navigate to Security > User > Define.

Type F11, enter the username that you wish to add the responsibility to, then type Ctrl+F11. Click under Direct Responsibilities, then click the New button. Select the name of the responsibility entered in the above step. Then click Save.

Setting Profile Option

Step 1:        The profile value must be set for the new responsibility so that the default number of copies for the report is one. Navigate to Profile > System.

In the Responsibility field, enter the responsibility set up in the previous section. In the Profile field, enter “Concurrent%” and then click Find.

Step 2:        Locate the Profile “Concurrent:Report Copies”. Under Responsibility, set the value of the field to 1. Save the change.

Scheduling Concurrent Program

Step 1:        To set up the schedule for the report, click the Switch Responsibility button.

Step 2:        Select the custom responsibility for the expediting report.

Step 3:        Navigate to Requests. The Submit Request form automatically appears since there is only one report registered in this responsibility.

Step 4:        Click in the Parameters field and enter the following parameters. Then click OK.

Start Date 01-Jan-2001
End Date 01-Jan-2010

Step 5:        Click the Schedule button.

To schedule the report to run every 30 minutes, select Periodically, then enter 30 in the field. Click the down arrow head and choose Minute(s). Then click OK.

Finally, click Submit. The report begins running immediately and will execute every 30 minutes thereafter.

Creating Database Link To Transfer FSG Reports

Posted by on January 29, 2007 No comments

Problem: A database link must be created in the Target instance to pull (transfer) FSG information to the production instance from the test instance.

Solution: Use Define Database Links in Oracle Applications.

To define a database link in General Ledger perform the following steps

on the Target instance (the one you are copying to):

Step 1:        Log on as sysadmin user and select a GL responsibility.

Step 2:        Navigate to Setup > System > Database Links.

There are six fields that have to be entered:

  1. Database Name
  2. Description
  3. Connect String
  4. Domain Name
  5. APPS Username
  6. APPS Password

Step 3:        In the source database, enter the following SQL query:

SELECT value FROM v$parameter
WHERE UPPER(name) = 'DB_NAME';
VALUE
--------------
PROD

This value is to be entered in the ‘Database Name’ field in Oracle Applications.

Step 4:        In the source database, enter the following SQL query:

SELECT value FROM v$parameter
WHERE UPPER(name) = 'DB_DOMAIN';
VALUE
---------------------

This value must be entered into the ‘Domain Name’ field in the form. If it is null, any value can be entered into this field (e.g. WORLD).

Step 5:        On the target database, grant privilege to apps user (log on as system user):

grant create database link to apps;

Step 6:        Ensure the two hosts are in the hosts file on each host.

127.0.0.1     localhost
128.x.x.x   oracleserver.domainname  oracleserver
128.x.x.x   oraclesrv.domainname     oraclesrv

Step 7:        Update the TNSNAMES.ORA file on each server with the entry for both instances:

PROD=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=ORACLESERVER.domainname)
(PORT=1525))
(CONNECT_DATA=
(SID=PROD)
)
)
MFGP=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=ORACLESRV.domainname)
(PORT=1527))
(CONNECT_DATA=
(SID=MFGP)
)
)

Step 8:        Ensure that the TNSNAMES.ORA was set up correctly using tnsping to ping the remote instance.

Step 9:        Ensure that SQL Restriction is turned off

Step 10:   Bounce the 920 TNS listener on each node.

Step 11:    Ensure that you can log on the other instance using SQL*Plus.

Step 12:   Enter the following values into the form:

Field Value
Database Name PROD
Description Test Database
Connect String PROD
Domain Name WORLD (since it is null, any value can be entered)
APPS Username apps
APPS Password apps

In the SQLNET.ORA file, I had to comment out the line: sqlnet.authentication_services= (NTS)

# sqlnet.authentication_services= (NTS)

Refer to Metalink Documents:

Doc ID 161635.1: (FSG Transfer Troubleshooting Guide)

Doc ID:  Note:1057188.6 (WHERE DO YOU DEFINE DATABASE LINKS FOR FSG’S?)

[amazon asin=0070077290&template=iframe image&chan=default]    [amazon asin=1453742735&template=iframe image&chan=default]    [amazon asin=0615238440&template=iframe image&chan=default]

REP-3002 Cannot Print to Printer After Installing

Posted by on December 12, 2006 No comments

Problem: After installing a fresh instance, when Active Users report is run, it exits with error.

Solution: Run ccmsetup. Delete the concurrent manager service, then add back service. Remember to set apps password, database sid and Automatic  checkbox. Reboot the computer.

Excel Not Launching Properly from Web ADI

Posted by on December 1, 2006 No comments

Problem: When Web ADI launches Microsoft Excel, the output Excel spreadsheet does not run.

Solution: This problem seems to be occurring only in Microsoft Excel 2003. In Excel 2003, Enable Trust VB Projects.

Step 1:        After launching Excel 2003, navigate to Tools > Options.

Step 2:        Click the Security tab.

Step 3:        Click the Macro Security button.

Step 4:        Click the Trusted Publishers tab.

Step 5:        Ensure that Trust access to Visual Basic project is checked.

Step 6:        Click OK to exit the option. Click OK again.

Refer to Metalink Doc ID:  Note: 106528.1 (Subject:  Application Desktop Integrator – Product Documentation)

Refer to Metalink Doc ID:  Note: 376976.1 (Subject:  WEB ADI “Run-Time Error ‘50290’ Method ‘Run’ Of Object ‘_application Failed”)

Refer to Metalink Doc ID:  Note: 295901.1 (Subject:  No Excel File Created When Using Excel 2002; Excel 2002 Does Not Appear In Viewers LOV)

See also http://support.microsoft.com/default.aspx?scid=kb;en-us;282033

Recreating DBC file

Posted by on November 22, 2006 No comments

Problem: While installing vision instance, the post-install check “JSP Check” fails with the message “DBC file may be invalid”.

Solution: Recreate DBC file.

Note: Run these commands from $FND_TOP/secure. Also, source environment file first.

To create a DBC file and server ID:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis ADD FNDNAM=apps GWYUID=applsyspub/pub TWO_TASK=vis SECURE_PATH=%FND_TOP%secure GUEST_USER_PWD=guest/guest APPS_JDBC_DRIVER_TYPE=THIN DB_HOST=eam.clientnetwork.com DB_PORT=1522

To check status:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis STATUS DB_HOST=eam.clientnetwork.com DB_PORT=1522

To delete DBC file:
java oracle.apps.fnd.security.AdminAppServer apps/apps@vis DELETE DB_HOST=eam.clientnetwork.com DB_PORT=1522

Also, you can run adgendbc.sh, located in $COMMON_TOP/admin/install/

For Database Connectivity problems, ensure that the hosts file is set up properly:

127.0.0.1 localhost.localdomain localhost
hostname.domainname hostname

On Windows, use java. On Linux/Unix, use JRE.

Reference:
Metalink Doc ID: 108865.1 (How To Create a Database Connection(DBC) File and Troubleshooting Common Problems)

No TNS Listener Installing Instance

Posted by on November 6, 2006 No comments

Problem: In step 5 of 5 during installation of Oracle Applications instance, TNS listener does not start.

Solution: hosts file configured incorrectly.

The correct format of the hosts file is:

Under Windows:


xx.xx.xx.xx hostname.domainname alias
127.0.0.1 localhost.localdomain localhost

Another symptom that the hosts file was not set up correctly: the StartCD did not stage properly.

Creating A Custom Application

Posted by on October 11, 2006 No comments

This documentation covers how to create a custom application, program and executable in Oracle Applications. The custom application will load data from feeder systems into Oracle Application’s interface tables.

A custom application needs to be set up only once. The custom program executable will then need to be set up and the program defined. Finally, the program must be added to a request group, so that it appears in a user’s responsibility.

Step 1:        Create a new application: Log on as the SYSADMIN user. Select the System Administrator responsibility, then navigate to Application, and then Register.

Step 2:        Click the New button to insert a new row.

Insert a new application, Maryland Financial Group Limited. The Short Name chosen is MFGL and Basepath is MFGL_TOP. Save the record.

Step 3:        Create a directory d:PRODprodapplmfgl on oracleserver. Under mfgl, create a directory ‘11.5.0. Under this directory, create the directories: bin, data, log, out, reports, and sql.

The d:PRODprodapplmfgl11.5.0 directory will be set to the environment variable MFGL_TOP.

Step 4:        Under Windows, Oracle Applications stores the application top folders in the registry. Update the registry on oracleserver to add the MFGL_TOP base path:

[HKEY_LOCAL_MACHINESOFTWAREORACLEAPPLICATIONS11.5.0 PROD_oracleserver]

MFGL_TOP=”d:PRODprodapplmfgl11.5.0″

Step 5:        To add MFGL_TOP as an environment variable, create customPROD_oracleserver.cmd in the d:PRODprodappl directory and put the following path into this file.

set MFGL_TOP=d:PRODprodapplmfgl11.5.0

Step 6:        Navigate to Security, then ORACLE and finally DataGroup.

Insert a new record. Select the Maryland Financial Group Limited application, add APPS as Oracle ID and enter an optional description. Click Save.

Note that steps 1 to 6 only need to be done once. Since these steps have already been done, there is no need to go do them again.

Step 7:        The data will be loaded via SQL*Loader. Create the control file GLMLAS400.ctl file and place the SQL*Loader command in it. Place the control file in the d:PRODprodapplmfgl11.5.0bin folder.

Step 8:        Set up the concurrent program executable: Navigate to Concurrent, then Program and finally Executable.

Insert a new executable program. Ensure that the Execution Method is SQL*Loader, since selecting Host causes Oracle Application to look for an executable (“.EXE”) program rather than a “.CMD” program on Windows. Click Save.

Step 9:        Define the concurrent program: Navigate to Concurrent, then Program and finally Define.

Insert a new record and fill in the fields to add the new program. Click Save.

Step 10:   Click the Incompatibilities button. Insert a new incompatible program ‘Maryland – Load AS/400 GL Journals’. This will prevent another instance of this program from running if it is running already.

Step 11:    The program must now be set up so that it can be submitted from Standard Request Submission. To submit the program from the General Ledger Manager, the request group for the responsibility must be found. Navigate to Security, then Responsibility, and finally Define.

Search for the ‘General Ledger Manager’ responsibility. Note the name of the Request Group.

Step 12:   Add the new program to the Request Group. To do so, navigate to Security, then Responsibility and finally Request.

Search for the group noted in the previous step (in this case, ‘GL Concurrent Program Group’). Insert a new record for ‘Maryland – Load AS/400 GL Journals’.

Step 13:   Before running the concurrent request, place the data file in the d:PRODprodapplmfgl11.5.0data directory, under the name GLMLAS400GL.dat. If this file already exists in the directory, it can be overwritten.

Step 14:   Choose the General Ledger Manager responsibility. Submit a new request, ‘Maryland – Load AS/400 GL Journals’.

No parameters need to be entered for this request. The request will automatically search for the data file and load it if present. If not, the request completes in error and the log will have to be checked to determine the cause of the error.

For additional information on setting up a custom application, refer to Metalink Doc ID: Note:105127.1, Subject: FAQ (Customization).

Journal Importing GL_INTERFACE Data

Posted by on October 10, 2006 No comments

This documentation shows how to load journals that were loaded into the GL_INTERFACE table.

Step 1:        Log on as a user with access to the GL responsibility and select the General Ledger Manager responsibility.

Step 2:        Navigate to Journals > Import > Run.

Step 3:        Enter the Source and Group ID. Select Without Validation.

Step 4:        Click Import.

Step 5:        To delete imported journals, navigate to Journals > Import > Delete.

Step 6:        Enter the Source, Request ID and Group ID.

The Request ID is that of the request used to import the journals (check View Requests to determine this ID).

Deleting Print Job

Posted by on October 6, 2006 No comments

Problem: When a print job is deleted from the queue, it remains in a state of ‘deleting’.

Solution: Stop and restart “Print Spooler” service on the print server.