Oracle 1z0-1057-22 Oracle Project Management Cloud 2022 Implementation Professional Exam Practice Test

pplications-security.html#OSCUS2287154

Predefined Notification Templates

Notification Template

Description

Password Expiry Warning Template

Warns the user that a password is expiring soon and provides instructions for resetting the password.

Password Expiration Template

Notifies the user that a password has expired and provides instructions for resetting the password.

Forgot User Name Template

Sends the user name to a user who requested the reminder.

Password Generated Template

Notifies the user that a password has been generated automatically and provides instructions for resetting the password.

Password Reset Template

Sends a reset-password link to a user who requested a new password.

Users can request new passwords by selecting the Forgot Password link on the application Sign In page, or by selecting the Password option on the Preferences page (Settings and Actions > Set Preferences).

Password Reset Confirmation Template

Notifies the user when a password has been reset.

New Account Template

Notifies a user when a user account is created and provides a reset-password link.

New Account Manager Template

Notifies the user's manager when a user account is created.

When you create a user category, it's associated automatically with the predefined notification templates, which are all enabled.

You can't edit the predefined templates. However, you can create templates and disable the predefined versions. Each predefined event can be associated with only one enabled notification template at a time.

Ref: billing-configuration-define-transfer-pricing.html#OAPFM3094619

Reference

Topic - Contract Actions and Status Changes: Explained

Ref: 19b/oapfm/project-foundation-configuration-define-project-resource-breakdown-structures.html#OAPFM180158_2

Why can't I find persons in the list of resources when I enter team members, planning resources, or person rate schedules?

You can't find persons in the list of resources when you enter team members, planning resources, or person rate schedules in the following situations:

• The administrator didn't assign a department while creating users. Persons must have an active assignment and be assigned to a department in Oracle Fusion Human Capital Management before they can be added as team members or entered as resources on the planning resource breakdown structure or person rate schedule.
• The resource isn't active in Oracle Fusion Human Capital Management because the current date is before the effective date of the resource. If you want to include persons who will start in the future, select the Include people with future-dated effective start dates option when you search for the person.
• Persons assigned as project managers aren't active as of the project start date.
• The assignment of the person is terminated, and an appropriate value isn't set for the number of days to display people with terminated assignments. You can set the profile value appropriately at the site profile level using the Specify Number of Days to Display People with Terminated Assignments task in the Setup and Maintenance work area.

Reference cloud/latest/projectcs_gs/OAPFM/OAPFM1125357.htm#OAPFM1125357

Assignment of Supporting References

Supporting references may be used to capture transaction values on journal entry lines. A supporting reference can be used on a journal entry rule set only if it's assigned a source from the event class of the journal entry rule set.

Creating Supporting References: Explained

Supporting references are used to store additional source information about a subledger journal entry at the line level.

Supporting references with balances establish subledger balances for a particular source and account for a particular combination of supporting references plus the account combination.

For example:

• If a journal line contains a supporting reference that includes two sources, Customer Type and Customer Name.
• Balances are created for the account combination, plus customer name and customer type.

Examples of how you may want to use supporting reference balances are to:

• Facilitate reconciliation back to the subledgers and source systems by tagging journal entries with transaction and reference attributes.
• Create balances by dimensions not captured in the chart of accounts.
• Reporting using dimensions not captured in the chart of accounts.
• Enrich Oracle Fusion Business Intelligence Applications reporting on subledger journals.
• Profit and loss balances by dimensions not captured in the chart of accounts

Define supporting references to hold additional supporting information for detailed account balance maintenance or reconciliation and reporting requirements.

Reference /implementing-security-in-oracle-fusion-project-portfolio-management.html#FASER1722595

Ref to “Securing Project Financial Management and Grants Management Applications”

Table lists predefined enterprise roles and the type of security that grants the role access to data in a work area or dashboard.

Enterprise Role

Work Area or Dashboard

Data Security Based On

Project Accountant

Asset

Project business unit

Project Accountant

Costs

Project expenditure business unit

Project Accountant

Revenue

Contract business unit

Project Administrator

Project Financial Management

Project business unit

Project organization

Project Billing Specialist

Invoices

Contract business unit

Project Creator

Project Financial Management

Project business unit

Project organization

Project Management Duty

Project Management Infolet Dashboard

Project assignment

Project Management Duty

Project Performance Dashboard

Project assignment

Project Manager

Project Management Infolet Dashboard

Project assignment

Project Manager

Project Performance Dashboard

Project assignment

Project Manager

Project Management

Project assignment

Project Manager

Project Manager Dashboard

Project assignment

Project Team Member

Project Financial Management

Project assignment

Grants Accountant

Invoices

Contract business unit

Grants Accountant

Revenue

Contract business unit

Grants Administrator

Awards

Contract business unit

Grants Administrator

Contracts

Contract business unit

Grants Administrator

Project Financial Management

Project business unit

Principal Investigator

Awards

Award assignment

Principal Investigator

Contracts

Award assignment

Principal Investigator

Project Financial Management

Project assignment

Shift is one of the key elements in defining project and resource calendars. Two additional key elements that are required to define the project and resource calendars are:

• Schedule Exceptions: These are dates or periods that override the regular workday patterns and shifts of a calendar. They can be used to define holidays, vacations, or other special events that affect the availability of resources or projects.
• Workday Patterns: These are patterns of working and nonworking days that repeat over a period of time. They can be used to define the standard working days and hours for a calendar. Time off, expenditure type, and accounting calendar are not key elements in defining project and resource calendars. Time off is an attribute of a resource assignment that reduces the availability of a resource. Expenditure type is a classification of costs that determines how they are processed and accounted. Accounting calendar is a calendar that defines the accounting periods and dates for transactions. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-resources.html#OAPFM2356131

The project requirements work area is a work area that allows you to define and manage requirements for your projects using various methods and sources. Requirements are statements of needs or expectations that must be met by the project outcome. Backlog items are a type of requirement that are used for agile projects that follow an iterative and incremental approach. Three of the tasks that can be performed using the project requirements work area are:

• creating projects and tasks in the context of backlog items: This task allows you to create new projects and tasks or link existing projects and tasks to backlog items. This helps you to plan and execute the work that is required to fulfill the backlog items.
• creating issues for the backlog items: This task allows you to create new issues or link existing issues to backlog items. Issues are problems or risks that affect the progress or outcome of a project or requirement. This helps you to track and resolve the issues that are related to the backlog items.
• tracking backlog item status from the requirement storyboard: This task allows you to view and update the status of backlog items from the requirement storyboard. The requirement storyboard is a graphical representation of the progress and completion of backlog items using various stages and lanes. This helps you to monitor and control the delivery of backlog items. Adding scrum master to backlog items and creating change orders for the backlog items are not tasks that can be performed using the project requirements work area. Adding scrum master to backlog items is a task that can be performed using the project team work area, as scrum master is a role that is assigned to a project team member who facilitates and coordinates the agile project activities. Creating change orders for the backlog items is a task that can be performed using the project change management work area, as change orders are documents that capture and approve changes to a project scope, schedule, or budget. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-execution.html#OAPFM2356321

The Project Integration Specialist role should be assigned to a user for using the rapid implementation feature to set up the Project Financial Management offering by populating and uploading a Microsoft Excel workbook. This role allows the user to access the Functional Setup Manager and perform the common setups for project costing and billing using predefined templates and spreadsheets. The user can also monitor and validate the setup data using reports and dashboards. Reference:

Reference

Reference Data Sharing Methods

Variations exist in the methods used to share data in reference data sets across different types of objects. The following list identifies the methods:

Assignment to one set only, no common values allowed. This method is the simplest form of sharing reference data that allows assigning a reference data object instance to one and only one set. For example, Asset Prorate Conventions are defined and assigned to only one reference data set. This set can be shared across multiple asset books, but all the values are contained only in this one set.

Assignment to one set only, with common values. This method is the most commonly used method of sharing reference data that allows defining reference data object instance across all sets. For example, Receivables Transaction Types are assigned to a common set that is available to all the business units. You need not explicitly assign the transaction types to each business unit. In addition, you can assign a business unit-specific set of transaction types. At transaction entry, the list of values for transaction types includes the following:

Transaction types from the set assigned to the business unit.

Transaction types assigned to the common set that is shared across all business units.

Assignment to multiple sets, no common values allowed. The method of sharing reference data that allows a reference data object instance to be assigned to multiple sets. For instance, Payables Payment Terms use this method. It means that each payment term can be assigned to one or more than one set. For example, you assign the payment term Net 30 to several sets but assign Net 15 to a set specific only to your business unit. At transaction entry, the list of values for payment terms consists of only the set that is assigned to the transaction's business unit.

Note: Oracle Fusion Applications contains a reference data set called Enterprise. Define any reference data that affects your entire enterprise in this set. Also update the data set going forward as you create new reference data items.

Ref:

Topic Approval Groups

Each approval group includes a set of users that you configure to act on tasks in a certain pattern. Tasks can be defined to get routed to an approval group instead of an individual user. You can nest approval groups within approval groups.

You have two options for defining the group:

• Static: Select the specific users to include in the group.
• Dynamic: Provide the logic to use to determine the users in the group.

Ref: PJC94831

• Spread Evenly
• The allocation rule divides the source pool amount equally among all the chargeable target tasks included in the rule. This is the most simple and direct basis method.
• Target Percentage and Spread Evenly
• Specify the percentage of the source pool that is required to allocate to each target line. The total specified target percentage must always equal 100 percent. The allocation rule calculates the amount to allocate to the target line, and then spreads the results evenly among the chargeable tasks.
• Prorate
• The allocation generation uses the attributes defined in the allocation rule to derive the rate at which the source pool amount is apportioned among the target projects and tasks. For this basis method, the allocation rule uses the basis attributes to apportion the source amount among all the tasks defined by the rule. The Prorate basis method provides precise control over how the rule distributes the source pool.
• Target Percentage and Prorate
• The allocation rule first uses the target percentage to calculate the amount to allocate to the line, and then apportions the results among all the tasks. The Target Percentage and Prorate basis method provides precise control over how the rule distributes the source pool.

Application Composer is a tool that allows you to configure standard objects or create custom objects to include business specific attributes for Project Execution Management. Four of the standard objects that you can configure using Application Composer are:

• Project Gates: These are checkpoints that mark the completion of a phase or stage in a project lifecycle.
• Project Issues: These are problems or risks that affect the progress or outcome of a project.
• Project Milestones: These are significant events or achievements that indicate the status or completion of a project or task.
• Project Deliverables: These are products or services that are produced or provided as part of a project or task. Project Resource Request and Project Resource Assignment are not standard objects that you can configure using Application Composer. These are features that allow you to request and assign resources for projects and tasks based on various criteria such as availability, qualifications, preferences, etc. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-execution.html#OAPFM2356201

When an invoice is entered with an invoice date in the open project accounting and closed accounting periods, the accounting date is the same as the original invoice date, but the project accounting date is the first day of the first open project accounting period. This ensures that the invoice is accounted in the correct accounting period and recognized in the correct project accounting period. Reference:

Reference gs/OAPEX/F1082603AN23E61.htm

Manage Project Enterprise Labor Resource Maintenance Conditions

Project Enterprise Labor Resources: How They Are Automatically Created and Maintained

Run the Maintain Project Enterprise Labor Resources process to create resources, remove resource availability for staffing, and maintain the resource search index.

Settings That Affect the Maintain Project Enterprise Labor Resources Process

Create and maintain project enterprise labor resources by defining a set of conditions that specify the employees and contingent workers in Oracle Fusion Human Capital Management (HCM) to create as resources in Oracle Fusion Project Portfolio Management. Define the resource attribute values, such as the resource calendar and primary project role, to assign to the new resources.

The following table lists the criteria that you define for selecting HCM persons to create as project enterprise labor resources.

Selection Criteria

Description

Person type

Select the HCM person type for the process to use as criteria when selecting HCM persons to create as resources. Available person types are employees, contingent workers, or both employees and contingent workers.

Option to select people based on job

Select this option for the process to create resources for HCM persons with specific jobs.

Caution If you do not select job criteria for this condition, the process will create resources for all eligible people based only on the person type.

Jobs

If you selected the option to select people based on job, then select the jobs for the process to use as HCM person selection criteria.

The following table lists the attributes for which you specify values to assign to resources that are created for the condition.

Resource Attribute

Description

Option to manage resource availability and staffing

Select this option for resource managers to manage the availability and project staffing of resources who are created based on the condition. Resources who are managed in Oracle Fusion Project Resource Management are eligible to fulfill project resource requests.

Calendar

Select the resource calendar for resources that are created based on the condition. The resource calendar defines the work schedule for project enterprise labor resources, and includes working days and hours and any exceptions, such as holidays.

Primary project role

Select the primary project role for resources that are created based on the condition. Project roles are maintained in Oracle Fusion Project Management.

Cost rate and currency

Enter the cost rate and currency for resources that are created based on the condition.

Bill rate and currency

Enter the bill rate and currency for resources that are created based on the condition.

The employees and contingent workers will be able to modify their time cards in the Time work area. This work area allows them to enter, review, edit, and submit their time cards for approval. They can also view the status and history of their time cards and make corrections as needed. The Time and Cost work area allows the project managers and cost accountants to review, adjust, and transfer time card transactions to projects and tasks. The Asset work area allows the asset managers and cost accountants to review, adjust, and transfer asset transactions to Oracle Fusion Assets. These work areas are not used by the employees and contingent workers to modify their time cards. Reference:

Reference

To import and process third-party transactions that are costed and accounted, you need to set the Transaction Source Options for the transaction source that you use to import the transactions. The Transaction Source Options allow you to specify whether the transactions are costed and accounted by the source system or by Oracle Fusion Cost Management. You can also specify whether to validate and transfer costs and accounting entries to projects and general ledger. Reference:

Ref:

REST API = REpresentational State Transfer (REST) Application Programing Interface (API)