Monday, June 26, 2017

Why query is not visible in Query Manager

Did you ever felt embarrassed by not being able to even open the Query in Query Manager let alone modify it despite having access to it i.e having access to records used in query and to make the matter even worse, this all happened when you are a PeopleSoft consultant who is believed to know such technical glitches.

Well, guess what, this was exactly what happened to me few years ago. There was a query of type Role with a simple SQL text 

SELECT OPRID FROM PSOPRDEFN

These were the properties of the query




There was requirement to make some changes in this so I quickly tried to open it in Query Manager but it didn't come in search result. Whenever we come across this particular incident, there are two things that you believe could cause this:


You don't have access to Query

If you don't have access to all records used in Query through Query Security Tree then you won't see the query neither in Query Manager or Query Viewer. So, I open the query in Query Administration (Peopletools - Utilities - Administration - Query Administration) and checked the SQL and discovered that only one record PSOPRDEFN has been used in this query to which I already have access which effectively authorizes me to open the query in Query Manager but it didn't.

Note - Query Administrator page empowers you to open any type of query whether or not you have access to it.


Query is private

Having had no luck here, I then turned my attention to what if Query is Private ? so I looked closely at the attributes of this query in Query Administration.



Having discovered that query isn't private either because it's not assigned to any user, when it's assigned to a user then it means it's private, I then started to feel puzzled as to what the heck is going on. Then after digging through little more I felt so stupid when I finally figured it out. I went to query manager again and clicked on Advance Search



There it is..! by default the query type selected by system is User so when I entered the query name and hit on search, the Query Manager tried to search only those with type User whereas my query was of type Role hence despite having full access to it and query being public too, I couldn't fetch it.

So all I did was, change the value in the drop down above to Role and then performed the search again and it did the trick.

Thursday, June 22, 2017

Creating a Component Interface in PeopleSoft

You can gain in-depth knowledge on CI with a live example by just paying below amount


I have a complete session in two parts which explains:

  1. How CI works - Overview, all the elements of CI etc..
  2. Creating an Inbound interface, that loads data on a multi level component using CI and App Engine
Below are the links to videos in YouTube.

CI Part 1
CI Part 2

Click here to know how it works

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

Wednesday, June 21, 2017

How it works

Send an email/message on either of below contact to know how to make payment

santosh.tripathi87@gmail.com
Whatsapp - +91 8800648297
skype - santosh.tripathi72


Once the payment is done, you will get access immediately to the videos shown in the link on the shared Gmail ID, a email notification with link to videos will also be sent

Done..!!

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

Saturday, June 17, 2017

PeopleSoft Benefit Record Number Vs Employee Record Number

These two elements are always confusing especially for the person who isn't well versed with the Person Model.
The Employee record Number (ERN) is updated whenever a new assignment is created.The Benefit Record Number is defaulted to 0 to attach the new job with Benefit Record Number 0 but can be overridden to the particular number if it needs to be attached to that Benefit Record Number.

The Benefit Record Number is used by benefit module to track benefit entitlements of employees. Multiple Employee Records (EMPL_RCD) can be grouped under one Benefit Record Number.

Lets try to understand this with a very simple scenario.

Lets say a person is a professor in a college with Employee Record 0 and is eligible for various benefits so we assign the Ben Record Number as 0 to track his eligibility and enrollments in various benefit plans.

Lets say this person got appointed as a Dean of the same college after some time so a new job got created with Empl Record 1 but since this new job doesn't make him eligible for any new benefit program so we keep the Ben Record Number as 0.

But after sometime, lets say this person appointed as a physician also in the same college so we created a new job with Empl Record 2. However, this new job entitles him for an additional benefit program but can't be mixed with previous one so we assign ben record number for this new job as 1 for eligibility and enrollment of this employee under new benefit program.

Saturday, September 24, 2016

PeopleSoft Time and Labor Setup Architecture

Lets first have a look at this image:


Time and Labor Setup, Time and Labor Architecture

The image shows how all the elements in Time and Labor setup are related.

Holiday Schedule

They contain the calendar for public holidays which can be defined for a country, region within the country or at business unit level etc... It’s a very vital element because when the time is reported for a period through the timesheet page, system must know if there is any public holiday in that period.

Work Schedule

This represents the working pattern of employees for example an employee’s work patter could be any of these:

  1. Monday to Friday 8 hours each day with Saturday and Sunday weekly offs
  2. Monday to Wednesday 8 hours each day, Thursday to Friday 10 hours each with Saturday and Sunday weekly offs
  3. Tuesday to Saturday 4 hours each day with Sunday and Monday weekly offs

Having work pattern details in Time and Labour is very important because according to this only employees will report their time.  Work Schedules are grouped together to form Schedule Groups.

Time Period

It’s the date range for which employees will report their time for example Daily, Weekly, Monthly, Bi-Weekly etc...

Time Reporting Code(TRC)

These are used to just track employee’s time for administrative or compensation needs. 
For example:
We can define a TRC as REGLR for reporting regular weekly time
We can define a TRC as PAIDLV for reporting paid leave
We can define a TRC as OVRTME for reporting over time.

For instance, if an employee who is supposed to work 40 hours a week, works for 35 hours in which 3 hours of overtime on Friday is included and takes 1 leave then this is how the time will be reported against corresponding TRCs:

Mon  Tue  Wed  Thu  Fri   Sat  Sun   TRC
 8     8      8      8                         REGLR
                              8               PAIDLV
                           3                  OVRTME


Similar TRCs are grouped together to form TRC Program.

Compensatory Time Plan

These are used to administer compensatory time for employees. The system maintains
each instance of a time reporter's earned compensatory time and the quantity and date earned.
Example:
Employee works on two holidays falling in a time period and on Saturday so when they report time for that period, this is how they would do (Here COMPH and COMPW are the TRCs defined for Comp Time):

Mon  Tue  Wed  Thu  Fri   Sat  Sun   TRC
 8       8     8                                 REGLR
                       8     8                 COMPH
                                   8           COMPW

Since, employee isn’t supposed to work on holidays or weekly offs but even then they worked in this period, the hours worked in these days get added as Compensation Earnings. So now employees can avail these earned hours just as paid leaves.

Workgroup

Similar to Paygroup in Payroll module.  All the employees in a workgroup share identical compensation requirement. All the previous elements are mapped to the workgroup.
All the workgroup members share:

  • Same reporting type: exception or positive
  • Same holiday schedule
  • Same TRC program
  • Same compensation rules
  • Same needs for time approval
  • Same association to a comp. Off plan
  • Same day breaker
  • Similar rounding rules

Taskgroup

A taskgroup is a group of employees who have similar work or task – reporting requirements
Taskgroups identify the default time reporting template, task template, and task profiles that are valid for members of the taskgroup.
Some organizations refer to taskgroups as labor classes or labor class rate groups.
Task: attributes of reported time such as department, product or project – that defines how or where time was spent
Task template you specify which task entities you want members of a taskgroup to report their time to (i.E. Company , department , project)
Task profile “fill in the blanks “ for a task template. If used, a time reporter task related fields will be completed automatically with the values in the task profile

Time Collection Devices(TCD)

Used to collect and report the time that is recorded through a third party time clock tool. TCD interface provides packaged integration points to:
  • Collect clock and elapsed time from any TCD
  • Send necessary setup data to these devices for reporting
System supports scheduling, reporting, managing and applying rules to TCD time. You can create a separate group for TCD time reporters





Want to learn PeopleSoft Time and Labor module thoroughly?

I have a several videos with total duration of 18 hours.Click on the following link leading to YouTube playlist for Time and Labor videos.Time and Labor

Check out the course contents covered in these videos.

Click here to know the procedure to proceed further.

However, if you are interested to learn more modules then visit this for more details PeopleSoft Functional and technical online training

Wednesday, September 7, 2016

How the Time is Processed in PeopleSoft Time and Labor

There are different stages in the time processing right from the stage when the time is reported till the stage when the time is ready to be picked up by payroll. Lets discuss those stages in the same sequence the time goes through when its processed.

Stage 1 - Time Reporting

This is the stage where employees report their time based on the work schedule assigned to them. There are broadly two ways to report the time:

Online

The time is directly entered into Time and Labor system through online pages and it can be done by one of the following ways:


Timesheet page for employees (ESS  – Time Reporting – Report Time – Timesheet)
Used by employees to report their time for a particular period.

Mass Time page for employees (ESS  – Time Reporting – Report Time – Mass Time)
Used by employees to report their time for a date range and can include multiple periods.

Timesheet page for managers (MSS – Time Management – Report Time – Timesheet)
Used by managers to report time for their direct reports for a particular period.

Mass Time page for managers (MSS – Time Management – Report Time – Mass Time)
Used by managers to report time for their direct reports for a date range and can include multiple periods.

Rapid Time page for Time Admins (Time and Labor – Report Time – Rapid Time)
Used by administrators to quickly report time for group of employees. No up-front validations are done when the time is submitted here and rules are applied during the time admin process run.

Using Time Collection Devices (TCDs)

In many organizations, employees have to punch in/out to record the working hours based on which they are paid. The difference between Punch In time and Punch Out time is then sent to PeopleSoft Time and Labor through interface file which is then captured in PeopleSoft by TCDs (Time Collection Devices)

Stage 2 - Reported Time

Time reported through either of the methods is called reported time and is brought in the table TL_RPTD_TIME where it awaits for approval if the approval is setup to be required which is optional though. There are three possibilities if approval is required:

Manager approves the time

Once approved, the time is now considered as final reported time. 

Manager pushed it back

The time is sent back to employee for correction and to submit back again. 

Manager denies the time

If it’s denied then employee can’t take any further actions on this time but manager can still make corrections individually and submit back again for approval which has to be approved by N+2 and then the Time Admin process TL_TIMEADMIN will pick it up again. After that it will be converted into Payable time which again has to be approved by N+2.

After approval, its fully considered the reported time and stays in the table TL_RPRTD_TIME with Reported Time status as ‘Approved’ and its ready for being processed by Time Admin process.



Stage 3 - Processing the Reported Time(Time Administration)


In this stage we run the approved reported time lying in the table TL_RPTD_TIME table using the time admin process TL_TIMEADMIN (Navigation: Time and Labour –  Process Time – Request Time Administration).
On a very high level, following tasks are performed in this stage:

1) Time admin process TL_TIMEADMIN collects eligible employees based on the Group ID supplied in run control page.

2) It picks the reported time for all those employees, process the time based on the rules defined and generate exceptions for issues. The exceptions have to be addressed and the process should be run again.
3) Finally, this process generates payable time which is brought in to the table TL_PAYABLE_TIME.
4) All the exceptions generated in this step are stored in the table TL_EXCEPTION.


Stage 4 - Payable Time


The payable time generated in the previous step and lying on the table TL_PAYABLE_TIME awaits for approval if the approval is setup to be required which is optional though. There are three possibilities if approval is required:


Manager approves the time

Once approved, the time is now considered as final payable time and is ready to be sent to payroll.

Manager pushed it back

The time is sent back to employee or originator for correction and submit back again in which case the time will have to go through all the stages again.

Manager denies the time

If it’s denied then employee can’t take any further actions on this time but manager can still make corrections individually and submit back again for approval. Even in this case, when the time is submitted again, it will be treated as reported time which has to be approved by N+2 and then the Time Admin process TL_TIMEADMIN will pick it up again. After that it will be converted into Payable time again which again has to be approved by N+2. 



Monday, August 1, 2016

How to enable Signon Tracing option in PeopleSoft

Imagine a situation where you are banging your head trying to debug the PeopleCode to find out the root cause of an error/warning message appeared while doing transaction on a component. When the component is too big like JOB_DATA then its like looking for a needle in a haystack.

Fortunately, PeopleSoft has some sort solution for every problem and this particular case is not an exception. Do this to tackle it:
  1. Enable the Sign on trace options
  2. Sign in and do the same transaction 
  3. Retrieve the trace file generated in the app server
  4. Look for the place where the error/warning message has been produced
Done..!

The sign on tracing can be enabled by just appending trace=y to the URL as shown below:



As soon as the parameter is appended press Enter and the tracing options will be available. 




It is however very important to note that we must not check all the options under each category because:
  • It will cause the portal to become very slow
  • The generated trace file will be excessively huge 
Therefore, If for example you want to debug an error occurred on the page then simply select the options as shown in the above image and go on. You can also change the selection based on the type of debug you want to perform.

Once you are done doing the transaction, its time to locate the trace file that have been generated. The trace file can be found under:

PS_HOME/appserv/INSTANCE_NAME/LOGS

Where PS_HOME and INSTANCE_NAME can be replaced with the appropriate values for the instance you are working on. For example if PS_HOME is pt854 and INSTANCE_NAME is HRDEMO the path on a UNIX server will look like:

xx/xx/pt854/appserv/HRDEMO/LOGS

And the trace file name will be something like: OPRID_xxxxxxxx.tracesql where xxxxxxxxx will be a number.