Flashin Leather

Data permission security can be administered trough tree-based or role-based security. Both methods involve assigning data access to user permission lists.

Customizations to delivered objects present an on-going maintenance issue.

So, if you customize a delivered piece of code or a page or a component, when you upgrade (or even just apply a bundle that updates that object), it is going to overwrite the object with the newly delivered version, then you are going to have to go back in and reapply your customization.

Bolt-on objects are just brought forward in an upgrade. So for example, the custom page you have in release 8.9 will come through the upgrade looking exactly like it did in the upgraded 9.1 database. So from the perspective of not having to continually reapply your modifications to delivered objects once they get updated in a fix or upgrade, bolt-on objects are easier to maintain.

However -- the catch is that the bolt-on object still has to be tested and may or may not require re-development. It may point to or relate to delivered objects that have changed or disappeared, so from this perspective, there may be effort to redevelop your bolt-on objects too.

To my mind, though, there is less effort involved with custom-added (bolt-ons) because you may or may not have to do anything to your bolt-ons depending on what you find in testing, but with modification you are always advised to take the newest delivered version of a PeopleSoft object, then reapply your modification to it.

Didi Mau is a Vietnamese expression mean "go, go quickly". Didi Mau is pronounced Diddy Mow.

I came across this expression in James Wesley Rawles's (JWR) book "Patriot".

JWR is also the founder and editor of a great blog, The Survival Blog. Check it out here.

From the login page type trace=y at the end of the url.

https://diverseyhr.oracleoutsourcing.com/psp/PJDI2J/?cmd=login&languageCd=ENG&trace=y

Open up the userid that you are using to run the Excel to CI.

People Tools > Security > User Profiles

Go to the Roles tab.

Click the View Definition link next to any role.

Click on the Permission Lists tab.

Click on View Definition next to any permission list.

Click on the Component Interfaces tab.

Enter CI_JOB_DATA and click save.

Click edit.

Set each method to full access.

Click edit.

Set each method to full access.

Setup and configure workflow

1) Main Menu > Set Up HRMS > Common Definitions > Approvals > Register Transaction ----- Create Approval Process ID (Cross reference table , Header table , App class ,Approval component is defined).

2) Main Menu > Set Up HRMS > Common Definitions > Approvals > Setup Process Definitions ----Create Definition ID for the Process ID, Definition Criteria ,Stages ,paths ,steps

3) Main Menu > Set Up HRMS > Common Definitions > Approvals > Configure Transaction ----- Add Events and notifications to transaction.

4) Main Menu > Set Up HRMS > Common Definitions > Approvals > Workflow Transaction ----- Register workflow transactions.

5) Main Menu > Set Up HRMS > Common Definitions > Approvals > Maintain User Lists ------ Define the user list or hierarchy used for routing transactions for approval.

6) Main Menu > Set Up HRMS > Common Definitions > Approvals > Generic Templates ------ Maintain email templates.

7)Main Menu > Set Up HRMS > Common Definitions >Self-service > System workflow rules ------ Workflow rule for specific SETID.


Approvals and Delegation

1) Main Menu > Workforce Administration > Self Service Transactions > Add Delegation Request ----- Add a new delegation request on behalf of a delegator.

2) Main Menu > Workforce Administration > Self Service Transactions > Administer Delegation ----- Admin for the Delegation. Admin can delegate the transactions .

3) Main Menu > Workforce Administration > Self Service Transactions > Administer/Monitor Approvals ----- AWE admin for the Approvals. Admin can approve transactions.

4)Main Menu > Workforce Administration > Self Service Transactions > Approvals Audit Report ----- Approvals Audit Report.


Delegation setup

1)Main Menu > Set Up HRMS > Common Definitions > Delegation > Installation settings ----- Configure AWE Admin Role , Enable Hierarchies , Duration to check for active proxies

2)Main Menu > Set Up HRMS > Common Definitions > Delegation > Configure Delegation Transactions ----- Configure Delegation Transaction.

Main Menu > PeopleTools > Utilities > International > Languages

Once new languages are selected and saved the application server needs to be rebooted.

If Excel to CI is generating an error stating that the connection has timed out, you might have a permission list error. Take a look at the EXCEL_TO_CI permission list and make sure it is attached to the user id that you are using to run the Excel to CI.

Here is the checklist for VETS100 data set up:

1. Check if the Establishment is linked to a valid Company and has country and Regulatory Region set to USA.
Navigation : Set up HRMS > Foundation tables > Organization > Establishments
Open the establishments for which you are running the report.

2. Check if the Establishment is linked to US Locations(On the location set up - Under USA flag)
Navigation : Set up HRMS > Foundation tables > Organization > Locations
This can be verified by querying PS_ESTAB_US_VW.

3. In the Establishments set up:
EEO-1 Gov't Contractor Type is NOT set to 'Not Applicable'.
This field can be found in the Establishment set up.
Navigation : Set up HRMS > Foundation tables > Organization > Establishments
Open the establishment definition for which you are running the EEO report and verify the above values under the USA flag.

4. Ensure that Employees are linked to the correct Establishment in Job data.
This can be verified by querying PS_JOB. Check if you have Employees linked to the Estabishments(ESTABID)for which you are running the report.

5. Ensure that the Employee's Job record is active during the period for which the report is being run.
Employee is a Regular Employee(Job data - Job Information)
Note that only the primary jobs are picked up.(Job data - Work Location)
Employee's EEO_CLASS value is NOT set to 'Exclude'(Job data - Job Information - under USA flag)

6. Ensure that the Employees also have a Job code linked to the Job data and this Job code has been classified into the appropriate EEO1 Job category in the Job code set up(USA flag).
From the list of Employees verify the Job code(JOBCODE) attached to them and check if the Job code set up has a EEO categories set up correctly.
Navigation : Set up HRMS > Foundation Tables > Job Attributes > Job code
Verify if the Job codes are linked to the appropriate EEO1 category.

7. In the Employee's personal information, verify if the Employee has been associated with the appropriate Military Status
Workforce Administration > Personal Information > Modify a Person
Open up the personal information of the Employees and check if the Employees are linked to the appropriate Military status under the USA flag on the Regional tab.
For 2008 reporting, Military status is set to one of the following:
3- Veteran of Vietnam Era
4- Other Protected Veteran
9- Vietnam & Other Protected Vet

If flags, denoting regional information, are not showing up throughout the PeopleSoft 9.1 system, check the Global Security Settings. This can be accessed at Set Up HRMS > Security > Component and Page Security > Setup Global Security. From here enter the name of the the primary permission list assigned to your USERID and add the country whose regional information is missing to the list.

This view is used on POSITION_DATA6 on the position component. It shows the incumbents for the position.

PS_INCUMB_WS1

Join this view to PS_JOB.reports_to to obtain supervisor information when using position management.

To assign a query to a group, the record GB_QRY_LINK_VW, must be part of the query. It GB_QRY_LINK_VW is not a record in the query, the query will not be accessible from the drop down list when creating a group.

A “wedge” row is a row of data that is wedged between two existing effective dated rows. For example:

First or a Historical row: CY070735 (emplid), 1/1/1980 (effdt)
Historical row: CY070735 (emplid), 4/1/2003 (effdt)
Wedge row: CY070735 (emplid), 4/1/2005) (effdt)
Current row: CY070735 (emplid), 9/14/2009 (effdt)

The Load Group Increases job, JOB006 will insert “wedge” rows.

If the Update Future Rows check box is on, the salary increase inserted on the wedge row will be carried forward to the future dated rows.

FYI: People originally saved as a person of interest, say an Applicant, will not be written to the per_org tables. They get written to PS_PER_POI_ONLY.

I was getting buffer errors when trying to access action reasons on-line. If I clicked the included history button, the window would open up. The problem turned out to be mismatched rows in child records.

The parent table is ps_actn_reason_tbl. When an action reason is created on-line the following child tables are updated in addition to ps_actn_reason_tbl;

ps_act_rsn_tbl_na
ps_act_rsn_tbl_aus
ps_act_rsn_tbl_ger
ps_act_rsn_tbl_mex
ps_actn_reason_bra
ps_act_rsn_tbl_esp
ps_actn_rsn_comm

If you are having buffer issues, pay particular attention to reason_bra and rsn_tbl_esp, in bold above. Check the database to make sure each value in the parent table has matching records in reason_bra and/or rsn_tbl_esp.

I was able to resolve the buffer issue by entering rows in the tables above if they were missing or mismatched. Also, since we are not using Brazil and Spain functionality, deleting the rows in those two tables got rid of the buffer issues as well.