Oracle 1z0-1057-22 Dumps

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.

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.

Ref:

Reference

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: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-resources.html#OAPFM2356181

Reference

Below is an example of the Financial Summary view on the Cost tab of the Project Overview page.

FM2159921

Configuring Rapid Implementation: Procedure

Project application administrators can use the rapid implementation feature to set up the Project Financial Management offering. Use the Rapid Implementation for Project Financial Management Applications macro-enabled Microsoft Excel spreadsheet to enter setup data and generate the ProjectsWorkbook.zip. Upload this .zip file to the Setup and Maintenance work area. When the upload completes, the offering is configured based on the setup information that you provide.

Perform the following steps to configure rapid implementation for the Project Financial Management offering:

• Prepare setup data.
• Generate CSV files.
• Upload setup data.
• Correct errors, if any, and reload the data.

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

Topic - Entering Planning Resource Breakdown Structure Details

• Click Navigator > Setup and Maintenance, and search for the Manage Planning and Billing Resource Breakdown Structures task.
• Click the Manage Planning and Billing Resource Breakdown Structures link.

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 the Create icon 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 the Allow resource changes at project level check 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 a Job Set as a source of jobs for creating planning resources on your planning resource breakdown structure.
• Click Save.

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: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-resources.html#OAPFM2356001

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:

Selecting the offering you want to implement and enabling optional functional areas and features by opting in are not part of managing an implementation project. These are part of configuring an implementation project, which is done before managing an implementation project. Configuring an implementation project allows you to define the scope and features of your implementation based on your business needs. Managing an implementation project involves assigning tasks to various users who are responsible for managing setup data, monitoring the progress of completing setup tasks, and generating a list of setup tasks. These are part of executing an implementation project, which is done after configuring an implementation project. Executing an implementation project allows you to perform the setup tasks and validate the setup data for your implementation. Reference:

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:

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: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/set-up-project-financial-management.html#OAPFM2356271

The section on the Manage Project Transaction Sources page that will allow you to enable these options is Document Entries. This section allows you to define the attributes and options for each document entry type that is associated with a transaction source. A document entry type represents a group of transactions that have similar characteristics and processing rules. For example, you can define a document entry type for expense reports and enable adjustment and reversal options for this document entry type. The Documents section allows you to define the attributes and options for each document type that is associated with a transaction source. A document type represents a source document that contains one or more transactions. For example, you can define a document type for expense reports and enable validation and transfer options for this document type. The Transaction Source section allows you to define the attributes and options for each transaction source that is used to import transactions from an external system. A transaction source represents a system or application that provides transactions to Oracle Fusion Project Costing. For example, you can define a transaction source for expense reports and enable costing and accounting options for this transaction source. The Transaction Entries section allows you to review and manage the transactions that are imported from an external system using a transaction source. You can view, edit, adjust, reverse, validate, and transfer transactions in this section. Reference:

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapem/define-project-deliverables.html#OAPEM1122079

Associate deliverables with one or many tasks or requirements at any level. Associate existing deliverables to tasks or requirements or create deliverables directly for tasks or requirements. You can delete a deliverable in New status if it is not associated with tasks or requirements.

Can deliverables for projects and tasks be inherited from associated requirements?

No. A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement.

You associate a deliverable with a task, independent of associating a requirement with a task.

Ref: st-transactions.html#OAPJC284872

What's a borrowed and lent processing method?

A method of processing cross-charge transactions that generates accounting entries to share revenue or transfer costs from the provider organization to the receiver organization within a legal entity. An internal invoice isn't created but costs or revenue are shared based on the transfer price rules. This method provides a financial view of the performance of an organization.

Budgetary control is a feature that allows you to monitor and control project costs against approved budgets. You can enter the amounts in the budget versions for these projects at two levels: Task and Project. These levels correspond to the budgetary control levels that are defined for the project type. You can also view and compare the budget amounts and actual costs at these levels using reports and dashboards. Expenditure Type, Top Resource, and Expenditure Category are not levels at which you can enter the amounts in the budget versions for these projects. These are attributes that can be used to group and filter the budget and actual amounts for reporting purposes. Reference:

Reference roject-control-configuration-manage-financial-and-project-plan-types.html#OAPFM79055

Topic - Project Date Cascade Options

Use the Cascade option choice list to determine whether your changes to project dates cascade to tasks.

Use the Basic Information region on the Edit Project Template page to select one of the following options:

• Do not cascade project date changes to tasks: Both start and finish dates are editable. However, you must ensure the following:

• Cascade project start date change to affected tasks: You can edit only the project start date.
• Cascade project finish date change to affected tasks: You can edit only the project finish date.

Do not cascade project date changes to tasks is the default value. You must select the cascade option each time you change the project dates, as your selection isn't saved for future date changes.

If you select to roll up planned dates for tasks or are using an external application for scheduling, then you can't modify the project start or finish dates.