Search This Blog
e-learnings - a functional point
PAY_ONE_TIME - You would have heard about this table for making adjustments after pay run first calc. Point is, if you are adjusting by (an app engine for example) process, the adjustment entries may be not of PAY_CHECK's. Technically what I am trying to say is, "When you are making entries into PAY_ONE_TIME, dont join PAY_CHECK, just join PAY_EARNINGS with SINGLE_CHECK_USE in P or N. The Pay Calc will take care of pulling it off in Paycheck".
Peoplesoft Navigation of the setup components. - In simple query.

There is a catch –It doesn’t work for the transaction components like JOB_DATA.
This record is used in setup manager and hence doesn’t have details for the transactional components.

Below query gives for all tables (including hidden).. based the level of navigation (for example Main Menu --> Careers, for this two tables should be joined.. so if you are not getting the results, you have to keep reducing the no of joins :)) it is configured the self join table's count should be increased/decreased...
Oracle------
SELECT D.PORTAL_LABEL ' -->' C.PORTAL_LABEL' -->' B.PORTAL_LABEL ' -->' A.PORTAL_LABEL
FROM PSPRSMDEFN A, PSPRSMDEFN B, PSPRSMDEFN C,PSPRSMDEFN DWHERE A.PORTAL_PRNTOBJNAME = B.PORTAL_OBJNAMEAND B.PORTAL_PRNTOBJNAME = C.PORTAL_OBJNAMEAND C.PORTAL_PRNTOBJNAME = D.PORTAL_OBJNAMEAND A.PORTAL_URI_SEG2 ='JOB_DATA_HIRE'
MSSQL-----
SELECT D.PORTAL_LABEL+ ' -->'+C.PORTAL_LABEL+' -->'+ B.PORTAL_LABEL +' -->' + A.PORTAL_LABEL
FROM PSPRSMDEFN A, PSPRSMDEFN B, PSPRSMDEFN C,PSPRSMDEFN DWHERE A.PORTAL_PRNTOBJNAME = B.PORTAL_OBJNAMEAND B.PORTAL_PRNTOBJNAME = C.PORTAL_OBJNAMEAND C.PORTAL_PRNTOBJNAME = D.PORTAL_OBJNAMEAND A.PORTAL_URI_SEG2 ='JOB_DATA_HIRE'
Manivannan Ramar
Subscribe to:
Posts (Atom)