Free and Premium Oracle 1z0-1057-24 Dumps Questions Answers

Reference 816855

Spread curves let you distribute quantity, cost, and revenue amounts automaticallyacross accounting or project accounting periods. You assign a spread curve to each resource class. Planning resources (in the planning resource breakdown structure) inherit the spread curve setting from the associated resource class. You can change the spread curve for the planning resource and for any corresponding task assignments, or budget or forecast lines.

Reference 43

Topic - Manage Project Unit Organizations

The project resource search index is used to store and retrieve information about project resources such as their availability, qualifications, preferences, etc. The project resource search index is used for three purposes:

Display resource details: The project resource search index provides the resource details such as name, email, job title, organization, etc. that are displayed on the resource search page.

Filter counts while you search for resources: The project resource search index provides the filter counts that show how many resources match each filter criterion on the resource search page.

Calculate Resource Qualification Scores: The project resource search index provides the qualification information such as skills, certifications, languages, etc. that are used to calculate the Resource Qualification Scores for each resource based on their match with the resource request. The project resource search index does not provide absence details for resources or calculate Resource Availability Scores. These are provided by other components such as Oracle Fusion Absence Management and Oracle Fusion Human Capital Management. Reference:

When the Accrue at Receipt option is set to Yes on a PO, the cost of the items or services is accrued when they are received, not when they are invoiced. Therefore, the cost is transferred to projects by Cost Management and not by Payables. However, if the PO is closed for receiving without creating a receipt, there will be no accounted receipt lines and no cost will be transferred to projects. To transfer the cost to projects, you need to either create a receipt or reopen the PO for receiving.Reference:

Ref:

Ref:

Fusion Middleware Administrator's Guide for Authorization Policy Manager

Managing Security Artifacts

This chapter describes the procedures an administrator follows to manage application-specific security artifacts, view the external role hierarchy, manage the application role hierarchy, andmanage the many-to-many mapping of application roles to external roles from both the application and the external role point of view.

This chapter is divided into the following sections:

Managing Application Security Artifacts

Viewing the External Role Hierarchy

Managing the Application Role Hierarchy

Mapping Application Roles to an External Role

Mapping External Roles to an Application Role

Role Mapping Policy

A Role Mapping Policy is used to determinewhat external subjects(users, groups orExternal Roles) are assigned to the applicable Application Role. The Application Role, when referenced in an Authorization Policy, defines the principals affected by the Authorization Policy. Role Mapping Policies may also include conditions

Oracle Identity Manager –Not used for mapping application roles to external roles

How do Users Interact with Oracle Identity Manager?

Oracle Identity Manager provides an end-user interface, called the Identity Self Service console, and a system administrator interface, called the Identity System Administration console. Both end-users and system administrators use the web browser to log on to Oracle Identity Manager. Oracle Identity Manager (OIM)

OIM provision users, roles, and defines what a user can do in Oracle Cloud

Duty Roles are mapped to jobs and assigned access privileges (Data Security)

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:

Reference le.com/helpPortal/topic/TopicId_P_8718794B26A7BB93E040D30A688149A3

To access transactions for a business unit, the project accountant needs to be assigned to an external role that grants access to that business unit. The external role is defined by the security profile of the business unit and can be different for each business unit. The job role and the legal entity are not relevant for accessing transactions for a business unit. The ledger is relevant for accounting transactions, but not for project transactions.Reference:

The borrowed and lent cross charge method is a method that allows you to process cross charge transactions between provider and receiver organizations that belong to different legal entities within the same primary ledger. This method does not generate internal invoices or intercompany accounting entries for cross charge transactions. Instead, this method creates accounting entries that move an amount equal to the transfer price between the provider and receiver organizations using borrowed and lent accounts. Two statements that are true about this method are:

Internal Invoice is not generated with this method. This method does not create internal invoices for cross charge transactions, as these transactions are accounted within the same primary ledger using borrowed and lent accounts.

This method allows you to process cross charge transactions across legal entities. This method allows you to process cross charge transactions between provider and receiver organizations that belong to different legal entities within the same primary ledger, as long as they share the same chart of accounts, calendar, currency, and subledger accounting method.

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 balancemaintenance or reconciliation and reporting requirements.

To sell items not tracked in inventory, inventory items, and services, you can create two contract lines with different line types. The line type of “sell intent, free-form, project-based” allows you to sell any item or service without specifying the item number or quantity. The line type of “sell intent, item, project-based” allows you to sell inventory items by specifying the item number and quantity. Both line types are project-based, meaning they are linked to a project and generate revenue based on project performance.Reference:

Ref: oracle.com/en/cloud/saas/project-portfolio-management/19a/oapem/execute-project-tasks-and-deliverables.html#OAPEM1122082

Followers are persons who aren't working on the task but have an interest in reviewing the task progress. Only the resources and other followers can add followers to a task. If a resource assigns the task to another team member, the application automatically changes the original resource to a follower.

What's the difference between my tasks and tasks that I follow?

You can edit task details and enter progress for your tasks on the Manage Tasks page. If a task has multiple resources, only the primary resource can edit the task.

When you follow a task, you can view the task details and see the task activity stream. You receive e-mail notifications of changes that team members make to the task.

If a resource reassigns the task to another team member, then the previous resource automatically becomes a follower.

The reason for this problem is that the two expenditure types are not assigned to the reference data set that is assigned to the project unit in which the transaction is performed. Expenditure types are a type of reference data that can be shared across different business units or organizations using reference data sets. To make an expenditure type available for selection when you enter an expenditure batch, you need to assign it to the reference data set that is assigned to the project unit of the transaction. The project unit determines the reference data set for expenditure types. The reference data sets that are assigned to the project expenditure organization, the business unit, or the project-owning organization do not determine the reference data set for expenditure types. These reference data sets may determine other types of reference data such as expenditure categories, expenditure item dates, etc. Reference:

 Project Management is the product offering that enables you to collaboratively plan and deliver projects by leveraging intuitive and integrated scheduling tools. Project Management allows you to create and manage project plans, tasks, deliverables, issues, milestones, gates, etc. using various methods and sources. You can also monitor and control project progress and performance using dashboards and reports. Resource Management is the product offering that enables you to optimize the utilization and allocation of resources for projects and tasks. Resource Management allows you to create and manage resource requests, assignments, pools, calendars, etc. using various criteria and sources. You can also monitor and analyze resource availability and demand using dashboards and reports. Project Control is the product offering that enables you to simplify the planning, budgeting, and forecasting capabilities for projects and tasks. Project Control allows you to create and manage project budgets, forecasts, financial plans, etc. using various methods and sources. You can also monitor and control project costs and variances using dashboards and reports. Project Costing is the product offering that enables you to capture and process project costs from various sources and applications. Project Costing allows you to create and manageproject transactions, expenditures, assets, etc. using various rules and options. You can also generate project costing and accounting entries using dashboards and reports. Reference:

Reference

According to Oracle sources1, the inheritance between requirements, tasks, and deliverables works as follows:

You can associate a deliverable with a task independent of associating a requirement with a task. You can also associate a deliverable with a requirement independent of associating a task with a requirement1.

A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. You must manually associate the deliverable with the tasks that produce it1.

Therefore, the correct answer is B and D.

1: Can deliverables for projects and tasks be inherited from associated requirements? - docs.oracle.com (index 1)

In Oracle Project Management, you can define requirements, tasks, and deliverables for your project based on your project methodology and lifecycle. Requirements are statements of needs or expectations that must be met by the project outcome. Tasks are units of work that must be performed to complete the project. Deliverables are products or services that are produced or provided as part of a task or requirement. Two correct statements about how the inheritance between requirements, tasks, and deliverables works are:

You associate a deliverable with a task independent of associating a requirement with a task. This means that you can create a deliverable for a task regardless of whether the task is linked to a requirement or not.

A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. This means that you have to manually associate a deliverable with a task even if both the deliverable and the task are linked to the same requirement.

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:

Reference

Settings That Affect Performance Data Summarization

You can summarize performance data for a project unit, business unit, a range of projects, or projects managed by a project manager. When you run the Update Project Performance Data process from the Scheduled Processes page, select one of the summarization methods from the following table:

Summarization Method

Usage

Incremental

Summarizes new transactions that are yet to be summarized

Delete and re-summarize

Correct summary data when the source system data changes outside the regular transaction flow.

Do not use this summarization method when you run the Update Project Performance Data Without Producing Report process unless you are advised to do so.

Resource breakdown structure

Migrate all summary data from one resource breakdown structure version to the next.

If you select this option, you must also specify the resource breakdown structure header.

Ref: oject-financial-management-applications.html#FAPFM969761

Topic - Entering Planning Resource Breakdown Structure Details

ClickNavigator > Setup and Maintenance, and search for theManage Planning and Billing Resource Breakdown Structurestask.

Click theManage Planning and Billing Resource Breakdown Structureslink.

Use the Manage Planning and Billing Resource Breakdown Structures page to create new planning resource breakdown structures and to review existing planning and billing resource breakdown structures.

Click theCreateicon in the Planning Resource Breakdown Structures section.

Use the Create Planning Resource Breakdown Structure: Basic Information page to provide basic resource breakdown structure information including the name, active dates, and project unit.

Enter a planning resource breakdown structure name and select a date from which the resource breakdown structure is available for use.

Optionally, provide a description and a date to which the planning resource breakdown structure is available for use.

Select a project unit. Only projects created for the selected project unit can use this planning resource breakdown structure.

If you want to allow project managers to add planning resources at the project level, then select theAllow resource changes at project levelcheck box.

Tip:Changes at the project level don't move back to the parent planning resource breakdown structure.Deselect this option to ensure all project using the planning resource breakdown structure use the same resources.

Optionally, select aJob Setas a source of jobs for creating planning resources on your planning resource breakdown structure.

ClickSave.

When you use Create Tree or Create Tree Version in the action menu, you create a new organization tree or a new version of an existing tree, respectively. These actions result in an Inactive status for the organization tree, until you activate it. When you use View Tree Version or select the Edit icon or click the name of the tree, you open an existing organization tree that has an Active status.Reference:

When a project invoice is transferred or created in Receivables, the project sends only the invoice header and invoice line description to Receivables, not the invoice distributions. The invoice distributions contain the detailed information such as quantity, unit price, and line total. Therefore, the Receivables invoice does not show these details, but only shows a quantity of 1 and a unit price equal to the line total.Reference:

 If the Require Complete Asset Definition option is enabled on a project type, the “Transfer Assets to Oracle Fusion Assets” process will place asset lines with complete definition into the Hold queue in Oracle Fusion Assets. This queue holds the asset lines that require manual review and approval before they can be posted to the asset register. Asset lines with incomplete definition will be placed into the Error queue in Oracle Fusion Assets. This queue holds the asset lines that have errors or missing information that need to be corrected before they can be transferred to the Hold queue. Reference:

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

The Resource Qualification Score is a percentage that indicates how well an individual matches the qualifications required for a resource request. An individual’s score is 100% if either of the following conditions are met:

The resource request has a qualification, but no proficiency is specified, and the resource has the qualification. This means that any level of proficiency is acceptable for the qualification.

The resource request has a qualification with a specified proficiency and the resource has the qualification that meets the specified proficiency. This means that the resource has the exact level of proficiency required for the qualification. An individual’s score is not 100% if the resource request has a qualification with a specified proficiency and the resource does not have the qualification or has a different level of proficiency than required. In this case, the score is calculated based on how close the resource’s proficiency is to the required proficiency. Reference:

Password complexity criteria are criteria that determine how strong or secure a password must be for a user account. Password complexity criteria can include requirements such as minimum length, uppercase letters, lowercase letters, numbers, special characters, etc. Three of the valid password complexity criteria while setting up password policies are:

Complex: At least 8 characters, 1 uppercase, and 1 number

Very Complex: At least 8 characters, 1 uppercase, 1 number, and 2 special characters

Very Complex: At least 8 characters, 1 uppercase, 1 number, and 1 special character Simple: At least 8 characters and 1 number is not a valid password complexity criterion while setting up password policies, as this criterion does not meet the minimum security standards for Oracle Cloud applications. Very Complex: At least 6 characters, 1 uppercase, 1 number, and 1 special character is also not a valid password complexity criterion while setting up password policies, as this criterion does not meet the minimum length requirement of 8 characters for Oracle Cloud applications. Reference:

When the invoice is created, the unbilled receivables balance is reduced and the accounts receivables balance is increased by the invoice amount. This is because the revenue has already been recognized and the invoice is just a request for payment from the customer.Reference:

The option that allows you to achieve this requirement is Appearance Page. This page allows you to create and apply a new theme for the application user interface by selecting various options such as colors, fonts, logos, etc. You can also preview and publish your theme changes using this page. Structure Page is not an option that allows you to achieve this requirement. This page allows you to customize the structure and layout of the application user interface by adding or removing components such as regions, tabs, fields, etc. Setup and Maintenance Work Area is not an option that allows you to achieve this requirement. This work area allows you to perform various setup tasks for implementing and configuring Oracle Fusion applications using predefined templates and spreadsheets. User Interface Text is not an option that allows you to achieve this requirement. This option allows you to customize the text and labels of the application user interface by editing or translating them using various tools such as Text Editor or Translation Workbench.Reference:

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:

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:

Ref: tor-job-role.html#Project_Administrator_privileges

Project Manager has duty role ‘Project Forecast Approval Duty’ assigned but

Project Administrator has duty role ‘Project Forecast Inquiry Duty’ – no approval authority

Both roles have duty role ‘Project Forecast Management Duty’ which enables them to Allow creation, submission, update, and deletion of working versions of project forecasts. (Cloud _Roles_Duties.xlsx)

The BPM Worklist component provides a human workflow service that handles all interactions with users or groups in business processes. The BPM Worklist allows users to view, act on, track, and administer workflow tasks that require their attention. Users can also delegate, escalate, or reassign tasks to other users or groups as needed. Reference:

Ref: plementing-project-execution-management-applications.html#FAPFM1718570

Topic -Manage Maintenance Conditions for Project Enterprise Labor Resource

Reference

Topic – Creating Calendars for Projects and Resources: Procedure

Project Schedules are used as a base for project and resource calendars in Project Execution Management applications. The smallest scheduling unit is a day. For example, you can define the number of hours in a day but, you can't schedule work for a specific time of the day.

The following are the elements of a schedule:

Shifts

Workday patterns

Exceptions

To put in a validation process that allows only a certain number of maximum hours an employee can charge in a day, and a minimum of hours he or she can report in a week, you need to use time entry rules. Time entry rules allow you to define the conditions and actions for validating time entries based on various attributes such as hours, dates, projects, tasks, etc. You can also specify the error messages and severity levels for the time entry rules. Reference:

Project classifications are used to group and report on projects based on different criteria. A project template can have one or more project classifications, which can be either required or optional. When a project is created from a template, the required project classifications must be entered, while the optional ones can be left blank. A project class category in a project classification must be associated with a set code, which determines the list of values for the project class. Project classification is not a mandatory field on a project template, but it is recommended to use it for reporting purposes.Reference:

The Deploying step within the functional setup manager helps you to move your verified setup data from the test environment to a production environment. This step allows you to export and import setup data across instances using spreadsheets or configuration packages. You can also compare and validate setup data across instances using reports and dashboards. Reference: