Search This Blog

Showing posts with label hrms. Show all posts
Showing posts with label hrms. Show all posts

HRMS interview questions

HRMS Fundamentals 9.0
 
1. What are all the components will have data permission security control access?
• Departtments
• Employee, Contingent Worker, and POI with Jobs.
• POI without jobs.
• Recruiting Federal People with jobs.
• Template based hires.
 
2. What are all the organisational relationships available while hiring an employee?
• Employee
• Contingent Worker
• Person of Interest (POI)
 
3. List down the people part of the POI?
• COBRA Participants
• Pension Payees
• Global Payroll Payees
• Stock non-HR Person
• Stock board members
• External Instructor
• Payroll Employees
• External Trainers
 
4. What are all the People Tools Security?
• Permission List
• Roles
• User Profiles
 
5. What are all the default programs you need to run after the creating the user profile?
• Refresh SJT CLASS ALL
• Refresh Trans. SJT tables
• Refresh SJT OPR CLS
 
6. What are all the default Permission List used while creating the User ID?
• Navigator Homepage Permission List
• Process Profile Permission List
• Primary Permission List
 
7. What are all the methods for assigning Data Permission Access to Permission List?
• Tree based data permission security
• Role based data permission security
 
8. What are all the Access types for Department security sets?
• Departments by Tree
• Departments by non – tree
• Departments by set id
 
9. What are all the Access types for People with jobs security sets?
• Job department tree
• Job location
• Jon business unit
• Job Company
• Job regulatory region
• Job salary grade
• Person organisation
• Department ID – non tree
• Company – Pay group
 
10. What are all the Access types for People without jobs security sets?
• POI Business Unit
• POI Location
• POI Institution
• Person of Interest
 
11. What are all the Access types for Recruiting Job Opening security sets?
• RS Company
• RS Business Unit
• RS Department ID
• RS Location
• Recruiting Team
 
12. What are all the Access types for Template Based Hire security sets?
• Template ID
• Template Category
• Person Organisation
• Country
 
13. What is the default tree name need to give while creating the new tree?
Dept_Security followed by any name as per your requirement.
 
14. What would be the default effective date for creating the new tree?
1/1/1900 or 1/1/1901
 
15. What are all the tree manager definitions?
• Level
• Node
• Parent
• Sibiling
• Child
 
16. What are all the various types of SJT?
• SJT_CLASS
• SJT_CLASS_ALL
• SJT_PERSON
• SJT_DEPARTMENT
 
Adding People in the PeopleSoft System
 
17. What are all the organisational instance components?
• Add Employment Instance (Job_Data_Emp)
• Add Contingent Worker Instance (Job_Data_CWR)
• Add Person of Interest Job (Jon_Data_POI)
 
 
18. What are all the job instances used for POIs?
• COBRA qualified beneficiaries
• Stock employees not administered in Human Resources
• Global Payroll Employees
• Pension Payees
• Stock board members
 
19. What are all the purpose of the Job Earnings Distribution Information Page?
We can distribute the worker’s compensation on the basis of the following:
• Department
• Job Code
• Earnings Code
• Business Unit
• Shift
• Position Number
• General Ledger Pay type
 
20. What are all the job level defaults?
• Work
• Job Information
• Job Labor
• Payroll
• Salary Plan
• Compensation
• Employment Information
• Benefit Program Participation
• Earnings Distribution
 
Adding Workers Through Template-Based Hires (SmartHire)
21. What are all the main components for setting the hire template?
• Template Record/Field
• Template Section
• Template Category Table
• Template Creation
 
22. What are all the statuses used to define templates?
• Test (Default Value)
• Active
• Inactive
 
23. What are all the statuses available on the template hire status page?
• Pending Hires
• Cancelled Hires
• Processed Hires
 
Maintaining Person and Job Data
 
24. What are the methods available to update worker’s compensation packages?
• Seniority Pay increases
• Grade Advance increases
• Automated step increases
• Step increases using review bands
• Amount increases
• Percentage increases
 
25. What are all the components available under Setup HRMS?
• Install
• Security
• Upgrade
• Foundation Tables
• Common Definitions
• Product Related
• System Administration
 
26. What isEffective Date?
Information Component /Record linked to the data EFFDT. Information changes based on the EFFDT.
 
27. What is Effective Sequence?
Identifier to find the order of multiple transactions occurring on a same EFFDT.
 
28. What is the effective sequence’s default number?
0
 
29. What are all the two statuses will be available on the top of the job data?
 
30. What are all the different types of action/reasons available on the system?
 
31. What’s the difference between a position number and a job code?
Position number is the unique identification number for driven by business unit , department ,location , job code and other parameters
 
32. What do you mean by budget and incumbents?
 
34. What is the purpose of update/display mode?
To add the new information current and future as well view the current data.
 
35. What is the purpose of correct history mode?
To correct the past and current information based on the EFFDT.
 
36. What is the purpose of include history mode?
To view the past information based on the EFFDT.
 
37. What is difference between Person ID and Employee ID?
 
38. What is Employee Record Number?
Number to identify an employee’s different organizational relationships.
 
39. What are all the mandatory fields need to key in while add a person on the system?
1) Name
2) Organizational relationship
 
National ID , Address, Birthdate gives us warning message.
 
40. What is employment instance?
Employee relationship with organization. Where employee can have multiple relationship (instances) with the organization.
 
41. What is the difference between Set Id and a Business Unit?
Where a Business Unit organizes your company or your organization, SetIDs help you organize your data within the system. The HRMS system uses tables (Control Tables or Prompt Tables) that use a high-level key that enables you to identify and retrieve data from the system. A secondary high-level key, referred to as a SetID, has also been added on various tables. SetIDs are simply the labels used to identify a TableSet. Business Unit and SetID functionality in PeopleSoft also provides you with a higher business level for reporting purposes and other business data roll-up.
 
42. What is HCCPALL?
Delivered primary permission list with access to all the components and pages
 
43. What is HCDPALL?
Delivered row level security permission list with full access.
 

PeopleSoft Authorization ID's

User IDs:

A PeopleSoft user ID is the ID you enter at the PeopleSoft sign-in dialog box. You assign each PeopleSoft user a user ID and password. The combination of these two items grants users online access to the PeopleSoft system. The system can also use a user ID stored within an LDAP directory server.

The user ID is the key used to identify the user profile definition.

Connect ID:
The connect ID performs the initial connection to the database.

Note. PeopleSoft no longer creates users at the database level.
A connect ID is a valid user ID that, when used during sign-in, takes the place of PeopleSoft user IDs. Using a connect ID means you don’t have to create a new database user for every PeopleSoft user that you add to the system.

Note. A connect ID is required for a direct connection (two-tier connection) to the database. Application servers and two-tier Microsoft Windows clients require a connect ID. You specify the connect ID for an application server in the Signon section of the PSADMIN utility. For Microsoft Windows clients, you specify the connect ID in the Startup tab of PeopleSoft Configuration Manager. You can create a connect ID by running the Connect.SQL and Grant.SQL scripts.
Warning! Without a connect ID

Access IDs:

When you create any user ID, you must assign it an access profile, which specifies an access ID and password.

The PeopleSoft access ID is the RDBMS ID with which PeopleSoft applications are ultimately connected to your database after the PeopleSoft system connects using the connect ID and validates the user ID and password. An access ID typically has all the RDBMS privileges necessary to access and manipulate data for an entire PeopleSoft application. The access ID should have Select, Update, and Delete access.

Users do not know their corresponding access IDs. They just sign in with their user IDs and passwords. Behind the scenes, the system signs them into the database using the access ID.

If users try to access the database directly with a query tool using their user or connect IDs, they have limited access. User and connect IDs only have access to the few PeopleSoft tables used during sign-in, and that access is Select-level only. Furthermore, PeopleSoft encrypts the sensitive data that resides in those tables.

Note. Access profiles are used when an application server connects to the database, when a Microsoft Windows workstation connects directly to the database, and when a batch job connects directly to the database. Access profiles are not used when end users access applications through Pure Internet Architecture. During a Pure Internet Architecture transaction, the application server maintains a persistent connection to the database, and the end users leverage the access ID that the application server domain used to sign in to the database.
Note. PeopleSoft suggests that you only use one access ID for your system. Some RDBMS do not permit more than one database table owner. If you create more than one access ID, it may require further steps to ensure that this ID has the correct rights to all PeopleSoft system tables.

Symbolic IDs
PeopleSoft encrypts the access ID when it is stored in the PeopleTools security tables. Consequently, an encrypted value can’t be readily referenced or accessed. So when the access ID, which is stored in PSACCESSPRFL, must be retrieved or referenced, the query selects the appropriate access ID by using the symbolic ID as a search key.

The symbolic ID acts as an intermediary entity between the user ID and the access ID. All the user IDs are associated with a symbolic ID, which in turn is associated with an access ID. If you change the access ID, you need to update only the reference of the access ID to the symbolic ID in the PSACCESSPRFL table. You do not need to update every user profile in the PSOPRDEFN table.