� � � � � � �

PeopleSoft Crystal Reports

8.5/9/XI

Troubleshooting Guide

T I T L E OF PAPER

7 / 2 4 / 2 009

Crystal Troubleshooting Guide

Reference Number: PTOOLS001

Reporting Tool’s Product(s): Crystal Reports 8.5/9.0

Business Objects Enterprise XI

PeopleTools Release(s): 7.x, 8.1x, 8.4x

Revision Number: Rev3

Contains:

√

√

√

√

√

√

Table of Contents

Table of Contents........................................................................................................................................................3

Introduction .................................................................................................................................................................4

Structure of this Troubleshooting guide 4

Related Materials 4

Chapter 1 - Executive Overview ................................................................................................................................5

Chapter 2 - Crystal Reports in a Client Environment - Configuration and Use....................................................6

Chapter 3 - Crystal in a Client Environment - Troubleshooting.........................................................................14

Chapter 4 - Crystal in a Web Environment – Configuration and Use ...............................................................19

Chapter 5 - Crystal in a Web Environment - Troubleshooting ...........................................................................21

Chapter 6 - Business Objects Enterprise Java Environment – Configuration and Use..................................30

Chapter 7 - Business Objects Enterprise Java Environment – Troubleshooting ............................................31

Appendix A - Important Doc IDs..............................................................................................................................33

Appendix B - Important Incidents ...........................................................................................................................34

Appendix C - Validation and Feedback .................................................................................................................35

References.................................................................................................................................................................36

Introduction

This practical troubleshooting document is designed for Crystal Reports and Business Objects Enterprise (BOE) users – beginning and advanced – as well as for Oracle Global Customer Support (GCS). The scope of the document includes Crystal Reports and BOE software installation, configuration, and use with PeopleSoft PeopleTools. Troubleshooting tips are given for previously reported Crystal and BOE problems. BOE is a java-based report repository and scheduling tool that uses reports designed with Crystal Reports software; BOE is therefore included in the scope of this document. Much of the information contained in this document is based on real-life problems. Issues discussed here are ones reported most frequently or are the most troublesome.

STRUCTURE OF THIS TROUBLESHOOTING GUIDE

This Guide provides help on different troubleshooting approaches for different Crystal Reports and BOE related issues. This document is updated as needed so that it reflects the most current feedback received from the field. Therefore, the structure, headings, contents, and length of this document is likely to vary with each posted version. To see if the document has been updated since download, compare the version date to the date posted on the Oracle Portal.

RELATED MATERIALS

It is assumed that the reader is familiar with PeopleSoft Administration. To take full advantage of the information covered in this document, it is recommended that users have an understanding of basic Windows system administration concepts, workings of the internet, relational database concepts, SQL, PeopleTools and the use of PeopleSoft applications. This document is not intended to replace other documentation delivered with PeopleTools, including Installation Guides and Notes, PeopleBooks, Hardware and Software Guides, or any Crystal Reports/ BOE specific documentation. It is recommended to read the appropriate release of PeopleBooks Crystal Reports for PeopleSoft to ensure a well-rounded understanding of our technology, before using this document. Note: Some of the information in this document is previously incorporated into PeopleBooks.

Chapter 1 - Executive Overview

Crystal Reports/BOE is third party reporting software, now owned by SAP. PeopleSoft uses this software for delivered PeopleSoft applications reports. Crystal is one of the most highly used reporting tools within the scope of PeopleSoft applications. There are many delivered individual Crystal reports in the delivered PeopleSoft applications products PeopleSoft application end-users may utilize the delivered Crystal reports as-is, may customize the delivered Crystal reports, or may create totally new reports, according to their requirements. Users design and/or customize reports by means of the Crystal Designer client software tool. After successful testing of these reports with the Crystal Designer tool, customized or new reports may be implemented within a PeopleSoft environment. Crystal Reports Software Availability The Crystal Reports client software for developing Crystal reports is licensed for use with PeopleTools and is downloadable from: URL: http://edelivery.oracle.com Set Product Pack to “PeopleSoft Enterprise” and Platform to “Microsoft Windows 32” and click GO. Scroll down to the appropriate PeopleTools entry for the desired environment. For example, “PeopleTools Enterprise – PeopleTools 8.49 Media Pack”. Click the Description link. On the following page, click the Download link in front of the desired Crystal Reports product. For example, “Crystal Reports 9.0 English”. Crystal Reports Related Executable Programs Windows software programs to run Crystal Reports within the PeopleSoft application are delivered with PeopleTools. The necessary program files are installed during the PeopleTools installation on a Process Scheduler host machine. PeopleTools delivers Windows Crystal executables such as “PSCRRUN.exe” and “PSCVTRPT.exe” under the following folders: %PS_HOME%\bin\client\winx86 %PS_HOME%\setup Crystal Reports Format Files The Crystal Report application report format files are delivered in the following folder: %PS_HOME%\crw Language versions of the same reports are delivered in the sub-directories. %PS_HOME%\crw\ENG %PS_HOME%\crw\ARA %PS_HOME%\crw\CFR %PS_HOME%\crw\CZE Etc… Crystal Reports Related Queries Access to the PeopleSoft database is via the ODBC(RDO) PeopleSoft PeopleTools driver for from Crystal Reports and via the Integration Gateway and Query Access Services for BOE. The PeopleTools accesses enable a view of accessible PeopleSoft Queries. This data access method enables PeopleSoft Security to be applied to the reports

produced with Crystal/BOE. Each Crystal Report delivered with the PeopleSoft application is associated with a Query. Often the Query has the same name as the report format file. For example, the XRFWIN Crystal Report

uses the Query “XRFWIN”, which may be viewed from the PeopleSoft Query Manager. No Crystal Report may be

run from the PeopleSoft Application for which the data source is not a Query.

Chapter 2 - Crystal Reports in a Client Environment - Configuration and Use

Crystal Reports may be run from a variety of software tools using any of the following connectivity methods. Summary of Crystal Reports Client Software and Connectivity Methods

Connectivity Method

Crystal Reports PeopleSoft

2-Tier Crystal Designer Client (crw32.exe)

Application Designer (pside.exe) Query (psqed.exe)

3-Tier Crystal Designer Client (crw32.exe)

Application Designer (pside.exe) Query (psqed.exe)

Web PIA login to PeopleSoft environment then submit to Process Scheduler

2-Tier Connect to the database directly using database connectivity software. May be used for either the Crystal Designer or PeopleSoft Query tools Helpful when no PeopleSoft Application Server is accessible. 3-Tier Connect to the database using the PeopleSoft application server May be used for either the Crystal Designer or PeopleSoft Query tools Helpful when database connectivity software is not configured on the workstation. Reduces the number of individual database connections. Web Login to a web server based PIA session to access the Process Scheduler Using the Crystal Designer client software, with either a 2- or 3-tier connection to the database, users may configure, run, and print Crystal Reports via the Process Scheduler

When to Use Crystal Designer Client Software Situations when Crystal Designer client software may be desired or helpful: 1) Developing new Crystal Reports to accompany reports delivered with the PeopleSoft application 2) Customizing the PeopleSoft delivered Crystal Reports to modify or extend their functionality. 3) Testing the newly developed and customized Crystal Reports 4) Running Crystal Reports against a PeopleSoft database, generating an .RPT output file, and sending it to

“Printer” or “File” output type. 5) Upgrading PeopleTools or Crystal software and using the PeopleSoft Crystal Reports converter program

PSCVTRPT.EXE to update the reports for the new environment. NOTE: The primary delivered output format of Crystal Designer is to the proprietary Crystal *.RPT format. Crystal software is required in order to read RPT files. Crystal Designer output may also be exported to a number of different standard formats such as PDF, HTM, DOC, XLS, CSV, and others. Configuring Crystal Designer Client Follow these steps to work with Crystal Designer client software over a 2- or 3-tier connection.

1) Confirm that the Crystal software version being used is certified with the respective PeopleTools release. View

the “Third party” software certification details in Metalink: URL:

https://metalink3.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=747587.1 2) Download and install the appropriate release of Crystal Reports based on the certification details, from the

following location: URL: http://edelivery.oracle.com 3) Perform the Configuration Manager Workstation Install on the desired machine. Follow the details given in

PeopleBooks: Crystal Reports for PeopleSoft > Using Crystal Reports 9

Start the PeopleSoft Configuration Manager by clicking the executable PS_HOME\bin\client\winx86\pscfg.exe. Then set the correct configurations in these locations for the following parameters:

a) Navigate to: Profile > Edit > Default > Process Scheduler.

b) PS_HOME – point to the local PeopleSoft File Manager

c) DBBIN - point to the location of the database connectivity software

d) CRWRPTPATH - point to the top-level directory where the Crystal Report RPT files are found. Do not include a language directory, such as ENG, in this path.

e) Navigate to Client Setup > ODBC Administrator

f) Highlight PeopleSoft PeopleTools > click Configure

g) For 2-tier, configure the Data Source Name, Database Type, and the Database Name as shown in the below example

h) For 3-tier connectivity, please perform the following navigation: Navigate to Profile > Edit > Default. Click the Application Server radio button and add an Application Server Domain name, machine name and port number. Click Set. Return to the Client Setup page and click Apply

NOTE: Incident 1325413000 tracks a reported issue preventing the use of 3-tier connectivity for Crystal Reports in certain PeopleTools releases. The issue is fixed in PT8.46.14, PT8.47.07, and PT8.48.00.

i) For a 3-tier connection via the Application Server to the database, from the Crystal Designer client use the following navigation and formatted entries:

Create New Connection > ODBC (RDO) > PeopleSoftPeopleTools

Server: PeopleSoft PeopleTools

UserID: <PeopleSoft User Profile Operid>

Password: <PeopleSoft User Profile Password>

Database: <machine name>:<port>/<database>/<domain>

Using PeopleSoft Query to Crystal Client Software

For running “Query to Crystal”, there are several additional required configurations. 1) Set the correct path for CRW32.exe in the field “Crystal Exes Path” in Configuration Manager > Crystal/Bus.

Interlink/Jdeveloper” on the workstation where the software will be used.

Usually CRW32.exe is found directly below the installation top directory of the Crystal Reports software on any system. Example: C:\Program Files\Crystal Decisions\Crystal Reports 9\CRW32.EXE

2) Set a path for the Default Crystal Reports field in “Configuration Manager > Crystal/Bus. Interlink/Jdeveloper”.

As this field is used by PeopleSoft Query, to avoid overwriting delivered files, it may be advisable to specify a different location from the delivered Crystal Reports path. If a path is not specified however, PeopleSoft Query will write the file to the language directory beneath the Crystal Reports CRWRPTPATH

Example: C:\TEMP\CRW

3) After adding these configurations and re-executing the Workstation Install, users should be able to generate

query output to Crystal from the PeopleSoft Query client software. Sending Query output to Crystal Reports format is done by clicking the 3

rd button in the Query Manager.

Chapter 3 - Crystal in a Client Environment - Troubleshooting

Various issues may occur while running Crystal client software using a 2- or 3-tier environment. Points to consider before applying any solution steps for Crystal issues are:

Checklist 1. Does the issue occur with ALL reports? Or only SOME reports? 2. Does the issue occur on ALL workstations? Or only SOME workstations? 3. Is the issue intermittent? 4. Has the report operated in the past without this issue? In the same environment? 5. Are the PeopleTools and Crystal releases certified on the problem environment? 6. Does the issue relate to the RPT Converter?

When the issue occurs with ALL reports There is a probability that the issue is caused by configurations. Check the below points: 1) Confirm the entries for “Crystal /Bus. Interlink/Jdeveloper” and “Process Scheduler” tabs in the

“Configuration Manager”. 2) Perform the Workstation Installation on the host machine as described above. For details, refer to Enterprise

PeopleTools 8.49 PeopleBook: Crystal Reports for PeopleSoft > Using Crystal Reports 9 > Running Client Setup

3) Confirm whether the issue is occurring with all the host machines or just specific ones. If the issue is

happening with specific machines, confirm the supportability of the machine OS and Crystal software versions. For example, Crystal on Windows 2000 may get an “IM003” error message while running Crystal reports. Search for any previously reported specific software issues.

4) Confirm whether the issue is occurring with a specific user or all users. If the issue occurs only with specific

users, the issue may lie with the Query Access Security of the underlying Query. Has access been granted to the problem User Profile?

5) Confirm there are not two or more PeopleTools versions or Crystal versions installed on the same host

machine. 6) In scenarios where users are not able to connect to the PeopleSoft database within Crystal Designer, confirm

the connection is being made under the Create New Connection > ODBC (RDO) > PeopleSoft PeopleTools driver.

7) If users are not able to find all the queries available in the database under PeopleSoft PeopleTools, please

review: E-CR: All Queries are not available in Database Explorer in Crystal Designer (Doc ID 661444.1)

When the issue occurs with only SOME reports These types of issues commonly happen with Application specific Crystal reports such as Crystal Reports checks APY2021. When the issue occurs with only certain specific Crystal reports, this indicates that the basic configurations for running Crystal reports in 2- or 3- tier may be correct. For troubleshooting these type of issues, confirm these points: 1) Confirm if the same report is running successfully in another environment, such as Test or Demo. If yes, then

copy the problem Crystal report from that working environment to the problem environment and retest. There may have been an RPT file corruption in the problem environment causing the issue.

2) If the Crystal report is not generating the correct data, the issue may be caused by the underlying Query

associated with that specific Crystal report not fetching the correct data. In that case open the associated Query in Query Manager and run the Query Check and compare the results.

If the results are correct for the Query, associate the query to the Crystal report again with the Database > Verify Database option.

3) For Crystal Reports 9.0 there are specific steps to follow to perform “Verify Database”. Refer to: E-CR: How to

change the Query a Crystal 9 Report is using? (Doc ID 638844.1) 4) For printer issues, first confirm the status of the “No Printer” box inside the Report definition within Crystal

Designer. Whenever the “No Printer” box is checked, that Crystal report is not permitted to be sent to a Printer.

Open the report and go to File > Printer Setup. Uncheck the No Printer box.

5) Sometimes a specific User Profile is not successful running a specific Crystal report. In such scenarios, confirm

whether the Query is public and no other Query is a duplicate. The specific User Profile must have PeopleSoft Security Query Access to run each specific Query.

6) Occasionally a User Profile may run one specific Crystal report and data is not refreshed. Older data is in the

report output. In such situations, open the problem Crystal report in Crystal Designer and check if File > Options > Reporting > Save data with report is checked. If it is checked, the same data will continually be in the Crystal report output.

When the issue occurs on specific workstations 1) The issue may be somewhere at the software configuration level. Please confirm the basic Crystal

configuration as described above in Chapter 2 2) There are some “IM003” related error messages reported with Windows 2000 machines. Locate another

machine with a different operating system such as Windows XP or Windows 2003, install your software, and attempt to replicate the issue.

3) If the issue persists with Windows XP, search the problem machine for the DLL called PSSECURITY.DLL. The

machine may have one or more copies of this DLL, depending on whether the PS_HOME is also on this same host machine.

4) For security issues, you may copy the PSSECURITY.DLL file from the PeopleTools \bin\client\winx86 folder to

"C:\Program Files\Crystal Decisions\Crystal Reports 9". Always make a copy of any file which is overwritten. When the issue is with the RPT Converter PeopleSoft delivers a report conversion utility known as RPT Converter. This program converts Crystal reports from one release to another. The RPT Converter may be useful in resolving problems after upgrading PeopleTools as well as Crystal Reports. Configure the environment for using the RPT Converter by performing these steps:

• Go to: Start/Programs/PeopleTools/Configuration Manager;

• In the tab 'Client Setup' to select 'PeopleTools RPT Converter' and 'Install Workstation' When running Crystal reports against RPT converter, do the following: 1) Create a separate folder such as C:\USER\CRW and copy the specific problem Crystal reports which one wish

to convert to that folder. Avoid running the RPT Converter on the entire delivered folder, such as CRW\ENG. This will avoid any possible loss to original report files as a result of the RPT Converter’s actions and reduce the number of reports converted at one time.

2) To start the RPT Converter

a) open the Report Converter executable from the workstation START > PROGRAMS > Crystal Reports program group > RPT Converter, or

b) b) click on the executable PS_HOME\bin\client\winx86\PSCVTRPT.EXE

3) If the reports contain any graphic, ole objects or soft fonts, confirm the workstation which is used to run the RPT Converter has those soft fonts and printer drivers supporting those fonts already installed.

4) The RPT Converter must run on a workstation with only the target PeopleTools and Crystal Reports releases

installed. No other versions of PeopleTools or Crystal must be installed. Select the directory to be converted. Select all 3 check boxes.

5) After the report converter process is completed, copy the resulting file back into the original source directory and

retest using the process scheduler.

Chapter 4 - Crystal in a Web Environment – Configuration and Use

Crystal Reports may be submitted to a PeopleSoft Process Scheduler for batch processing from a Web login For running Crystal reports through a Process Scheduler there is no requirement to install Crystal Software on the Process Scheduler machine. When a Crystal report is run by a Process Scheduler, it executes a special Crystal Reports API binary (PSCRRUN.EXE or PSBOERUN.EXE) on the Process Scheduler host machine. The exact API executed depends on whether Business Objects Enterprise has been implemented in the environment. The “PSPRCS.CFG” file contains a parameter CRWRPTPATH which points to the top-level directory location where the Crystal Reports RPT files will be found if the PSCRRUN.EXE is executed. The User’s LANGUAGE_CODE is then appended to the CRWRPTPATH to determine the sub-directory from where the report is taken. The Process Scheduler configuration file (PSPRCS.CFG) is found at the below location: %PS_HOME%/appserv/prcs/domain name/ Configuration Manager Workstation Installation With PeopleTools 8.44 onwards, the necessary Crystal DLLs and ODBC driver files are installed during startup of the Process Scheduler domain. Additionally, the Workstation Installation After changes are made to the Configuration Manager > Process Scheduler tab, perform the Workstation Installation to incorporate those changes into the Windows Registry and copy necessary files into the correct system locations. The Workstation Installation is described above in Chapter 2. The Workstation Install process creates a log showing each step in the WI process. This is the psinstal.log file written to the %TEMP% directory, which contains: Errors, the exact source and destination of each file copied, updates to the Windows Registry, and shortcuts created During WI process, these directories are written from: %PS_HOME%\setup\CrystalBin %PS_HOME%\setup\WINDOWS\SYSTEM These directories written to: C:\Program Files\Common Files\Crystal Decisions\2.0\bin C:\WINDOWS\system32 Crystal Reports are often submitted by end users from a run control page. It may be necessary to do the following in order to incorporate a custom Crystal Report into the application: Add a “Process Definition” for the Custom report :

PeopleTools > Process Scheduler > Processes > Add new Value 1) Update existing or create a new run control page using Application Designer 2) Update existing or create a new Component or Menu using Application Designer 3) Update existing or create a new Query 4) Update the Query Access List and/or other PeopleSoft Security Crystal reports can also be run, within a PSJOB, along with different other Process types. Users can run Crystals to different output types and output formats. Different Output types, available for Crystals in web environment:

Different Output formats, available for Crystals in web environment:

For more detail regarding Crystal, please refer to PeopleBooks: Home > PeopleBooks > Enterprise PeopleTools 8.49 PeopleBook: Crystal Reports for PeopleSoft > Crystal Reports for PeopleSoft Enterprise Preface

Chapter 5 - Crystal in a Web Environment - Troubleshooting

When troubleshooting Crystal Reports run by the Process Scheduler in a Web environment, consider these questions to clarify the issue, determine the root cause, and finally resolve the problem: Checklist: 1) Is this issue happening with all Crystal reports or with only some/one specific Crystal reports? 2) Is this issue happening when Crystal reports are run to specific output type (like web, printer, email etc.) or

specific output formats (like .PDF, .XLS, .HTM etc) 3) Is this issue intermittent in nature? 4) Is this issue happening with some specific group of users or with all the users? 5) Has the user ever successfully run the problem Crystal reports without this issue in the past, in the same

environment? 6) Are users able to run other Process Types like nVision or SQR successfully or is the issue specific to Crystal

reports only? 7) Are users able to run Crystals in other environments (like DEMO or TEST)? 8) What is the Crystal version and exact PeopleTools release? 9) Confirm there are not two or more different PeopleTools releases or Crystal versions running on the problem

Process Scheduler host machine.

When issues are happening with only ONE Crystal Report If the issues are happening with one or more specific Crystal reports, but not ALL, this indicates that basic setup for running Crystal reports from the Process are likely configured correctly. The issue may be within the Crystal report definition, the specific format, the Query, PeopleSoft Security, or other report-specific area. Review the below points: 1) Attempt to run the same Crystal report from the Crystal Designer client. 2) If not successful, the issue could be at the Query level. Please try to run the underlying Query from

ReportingTools > Query Manager. If the Query is not successful, correct the Query and then re-associate the modified Query to the Crystal report with the steps suggested in: (Doc ID 638844.1) “E-CR: How to change the Query a Crystal 9 Report is using?” Now retest.

3) Sometimes the issue happens on passing prompts in the command line which is generated for the Process

Scheduler. Confirm that the prompts are created in the PeopleSoft Query and not in the Crystal report. This is a PeopleSoft requirement.

It is also critical that the prompts created in the Process Scheduler command line are listed in the exact order as listed in the Query Prompts and in the SQL of the Query. Confirm that the prompts are in the correct order in the Process Definition for this Crystal report. The order of the prompt values are defined in the Crystal report Process Definition PeopleTools > Process Scheduler > Processes > Override Options > Parameter List > Append > Parameters. For a sample Crystal Report using 3 prompts the Parameter line would appear something like:

-ORIENTL :RUN_CNTL_AP.OPRID :RUN_CNTL_AP.RUN_CNTL_ID :RUN_CNTL_AP.START_DT

The prompts must be in the correct order expected by the Query Refer to PeopleBook Crystal Reports for additional information regarding dynamically selecting prompt values at runtime.

4) Determine if there are subreports attached to the problem Crystal report.

In Crystal Designer, open the report, highlight the subreport field and right click on it. Select the Change Subreport Links menu option. Click the drop down arrow and change the Subreport Parameter Field to Use value from the default value of "?Pm-xxxx" to "?xxxx" (where xxxx is the field name). The "Select data in subreport based on field" checkbox and drop down will become disabled. Click OK. Save the report and try rerunning it. Crystal Reports on-line Help explains Implicit and Explicit links between subreports and main reports. Review the information below:

---------- Crystal reports containing a subreport with prompts when running on the Web Linking a Subreport to the Main Report When a subreport is inserted, Crystal automatically creates a parameter field to link the subreport to the main report. This is called an Implicit Link. Depending on the needs of the subreport, the parameter may need to be changed. For instance, the main report may pass in a summary value that can be used in calculations by the subreport, or the main report may pass in the title of the subreport. When a field in the main report is linked to a parameter field in the subreport, it's called an Explicit Link. To change the subreport link: 1. Right-click on the subreport on the Crystal Reports - Report Template page. 2. Select Change Subreport Links to display the Subreport Links dialog window. 3. Click the Subreport parameter field to select from a dropdown list.

A small scroll bar will display. 4. Scroll to select the parameter field from the subreport. 5. Select the OK button to save the change.

See also Crystal Reports documentation. ----------

5) If the issue started happening suddenly, it may be caused by conflicting data in either the cache or the run

control record which can lead to errors. Shutdown the process scheduler and remove the existing cache directories. Restart the process scheduler and submit the same Crystal report with a new Run Control ID.

6) If the issue persists, turn on the Crystal trace in the PSPRCS.CFG file, restart the process scheduler, then re-

submit the problem Crystal report. A trace file will be created for that Crystal report in the specified directory which may be helpful in troubleshooting. Turn on the Crystal Trace by setting parameters under the Crystal section of the PSPRCS.CFG file. It looks like this.

[Crystal] ;========================================================================= ; Trace settings for Crystal ;========================================================================= Trace=NO TraceFile=%TEMP%\CRYSTAL.TRC Set the Trace=Yes and specify a location for the trace file to be written. By default it will be written to C:\Temp. After making changes in PSPRCS.CFG file, please reboot the Process Scheduler so that these changes will take effect.

7) Determine if the same report is running successfully in another environment, such as TEST or DEMO. If yes, compare the Process Definition of the same Crystal report in both the environments. If there is any difference, change accordingly. After making the changes, delete the Process Scheduler cache and then reboot the scheduler domain.

8) If the Crystal report is not generating the correct data, the issue may be with the Query associated with that

specific Crystal report. In that case, open the associated query in the Query Client or from the Web ReportingTools > Query Manager and run it. Compare the results of the query. If the results are correct for the Query, associate the query to the Crystal report again inside the Crystal Designer using the Database > Set Data Source Location option. For Crystal 9.0 there are specific steps to follow to perform the Set Datasource Location. Please review: E-CR: How to change the Query a Crystal 9 Report is using? (Doc ID 638844.1).

9) Sometimes an issue happens when a specific Crystal report errors out when sending to a printer. In those

scenarios open the report in Crystal Designer and go to

File > Printer Setup and “uncheck” the “No Printer” box. If that box is checked, the crystal report may not be sent to a Printer.

10) Confirm that the Query associated with a problem Crystal report is Public. Also, the name of the Query must

be unique. If the issue is happening with ALL Crystal reports If the issue is happening with all the Crystal reports, when running through the Process Scheduler, it may mean the issue is at the Process scheduler setup level. If Crystal reports are erroring out on a consistent basis, confirm the below 1) Perform a manual Workstation Installation on the Process Scheduler box, as discussed earlier. 2) If the issue started happening suddenly and the crystal reports were running fine, try deleting the Process

Scheduler cache and then rebooting the Scheduler domain. 3) If an error is received while sending Crystal report output to a Printer or sending output to a network drive,

confirm the BEA ProcMGR Tuxedo Service is started using "This Account" as opposed to LocalSystem. Start the BEA Tuxedo Service with the same EXACT Windows Login ID/Password that is starting the host machine and logging on to the Network Domain Upon startup of the host machine from a stopped state, when the Network Domain login screen appears after doing the Control + Alt + Delete, this must be the same Windows LoginID/Password which is starting the BEA Tuxedo Service under "This Account" .

4) Confirm there are not two or more different PeopleTools versions installed on the Process Scheduler host

machine. Multiple releases on the same host machine can be problematic for the following reasons:

Due to the Windows Registry design of the ODBC key under HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER, there is only one file location for the designated PSQODB32.DLL The Workstation Install copies DLLs from the PeopleTools File Manager Setup directories, as described above, into the system directories (C:\Program Files\Common Files\Crystal Decisions\2.0\bin and C:\WINDOWS\system32) Since the Workstation Install is performed with each Process Scheduler startup, the files are overwritten with the PeopleTools release last started. This may leads to many issues when multiple releases of PeopleTools are installed on the same host machine.

5) Anti-Virus software has been associated with damaging of Crystal Reports DLL running in memory or residing

on disk on a Process Scheduler box. Steps to troubleshoot 1) Check Process Scheduler logs for any error messages. The Process Scheduler logs are available in this

location

%PS_HOME% \appserv\prcs\<Process Scheduler domain name>\LOGS

2) The process Message Log accessible from the Process Monitor > Details page may contain important information. The Error message may help further troubleshoot the issue.

3) Try to determine whether the issue is happening with all the Crystal reports or some specific Crystal reports.

Test run the XRFWIN Crystal report in the Web environment from this navigation:

PeopleTools > Process Scheduler > System Process Requests 4) Select XRFWIN Crystal report to output type WEB and output format as PDF and run. If that runs to success

then the issue is likely specific to the certain Crystal reports only. 5) Determine whether the issue is happening with Crystal reports to some specific output formats such as: PDF.

DOC, or HTM 6) Test running XRFWIN Crystal report to different output types and output formats in combination. 7) The issue may be caused by damaged DLLs which are responsible for exporting Crystal output to the specific

format. For example the CRXF_PDF.DLL and ExportModeller.DLL are responsible for writing output to PDF. If the issue is only with using the PDF format then copy the DLLs from a working environment to the problem environment and retest.

8) Determine whether the issue is happening with Crystal reports to a specific output type such as: web. EMAIL or

PRINTER. For example, if the Crystal reports are running successfully when running to output format as WEB but failing when sending Crystal report to EMAIL or PRINTER, then the issue may be with underlying EMAIL or PRINTER configurations.

Investigate printer setup on the process scheduler host machine and SMTP services on the same machine.

9) If the error “wrong language selected” occurs when running Crystal reports, it is likely caused by a run control

record having been mistakenly created using a Language Code other than ENG.

To resolve the issue, update the run control record language code to ENG. Additionally, examine the run control tables for a non-supported language. PeopleTools does not prevent an incorrect language code from being submitted. Report run control tables may have names like PS_RUN_<report name> OR PS_RUN_CNTL_<report name>. Run control data is also present in PS_PRCSRUNCNTL table. Example SQL to execute: select OPRID, RUN_CNTL_ID, LANGUAGE_CD from PS_PRCSRUNCNTL where LANGUAGE_CD <> 'ENG' order by OPRID, RUN_CNTL_ID, LANGUAGE_CD

Check the same run control tables in ALL other environments, such as DEV, DEMO, TEST, etc., to assure the issue is stopped. After fixing the Language Codes in the run control tables or all environments, stop and re-start the PSNT Process Schedulers and test running the Crystals again

If the issue is happening intermittently with ALL Crystal reports If the basic delivered functionality of Crystal Reports through the Process Scheduler is working for delivered sample reports, such as the XRFWIN report, yet intermittently reports go to error, examine the following: 1) Intermittent issues happen due to corruption of Process Scheduler cache or a block of resources. Firstly,

delete the Process Scheduler cache and then restart the Scheduler domain. Retest. 2) When Crystal reports start remaining in Queued status or remain in the Processing status, there may be a out-

of-sync condition or blocked status with the Process Scheduler tables.

a) Confirm the PSPRCSRQST and PSPRCSQUE records have the same number of rows

SELECT COUNT (*) FROM PSPRCSRQST SELECT COUNT (*) FROM PSPRCSQUE SELECT COUNT * FROM PS_MESSAGE_LOG b) Execute the following SQL to determine the rows that are out of sync (Oracle) and Delete any rows returned by these queries:

SELECT A.PRCSINSTANCE FROM PSPRCSRQST A WHERE NOT EXISTS (SELECT 'X' FROM PSPRCSQUE B WHERE B.PRCSINSTANCE = A.PRCSINSTANCE) / SELECT A.PRCSINSTANCE FROM PSPRCSQUE A WHERE NOT EXISTS (SELECT 'X' FROM PSPRCSRQST B WHERE B.PRCSINSTANCE = A.PRCSINSTANCE) /

c) Check the PSPRCSRQST record for old Crystals stuck in “Queued” status d) Check the PSPRCSRQST and PSPRCSQUE records for previous requests in Error or Blocked status. There may be some queued processes in the PSPRCSRQST record and the PSPRCSQUE record from an old system. Delete any such processes from the PSPRCSRQST and PSPRCSQUE records. Then delete cache files and restart the Scheduler.

3) If the issue happens only when multiple Crystal reports are running simultaneously, increase the Max

Concurrent setting for Crystal in the Server definition page:

Example: Max API Aware: 7 Crystal Max Concurrent: 3 Each Scheduler server has a Max API Aware number for Concurrent tasks and each Process Type has a Max Concurrent for that process type. Max API Aware =5 COBOL=3 Crystal=3 SQR=3

If 3 processes of each process type are submitted, then there are 9 processes running. The maximum number of API-aware processes will never exceed the MAX API configuration. Depending on the total number of processes submitted, there may be insufficient slots for the Crystal Reports to be initiated in the timeframe desired.

4) There are reported issues with Crystals remaining in the Queued status, when a Master Scheduler service is

running. Refer to E-CR: Command line length being truncated (Doc ID 612557.1) 5) Crystal Reports 9.0 SP7 patch is required. In the absence of the SP7 patch, one may receive the 'memory

full' error during export and 'Not enough memory for operation' when running via Process Scheduler. Refer to: E-CR: CR9 Error 'memory full' during export and 'Not enough memory for operation' (Doc ID 658499.1) for more details

Crystal reports printer issues: 1) For Crystal reports or nVision reports to print successfully to network printers specified by the UNC pathname.

the network printer must be configured on the process scheduler as a "Network" printer, having a Standard TCP/IP port. When configuring the printer, the "Network" option should be chosen and not the "Local" option.

2) The “BeaProcMgr” Tuxedo service, must be started as “This Account” instead of “Local System Account”.

Start the BEA Tuxedo Service with the same Windows Login User ID/Password that is physically booting up the PSNT Server machine and logging on to the Network Domain When starting the process scheduler manually login to the machine with the same UserID/Password as was used to connect to the network. When starting the process scheduler as a Windows Service, specify the same UserID/Password in the Services page > Log On As field.

3) Confirm that Printer Drivers are installed properly on the Process Scheduler machine

If the printer driver is properly installed and the BeaProcMgr service is logged in as “This Account”, Crystal reports should go to a printer successfully. Test sending the XRFWIN Crystal report to the printer.

Crystal Issues with “Email” output type

1) For sending Crystal reports to Email output type, confirm that the SMTP server is configured correctly in the PSPRCS.CFG

and PSAPPSRV.CFG file. 2) The User’s email ID is a functioning address defined at the User Profile level and is authorized to view the reports.

Crystal issue is with some specific Users 1) If only some users are not able to run Crystal reports, confirm that the problem users have access to run the

Queries behind those Crystal reports. This may be confirmed by running the underlying Query from the ReportingTools > Query Manager

Crystal Performance: 1) If the issue started happening suddenly, the problem may be caused at the Process Scheduler level. In these

scenarios, delete the Process Scheduler cache and then restart the Scheduler domain. Check the number of subdirectories and files in the directory specified as Log/Output Directory in the psprcs.cfg scheduler configuration file.

2) If the performance issue is with only one Crystal report, determine if subreports are included in that report. If

yes, check if subreports are defined in the “detail” section of the main report. If yes, this is a known issue with Crystal Software itself. In this case, define the subreport in the Crystal report’s “header” as opposed to the “detail” section.

Below are the inputs of Business Objects/SAP

------- The best way of using Subreports is to put them in the Group Header, Group Footer, Report Header, Report Footer sections but avoid using it in the Details section.

In case one does not want to move the subreport from the “Details section” then try to make the subreport 'On -Demand'. To make a subreport On-Demand, go to the Design view of the Report. Right click the subreport and click on Format Subreport. Now go to the Subreport tab and check the On-demand subreport check box. Click OK When a subreport is called as On-Demand, it creates a hyperlink of the subreport. Every time the report is run, there is an option of clicking on the hyperlink to show the data of the subreport. In case one does not need the subreport to be evaluated, simply do no click on the link and hence the data retrieval time is saved. ---------

3) If the Crystal takes a long time, run the Query behind this Crystal report to determine if the performance

degradation is with the Query. If it is at the Query level also, then correct the Query performance first. 4) Check that indexes are not corrupted (incorrect) and are being used by the query. (The DBA should have

tools to help with this task.). If the indexes are corrupt, drop and recreate them. If the SQL runs slower with the index that without it, then consider dropping the index (this sometimes happens). Confirm that database statistics are recent and are FULL SCAN rather than sample.

5) Open the Process Scheduler logs and determine what ran and how long it ran. When the processes ran long,

from the scheduler logs, determine what else was running at that same time. Was the problem caused by over-use of the available resources on the host server? Open the Windows Task Manager and monitor the resource usage at the time users are running these reports. Confirm there is memory available and users are not running more processes simultaneously than the resources available. What else is running on the same host?

6) Check server definition (PeopleTools >Process Scheduler > Servers) Perhaps 6 concurrent Crystal Reports is

too much with the other reports that may be running on the host. Reduce the Crystal Reports Max Concurrent to 3 or even fewer. After making any changes, reboot the scheduler domain and clear the cache before restarting. Reducing the number of concurrent processes will also have an impact at the database level.

7) Confirm there is adequate system global area and temporary database space for sorting. The DBA typically

looks at this. 8) If development work is being performed on the same machine as the production scheduler, relocate it to

another host. 9) Create another scheduler on a different host to attempt isolation of the machine as a possible cause.

Crystal Formatting Issues: Some formatting issues have been reported for Crystal Reports. The issues deal with:

• Extra pages in the report output

• Extra columns

• Fonts too big or too small

• Extra lines in the report output

• Column widths of variable size Examples: “The reports are running fine on our system but the only issue is that they are not running correctly to populate the cells of Excel spreadsheet or CSV format as it would show in a PDF format. See attached files...”

1) Check if the formatting issue is happening only when crystals are running to any specific formats or with all the formats. In most cases, these formatting issues happen when running Crystals to any specific formats, such as: XLS or CSV or PDF etc. In these situations, check if the same report is showing the formatting issue when running to other output formats.

Determine if the same report is showing the same behavior in DEMO or other environments also. If not, there is very much probability that the specific DLL (responsible to export the crystal output to that specific format) has been corrupted in memory or on disk. In these scenarios, please rename the same DLL in the problem environment, and copy the same DLL from the working environment to the problem environment. Restart the Scheduler and re-test.

If the issue persists, please check ICE for previously reported issues. Below are important Oracle Knowledge Documents dealing with format-related issues of using Crystal reports in a PeopleSoft environment:

• E-CR: Crystal 9 Outputting report to PDF format and then printing, generates lo (Doc ID 624700.1)

• E-CR: Crystal 8.5 PDF output does not handle Long-Char Fields correctly (Doc ID 648781.1)

• E-CR: Crystal - Graph not exported in PDF and HTML format (Doc ID 615356.1)

• E-CR: HTM format Crystal Report fonts gets large and not aligned after 30 pages (Doc ID 653361.1)

• E-CR: Crystal Reports 8 Exporting options/limitations - White Paper (Doc ID 616257.1)

• E-CR: Crystal to PDF and Font is bad when viewing PDF document (Doc ID 622504.1)

• E-CR: Cannot display Chinese characters in PDF format (Doc ID 624236.1)

Application specific Crystal Issues To determine whether the issue is PeopleTools specific or Application specific, run the basic “Cross reference” Crystal reports XRFWIN.RPT in the problem environment. If that report goes to Run Status = Success, this is a strong indication that basic Crystal functionality is working as designed. If the issue is happening only while running a specific Application Crystal report, then examine the following: 1) Some reports are not able to opened using the Crystal Designer client using a 2-tier connection and are

receiving “data out of memory” related error messages.

In this scenario, often the issue is due to a damaged specific RPT file. In this situation, open the same file in any other environment. If the same report may be opened in another environment, replace that .RPT file from the working environment to the non-working environment.

It may be helpful to use the crystal .RPT report layout from the Demo environment.

2) There are issues reported with printing MICR Fonts on Crystal Checks or simply with printing Crystal checks

(for example: APY2021).

For troubleshooting this issue, confirm that users are able to print Crystal reports such as the delivered XRFWIN successfully. If not, resolve the basic printer functionality by following the above points under “Crystal Printing Issues”. If XRFWIN Crystal is printing successfully, it indicates that the issue is Application specific. Please refer to the below Doc IDs before opening a new SR

• EAP - Unable to print MICR font on new printer Troy 2420 (Doc ID 657793.1)

• EAP: Not able to print MICR fonts for APY2021 Crystal Checks (Doc ID 636857.1)

• E-CR: Troubleshooting AP Checks Printer Errors (Doc ID 651735.1)

• AP: Paycycle error Selected Process Scheduler not currently running (7250,15) (Doc ID 612452.1)

Chapter 6 - Business Objects Enterprise Java Environment – Configuration and Use

Business Objects Enterprise (Crystal Enterprise)

Business Objects Enterprise XI (BOE XI), also known as Crystal Enterprise, is supported by PeopleTools starting in PeopleTools 8.46 as the java-based version of Crystal Reports. PeopleTools T 8.46 and PeopleTools 8.47 support “Crystal Enterprise 10”. Starting in PeopleTools 8.48 “BOER XI” is supported.

Crystal Reports Environments for PeopleSoft Enterprise PeopleSoft applications are delivered to work with the Crystal Reports 9 runtime environment. PeopleSoft Process Scheduler report definitions are configured to use the Crystal Reports 9 print engine, and the delivered Crystal Report definition files are in the Crystal Report 9 format. You use the Crystal Reports 9 product to create and edit report definitions. If you are using PeopleSoft PeopleTools 8.48 and above, you can optionally use the Business Objects Enterprise XI runtime environment to run and view your reports. With Business Objects Enterprise XI, you use the Crystal Reports XI product to create and edit report definitions. A PeopleSoft-supplied conversion program, pscrconv.exe, converts the Crystal Report definition files from the Crystal Reports 9 (CR9) format to the Crystal Reports XI format. The BOE XI reports are stored in a database, rather than as flat files. The executable used to run this report is java-based, rather than the DLL based as with CR9. For PeopleSoft applications, you must use either the Crystal Reports 9 or the Business Objects Enterprise XI runtime environment. You cannot run a mixed environment in which some reports run using Crystal Report 9 and some reports run using Business Objects Enterprise XI. PeopleBooks for Crystal Reports describes how this product works.

When to Use BOE(CE)

The most important benefit of using BOE XI instead of CR9, is the ability to run Crystal Reports on UNIX process schedulers.

BOE Installation and Configuration Documentation for installation and configuration of BOE XI (CE) is available at the hosted PeopleBooks site: Crystal Reports for PeopleSoft Enterprise which describes how this product works. http://download.oracle.com/docs/cd/E13292_01/pt849pbr0/eng/psbooks/tcyr/book.htm

Search for "Using Crystal Reports XI" and "Understanding Crystal Reports XI Compatibility Issues" Begin any installation of BOE XI(CE) with a thorough reading of the appropriate PeopleSoft Enterprise PeopleTools Installation guide for your database platform. Installing and Configuring Software for Crystal Reports, Administering and Using Business Objects Enterprise XI.

Chapter 7 - Business Objects Enterprise Java Environment – Troubleshooting

References: 1) BOE XI Platforms.txt for Windows - available on DISK1, DOCS\en folder, downloadable from http://edelivery.oracle.com 2) BOE XI Install.PDF for Windows - available on DISK1, DOCS\en folder, downloadable from http://edelivery.oracle.com 3) PeopleTools 8.48 Installation Guide. - http://www.peoplesoft.com>Site Index>Installation Guides and Notes>PT8.48

PeopleTools Installation Guide Referenced Issues:

Task 11-3-3: Installing Business Objects Enterprise XI on Windows If the installation program gives an error when trying to access the files on the 2

nd and 3

rd CD, it may be necessary

to copy the ~\win32\* files from those 2 CDs to the 1st CD ~\win32 directory. In other words, you may have to copy

the 2nd and 3

rd CDs to the common directory on the 1

st CD.

Task 11-3-12: Configuring the PeopleSoft Application for Business Objects Enterprise XI Integration After running the indicated DMS script and project, check the process type definition in your environment. You may still need to manually update the Process Type definition for Crystal for the specific database to reflect the new command line executable. %%TOOLBINSRV%%\PSBOERUN.EXE Task 11-3-14: Verifying the PeopleSoft to Business Objects Enterprise XI Integration When testing a report and viewing the output from the Process Monitor or the Report Manager, the report is being pulled up directly from the PSREPORTS report repository using the PIA web server. The documentation indicates the viewer will be the BOE Info Viewer, which does not appear to be the case. Here is the doc…

2. View Report output in InfoViewer a. Using the Process Instance ID, ensure the process runs to completion in process monitor. b. Select Reporting Tools, Report Manager, and select the Administration Tab. c. Search for the report using the process instance id generated from step 2. d. Click the Details link next to the report, then the .RPT link to view the report in the Business Objects Enterprise XI report viewer.

Task 11-8-2: Converting Reports from Crystal Reports 9 Format to Crystal Reports XI Format It is necessary to have both Crystal Reports 9 and Crystal Reports XI installed on the workstation simultaneously for this step to complete.

Problems and Solutions: 1- “Error: Create top level folder failed” during conversion Solution: Login to BOE XI and add BOE_ADMIN to Administrators Group. 2- “Error: Failed to retrieve the 0-th formula field of the report” Solution: Grant QUERY_TREE_PT to PeopleSoft BOE_ADMIN

a) Login to PeopleSoft, navigate to PeopleTools > Security> User Profile > open BOE_ADMIN and determine the Primary Permission List

b) Navigate to Security> Permission Lists > open the Primary Permission List c) Navigate to PeopleTools Tab > click Query Access d) Navigate to Query Tab > Access Group Permissions > Add QUERY_TREE_PT e) SAVE

3- “Error: Failed to open the Report File” Solution:

a) Deinstall all prior releases of Crystal Reports, clean the Windows Registry and remove all installation directories

b) Install Crystal Reports 9 c) Install Crystal Reports XI d) Add the location of Crystal Reports 9 CRW32.exe to the Configuration Manager Workstation install.

Appendix A - Important Doc IDs

Below is, a sample of Doc Ids, dealing with various types of Crystal issues

• E-CR: Cannot display Chinese characters in PDF format (Doc ID 624236.1)

• CR: Master Resolution for Crystal Reports Print Engine error text: Error in Fil (Doc ID 614753.1)

• E-CR: Crystal Date Format Issue (Doc ID 619839.1)

• E-CR/NV: If one Crystal report hangs, then subsequent Crystal reports all error (Doc ID 619991.1)

• E-CR: Crystal Trace error, "Error Starting PeopleTools" (Doc ID 618497.1)

• E-CR: How to change the Query a Crystal 9 Report is using? (Doc ID 638844.1)

• E-CR: Troubleshooting AP Checks Printer Errors (Doc ID 651735.1) Crystal/Printer issues:

• E-CR: Crystal report on the Web with output directly to printer and getting err (Doc ID 611395.1).

• EAP: Troubleshooting Crystal Check Signature, MICR and Printer issues (Doc ID 636478.1)

• E-CR: Troubleshooting AP Checks Printer Errors (Doc ID 651735.1) • E-CR: Crystal Report printing is generating "PSPAL::Abort" error (Doc ID 654202.1)

• E-CR: Crystal PDF output goes to Portrait instead of Landscape (Doc ID 616198.1)

• E-CR: How to correctly specify the Printer and Orientation in Crystal? (Doc ID 621234.1)

• E-CR: Crystal AP Checks - output to specific printer trays - APY2021, CHECK1, 2 (Doc ID 640344.1)

• E-CR: Crystal-language issues and Printer issues via the Web/PIA (Doc ID 641292.1)

• E-CR: Crystal Printing issues/errors via the Web (PIA) (Doc ID 654039.1)

• E-CR: Crystal Reports 8.5 produce error of, "No Default Printer" (Doc ID 617896.1)

• E-CR: Crystal reports through the Process Scheduler will not print to Legal siz (Doc ID 618585.1)

Crystal/Email issues:

• E-AS: How to interpret SMTP tracing (Doc ID 611273.1)

• E-CR/NV: Crystal's and nVision's error to "Email/PDF" after Tools Patch 8.45.18 (Doc ID 643185.1)

• E-WF/PRCS: How to configure SMTP PeopleTools 8.1x, 8.4x (Doc ID 610132.1)

Appendix B - Important Incidents

Below are some important issues with Crystal Reports previously reported to Development.

Incident # 1325413000 -- Unable to perform Queries using PSODBC in 8.46 Tools for BAM Connectivity

(Business Analysis Modeller)

Incident # 1376228000 -- Crystal 9 is getting an error if left idle for 20 minutes

Error may be:

Incident # 1655734000 -- Language code for Crystal Report getting overwritten with lang code of another report

run at exactly the same time by another user.

Incident # 122146000 -- Crystal report: custom date/time format has no impact of the output layout

Incident # 1343207000 -- Crystal's don't email to Distribution for "Email/PDF" after Tools Patch 8.45.18

Incident # 110799000 -- Crystal 9 - Add ability to export to XML output format.

Incident # 1728266000 -- pstowordsloc function is not producing correct results for ITALIAN language

Incident # 150577000 -- Crystal checks & file copy sent to printer will only print from the default tray

Incident # 142287000 -- Crystal formats all dates and times based on the server's locale, not the report

requester's locale

Appendix C - Validation and Feedback

This section documents customer response to this Troubleshooting Guide. Customer Validation PeopleSoft is interested in obtaining feedback regarding this document. Additional content will be verified, replicated and posted here.

References

1) PeopleBooks

http://www.oracle.com/pls/psft/homepage > PeopleTools Release > Crystal Reports for PeopleSoft

2) Oracle MetaLink

https://metalink3.oracle.com

• Knowledge > Tools and Technology > ReportingTools

• Product Certifications > PeopleSoft Enterprise Certifications

• Patches and Downloads > edelivery.oracle.com

3) PeopleTools Installation Guides and Notes

https://metalink3.oracle.com

• Knowledge > Browse Home > Tools and Technology > Documentation > Installation Guides and Notes

4) Crystal Reports and Business Objects Enterprise references

http://www12.sap.com/usa/solutions/sapbusinessobjects/index.epx

PeopleSoft Crystal Reports 8.5/9/XI Troubleshooting Guide By Sandeep Verma and Kirsten Zurbrugg [March] 2009 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com Copyright © 2009, Oracle. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. One specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.