My Oracle Support Banner

EPY: Troubleshooting Online Checks (Primary Solution) (Doc ID 623262.1)

Last updated on APRIL 11, 2024

Applies to:

PeopleSoft Enterprise HCM Payroll for North America - Version 8 and later
Information in this document applies to any platform.

This document was previously published as Customer Connection Solution 200772000


Here are some things to be aware of when using the Online Check functionality within PS Payroll:

1. The online cheque feature is a remote call process (i.e., COBOL).  In version 7 and beyond, where it is executed depends on how the users are logged in.  If you log into the application in two tier, then the Online Check COBOL processes are executed on the client workstation.  If you log into HRMS in three tier, then Online Check processes are executed on the Application Server.  The customer cannot override this and alter these run locations.

2. The Key:  Where is the software executed, on the client workstation, or on the AppServer?  Your COBOL executables (compiled programs) must be current for your run location, whether client or AppServer.  PeopleSoft no longer delivers compiled COBOL executables for the client workstation.   If a posted fix, tax update, or AU includes changes to any of the COBOL modules used by Online Check (for Paycalc, Confirm, Check Print, etc.), then these COBOL program changes must be reflected on the client workstation -- i.e., the customer must recompile the COBOL programs for the client.

Some customers have reported that their organization has a policy that they do not do workstation COBOL compiles.  These customers have problems because the COBOL being executed on the workstation is not current with the Tax Updates and other product changes that they have installed.

If the customer customizes COBOL modules like PAYCALC, and compiles the COBOL programs only on the Server, then these COBOL customizations will not be reflected in the Online Check processes executed on the workstation.  Customers must recompile on the workstation to reflect their changes; if they don't then the Online Cheque functionality may not work correctly.

If the customer does not have a client COBOL compiler, and therefore cannot compile the COBOL programs so they can be executed on the client workstation, then the Online Check functionality may not work correctly.  In this circumstance, the only way they will be able to run the online cheques (or ANY remote call processes) is to log in three tier mode.  Even then they must have a compiler compatible with the Application Server (NT or Unix), and keep that codeline current.

Some of the Common Error messages GSC come across when running online checks
Customer is trying to generate Online checks  getting errors.

Error  REMOTE PROGRAM PSPPYRUN FAILED WITH RETURN CODE 8075.  Reason an unsupported Parameter datatype was specified in section SQLRT:9003

We are getting the following error when attempting to run the on-line check process:
"Remote program PSPPYBLD failed with return code : 9998. Reason: Invalid action request. In section : SQLRT: MAIN(2,-1) at FUNLCIB_PAY.RETURN_CD.FieldFormula emulate_paysheet PCPC:8471 Statement:124"

This occurs after "Yes" is entered for "Do you wish to use the paysheet creation process to create data for this employee for online use? (2000,139)"


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.