Tuesday, July 23, 2013

HCM/HRMS Tables for the PS QUERY - Querying HCM/HRMS table in peoplesoft

HCM/HRMS Query reporting

The following are the main tables used to query HR related data

Human Resources Information/ Personal Data:


PERSONAL_DATA, PERS_NID
 
Employment Data:


EMPLOYMENT- general employment data, such as various service dates, etc.
 
Department Inforamation
 
DEPT_TBL --This is one of foundation tables in HR. You will rarely query against it directly; more


likely you will join to it to get the description or short description. Department codes in PeopleSoft are

different from what was used in HRS/Legacy, and department data is effective dated.
 
Job code information
 
JOBCODE_TBL --This is also a foundation table. This table holds job codes, descriptions and related


data such as FLSA classification, pay plan, grade and structure information.
 
Job Data:


JOB-- Job (roughly equates to assignment records in legacy). Contains job records along with other

data. Effective dated someone's job history will be stored in this table. Remember, Empl Records

refer to an employee's job record(s). The existence of multiple Empl Records means that they have

had or are currently holding multiple jobs Empl Records start with 0, and their benefits are tied to

Empl Record #0.
 
Benefits Data :


BEN_PROG_PARTIC – Stores the Benefit Program to which the employee is assigned.

LEAVE_PLAN – Stores enrollment in leave plans.

HEALTH_BENEFIT – Stores e nrollment in health insurance plans

SAVINGS_PLAN -- Stores enrollment in TDA, ORP and Deferred Compensation

LIFE_ADD_BEN -- Stores enrollment in life insurance plans.

RTRMNT_PLAN – Stores TRS enrollment.

DISABILITY_BEN – Stores enrollment in disability plans.
 
 
Tax Data:


FED_TAX_DATA – Contains federal tax data, including nonresident alien data

STATE_TAX_DATA – Although there is no state withholding in Texas, this record is necessary to

maintain state of residence and unemployment jurisdiction.
 
Payroll Data:


Payroll processing check data (records used by the payroll process to store check history)

PAY_CALENDAR

PAY_CHECK

PAY_LINE

PAY_CHECK

PAY_EARNINGS

PAY_OTH_EARNS

PAY_DEDUCTION

PAY_TAX
 
Payroll funding distribution data (records that tie funding to payroll actuals):


PAY_ERN_DIST

PAY_DED_DIST

PAY_TAX_DIST
 
Other employee level payroll data:


GENL_DEDUCTION - Genearl deduction.

GENL_DED_CD        - General deduction code.

ADDL_PAY_EFFDT -  additional pay effdt.

ADDL_PAY_DATA   - additional pay data.

ADDL_PAY_ERNCD - additional pay earn code.

DIRECT_DEPOSIT  - Direct deposit.

DIR_DEP_DISTRIB - Direct deposit distribution.
 
Position Data:


POSITION_DATA—identifies position data for each business unit.

Tenure Data:

EG_TENURE  Tenure Data.
 
Hints:-
 
Use the Employees table whenever possible. Queries using this table will generally have better


performance for several reasons. This tables has name, Empl ID, empl records, job title, job code,

dept title, dept code, location code, comp rate, comp frequency, position number, standard hours,

etc., data for active employees. Two fields that it does not have are Empl Class and FTE. This table

is not a transactional table, meaning that records are not actively written to it throughout the day.

Rather, it is refreshed nightly on process scheduler. There may be a one-day lag time for new data to

hit the table, but for most reporting this is acceptable

Peoplesoft HCM Process - Scheduled process.

HR_PERSDATA Application Engine - Updates the PERSONAL_DATA snapshot table with future dated entries as they become effective.

NAME_DISPLAY Application Engine - Refreshes the NAME_DISPLAY and NAME_FORMAL fields in all records with the NAME_GBL_SBR. Use when the criteria used to change these fields is changed.

PER099 Application Engine - Fill EMPLOYEES Table.

PTAF_NEM Application Engine - PTAF_NEM - Approval Framework Escalation App Engine.           AWE Workflow escalation process.

SCRTY_OPRCLS Application Engine - SCRTY_OPRCLS - Updates the SJT_OPR_CLS security Join Table.

SCRTY_SJTDLY Application Engine -  Nightly update for SJT Records -  Update of all effdt rows that have become current as of this data.

HRS_AM Application Engine - Applicant Search Auto-Match -Recruiter Applicant Search auto-match process.

HRS_DUPE_PRC Application Engine - Find Applicant Duplicates - Finds applicant duplicates given certain criteria.

HRS_JOB_AGNT Application Engine - Job Agent - Run the Job Posting Search Agent process.

HRS_JSCH_IDX Application Engine -Verity based Job Posting Index build process.

HRS035 SQR Report - Application Analysis (USA).

PER506 SQR Report - Department Tbl & Departmental - This report lists any departments that you have created in the Department Tree but have not yet added to the departmental security tree, It also lists any changes in departments since the effective date of the current security tree.

PER900 SQR Report - Core HR Data Integrity Audit. - Audit of the CORE HR Tables for Data Relationship Integrity.

PSBARUN - Cobal Job - For the Benefit Administration - scheduled to run twice each night with some custom pre and post processes. 

Implementing CAPTCHA using ReCaptcha in PeopleSoft

You can use this for the forgot password component , carrer login page (applicant login) or any other similar pages strighat way.

Following are modified steps from the reCAPTCHA website for the PeopleSoft Implementation.

First, go to the reCAPTCHA web site and create an account. As part of that account creation process you'll have to specify the domain your reCAPTCHA will be protecting. The reCAPTCHA site will will give you a key pair for that domain. The key pair allows you to authenticate your reCAPTCHA requests to the reCAPTCHA servers

Second, Create the HTML Area in the PeopleSoft page where you want the ReCaptcha to apper
in the HTML Defination add the follwing Java script code, you need to enclose it with form tags.
make sure you replace   - with the public key from the key pair created in reCaptcha website.

Download the Java API library in the following location

http://code.google.com/p/recaptcha/downloads/list?q=label:java-Latest - Place the jar file in the class path/folder for the java in the appserver.

Add button on the page, similar to submit button for the page, on field change of the button you can write the code as below.

PS: Make sure you replace the private in code with the private key generated by reCaptcha for your domain.
Hope this will be helpfull.

Paperless Office with PeopleSoft Forms & Approval Builder 

PeopleSoft applications are helping to make paper and email-based forms a thing of the past so that you will know what was submitted, when it was submitted, and who approved it. We recently released Forms and Approval Builder as a part of Common Components 9.1. Forms and Approval Builder allows you to build electronic forms that are configurable by business analysts, enabled with approval workflows, and immediately deployable and auditable to enable you to replace paper and email-based forms. Forms and Approval Builder is currently available, at no additional charge, to all PeopleSoft 9.1 customers. It was part of the FSCM Feature Pack March 2011, and it is also available in the Enterprise Components 9.1 Common Objects Bundle 1 2011 for use in any PeopleSoft 9.1 Pillar, including, of course, HCM. It does require PeopleTools 8.51.03 or greater.

Form Design


PeopleSoft Forms and Approval Builder enables business analysts to create electronic, routable forms without having to use PeopleSoft Application Designer. A typical form can be designed and in use within 30 minutes and requires no writing of code.

The intuitive wizard guides you step by step through establishing a form. Options include adding instructions to the form, similar to what you would find on the back of a paper form; adding attachments to the form for users to read, submit, or both; and being able to create your own fields on the form. These fields can be plain text, numbers, date and time, yes/no, fields that prompt against existing PeopleSoft records, and code fields. The code field type enables you to build a list of items on the fly that a person who is filling in the form can select from when perusing the drop-down list. You can create these user prompt values in the code fields without having to enter them in a standard PeopleSoft record beforehand.

Main Menu > Forms > Design a Form

Fields can be organized into one or two columns on the page, and every field on the form has the option of being made required to ensure that users thoroughly complete the form.


You specify the location of the form in the PeopleSoft Main Menu through an easy-to-navigate folder hierarchy, and you select the flow of approvers that the form will follow using the approvers from within the Approval Workflow Engine.

There is also the ability to make forms available for limited periods of time.

Efficient and Effective Forms Management for your Organization

Knowing how many of each type of form are in the system and their approval status is essential in monitoring your business processes. PeopleSoft Forms and Approval Builder comes with its own summarization table, enabling you to see at a glance how many forms of each type have been created and how many forms are in each approval status. This central Form Management repository also enables you to activate and deactivate your forms within the system in one place, eliminating the need to go back into the design of each form and activate it.

The ability to find a particular form in an instant is also important in supporting efficient operations. Forms are searchable by subject, form type, priority, due date, and approval status to eliminate the need for searching through piles of paperwork.


Easy to Navigate Forms Available to Your Users When they Need Them

Any given form may be accessed through either the central forms repository or the link you designate for it in within the PeopleSoft Menu navigation. Users open a blank form; enter the required information; download, read, fill in, and upload attachments; and submit their form for approval.

Forms are available to the approver instantly, and approvals are also available as soon as they are granted.

Finally, because the Forms and Approval Builder utilizes the existing infrastructure of the Approval Workflow Engine and the Supplemental Data Framework, your forms and approvals are migrated like all other application data during an upgrade between PeopleSoft Releases.

 

Thursday, April 11, 2013

SQR output and Fonts

There is limited support for True Type fonts in PeopleSoft.

Below is the extract from the PS delivered file. We may try with any font which is not listed below and in case if that font is not supported, PS converts it to the default font, which is Courier.

List of defined fonts in PeopleSoft:

Number --------------- Name
3 ----------------------- Courier

300 -------------------- Courier-Bold

4 ----------------------- Helvetica

400 -------------------- Helvetica-Bold

5 ----------------------- Times-Roman

500 -------------------- Times-Bold

6 ----------------------- AvantGarde-Book

8 ----------------------- Palatino-Roman

800 -------------------- Palatino-Bold

11 ---------------------- Symbol

12 ---------------------- ZapfDingbats

17 ---------------------- ZapfChancery-MediumItalic

18 ---------------------- Bookman-Light

23 ---------------------- NewCenturySchlbk-Roman

2300 ------------------- NewCenturySchlbk-Bold

30 ---------------------- Courier-Oblique

3000 ------------------- Courier-BoldOblique

31 ---------------------- Helvetica-Oblique

3100 ------------------- Helvetica-BoldOblique

32 ---------------------- Times-Italic

3200 ------------------- Times-BoldItalic

33 ---------------------- AvantGarde-Demi

34 ---------------------- AvantGarde-BookOblique

35 ---------------------- AvantGarde-DemiOblique

36 ---------------------- Palatino-Italic

3600 ------------------- Palatino-BoldItalic

37 ---------------------- NewCenturySchlbk-Italic

3700 ------------------- NewCenturySchlbk-BoldItalic

38 ---------------------- Helvetica-Narrow

3800 ------------------- Helvetica-Narrow-Bold

39 ---------------------- Helvetica-Narrow-Oblique

3900 ------------------- Helvetica-Narrow-BoldOblique

40 ---------------------- Bookman-Demi

41 ---------------------- Bookman-LightItalic

42 ---------------------- Bookman-DemiItalic


We can get this list of delivered SQR fonts in postscri.str file .



RVP for HCM and FSCM 9.2

The roadmap is clear, for HCM and FSCM 9.2. Yesterday, Release Value Propositions for HCM and FSCM 9.2 has been released by Oracle. Items like iPad certification (with Safari as browser) and Pivot Grids are great, however, more or less related to PeopleTools 8.52. So PT 8.52 has been a pre-requisite to use the same features/technology for HCM and FSCM 9.2.
Moreover, a new term has been introduced, PeopleSoft Interaction Hub for PeopleSoft Applications Portal. Unlike the old days, this product now comes with an HCM or FSCM license. This will be a great change for the customers who are using the most used features, Dynamic Unified Navigation and Site-wide branding. Earlier, for these features too, customers had to purchase the entire license.

HCM

Smart HR – extension on Template Based Hire
Headcount Pivot Grids
Profile Management Enhancements – based on Secure Enterprise Search
Open compensation cycle job changes
Compensation Pivot Grids
Compensation history
ePerformance Workcenter
ePerformance Outlook integration
E-learning homepage / self service
Recruitment Gateway – with various 360 screens like in CRM (Job Opening, Applicant)
Recruiting Pivot Grids
Benefits
Absence with Outlook integration
Approval via HTML e-mail
HR Helpdesk – self service homepage, FAQ enhancements, discussion forums


 FSCM
Extending Global Reach
Financial Control & Reporting Business Process Overview
Plan to Retire Business Process Overview
Program and Portfolio Management Business Process Overview
Order to Cash Business Process Overview
Plan to Produce Business Process Overview
Source to Settle Business Process Overview

Industry Enhancements – General Ledger, Healthcare, Higher Education / Research

PeopleSoft Cumulative Feature & Fit/gap analysis


In any PeopleSoft application or PeopleTools upgrade process, you will need to perform a fit gap between your current version of PeopleSoft in order to find the differences. This is a daunting task to do when it comes to delivered functionality. For example, many people want to know what are the major differences between my version and the new one.

Oracle provides a cumulative feature overview tool for PeopleSoft to start your fit gap analysis.This tool is basically an Excel spreadsheet, that enables you to quickly understand major changes that have occurred across multiple releases for any give product. For example, if you are on PeopleSoft FSCM 9.0 and are looking for the changes that have occurred between 9.0 and 9.1, this new tool allows you to enter your current version and will provide you with a list of these changes for all releases since your version with detailed descriptions. The same is applicable to any source and target PeopleTools release.

https://support.oracle.com/epmos/faces/DocContentDisplay?_afrLoop=1023358752541899&id=1117033.1&_afrWindowMode=0&_adf.ctrl-state=rturvgxol_4



SchedulerTransfer servlet - posting issue


Issue: Distribution agent failed to post the files to report repository.



Error message: The XML file returned by the web server is invalid. XML document object creation failed.

Solution: This is an issue with SchedulerTransfer servlet which requires authentication. When a report needs to get transfer to report repository, distribution agant use SchedulerTransfer servlet for this purpose. SchedulerTransfer servlet checks for the default local node and if there is no authentication there, it will get fail. The Default Local Node must have the Authentication Option set to 'Password'. Application server needs a restart post this change.


Navigation :  Peopletools > Integration Broker > Integration Setup > Nodes > Default Local Node
Must have Password Authentication.

PeopleTools->Portal- > Node Definitions





Portal Security Syncronization

PeopleSoft Internet Architecture (PIA) portal can be defined as the collection of folders and content refrences with the navigational structure. The portal registry is a tree structure where one need to register the content and further it can be organized. The portal registry consists of the following primary parts:



Folders
Content references
Nodes


The main table which consists of all the portal definitions is PSPRSMDEFN. Security mechanism is used for folders, content references, content reference links, tab definitions, pagelets, and user homepages. The hierarchical relationships and dependencies between objects in the portal registry determine what security settings each object must have. The portal won't work correctly if these security relationships aren't maintained.

A folder that is not public or hidden must have at least the level of access that its immediate child objects (folders, content references, and content reference links) have.

A content reference link must have exactly the same level of access as the object (content reference or content reference link) to which it links.

A content reference that represents a PeopleSoft component or iScript must have exactly the same level of access as the object that it represents.

Portal object security settings can become unsynchronized when you move portal objects from one database to another using the Project Copy feature in PeopleSoft Application Designer. When you merge projects this way, if the projects contain any portal objects with identical names, the security settings of the portal objects in the last project copied overwrite the security settings of portal objects copied earlier. Also, when a copied portal object doesn't overwrite an existing object, it changes the structure of the resulting portal registry hierarchy.

Use the Portal Security Synchronization page to reinstate the correct security relationships between objects in the portal registry after you copy a project that contains portal objects. The portal objects are synchronized as follows:

-- The security settings of each content reference are compared to the component or iScript that it represents, and updated to match.

-- The security settings of each content reference link are compared to the content reference or content reference link to which it connects, and updated to match.

-- The security settings of each content reference and content reference link are propagated to its parent folder, in addition to the parent folder's existing settings.

-- None of the parent folder's existing security access is reduced.

-- The security settings of each folder are propagated to its parent folder, in addition to the parent folder's existing settings.

Delete Invalid Security Option


When we move portal objects from one database to another, roles and permission lists assigned to folders and content references on the source database may not exist on the target database and therefore become invalid. Select the Delete Invalid Security check box on the Portal Security Sychronization page to remove non-existing roles and permission lists from folders and content references.


Main section >> calls INIT section >> and then CREFPERM

INIT

STEP01 -- Do Select -- Selects the OPRID and RUN_CNTL_ID from PS_AERUNCONTROL table (run control table for AE).


STEP02 -- Do Select -- Selects the PORTAL_NAME (EMPLOYEE, SUPPLIER etc...) and PORTAL_FLDRP_FLAG (This flag is to select if we wish to delete invalid security, we may skip this too and it will set to 'N') from PS_PORTAL_CSS_RUN.
CREFPERM
STEP01 -- PeopleCode -- Main step to do the processing for syncronization, invalid security etc...

Below are the tasks in brief what exactly PORTAL_CSS is all about .

1. Check for invalid permission lists.

This step figures out the Permission which is/are invalid and further it get deleted by the program for object in concerned portal.


2. Check for invalid roles.

This step figures out the Role which is/are invalid and further it get deleted by the program for object in concerned portal.


3. Check Parent folder permissions and roles.
Check for missing permission list on cref or differences in permission counts.



4. Compare permissions and permission count against PSAUTHITEM

5. Check for missing permission list on cref's parent folder.

6. Check for PeopleSoft iScript
7. Worklist URL

8. Some other type of CRef (UEXT, UGEN)

9. CRef Link Synchronization
Compare the link to it's parent folder. Also, it compares the permissions of the cref link against the object it's linked to

10. Folder Synchronization
Here, it will only select the nonpublic folders.



Navigation of PORTAL_CSS program: Main Menu > PeopleTools > Portal > Portal Security Sync



Bind Variables on PeopleSoft Home Page

Prior to PT 8.48 release, there was a record WEBLIB_MENU, using which we were able to pass the dynamic variables to show the same on PeopleSoft Home Page. Below is the


resolution (Resolution # 1, copied from Oracle PeopleSoft Metalink site)



From PT 8.48 and above, one will not be able to find out the record WEBLIB_MENU. The design has been changed. Below is another resolution (Resolution # 2) how to pass the bind

variables like User ID, Instance name etc on the home page.



Resolution # 1 (Prior to PT 8.48, Oracle PeopleSoft Metalink, resolution ID # 623430.1)



E-PIA : How do you add/modify bind variables to change the look and feel. [ID 623430.1]



Resolution # 2 (PT 8.48 and above)



1. Open up App Package PT_BRANDING > Class BrandingBase in application designer. Search for the string ‘add &addjs’. Add the below code above the comment which contains the string ‘add &addjs’:



&greeting = "User: " %UserId " in Database: " %DbName;





The overall code will be like:



/* Added to show the bind variables on the home page */

&greeting = "User: " %UserId " on Database: " %DbName;

/* add &addjs to PT_IFRAME_HDR_SWAN (bind 22) and PT_IFRAME_HDR(bind 23) */



If this looks fine in presentation, its okay, however, the style/font of this variable "&greeting" can be taken care by PSHOMEPAGE Style Sheet



2. Open the PSHOMEPAGE Style Sheet in application designer, locate the "greeting" style class and replace this piece of code with the below code:



/*.greeting {

color: #FFFFFF;

font-family: Arial, Helvetica, sans-serif;

font-size: 12pt;

font-weight: bold;

}*/



/* Customized for the home page bind variables looks*/



.greeting {

color: #FFFFFF;

font-family: Arial, Helvetica, sans-serif;

font-size: 10pt;

font-weight: bold;

}



The above delivered code is commented and below is the customized one. You can use more alterations according to your choice.