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.