Last updated on MARCH 25, 2013
Applies to:PeopleSoft Enterprise HRMS ePay - Version: 9
Information in this document applies to any platform.
Need performance tuning info for XMLP in regards to HCM 9.0 ePay View Paycheck. It is taking 1 minute or more to bring up a PDF paycheck when using XMLP.
Viewing self-service paycheck via XMLP generates tracesql files. Each time a self-service check is viewed, a file with a name similar to A20224_10050577wxp.andersencorp.com.tracesql is generated or appended to. How do we turn off this tracing? The login id does not active tracing on the login screen. The psappsrv.cfg file has these options - TraceSql=0, TracePC=0, TracePPR=0, TracePIA=0, TraceAE=0,TraceAnalytic=14380470,TracePPM=0. The check was generated from the standard PeopleSoft process "PY_SSP_PRINT".
What could be activating these traces?
Viewing self-service paycheck via XMLP generates tracesql files. Is this by design? We don't understand why the WriteToLog function is there. Can we comment out the WriteToLog function?
View self-service pay check fails sporadically and many users are facing issues. We upgraded our HRMS app from 8.8 to 9.0 and getting following error when user try to view paycheck.
"Unable to generate PDF output. (2002,580). The system failed to generate the PDF output. Ensure that the XML data file is in the file attachment table and in the right format"
An XML Publisher trace is generated for every XML Publisher process scheduled through the Process Scheduler. For example, AE_XRFWIN_1557.trc The generation of this trace file cannot be disabled by any of the trace or logging parameters that are in the psappsrv.cfg/psprcs.cfg file. How do we turn off the tracing for XMLP process types?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms