F1 Context Help for Peoplesoft Application Designer
Access Peoplebooks from Applicaiton Desinger.
Context Help for Application designer.
Follow the setps to configure F1 - context help for the application designer.
Press F1 in the application designer to get the help based on the URL configuration below.
It can take to the peoplebooks based on the context.
Navigate to PeopleTools > Utilities > Administration > PeopleTools Options
Under the help option you can set the URL to the People books.
URL needs to be in the following format.
http://helpwebserver:port/productline/f1search.htm?contextID=%CONTEXT_ID%&LANGCD=%LANG_CD%
%CONTEXT_ID% is the object name or context ID of the currently displaying page or dialog box.
%LANG_CD% is the three-letter language code for the user's preferred language.
Cntrl+F1 - can be used as alternative help URL to the website on the internet or the company's internal website.
Tools/Utilites & Applications for Peoplesoft Development.
Productivity tools for the Peoplesoft Development.
1) SQL-Formatter :- The Application engine sql statements invloving are not formatted well for understanding it.
SQL-formatter comes in handy to format the SQL. It helps in Debuggin ,Review & performance tunning of the complex qurey.
http://www.dpriver.com/pp/sqlformat.htm?ref=g_wangz - Online formatter.
http://www.dpriver.com/index.php?ref=g_wangz - Offline SQL Formatter.
Pros :- Works with different databases SQL statements.
Cons:- Doesn't recongnize many Peoplesoft Meta-SQL tags. Just replace them with sql function or static values then it works fine.
2) Pace Trace :- Pace-Trace is effectively a viewer for PeopleSoft SQL trace files. It reads a selected trace file and creates a grid that summarizes all the SQL actions contained in the file.
This quick access to trace file information can be used by everyone from business analysts to developers, speeding report design, custom development, and troubleshooting.
Following Trace files generated in different methods can be
1)Trace an entire session - Trace file generated by the entire session. Enabled on the login trace page.
2)Interactive Tracing - Enabled at PeopleTools > Utilities > Debug > Trace SQL.
3)Application Engine trace.
4)COBAL Tracing.
3) PS Pad editor :- This editor is very much similar to the Ultra edit and Edit plus which many of us know.
What makes it special is for the following reasons.
1) Peoplecode.INI file which is code highligter for the peoplecode like in the application designer - Why do we need this one for ?? Read the next reason.
2) Export to Clipboard as RTF feature (File > Export > Export to Clipboard as RTF) is allow you to copy the peoplecode from the editor with the code highlighter and paste in the word document or email. code highlighter formatting is retained.
3)SQR.INI file is also available for SQR programming.
Check out this link - http://xtrahot.chili-mango.net/2007/07/prettify-those-code-listings/
for details on how you can use it.
4) Zapgrab 1.0 :- The best , easiest & Free way to capture screens, and paste them into Documents & presentations.
It is very helpful to capture the screens for the Testcase results document , Technical design & Functional design documents.
ZapGrab allows you to capture your screen in two different ways: the whole screen or only a section with a quadrangular form selected by you with the mouse.
Just select the area on the screen and to Cntrl+v.
Cons:- Difficult to capture scrolling window screens.
Link:- http://www.softpedia.com/get/Multimedia/Graphic/Graphic-Capture/Zapgrab.shtml
5) SQR Express :- Developing SQRs Has Never Been So Easy! - In a powerful environment you can edit multiple files with unlimited length, maintain multiple database logins,
navigate in the source-code by clicking procedure-names or inside a treelike program-flow, variables, calls, includes or records.
Cons:- Not a freeware.
Detalied features here.
http://www.bcstools.com/SQRExpressInfo.pdf
6) JEdit :- Java based open source editor. Code highligther for SQR available
Pros: - A lot of open source plugins avaliable.
The only free ware text editor with help of plugins can create SQR tree like SQR Express.
Can create own plugins. Create plugins for intellisense.
Cons:- Not the easiest way installing plugins with different versions.
http://jjmpsj.blogspot.com/2009/08/using-jedit-to-edit-peoplesoft-files.html
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.
Online Peoplecode / SQL trace is not getting generated
Peoplecode / SQL Trace is not getting generated.
Check the Application Server configuration file APPSRV.cfg for the TraceSQMask and
TracePCMask.
PSADMIN can be used to set the parameter.
If the these mask parameter are set to zero then configuration file then trace files are not generated.
Process schedular configuration file needs the change for Applicaiton engine programs SQL / Peoplecode invoked in the Batch mode.
Important PeopleSoft HCM processes
1) Refresh the EMPLOYEES table.
2) Refresh the Personal Data Process.
3) Refresh the Personal Data table with future-dated data.
4) Refresh name display values.
5) Audit Human Resources data for integrity.
6) ID Change.
7) ID Delete.
8) ERN Delete process.
9) Refresh Compensation.
1) PERS_REFRESH – Refresh Personal Data Process. Based on the setup in the Personal data setup component. Personal data record will be refreshed. Process updates the current data asof the Current date / System date. What fields are populated is configurable in the personal data setup component.
Record: PS_PERSONAL_DATA
Setup Record:- PS_PERSON_DT_SETUP.
2) HR_PERSDATA - Refresh the Personal Data table with future-dated data. This process updates
Personal data table with all the PERS_DATA_EFFDT, NAMES, and ADDRESSES (optional) when that data becomes effective. This is should be scheduled as a nightly process in order to catch changes every day.
3) PER099 - Refresh EMPLOYEES Table. Refresh the PS_EMPLOYEES snapshot table as of the selected date or current date. This process also updates the PS_EMPLOYEES_LNG.
4) Refresh all records with the NAME_DISPLAY and NAME_FORMAL fields to reflect changes made to the People Code definition of those fields. You can choose to update records with all name format types or just with one name format type.
It has following options to choose from.

5) HRAUDIT - Audit Human Resources data for integrity.- Core HR Data Integrity. PER900. Initiate the Core Human Resources Data Integrity Audit.
Following things are audited.
• Persons were found in PERS_DATA_EFFDT that do not exist in PERSON
• Persons were found in PERSON that do not exist in PERS_DATA_EFFDT
• Persons were found in EMPLOYMENT that do not exist in PERS_DATA_EFFDT
• Persons were found in JOB that do not exist in EMPLOYMENT
• Persons were found in EMPLOYMENT that do not exist in JOB
• Persons were found in JOB that do not exist in PERS_DATA_EFFDT
• Persons were found in JOB that do not exist in JOB_JR.
• Persons were found in JOB_JR that do not exist in JOB.
• Persons were found in PERSON that do not have a Primary Name in NAMES.
• Persons were found in NAMES that do not have record in PERSON.
• Persons were found in ADDRESSES that do not have record in PERSON.
• Persons exist in DISABILITY that does not exist in PERSON.
• Persons were found in DIVERS_ETHNIC that do not exist in PERSON.
6) Change ID / Delete ID Process – HR_PER502 - This process is used for the correction of the employee ID it updates the all tables with new employee ID. This also used for the deleting ID as well. ID Delete control component contains the exclusion list of the records.
7) Delete ERN Process - HR_EERCD_DEL – This process is used to delete the Employee record Number or Empl RCD of an employee.
ERN Delete Field Names Component– EMPL_RCD different field names in the different records to look for. ERN Delete Exclusion List – List of the table to be excluded from the table.
ERN Delete Control – List of the message for the Exclusion list of table/ field names.
8) Refresh Compensation -
HR_CMP015 – Process to refresh the compensation. Refresh multiple worker compensation packages with current default values, and print a report that displays the new and previous compensation data of the impacted workers. It executes the process executes the same steps as the Default Pay Components button on the Compensation page.
Language Preference in Configuration Manager
Issue:
Users trying to access App Designer in Japanese language & it resulted in some Junk characters. Language Preference was set correctly.
Solution:
After analysis found that "East Asian Languages" were not installed on the NT Server [ Install files for East Asian languages is UnChecked ], installing this resolved the issue.
Duplicate row errors in DMS Scripts
IGNORE_DUPS Vs UPDATE_DUPS
Often we get the Duplicate row errors in the DMS Scripts based on the target environment in which import script is executed. Since DMS scripts can run in any target environment we need to handle this error in the DMS Script.
The best know method is IGNORE_DUPS statement in the DMS script
SET IGNORE_DUPS ;
IMPORT {record * } ;
The biggest disadvantage of this statement is it can only be run 'Bootstrap mode' which all the developers may not have access.
Is there way to avoid handle this error wihout running the DMS in the bootstrap mode ?
SET UPDATE_DUPS;
IMPORT { Record * };
Above statment can be used, it is not an exact replacement for the IGNORE_DUPS but it helps to slove problems in most of the cases.
UPDATE_DUPS - If the key values of the table exists in the target environment then it updates it with new values and insert the new rows in the .dat file.
Invoking the Remote call from AE/CI Process
In PT 8.4x you need to follow a certain sequence prior to invoking the PushButton field. The basics on calling COBOL from AE/CI PeopleCode is as follows. Note that "tweaking" may be necessary to get it to work.
1. AE (Application Engine) needs to have restart disabled in order to use CommitWork() to force a commit to the DB of the CI data.
2. Set the CI's properties, except for the "Pushbutton" field (usually Y/N) used to kick off COBOL.
3. Save the CI (call Save()).
4. If Save is successful, call CommitWork().
5. Set the CI pushbutton property (toggle it) to trigger the COBOL process.
6. COBOL will run asynchronously. So you usually need to put a dummy loop to wait until it's done processing to avoid having the next CI record "bump" into COBOL or in case you need to perform some post COBOL processing of the record.
Action value combinations of the Job data
Action Combination/ Action Paris - Reverse Action for each action.
Action - LOA – Leave of Absence , LWP – Leave with Pay
Reverse Action RFL – Return from
Action
LTD – Long Term Disability with Pay , LTO – Long Term Disability
STO – Short Term Disability , STD – Short Term Disability with Pay
- Reverse Action
RFD – Return from Disability
Action Reverse Action
SWB – Short Work Break - RFW – Return from Short Work Break
Action Reverse Action
LOF – Layoff REC – Recall from Layoff
Action Reverse Action
TAS – Create Temporary Assignment RFA – Return from Temporary Assignment
These are the actions that will create and stop the special temporary assignment relationship that puts the original instance in a suspended status while the person works on a temporary assignment.
Action Reverse Action
SUB – Create Substantive Job - RTS – Return to Substantive Job
These are the actions that will create and stop the special temporary assignment relationship that puts the original instance in a suspended status while the person works on a temporary assignment.
.
GenerateComponentContentURL / GenerateComponentPortalURL return NULL / Blank
PeopleTools > Portal > Node Definitions
The Base URI (e.g. http://www.myserver.com/psp/mysite/) is only available automatically in the context of a web server. If a process is not signed in via the web (e.g. Application Engine), the Node definition specified in the function is checked for that Base URI. Open the Node Definition (PeopleTools > Portal > Node Definitions) and enter the Content URI (.../psc/...) and Portal URI (.../psp/...) on the Portal page. These are used by the GenerateComponentContentURL and GenerateComponentPortalURL functions, respectively. By default these fields are empty.
