Scribd
Upload
39 views2 pages

Troubleshooting Forecasting (Remote Call) Issues in Global Payroll & Absence Management

Uploaded by

laguduvp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
39 views2 pages

Troubleshooting Forecasting (Remote Call) Issues in Global Payroll & Absence Management

Uploaded by

laguduvp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Document 963598.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...

Copyright (c) 2018, Oracle. All rights reserved. Oracle Confidential.

EGP/AM: Troubleshooting Forecasting (Remote Call) issues in Global Payroll & Absence Management (Doc
ID 963598.1)

In this Document

Purpose
Troubleshooting Steps

APPLIES TO:

PeopleSoft Enterprise HCM Global Payroll Core - Version 8.9 to 9.2 [Release 8.9 to 9]
Information in this document applies to any platform.
This document applies to customers using PeopleSoft Global Payroll and Absence Management. This is a living document and will be updated
periodically.

PURPOSE

The intent of this document is to cover the following topics.


1. Usage of “Remote Call” function in Global Payroll and Absence Management.
2. Troubleshooting Absence Forecasting Issues (technical & non technical)
3. Preliminary technical/non technical work required to be conducted prior to contacting Oracle Support.

TROUBLESHOOTING STEPS

Remote Call is a PeopleTools function, which is used to call a Tuxedo service from a PeopleSoft application. A typical use of Remote Call is
to run data-intensive, performance-sensitive programs near or on the application server.
In Global Payroll and Absence Management, Remote Call is used by Forecasting and Formula validation processes.
Absence Forecasting process is used to evaluate the impact of an absence event and to review absence entitlement balances.
Formula validation process is used to ensure the logic created is valid. If an attempt is made to run Global Payroll/Absence Management
process using a formula that is not validated, an error will be issued.
Absence Forecasting framework is comprised of 2 components, functional and technical. The following are a few functional guidelines
covering Absence configuration.
1. Please ensure that monthly entitlement calendars are setup correctly and attached to the forecasting calendar group.
2. The current batch design requires setup forecasting filters to process absences entered via Self Service. The forecasting filters are not
only intended to drive forecasting processing, they are also intended to drive
batch processing for those events entered via Absence Self Service .
3. Absence Forecast Transaction Entries are required.
Navigate via Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Elements, Absence Elements, Absence Forecast Transactions,
Transaction Definition
Country = "The country in which you are located" and Transaction ID = 100
&110 (Absence Event Forecast) and add an entry for WF Status = Approved.
4. Inconsistent results - Processing calendars out of order could impact forecasting outcome. The forecasting process computes the
balance utilizing the template. Hence with the template you are indicating what calendars to process and the sequence as well.
5. Off-cycle calendars normally do not get processed in forecasting since those types can t be included in the Template. However if you run
and confirm an off-cycle, then the next time you run On-cycle forecasting the start balance for your off-cycle will be included in the next
forecasting process.
As mentioned above, Absence Forecasting process uses Remote Call function to invoke Cobols on the Application server for computing and
forecasting the absence entitlement balances. For this reason, when an error occurs in the batch process(Forecasting), a generic error
message is produced online providing limited information.
The very first step suggested, when a Forecasting process returns an error, is to check the PeopleTools Remote Call Utility.
Navigation PeopleTools > Utilities> Debug > PeopleTools Test Utilities - Test Remote Call.
1) If the above test fails, its an indication that the environment is not setup with correct Remote Call frame work. A new Service Request
with PeopleTools Integration Tools is suggested in this case. The PeopleTools framework needs to be intact in order to perform forecasting.
Should the above test results in Success and still experiencing problems, please proceed further.
2) Please ensure that the Cobols on Application Server are in sync with the Cobols on Process Scheduler. Recompile all the cobols on
Application server and rerun STOREGP.dms.
3) In order to determine the exact error, a trace file is required. Tracing Remote Call process is not same as tracing any other cobol process
in the system. This task is generally executed by the PeopleSoft
System Administrators, as this would require read/write access to psappsrv.cfg

1 of 2 12/13/2018, 1:53 PM
Document 963598.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...

a) Open psappsrv.cfg in edit mode.


b) Modify the RCCBL Redirect parameter to 1.
c) Modify the TraceSQL parameter to 255
d) Save psappsrv.cfg
e) Reboot application server.

Note: Suggest to set the parameter 'Allow Dynamic Changes' to 'Y'


e.g Allow Dynamic Changes=Y
This allows for dynamic changes to certain setting without having to reboot to the application server domain. This includes TraceSQL
parameter.

The TraceSQL param will trace ALL the sql activity taking place on the appsrv domain. So please remember to turn it on just prior to
replication and turn it off right after replication.

4. Review the trace files to determine the problem/error.


The above will generate remote call trace files ( like *rmt*, *.err, *.out ) and sql trace file for GPPOLRUN(Forecasting) cobol process. The
above same settings are applicable for troubleshooting Formula validation errors as well, in case the online error is not clear enough.

Check the trace to see if there is a specific statement or several statements running slow or if the trace indicates overall slowness. And
action further to investigate and resolve that specific sql (e.g stats on table missing, index on table or tables missing etc ) or for overall
slowness, check if update stats required for all tables, look into DB tuning etc )

Didn't find what you are looking for?

2 of 2 12/13/2018, 1:53 PM

You might also like