Mar 30

SQR output and Fonts

Yes, its graphics…which matters a lot when it comes to output of reports. Especially with SQRs in PeopleSoft where developers are conscious about showing the output of their reports, at the end of day, presentation takes most of the credit.

While there are various options being provided by adobe, however there is limited support for True Type fonts in PeopleSoft. I have been asked to findout where the font setting have been stored/listed in PeopleSoft and in result, I got a file where the fonts and their code has been mentioned.

Below is the extract from the same PS delivered file. You 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

You can get this list of delivered SQR fonts in postscri.str file which you can access from the machine where scheduler is installed and configured.

Hope this helps… suggestions are always welcome in case I missed out something…

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2009/03/30/sqr-output-and-fonts/

Mar 26

Manage Hire (TAM – WFA integration)

Manage Hire is the integration point between TAM and WFA, the component from where WFA admin starts the addition of records of the interested applicant to the HR database and create a relationship between applicant and the organization (EMP, POE etc…). For Manage Hire to work, Integration Broker should setup on the webserver to pass the messages (sync/async requests) to and from DB.

Below are the couple of steps to accomplish the same.

1) Verify the IB Gateway is setup under PeopleTools >> Integration Broker >> Gateways

2) Go to PeopleTools >> Integration Broker >> Monitor >> Monitor Message >> Channel Status and verify the Channel HR_MNG_HIRES is running.

3) Go to PeopleTools >> Integration Broker >> Node Definitions and verify the Transaction Types are active (under the Transactions tab) for HIRE_REQUEST and POST_HIRE_REQUEST

4) Go to PeopleTools >> Integration Broker >> Monitor >> Monitor Message >> Node Status tab and verify you can ping the node PSFT_HR

5) Go to PeopleTools >> Integration Broker >> Monitor >> Monitor Message >> Domain Status Status tab and verify you can domain is active for your server

At this point the messaging between RS and HR is setup

6) Now go to Recruiting >> Find Applicants – Search for applicants in “Offer Accepted” Status

Next page you would see will be below:

Choose your applicant whom you want to hire.

In the Take Action drop down – Choose “Prepare for Hire” and hit Go

You should see the below page.

a) Choose Start Date as > today’s date
b) Choose Hire Type as “Hire”
c) Hit the “Save & Submit Request to HR”.

The subscription peoplecode sends an email to the Role Query specified in this setup – Setup HRMS >> Product Related >> Workforce Administration >> Hire Notifications

Now go to Workforce Administration >> Personal Information >> Organization Relationship >> Manage Hires
You should see this on Manage Hires Page

Now click on “your applicant” link.
The page displayed is Manage Hire Details

On this page – put in an EMPLID and hit the “Add Person” Button.

This button would launch the “PERSONAL_DATA” (Add Person Component). If you look at the Post Build – the component would know you are coming from Manage Hires and initialize a bunch of controllers. These controllers would make the service call to RS to pull the data into the component buffer.

Once you verify the data and hit the save button >> go back to Manage Hires and for the same applicant and now click on the “Add Job” button.

Now click on the “Add Job” button. This will launch the “Job” components. Look at the Post Build of this component on how it initializes the controllers.

Once you verify the job information and hit save >> the save code will fire POST_HIRE_REQUEST message.

As always, any correction(s)/suggestion(s) are always welcome…

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2009/03/26/manage-hire-tam-wfa-integration/

Mar 23

HRMS Store Scripts

HRMS PRODUCT’s STORE*.DMS SCRIPTS:

PeopleTools
%PS_HOME%srccblbaseSTOREPT.DMS

HR Common
%PS_HOME%srccblbaseSTOREHRM.DMS

Benefits Admin
%PS_HOME%srccblbaseSTOREBAS.DMS
Note: If you have this module, always run this one LAST

Pension
%PS_HOME%srccblbaseSTOREPEN.DMS

Payroll
%PS_HOME%srccblbaseSTOREPAY.DMS

Time & Labor
%PS_HOME%srccblbaseSTORETL.DMS

Payroll Interface
%PS_HOME%srccblbaseSTOREPYI.DMS

GL Interface
%PS_HOME%srccblbaseSTOREJG.DMS

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2009/03/23/hrms-store-scripts/

Mar 23

Global Payroll (Ind) Year-End Reports

At the end of the fiscal year, user has to generate certain statutory reports. Data needs to be setup in the system for the same purpose. Setup data for statutory reports is a critical part and the user has to ensure that the data setup for the report is done correctly. Below is a brief from my knowledgebase and that is for India (IND) country extension, application release HRMS 8.9.

Following are the setups that the user has to do:

a) Form 5 Data Setup
b) Form 6 Data Setup
c) Form 12BA Data Setup
d) Form 24 and 16 Data Setup
e) Form 24Q setup

Form 5

At the end of the fiscal year Professional Tax Remittance Details has to be given to the government in the form 5. To generate the form 5 certain details are to be setup in the system. Navigation below.

Global Payroll & Absence Mgmt > Year-End Processing > Define Form 5 Data IND

Data needs to setup:

Total Tax Paid for the Year: This is the amount payable as total Professional Tax for the year for all the employees of that Establishment.

Tax Paid: This is the PT paid till date by all the employees.
Balance Tax Payable: This is Balance PT that is yet to be deducted.
Tax Paid Under Challan: This is the Amount of PT paid under Challan.
Month: Select the individual month in this column.
Tax Deducted: Enter the amount deducted as PT for that particular month for all the employees of that establishment.

TDS Form 24 and Form 16

Form 24 reports the Income Tax details for each employee and is to be handed over to the employee at the end of each financial year.

There are two steps in TDS Form 16 generation

1. Define Form 24 and 16 Data
2. Create Form 24 Report
3. Create Form 16 Report

Define Form 24 and 16 Data

Before generating Form 24 and 16, the TDS remittance details should be entered using the following page. The information provided in this page will be used for Form 24 and 16 reporting.

Navigation: Global Payroll> Year End Processing> Define Form 24 and 16 Data


Period ID: Enter the Period ID for the period on which you want to enter the details.
Amount Deducted: Enter the TDS amount remitted for the period.
Voucher Number: Enter the remittance voucher number.
Voucher Date: Enter the remittance voucher date.
Bank ID and Branch ID: Select the Bank ID and Bank Branch ID for the bank branch from which the monthly remittance was transferred to the central government account. The Description displays once Bank ID and Bank Branch ID are selected.

Create Form 16 Report

Navigation: Global Payroll> Year End Processing> Create Year End Reports IND

Create Form 24 Report

Navigation: Global Payroll> Year End Processing> Create Year End Reports IND

Reports shares a common screen to run from.

TDS Form 12BA

Form 12BA reports the perquisite details for each employee for the financial year.

There are two steps in TDS Form 12BA generation

1. Define Form 12BA Data
2. Create Form 12BA Report

Define Form 12BA Data

Before generating Form 12BA, the Perquisite details can be modified for each payee based on the declarations and actual payments using the following page. The information provided in this page will be used for Form 12BA reporting.

Navigation: Global Payroll> Year End Processing> Define Form 12BA Data

Amount Paid: Enter the amount of the perquisite paid to the employee

Create Form 12BA Report

Navigation: Global Payroll> Year End Processing> Create Year End Reports IND

Common runcontrol page looks like below for most of the reports.

Report Name, Period ID, Payee Sort Option (option in which the entries are to be sorted)

As always…any comments/suggestions are welcome…

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2009/03/23/global-payroll-ind-year-end-reports/

Mar 23

Candidate Gateway (e-recruitment)

Candidate Gateway which earlier was known as e-recruitment til HRMS 8.8, enables applicants to View information about current job openings in the organization. Applicants can search, save search criteria, save job openings. There are three main functionalities of CW.

Applicants can search for jobs, apply for jobs, and employees can refer applicants.

Applicants can upload their resumes (depends on setup), submit job applications and resumes for specific job openings. Applicants can maintain and update their personal profile information.
There are certain steps needs to be done to setup this module to be accessible for external world (outside your domain). Below are some steps in brief to accomplish the same task in application version HRMS 8.9.

Create a permission list A and include the menus given below in that:

HRS_HRAM and HRS_HRS

In menu HRS_HRAM, make sure you have given the access of component HRS_CE only and under pages, for all pages:


In HRS_HRS menu, make sure you have given the access the components HRS_APP_SCHJOB and HRS_APP_SEARCHES only and with all the pages under that:

Make a new role B and add permission list A and HCCPRS1100 in that role.

Then create a new user say C, and assign role B to that user.

In ID info of this user, enter the following information:

Operator Alias value: PUBLIC

Now, make 2 app server domains and corresponding to each of them, create 2 web server domains choosing different web profiles (for examples if in one you have chosen DEV, in second, choose PROD).

In one domain, check the bypass signon checkbox in the PIA which you are configuring to setup for external candidate.

Here (arrow), enter the user ID which you have created and its password. After doing this, restart the app and web server domain in which you have done this proceeding with clearing the cache.

Now, in given below URL, enter your server and information which will redirect to Candidate Gateway page only and then test if it is working or not:

http://:/psc/ps/EMPLOYEE/HRMS/c/HRS_HRAM.HRS_CE.GBL?FolderPath=PORTAL_ROOT_OBJECT.HC_HRS_CE_GBL2&IsFolder=false&IgnoreParamTempl=FolderPath%2cIsFolder

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2009/03/23/candidate-gateway-e-recruitment/

Feb 24

Process Definition

When a process definition has been created, there are three main tables where it makes an entry and store definition of the . Those are:

PS_PRCSDEFN — The main page where you start creating “Process Definition”.
PS_PRCSDEFNPNL — “Process Definition Options” page where you define components, process group, recurrence etc…
PS_PRCSDEFNGRP — “Process Definition Options” page where you define components, process group, recurrence etc…

Apart from that, there are some more tables which get affects depends on options you have choosen while creating a process definition. Below are the same with description…

PS_PRCSDEFNCNTDIST — If you have specified “Output Destination Options” for some process, enteries goes to this table.
PS_PRCSDEFNXFER — If you have specified “Page Transfer Information” for some process, enteries goes to this table.
PS_PRCSDEFNNOTIFY — If you have specified ” Notifications” for some process, enteries goes to this table.
PS_PRCSDEFNMETA — If you have specified some value in “OS390 Option”, enteries goes to this table.
PS_PRCSDEFNMESSAGE — If you have specified some value for message from page “Schedule Message Information”, enteries goes to this table.

So there are two query sets here to delete any process definition…

First case in which you just have created a wrong process definition:

DELETE FROM PS_PRCSDEFN where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNPNL where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNGRP where PRCSNAME = ‘process name’

Second case in which you have created a wrong process definition with the options like Output destination, Page transfer etc…:

DELETE FROM PS_PRCSDEFN where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNPNL where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNGRP where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNCNTDIST where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNXFER where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNNOTIFY where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNMETA where PRCSNAME = ‘process name’
DELETE FROM PS_PRCSDEFNMESSAGE where PRCSNAME = ‘process name’

Its good to run second query set to eliminate any chances for any reference of Process Definition. Hope this will help sometime…

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2009/02/24/process-definition/

Dec 16

Error parsing file envmetadatadatamatchers.xml

Hello,

Yesterday I was caught up with a strange issue with CA while tried to view the environment info through CA. As soon as I was clicking the VIEW button, the CA was getting closed. After search with the log files of agents, viewer and CA, I noticed one error message in the CA log file…

EMF_CATEGORY – Error parsing file envmetadatadatamatchers.xml.
EMF_CATEGORY – Error parsing file envmetadatadatamatchers.xml.

I got nothing after extensive search what got missed and why this error message is coming up. There is actually no such file which was getting logged in the log file i.e. “envmetadatadatamatchers.xml” if we talk about CA specifically. But what if you can break this file name something like: “envmetadata data matchers.xml”?

Yes, this is where the CA viewer first looks to create the report and this file was missing from PS_HOMEPSEMViewwerenvmetadatadatamatchers.xml. Before start of my CA activity, I did a cleanup of the EMF HUB, Agent and Viewer and accidentally deleted matchers.xml…which should not get delete from any of the directory, neither from Agent’s directory, nor from Viewer directory.

Hope this will be of some help to you sometime…

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2008/12/16/error-parsing-file-envmetadatadatamatchers-xml/

Dec 10

Change Control Security

Change Control Security

If you have been gone through issue like Change Control has been enabled, however, any user can unlock the definition of any other user’s definition, then this is because of Change Control Security level setup which your administrator has been set according to instance. There are three types of access can be assigned if it comes to Change Control.

Restricted access
Developer access
Supervisor access

Using the Security component, you can assign users one of three Change Control access levels, depending on how much authority you want them to have. Below is a brief description about these different access levels.

Restricted access

This is top security level which can be setup to keep in mind that apart from admin, no one can chage/lock/unlock any other user’s definitions. This restricts users from locking or unlocking definitions. When Change Control locking is enabled, users with this kind of access can open PeopleSoft Application Designer development definitions in read-only mode only untill and unless admin help.

Developer access

This is for DEV instances which allows users to lock any unlocked definitions and to unlock any definitions that they have locked. This allows users only to deal with their OWN definitions, not other’s. They can then manipulate their owned definitions, as per their security profile.

Supervisor access

This is a generic level, can say for just INFO only to users among themselves. This access allows users to unlock any locked definitions, regardless of who locked them and lock the same by their profile. They can also access the Change Control Administrator dialog box, in which one can lock and unlock all definitions at one time and enable and disable Change Control locking and history. As per first comment, this kind of access is INFO only type, where one user can know who has locked this definition and accordingly take action / manipulate definition.

Note: Some contents have been taken from PeopleBooks…

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2008/12/10/change-control-security/

Nov 27

PeopleSoft Telephone format

Telephone format is by default of USA.

Telephone format is by default of USA if you want to add the field telephone in Personal information of employees through below navigation:

Main Menu > Workforce Administration > Personal Information > Modify a Person > Contact Details tab.

At times there are requirements to chnage the same in some other country format. I had been change the same Indian format.

In Application Designer, go to Tools > Miscellaneous Objects > Field Formats for PHONE. Define the phone number formats for any country you want to include.


This will hit the field PHONE (descr PS_PERSONAL_DATA for oracle platform).

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2008/11/27/peoplesoft-telephone-format/

Nov 26

Maximum number of records found

Maximum number of records found matching specified key(s)

I had been into an issue in past which was related to a warning message when tried to open the component Careers (Candidate Gateway). While trying to open the “careers” component, a warning message was poping up everytime stating “Maximum number of records found matching specified key(s)”. Later, it was figured out that due to the drop down limitation to fetch data upto 300 rows only, this message was coming. Below is the problem description and details of resolution applied.

Issue: Message was poping up on Careers component stating “Maximum number of records found matching specified key(s)”.
Reason: We had over 300 rows in PS_JOB_FAMILY_TBL. As a result, the Careers component was throwing the following message.
Resolution: Drop down can be changed to a prompt.

Resolution details:

The sub page HRS_CE_E_PREFS_SBP has a reference to Job Family as a drop down list item. The drop down list item can only fetch upto 300 number of items. If the list items exceed this limitation, a message is given that not all items could be displayed.

To fix the problem the drop down can be changed to a prompt.

1. Delete the drop down HRS_APP_JOBFAM.JOB_FAMILY
2. Insert an edit box in grid HRS_APP_JOBFAM (level 2)
3. Set the page field properties

Record name: HRS_APP_JOBFAM
Field name: JOB_FAMILY

Permanent link to this article: http://alokbhardwaj.com/oracle-peoplesoft/2008/11/26/maximum-number-of-records-found/

Older posts «

» Newer posts