I would like to find out what tables that needed to be converted over for activity and history Absence Management. Also I’d like to know if there is feature for EE can perfrom a cancelation action on his/her request, instead of manager has to do it.

Thanks for posting your question!

Tables used for Tracking Absence History:

ABSENCE_HIST

ABS_HIST_DET

ABS_HIST_CERT

Here are Self Service Access Details:

Thanks
Kannappan Krishnan

I have a requirement in PeopleSoft CRM.
there will be some VIP customers,only a particular user can search for those VIP customers during transactions like OC,Sales and other users can’t.

Is there any way to achieve this.

Thanks for posting your question!

Below are the Steps to achieve this:

§         VIP Customers related Transaction should be tracked by

o        Having a Row Level Security access like Dept Security using Tree Manager

o        Having a Separate Audit System

o        Having a FIELD to identify the VIP Transaction in Target Records

§         Separate ROLE should be created and the same should be assigned to those Concerned Users.

§         Based on above steps, Business Logic should be written to show VIP Transactions. If the criteria are not satisfied for the incoming Users, we need to hide to those transactions.   

§         Business Logic can be done either by using Component Search Record or by internally writing a code at Component level

Thanks
Kannappan Krishnan

I am still wondering as why we can’t have SQL and CALL Action in a single STEP in an Application Engine.

Also can I know about any site/repository which describes PeopleSoft GL Set Up.?

Thanks for posting your question!

§         Both SQL and CALLSECTION are mutually exclusive Actions. This is basically to avoid Lock.

Say for example:

We execute some DML transaction on Table T1 in SQL action (This is the first Action in a Step of Application Engine Section). If we are trying to do some DML transaction again on Table T1 using Call Section action, this will create a Lock on table T1.

Main Program
SQL – Update T1, set salary = salary * 2.
Call section – Calc

       Section Calc
       SQL Update T1, set salary = salary *3
       end-section
       (default commit)

Main Program
end-section
(default commit)

§         Since PS is creating a separate Database Session for these Actions, it is difficult to maintain COMMIT / ROLLBACK transaction controls.

Basic steps for PS HRMS GL Set Up 

1. Navigation for GL Interface:

Main Menu > Set Up HRMS > Product Related > Payroll for  

1. Setting up GL Business Unit (BU) under Review GL Business Unit Page
2. Mapping HR BU with GL BU
3. GL Account Codes Setup under Company component
4. Setting up Liability Accounts for Federal/State/Local taxes/Deduction
5. Setting up ChartField Configuration for GL Accounts
6. Grouping the GL Activities under GL Interface Navigation
7. Mapping the Expense for all ChartFields

For more Info: PeopleBook has provided a separate section for setting up GL related Interface tables and as well for Integration of Payroll with GL.

Thanks

Kannappan Krishnan