My Oracle Support Banner

EPI: Payroll Interface Export Process ABENDED at Step PI_INRUN.2EXPORT.Step01 (PeopleCode) - Troubleshooting Tips (Doc ID 610783.1)

Last updated on NOVEMBER 15, 2019

Applies to:

PeopleSoft Enterprise HCM Payroll Interface - Version 8.8 SP1 and later
Information in this document applies to any platform.
*** This document reviewed for relevancy on September 9, 2014 ***


Purpose

Listed below are troubleshooting tips to consider when Payroll Interface export process runs to "No Success" with the following (or similar) information displayed in logfile:

 

PI_INRUN Application Engine program calls COBOL program PIPINRUN using the Remote Call PeopleCode function. This error is a high level indication that a problem occurred during the COBOL process PIPINRUN. To trouble shoot the error requires more detail obtained from the console out file generated by the process named PIPINRUN_nnnnnn.out. This file contains all the displays generated by the various COBOL programs that are executed by the process chain initiated from PI_INrun (AE process)

Please note that when you reprocess the failed PI Run, the process scheduler may try to retart the prior failed AE process, causing a restart in the middle instead of a full reexecution from the beginning. This will result in the error: "all processes suspended".

To prevent this, delete all failed requests from the process request table via Process Monitor.

If you require further assistance in troubleshooting the error and log a Service Request, please attach the logfile (or "out" file) to your SR.  More information can be obtained by use of the Trace SQL option provided for COBOL processes.

 

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
References

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