Exam Number: 1Z0-218
Exam Title: PeopleSoft Human Resources 9 Fundamentals
Exam Details
Duration: 120 minutes
Number of Questions: 70
Passing Score: 66%
Validated Against: This exam has been validated against 9.0 and 9.1.
Format: Multiple Choice
Associated Certification Paths
PeopleSoft Human Resources 9 Consultant Certified Expert
OPN Certified Specialist
Exam Preparation
Training Increases Your Chance of Passing
Complete Recommended Training
Complete the training below to prepare for your exam (optional):
PeopleSoft Human Resources Rel 9.1
Additional Preparation and Information
A combination of Oracle training and hands-on experience (attained via labs and/or field experience) provides the best preparation for passing the exam.
Resources available to partners only
Training Opportunities for Oracle Partner Network Members
Oracle PeopleSoft Enterprise HCM Implementation Boot Camp
PeopleSoft Enterprise 9 Human Capital Management, Human Resources Consultant Certified Expert Boot Camp
OPN Guided Learning Path: PeopleSoft 9.0 Human Capital Management Implementation Specialist
Training Resources by Exam Topics
Review Exam Topics
PeopleSoft HRMS Fundamentals (R9)
Human Resources
Product Overview
Describe PeopleSoft Enterprise Human Resources
Set up core human resources foundation tables
Define and administer data permission security
Add people in the PeopleSoft system
Maintain people and worker information
Business Process Overview
Explain PeopleSoft Enterprise Human Resources Management System (HRMS) products and business processes
Explain PeopleSoft Human Resources core foundation tables
Explain PeopleSoft table setup considerations
Explain effective dating and action types
Use sources of information about PeopleSoft Human Resources
Setting Up Core Foundation Tables Related to Installation Settings and Companies
Define the Human Resources foundation table sequence related to Installation Settings and Companies
Define the Installation Table
Set up the Company table
Identify implementation and worker-level default options related to Installation Settings and Companies
Setting Up Core Foundation Tables Related to Business Units and TableSet Sharing
Define the Human Resources foundation table sequence related to Business Units and TableSet Sharing
Define setIDs, business units, and tableset sharing
Establish user and business unit defaults
Identify implementation and worker-level default options related to Business Units and TableSet Sharing
Setting Up Core Foundation Tables Related to Establishments, Locations, and Departments
Define the Human Resources foundation table sequence related to Establishments, Locations, and Departments
Set up the Establishment table
Set up the Location table
Set up the Department table
Identify implementation and worker-level default options related to Establishments, Locations, and Departments
Setting Up Core Foundation Tables Related to Compensation
Define the Human Resource foundation table sequence related to Compensation
Set up compensation rate code data
Set up the salary plan tables
Identify implementation and worker-level default options related to Compensation
Setting Up Core Foundation Tables Related to Jobs and Pay Groups
Define the Human Resource foundation table sequence related to Jobs and Pay Groups
Set up the Job Code table
Set up the pay group tables
Identify implementation and worker-level default options related to Jobs and Pay Groups
Administering Data Permission Security
Explain row level data permission security
Identify methods of granting data permission access
Administer tree-based security
Refresh security join tables
Adding People in the PeopleSoft System
Explain organizational relationships
Add a person in the PeopleSoft system
Add a job instance for a person
Explain job level defaults
Define multiple organizational instances, employment record numbers, and additional assignments
Adding Workers Through Template-Based Hires (SmartHire)
Define the SmartHire process
Set up template-based hire templates
Add a template-based hire
Manage the status of a template-based hire
Maintaining Person and Job Data
Maintain historical information for your workforce
Manage personal data and job data
Create action reason codes
Enter termination and last date worked information
View job summary information
Question 1:
In which two scenarios would you use Role-based data permission security method as compared to Tree based? (Choose two.)
A. Your organization is not hierarchical.
B. Your organization structure is hierarchical.
C. Users have access to data for people in specific areas of the organization.
D. You want a flexible way to grant security access to a person outside a department.
E. Your security structure is based largely on the organizational department structure.
Answer: A,D
Question 2:
Several tables are involved in setting up SetIDs, Business Units, and TableSet Controls.
Choose the correct order of these tables.
A. Create Set ID, Create business unit, Define user defaults in org defaults, Access TableSet Control component and map SetID to each record group
B. Create SetID, Create business unit, Access TableSet Control component and map SetID to each record group, Define business unit defaults, Define user defaults in org defaults
C. Create business unit, Define business unit defaults, Create SetID, Access TableSet Control component and map SetID to each record group, Define user defaults in org defaults
D. Create SetID, Access TableSet Control component and map SetID to each record group, Create business unit, Define business unit defaults, Define user defaults in org defaults
E. Create SetID, Map SetID to each record group, Create business unit, Define business unit defaults, Define user defaults in org defaults, Access TableSet Control component and map SetID to each record group
Answer: B
Question 3:
Which table has to be set up before configuring Job Codes?
Pass Your Certification With Marks4sure Guarantee 2
A. SetID
B. Location
C. Company
D. Pay Group
E. Department
F. Regulatory Region
Question 4:
Answer: A
On the Job Data Work Location tab for a new hire, Company is a required field.
You can default Company from the _____ table.
A. Location
B. Job Code
C. Position Data
D. Business Unit
E. Holiday Schedule
Answer: C
Question 5:
Your client is considering implementing a multi-step grade Salary Plan and is planning to use the Default Pay component functionality in Job Data. To accomplish this, which four core foundation table components need to be set up? (Choose four.)
A. Company
B. Installation
C. Salary Plan
D. Salary Step
E. Pay Group
F. Salary Grades
G. Comp Rate Code
Answer: B,C,F,G
Thursday, 5 April 2018
1Z0-218 PeopleSoft Human Resources 9 Fundamentals
Thursday, 29 March 2018
1Z0-588 Oracle Hyperion Data Relationship Management Essentials
Exam Number: 1Z0-588
Exam Title: Oracle Hyperion Data Relationship Management Essentials
Exam Details Duration: 120 minutes
Number of Questions: 73
Passing Score: 63%
Beta exam score reports will be available approximately January 3, 2013. You will receive an email with instructions on how to access your score.
Validated Against: This exam has been validated against version 11.
Format: Multiple Choice
Exam Preparation
Training Increases Your Chance of Passing
Complete Recommended Training
Complete the training below to prepare for your exam (optional):
Oracle Hyperion Data Relationship Management Implementation Boot Camp (available to partners only)
Oracle Hyperion Data Relationship Management 11.1.2 Administration
Additional Preparation and Information
A combination of Oracle training and hands-on experience (attained via labs and/or field experience) provides the best preparation for passing the exam.
Guided Learning Path: Oracle Hyperion Data Relationship Management Implementation guided learning path (available to partners only)
Review Exam Topics
Implementation Scope and Risks
Describe best practices for project scoping and establishing implementation timelines
Describe common implementation risks
Describe phasing implementations
Describe implementation roles and responsibilities
Evaluate common customer Issues
Evaluate common customer strengths
Describe testing and rollout best practices
DRM Overview
Describe DRM key features
Manage versions
Manage hierarchies
Manage nodes
Use Property Queries
Manage Exports / Reports
Use Audit Data
Describe user roles and responsibilities
Describe the DRM Architecture
Managing the Initial Data Load
Perform structural reconciliation
Manage naming collisions
Manage duplicate nodes
Managing Properties and Property Categories
Manage properties from upstream and downstream systems
Manage similar properties
Manage property defaults
Manage calculated properties (derived, inherited, lookup)
Manage property scoping
Manage node types
Manage property categories
Define and load properties and structure
Alternate Hierarchies
Define and build alternate hierarchies
Support differences or force consistency
Build alternate hierarchies from attributes and an export
Mappings
Manage basic one to one or one to many mappings using properties
Manage basic one to one or one to many mappings using hierarchies
Manage complex many to many mappings
Managing Data Feeds
Identify upstream and downstream systems
Identify and analyze interfaces used
Describe timing of feeds
Describe file format and restrictions
Describe Imports, Action Scripts, Blender, and Exports
Manage upstream data feed(s) and reconciliation
Manage downstream data feed(s) and reconciliation
Include skipping and padding levels in balance or recursive hierarchy feeds
Manage multiple downstream systems of the same type
Generate mapping tables for ETL processes for downstream systems
Implement automated data feed(s)
Versioning
Manage version composition
Manage version timings
Manage usage of version status
Manage synch methodology for what/if and planning versions
Business Rules
Manage business rules for downstream systems
Manage business rules for client processes
Manage business rules to address system issues
Users
Manage users and assign roles
Manage node access groups and property categories
Manage node access for users
Setup anonymous access
Workflow
Evaluate if workflow is needed and determine workflow requirements
Integrate workflow through the request API
API Integration
Evaluate API integration requirements
Integrate through the public API
QUESTION 2
Your operations group is in the middle of a large re-organization of the Entity dimension.
You create versions at the end of each closed month on the fifth work day.
Business users have access to update the Entity hierarchy within the working version to add new cost centers and move cost centers beginning on the seventh business day. Your CFO is requesting the complete chart of accounts hierarchy as of the 15th day of the month.
How can you deliver the CFO's request assuming the "AllowAsOf system preference has been set to True?
A. Use the Copy feature for versions and enter the "As Of" date.
B. Use the "As Of" feature and enter the "As Of" date.
C. Use the Copy feature and then use the transaction history to back out changes made since the desired date.
D. Rebuild the hierarchy from a backup.
E. Use the Copy feature for the hierarchy and enter the "As Of" date.
Answer: C
QUESTION 3
What two DRM features allow you to group hierarchies used for data mappings for easier selection and browsing?
A. Version
B. Property category
C. Hierarchy group
D. Node type
E. Hierarchy master
Answer: B,C
QUESTION 4
Identify the three true statements about using the "Asc" property types.
A. They are used to sort hierarchies in ascending order.
B. They are used to help maintain one-to-one or one-to-many mappings.
C. Associated nodes do not need to exist prior to import of the hierarchy.
D. They can reference nodes in different hierarchies.
E. They should be used with local node—level properties.
F. They pull in the node hierarchy and the node name.
G. They support bidirectional references.
Answer: A,C,F
QUESTION 5
You have built a validation to ensure that a hierarchy has no more than 20,000 nodes. What is the correct validation level?
A. Node
B. Hierarchy
C. Version
D. Global Node
E. Global Hierarchy
F. Merge
Answer: D
QUESTION 6
Identify the four true statements about designing property categories, property definitions, and validations for target and source systems.
A. Allow users to type in property values for properties that only have a limited set of valid values.
B. Create derived property definitions that are hidden from users that can be used in exports for target systems.
C. Create separate property categories for each target and source system.
D. Name property definitions different then target system names.
E. Create similar validations that are used by source systems.
F. Create similar validations that are used by target systems.
Answer: B,C,D,E
Exam Title: Oracle Hyperion Data Relationship Management Essentials
Exam Details Duration: 120 minutes
Number of Questions: 73
Passing Score: 63%
Beta exam score reports will be available approximately January 3, 2013. You will receive an email with instructions on how to access your score.
Validated Against: This exam has been validated against version 11.
Format: Multiple Choice
Exam Preparation
Training Increases Your Chance of Passing
Complete Recommended Training
Complete the training below to prepare for your exam (optional):
Oracle Hyperion Data Relationship Management Implementation Boot Camp (available to partners only)
Oracle Hyperion Data Relationship Management 11.1.2 Administration
Additional Preparation and Information
A combination of Oracle training and hands-on experience (attained via labs and/or field experience) provides the best preparation for passing the exam.
Guided Learning Path: Oracle Hyperion Data Relationship Management Implementation guided learning path (available to partners only)
Review Exam Topics
Implementation Scope and Risks
Describe best practices for project scoping and establishing implementation timelines
Describe common implementation risks
Describe phasing implementations
Describe implementation roles and responsibilities
Evaluate common customer Issues
Evaluate common customer strengths
Describe testing and rollout best practices
DRM Overview
Describe DRM key features
Manage versions
Manage hierarchies
Manage nodes
Use Property Queries
Manage Exports / Reports
Use Audit Data
Describe user roles and responsibilities
Describe the DRM Architecture
Managing the Initial Data Load
Perform structural reconciliation
Manage naming collisions
Manage duplicate nodes
Managing Properties and Property Categories
Manage properties from upstream and downstream systems
Manage similar properties
Manage property defaults
Manage calculated properties (derived, inherited, lookup)
Manage property scoping
Manage node types
Manage property categories
Define and load properties and structure
Alternate Hierarchies
Define and build alternate hierarchies
Support differences or force consistency
Build alternate hierarchies from attributes and an export
Mappings
Manage basic one to one or one to many mappings using properties
Manage basic one to one or one to many mappings using hierarchies
Manage complex many to many mappings
Managing Data Feeds
Identify upstream and downstream systems
Identify and analyze interfaces used
Describe timing of feeds
Describe file format and restrictions
Describe Imports, Action Scripts, Blender, and Exports
Manage upstream data feed(s) and reconciliation
Manage downstream data feed(s) and reconciliation
Include skipping and padding levels in balance or recursive hierarchy feeds
Manage multiple downstream systems of the same type
Generate mapping tables for ETL processes for downstream systems
Implement automated data feed(s)
Versioning
Manage version composition
Manage version timings
Manage usage of version status
Manage synch methodology for what/if and planning versions
Business Rules
Manage business rules for downstream systems
Manage business rules for client processes
Manage business rules to address system issues
Users
Manage users and assign roles
Manage node access groups and property categories
Manage node access for users
Setup anonymous access
Workflow
Evaluate if workflow is needed and determine workflow requirements
Integrate workflow through the request API
API Integration
Evaluate API integration requirements
Integrate through the public API
QUESTION 2
Your operations group is in the middle of a large re-organization of the Entity dimension.
You create versions at the end of each closed month on the fifth work day.
Business users have access to update the Entity hierarchy within the working version to add new cost centers and move cost centers beginning on the seventh business day. Your CFO is requesting the complete chart of accounts hierarchy as of the 15th day of the month.
How can you deliver the CFO's request assuming the "AllowAsOf system preference has been set to True?
A. Use the Copy feature for versions and enter the "As Of" date.
B. Use the "As Of" feature and enter the "As Of" date.
C. Use the Copy feature and then use the transaction history to back out changes made since the desired date.
D. Rebuild the hierarchy from a backup.
E. Use the Copy feature for the hierarchy and enter the "As Of" date.
Answer: C
QUESTION 3
What two DRM features allow you to group hierarchies used for data mappings for easier selection and browsing?
A. Version
B. Property category
C. Hierarchy group
D. Node type
E. Hierarchy master
Answer: B,C
QUESTION 4
Identify the three true statements about using the "Asc" property types.
A. They are used to sort hierarchies in ascending order.
B. They are used to help maintain one-to-one or one-to-many mappings.
C. Associated nodes do not need to exist prior to import of the hierarchy.
D. They can reference nodes in different hierarchies.
E. They should be used with local node—level properties.
F. They pull in the node hierarchy and the node name.
G. They support bidirectional references.
Answer: A,C,F
QUESTION 5
You have built a validation to ensure that a hierarchy has no more than 20,000 nodes. What is the correct validation level?
A. Node
B. Hierarchy
C. Version
D. Global Node
E. Global Hierarchy
F. Merge
Answer: D
QUESTION 6
Identify the four true statements about designing property categories, property definitions, and validations for target and source systems.
A. Allow users to type in property values for properties that only have a limited set of valid values.
B. Create derived property definitions that are hidden from users that can be used in exports for target systems.
C. Create separate property categories for each target and source system.
D. Name property definitions different then target system names.
E. Create similar validations that are used by source systems.
F. Create similar validations that are used by target systems.
Answer: B,C,D,E
Subscribe to:
Posts (Atom)