Oracle 1Z0-1057-24 Exam Dumps

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapfm/project-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.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapjc/allocate-project-costs.html#OAPJC94831

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: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapem/manage-project-requirements.html#OAPEM874365

Project Requirements: Explained

Requirements enable you to capture your business needs. If you manage projects using the Agile development methodology, you start by identifying the high-level requirements and decomposing them further to manage the completion of work on the requirement.

You use the Project Requirements work area to:

Organize backlog items by requirements

Manage your list of backlog items

Create project tasks for backlog items

Assignment of Supporting Reference:

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

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