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

Ref: roject-control-configuration-manage-financial-and-project-plan-types.html#OAPFM75315

Financial and Project Plan Setup Options

The following table describes the basic budget, forecast, or project plan setup options that determine how a plan type is used in the context of a project. Except for third-party scheduling, you can't edit these options at the project level.

Option

Location

Description

Planning amounts

Financial plan type

Indicates that the financial plan type supports the creation of versions with the following amounts:

Cost amounts

Revenue amounts

Both cost and revenue amounts

Either cost or revenue amounts

Approved budget or primary forecast

Financial plan type

Determines whether a financial plan type is used for creating approved budget versions or primary forecast versions that are used for plan comparison or project performance reporting.

Default financial plan type

Financial plan type

Determines whether the financial plan type is the default selection when you create budget or forecast versions.

Workflows

Financial plan type

Enables the use of a workflow for managing budget or forecast status changes.

Third-party scheduling software

Project plan type

Indicates whether project planning is performed in Microsoft Project.

If third-party scheduling is disabled in the project plan type, you can use the associated project or project template to create a project in Microsoft Project. However, you can't export the new project or link it to one created in Oracle Fusion Project Portfolio Management.

Multiple transaction currencies

Financial and project plan type

Enables entry of plan amounts in currencies other than the project currency.

Budgetary control settings

Financial plan type

Manages options for creating control budgets in Oracle Fusion Budgetary Control.

To allocate the rental cost to the projects and tasks based on the raw costs of the tasks from the previous month, you need to do the following:

Allocate rental costs once each accounting period by using the “full” allocation method. This method allocates the entire source amount to the target tasks in one run.

Allocate to all eligible tasks and prorate the allocation by the total actual raw cost accrued for each task during the previous accounting period. This ensures that the source amount is proportionally allocated to the tasks based on their relative raw costs.

Define allocation basis by using Actual Amounts with a period-to-date amount class. This allows you to use the actual raw costs of the tasks as the basis for allocation and to use the amounts from the previous accounting period. Reference:

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 usesthe target percentage to calculate the amount to allocate to the line, and then apportions the results among all the tasks. TheTarget Percentage and Prorate basis methodprovides precise control over how the rule distributes the source pool.

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: 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.

Reference d/latest/projectcs_gs/FAPFM/FAPFM1225328.htm

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:

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.

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:

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:

XML (Extensible Markup Language) is the data format that is supported by SOAP (Simple Object Access Protocol) Web services to establish communication between web services consumers and web services providers. XML is a standard format that allows data to be exchanged across different platforms and applications. SOAP Web services use XML to encode the messages and data that are sent and received between the web services endpoints. 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.

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:

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:

Ref: /saas/project-portfolio-management/19a/oapem/analyze-project-management-performance.html#OAPEM1313471

Topic - Project Labor Demand: How It's Calculated

Settings That Affect Project Labor Demand

Project application administrators must do the following to set up how project labor demand is calculated:

Organize projects into hierarchical groups on the Manage Enterprise Project Structure page.

Change the quarterly FTE hours for the organization on the Define Project Management Implementation Options page, if different from 520 hours.

Note: You can choose to view labor demand annually instead of quarterly.The Project Hierarchy Viewer uses thecurrent dateto determine which year or quarter to display.

To perform revenue recognition based on the Labor and Non-labor Burden schedule types, you need to create a revenue method with a revenue method classification of Rate Based. This classification allows you to use the burdened cost rates of labor and non-labor resources as the basis for revenue recognition. The burdened cost rates are derived from the burden schedules that are assigned to the project or task. Reference:

Ref: tml#Projects__Cross_Subject_Area_Analysis__Real_Time_SA_20

Analyze real-time information on project performance, including budgets, forecasts, costs, commitments, revenue, and invoices.

This subject area analysis allows cross subject area analysis between Funding, Invoices, Revenue, Budget, forecasts, Costs areas.

Ref:

How can I validate distribution sets for projects information?

Oracle Fusion Projects performs validations on Oracle Fusion Payables distribution sets for payables invoices at the time you create the actual distribution set lines. It validates the project and task number during the invoice validation.

Distribution sets are typically used on recurring transactions, and the associated project does not have transaction controls.When you create a distribution set in Oracle Fusion Payables, the distribution set line is not validated against the project transaction controls in Oracle Fusion Projects because you do not enter anexpenditure item date, which is required for transaction control validation.The expenditure item date is not provided because you use the distribution sets for an indefinite period of time.

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.

 The recommendation for this scenario is to define one business unit and two project units. A business unit is an organization that performs one or many business functions such as transaction processing or reporting. A project unit is an organization that manages projects within a business unit or across multiple business units. By defining one business unit and two project units, you can meet the following requirements of the client organization:

The management reporting and transaction processing requirements are the same for both the organizations: This can be achieved by using the same business unit for both the organizations, as the business unit determines the common setups such as ledger, currency, calendar, etc. for transaction processing and reporting.

The project planning, management, analysis and reporting requirements are different for each organization: This can be achieved by using different project units for each organization, as the project unit determines the specific setups such as project types, templates, options, etc. for project planning, management, analysis and reporting. Defining two business units and two project units is not recommended for this scenario, as this would create unnecessary duplication of setups for transaction processing

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:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapjm/index.html#_Toc468200732_1_12

Topic –Privileges- This table lists privileges granted to duties of the abstract role Project Management Duty.

Granted Role - Project Plan Management

Privilege – only A and C are listed

Ref: cs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapjb/record-accounting-for-project-billing.html#OAPJB340382

Topic - Accounting Period and Project Accounting Period Closing: How Validation Works

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:

Ref: tml#OAPJB70183

Bill Plan –Create a bill plan within a contract that uses the invoice method you require. Assign the bill plan to one or more contract lines. A set of instructions on a contract that define how to invoice a customer. Multiple contract lines on a contract can use the same or different bill plans. Invoice Method is used in creating Bill Plan – not a separate setup.

Billing Controls –Contract feature that controls the types of transactions, dates, and amounts a customer may be invoiced for and revenue can be recognized for a contract or contract line. Define billing controls at the contract or contract line level.

Topic -Creating a Contract for Percent Spent Invoice and Revenue Methods: Worked Example

This example describes a scenario where transactions for a contract line need to be invoiced and the revenue recognized using the percent spent method.

What are the revenue and invoice method classifications?Percent Spent

What is the billing extension calculation level for the contract line and project association?Project level

Summary of the Tasks

Create a contract, create the percent spent contract lines, create the bill plan, create the revenue plan.

Prerequisites

Create a project.

Create the project plan for percent spent revenue. Specify the plan type on the percent spent billing extension.

Create an approved cost budget.

Create cost and burden rates.

Enter labor and expense transactions for the project.

Collect costs for the transactions.

Configuration Steps

Creating the Contract

Creating the Percent Spent Contract Lines

Creating the Bill Plan - A set of instructions on a contract that define how to invoice a customer. Multiple contract lines on a contract can use the same or different bill plans.

Creating the Revenue Plan - Common set of instructions for recognizing revenue within a contract. Multiple contract lines on a contract can use the same or different revenue plans.

Invoice method classifications determine how transactions are invoiced. The invoice method determines how invoice amounts are derived.

Enter an invoice method on a bill plan, which you create for a contract and assign to contract lines to provide a set of instructions for creating an invoice.

Createbilling controlsfor a contract or contract line to define the valid transaction dates, billing resources, and amount limits for transactions associated with the contract.

Generate invoices to calculate the invoice amounts for a contract.

The following figure illustrates the components of a project and a contract that determine invoice amounts, and the relationships between the components.

Project and contract components used to determine invoice amounts and generate invoices.

Ref: o-management/19b/oapjb/manage-project-contract-revenue.html#OAPJB164173

Associated Project Percent Spent Example

The following formula calculates the percent spent revenue for the associated project.

((Sum of ITD Actual Cost for every subtask that is part of the associated task/Sum of Total Budgeted cost for every task that is part of associated task)

xAssociated Project Funded Amount) – Sum of Existing Invoice Event Amounts for the Associated Project

((60/300) x750) – 80 =70

((Actual Cost / Budgeted Cost) x Budgeted Revenue) – Sum of Revenue Event Amount

Ref:

Predefined Spread Curves

Name

Description

Dist. Factors

Even

Linear distribution of financial or project plan values across periods.

10-10-10-10-10-10-10-10-10-10

Prorated Even

Linear distribution of financial or project plan values across periods, with an exception of the first period and last period in the financial plan. Financial or project plan values for the first period and last period are prorated based on the number of days in the period.

10-10-10-10-10-10-10-10-10-10

Back Loaded

Back-loaded distribution of financial or project plan values across periods. Assigned amounts increase over succeeding periods.

0-5-10-15-20-25-30-35-40-45

Front Loaded

Front-loaded distribution of financial or project plan values across periods. Assigned amounts decrease over succeeding periods.

45-40-35-30-25-20-15-10-5-0

S Curve

S-shaped distribution of financial or project plan values across periods.

18-10-8-10-15-17-18-17-15-8

Bell Curve

Bell-shaped distribution of financial or project plan values across periods. Assignment of plan values is highest in the middle periods.

0-4-10-12-14-12-10-4-0-0

Daily Spread Analysis

Spread is based upon the number of days in each financial period throughout the duration of the task assignment. Amounts are proportionally distributed throughout all periods for the duration of the task assignment

None

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: /implementing-security-in-oracle-fusion-project-portfolio-management.html#FASER1840867

Reference (what’s a work type?)

In billing, you can use work types to classify work for the following purposes:

To determine the default billable status of expenditure items.

To classify cross-charge amounts into cost and revenue for cross-charge transactions.

Tip:To use work types to determine whether an expenditure item is billable you must set the profile option Work Type Derived for Expenditure Item toYes.

When you create or import expenditure items, the default work type is inherited from the associated task. Tasks, in turn, inherit work type values from parent tasks and ultimately from the project.Project types determine the default work type value for projects and project templates.

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.

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:

The Allow Override option for the Default Capitalized Interest Rate Schedule is specified on the Manage Project Type page. This option allows you to override the default capitalized interest rate schedule for a project or task that uses the project type. The default capitalized interest rate schedule is used to calculate the capitalized interest amount for a project or task based on the interest rates and dates defined in the schedule. 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:

To fix the problem of project resources not reporting their time promptly, you should enable track missing time at project unit. This option allows you to track and report on missing time entries for project resources based on their work assignments and schedules. You can also set up notifications and reminders to prompt resources to enter their time on a regular basis. Reference:

Ref:

Asset Cost Allocation Methods

The asset cost allocation method determines how indirect or common costs incurred on a project are allocated to multiple assets.

You can specify an asset cost allocation method to enable Oracle Fusion Project Costing to automatically allocate unassigned asset lines and common costs across multiple assets. Unassigned asset lines typically occur when more than one asset is assigned to an asset grouping level.

Projects and project templates inherit a default asset cost allocation method from the associated project type.You can override the default at the project level. If you use capital events to allocate costs, then you can also override the asset cost allocation method at the event level

Asset Cost Allocation Methods

The following table describes the available asset cost allocation methods.

Method

Basis of Cost Allocation

Actual Units

Number of units defined for each asset

Current Cost

Construction-in-process (CIP) cost of each asset

Estimated Cost

Estimated cost of each asset

Standard Unit Cost

Combination of the standard unit cost and the number of units defined for each asset

Spread Evenly

Equal allocation of cost to each asset