Search This Blog

Friday, September 20, 2013

PeopleSoft Security Overview

Before going into the details of PeopleSoft Security, let's see where all in the PeopleSoft application we come across security related stuff .

From the user's perspective:
1. To access application through PIA , one must have an UserID to login to the application.

2. Once logged in, we certainly have to do some tasks, like an Employee can go and apply for leave or see his performance data or view paychecks etc. That means we require access to certain pages in the application.

3. Once Employee access the pages there might be certain fields which need to be hidden .

4. Also if the Employee has a role of Manager, and if the Manager wants to know the list of resources available from his department so that he/she can assign them to different projects in such a case the search results should show only the Resources under his department which is nothing but access restriction at data level.

5. If user wants to run a job then a process profile is required so that access is given to run only those jobs.

6. Suppose user wants to run a query through PIA, then the same can be achieved through Query Manager. To build a query , a table is required. To restrict user to build queries on only certain tables you need to assign query access profile which controls user to access certain tables.

7. Also if the Client has more than one PeopleSoft application and user wants to connect to other application without providing credentials again , this can be achieved through Single Sign on.
8. If we want user not to update any data on the page and just view it then we can set the same at the Page Permissions.

Now lets dig further and see what restrictions are there at Developer level :
1. Developers login to the tool called App Designer to build applications. If we want developers to restrict that certain objects like CI etc then we assign security at Definition level.

At PSAdmin Level:
1. The Webserver and Appserver config files will have information related to security which is used in validation of the requests that come browser and then give access to valid users.

2. Not everyone will have access to webserver and App Server. These tasks are handeled by PeopleSoft Admins (PS Admin)

This post is intended to give an Overview of  PeopleSoft Security.

Thursday, September 19, 2013

BI Publisher: Basics in creating a RTF template

BI Publisher in PeopleSoft helps us to view output in different formats.
We use templates to design the output layouts. Let's see a sample example below.

Data Preparation:
I had an XML file which has Band and Description.
There are 20 rows of data. Now lets load this data into the template.
                                           

Loading Data into the Template:           
Open the MS Window and Go to Add-ins tab and click on Data-->Load XML Data. 

Designing the Template:
After that drag the fields from the Field Brower onto the document as shown below.

Below is the final draft of the document which has Band and Description.
Now Click on Preview to view the Output. In the Output our expectation is to view all 20 rows but to our surprise there is only row which comes up. This is because we have not looped through all the rows of XML.

To loop through all the rows, we need to add the for-each tag. Now let's add this tag and view the output.
Tag used in this example: for-each:@row_Band


Now lets see the preview below. As expected now we get all rows in the output.

This completes the sample example of designing a report layout using RTF template.
We will see in next post on how to place headers in the template.

Friday, September 13, 2013

SQR: BEGIN-SELECT to get Count value


In SQR, we use below select construct to retrieve data from database.

BEGIN-SELECT
COL1
COL2
.
.
FROM TABLE_NAME
WHERE CRITERIA
END-SELECT

Now I need count of EE working in Department '10'. Below is the code to achieve this.

BEGIN-SELECT
COUNT(EMPLID) &Count_EE
FROM EE_DEPT_TBL
WHERE DEPARTMENT_ID = 10
END-SELECT

Sometimes, by mistake we might use #Count_EE as column variable since the value of Count is numeric. So coming to basics, all column variables will be referred with & (Ampersand).

PeopleSoft Migration Queries

Most of us have come across the term Migration, where we migrate objects developed from one environment to other. Below are few queries related to Migration issues.


Migration Queries: BI Publisher

Scenario: There is a change done to the RTF template and this new template should be migrated to other environment. What are things to keep in mind while creating a project.
Most of us have come across the term Migration, where we migrate objects developed from one environment to other. Below are few queries related to Migration issues.

You need to include below objects in the project.
BI File Definition
BI Template Definition
BI Report Definition.

Note: If the template is using a new XML file as template file, then it is mandatory to have the file ID associated with the Template included in the project. If this is not done and migrated only Template and Report Defn, then you will end up with a weird error message while opening the report defn through PIA. This is because the FileID used for template does  not exist in target database.

Migration Queries: App Engine.
Scenario: Changes are done only to few step properties in a section. Now these steps should be migrated to other envrionment.

You need to include below objects in the project.
Section
Steps for which change is done.

Migration Queries: Record Properties. Adding AUDIT record.

There was Audit Record added to the Record at Record Properties and after migration through STAT the change is not getting reflected in the target environment.

To resolve this issue, in the project Compare options, there will be option to Keep Target changes flag for Audit. It should be unchecked so that the change will take place in the target environment.

Thursday, August 22, 2013

PeopleSoft: Audit Actions.

From the previous post, we have seen various ways of Auditing. Let's see the easy way to understand the Record Level Audit with below example.
Below is the sample Transaction Record and Audit Record.
 Lets now do below transactions and see how data is stored for Record Level Audit.


Scenario 1: Insert a new effective dated row for a Deduction.
Action : 'A'

Scenario 2: Changing a Non-Key Field.
Action : 'C'
Scenario 3: Changing a Key Field.
Action : 'K'
Action : 'N'                                      

Scenario 4: Deleting a row.
Action : 'D'
Note: The tables mentioned are only for example and the fields with * can be understood as KEY fields.

Monday, August 5, 2013

Field Label : Importance of Label ID and its usage

Field Definition: Importance of Label ID and its usage

When you create a new Field Definition in PeopleSoft, you not only choose Field Type/Length/Format but also you enter the Label for the field which should appear on the page.

So it makes a logical sense, to have atleast one Label ID for a field. This will be the Default Label.

Suppose that the same field definition should display different Labels in different pages. In such a case, we go for multiple labels.

In case of Multiple labels, if no default label is selected then the first one in the list will be treated as 'Default label'.

Below are the various places in PeopleSoft where we come across the Labels for a field that should be displayed on the page.

1. Field Definition Level
2. Record Field Properties Level
3. Page Field Properties Level
4. Peoplecode

Lets see each of them in detail.

1. Field Definition Level:
Lets take Example of EMPLID  field. You can see that the default Label ID here is EMPLID and hence the Name which is used for this Label Id will be displayed on the page. But which name would come up Long Name or Short Name. This can verified by simply creating a dummy page and inserting field on the page. In the Field Properties, you can see that By Default RFT Long Name gets selected.

Also Label ID can be same as Field Name.In this case both the Field Name and Default Label ID are same.

Some Rules while creating Field Label:
The LabelID should not contain any spaces. 
The other Labels for EMPLID are as shown above.

2. Record Field Properties Level:
Lets talk of a scenario where we want Label ID 'EMPLID3' (row number 20 in the above image)
instead of Default Label 'EMPLID'.
 This can done at Record Field Properties as shown below.
In the below snapshot, Defualt Label ID is used at Record Field Properties.




It can be observed that the precedence of values shown in DropDown list. Label ID followed by Short Name and then Long Name.
Now lets change the Record Field Label ID to the one which is desired. In this case, it is 'EMPLID3'.

So now the Name for the Label ID 'EMPLID3' will be displayed on the page.
To know which Name should be displayed, let's see the Page Field Properties
3. Page Field Properties Level
From the image below, we can set the Label as either None/Text/RFT Short/RFT Long.
When RFT Short/Long is selected appropriate value will get displayed for the Label ID 'EMPLID3'.
 


4. At Peoplecode Level.  
Also through peoplecode you can change the label of field that is displayed on the page using Field Class.
The label appearing on the page can changed by using below code.
The code checks the page name and if it is JOBDATA page then LongDescr which is set for the LABEL (‘EMPLID’) will be displayed on the page and vice-versa.

Local Field &FIELD;
&FIELD = GetField(RECORD.MYFIELD);
   If %Page = PAGE.JOBDATA Then
      &FIELD.Label = &FIELD.GetLongLabel("EMPLID");
   Else If %Page = PAGE.STUDENTAPPL Then
      &FIELD.Label = &FIELD.GetLongLabel("EMPLID3");
End-If;


Note:  JOBDATA,STUDENTAPPL  are Dummy Page Names used in the above example and ‘EMPLID’/’ID’ are the labels that will be displayed based on the condition. 


Peopletools MetaTables
PSDBFIELD -- Stores Field Definitions
PSDBFLDLABL -- Stores the Field Labels


This concludes the importance and usage of Label ID in PeopleSoft.

Saturday, August 3, 2013

Business Unit


The term Business Unit is used quite often in PeopleSoft.  There are various ways we can interpret the meaning of Business Unit. 

Basically, it helps organizations to track the day to day transactions and also helps in forecasting on things that require attention.

Now let’s see the various scenarios in which Business Units can be used.

Scenario 1: Think of a college that has different Departments like Computers/Mechanical/Civil and other Departments such as Administration/Cultural/Sports.

If the College Management want to know the details happening in each of these department then each department can be treated as one Business Unit. 

Scenario 2: Consider a Restaurant, which had outlets in major cities of the country.

If the Hotel Management want to know the transactions happening in each of these City Unit then each City Unit can be treated as one Business Unit.


Scenario 3: A Company that has Business operations covered in various countries.
In this case, each office operating  from each country can be treated as one Business Unit.

Thus Business Unit is nothing but a logical entity that is used by HR/Admin/Management/Finance and various other people to generate the reports that will be helpful in understanding the operations/transactions happening in each of the units.

Hope this post is useful..