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.

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.

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..