Oracle 1z0-1057-24 Dumps

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.

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:

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

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

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:

Program management is a capability that allows you to coordinate and track multiple related projects and tasks as part of a strategic program. To configure the program options as part of implementing the program management capability, you need to define three components:

Calendar: This component allows you to specify the calendar that is used to calculate the dates and durations for the program and its projects and tasks.

Calculation Methods: This component allows you to specify the methods that are used to calculate the progress, performance, and variance measures for the program and its projects and tasks based on various sources and formulas.

Derivation Methods: This component allows you to specify the methods that are used to derive the attributes and values for the program and its projects and tasks based on various rules and conditions. Currencies and Accounting Methods are not components that are required to configure the program options. Currencies are used to define the currency conversion rates and rules for the program and its projects and tasks. Accounting Methods are used to define the subledger accounting rules and options for the program and its projects and tasks. Reference:

Status tracking is a feature that allows you to track the progress and history of project invoice approval notifications. Status tracking provides information such as who approved or rejected the invoice, when and why they took the action, who is currently assigned to approve or reject the invoice, etc. Three of the information that can be tracked as status tracking for project invoice approval notifications are:

Person assigned for approval: This shows the name of the person who is currently assigned to approve or reject the invoice notification.

Prior actions: This shows the list of actions that have been taken on the invoice notification by previous approvers or rejectors, such as approve, reject, request information, etc.

Persons with whom it is still pending approval: This shows the list of persons who are still in the approval chain for the invoice notification and have not taken any action yet. Pre-approval activities and date-wise updates to the document are not information that can be tracked as status tracking for project invoice approval notifications. Pre-approval activities are tasks that need to be performed before submitting an invoice for approval, such as validating or transferring the invoice. Date-wise updates to the document are changes that are made to the invoice document after it has been submitted for approval, such as adjusting or reversing the invoice. 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:

Ref:

Topic -Resource Available Capacity Score: How It's Calculated

Calendars Used to Calculate Resource Available Capacity Scores

How the Resource Available Capacity Score Is Calculated

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

Project type is a classification that defines the common attributes and processing options for projects. Some of the correct statements about project type are:

Project type can be used as a source in subledger accounting. This allows you to create accounting rules based on the project type attribute.

Summarization options can be specified at project type. This allows you to control how the project transactions are summarized for reporting and performance purposes.

Project type can be associated with multiple project units. This allows you to share the same project type across different business units or organizations. Project type cannot be enabled for both billing and capitalization, as these are mutually exclusive options. Classifications cannot be assigned at project type, but at project or task level. Reference: management/20c/oapfm/set-up-project-financial-management.html#OAPFM2355971

 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:

Ref: ect-foundation-configuration-define-types-and-categorizations.html#OAPFM222700

Topic - Manage Project Class Categories

Setting Up Class Categories: Points to Consider

Available as Accounting Source

This option indicates if theclass category is available as an accounting source so that Oracle Fusion Subledger Accounting can use the category to create mapping sets, account rules, journal line rules, and description rules.

Only one class category at a time is available as an accounting source in Oracle Fusion Subledger Accounting. To change the class category that Oracle Fusion Subledger Accounting uses, deactivate the old class category and create a new one with a different date range.

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

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:

Reference

Ref:

Reference 0AN13D82.htm

How Resource Mapping Is Calculated

You can track the cost impact of every resource that has been assigned to a project task and use the resource breakdown structure to view the breakdown of these costs. Oracle Fusion Projects associates the costs of the resources used for tasks with branches and levels in the resource breakdown structure. The process for determining the correct association is managed by rules of precedence.

Oracle Fusion Projects uses the followingrules to associate cost amounts with resources:

Select thelowest levelin the resource breakdown structure to which atransaction can map.

If there is only one level to which the transaction maps, the cost amounts are mapped to that level.

If the transaction maps to more than one level, Oracle Fusion Projects sums the precedence numbers for all resource types in the branch and gives precedence to the resource element in thebranch with the lowest sum.

If more than one branch has the lowest precedence number at the lower level, the application uses the precedence number of thenext level up.

If the sum of precedence numbers is the same for more than one branch, precedence is given to the branch with the lowest number at the lowest level.

If one branch contains a user-defined resource type, precedence is given to the branch thatdoes not contain a user-defined resource type.

NoteOracle Fusion Projects gives more precedence to a lower precedence number. For example, a resource element with a precedence number of 1 is given precedence over a resource element with a precedence number of 10.

Project Control is the product offering that simplifies the planning, budgeting, and forecasting capabilities as part of Project Management Cloud. Project Control allows you to create and manage project plans, budgets, and forecasts using various methods andsources. You can also monitor and control project performance and variances using dashboards and reports. Reference:

 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

The source that can be used while defining the account rule to achieve this requirement is Expenditure Organization Cost Center Segment. This source allows you to retrieve the value of the cost center segment based on the expenditure organization of the transaction. The expenditure organization is an attribute of a transaction that represents the organization that incurs or owns the cost of the transaction.

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:

The expenditure type class that is recommended for the expenditure types that need to be defined for work order labor and equipment resource transactions is Work In Process. This class indicates that the transactions are related to work orders that are performed as part of a project-driven supply chain solution. This class also allows the transactions to be processed by Oracle Fusion Manufacturing applications and transferred to Oracle Fusion Project Costing applications. Supplier Invoice is not a valid expenditure type class for work order labor and equipment resource transactions. This class indicates that the transactions are related to supplier invoices that are entered in Oracle Fusion Payables applications and transferred to Oracle Fusion Project Costing applications. Usages is not a valid expenditure type class for work order labor and equipment resource transactions. This class indicates that the transactions are related to material usages that are entered in Oracle Fusion Inventory Management applications and transferred to Oracle Fusion Project Costing applications. Inventory is not a valid expenditure type class for work order labor and equipment resource transactions. This class indicates that the transactions are related to inventory movements that are entered in Oracle Fusion Inventory Management applications and transferred to Oracle Fusion Project Costing applications. 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:

The project start date is not later than the earliest task date.

The project finish date is not earlier than the latest task date.

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.

Reference le.com/helpPortal/topic/TopicId_P_8718794B26A7BB93E040D30A688149A3

The Accounts Member component of performance measures allows you to select the method that is used to measure accounts such as budget, forecast, and actual. The Accounts Member component defines the account dimension member for the performance measure, which represents the financial data that is measured. You can also specify the aggregation rule and calculation method for the account dimension member. Reference:

When you reclassify the billing offset balances in the first period, the accounting entry is:

Dr Accounts Receivables 10000 - Cr Unbilled Receivables 10000

This entry reduces the unbilled receivables balance and increases the accounts receivables balance by the invoice amount. This is because the invoice has been created and sent to the customer, and the billing offset account is no longer needed. 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.

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.

 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: /en/cloud/saas/project-portfolio-management/19a/oapex/define-project-management-configuration.html#OAPEX1357147

Topic - Microsoft Project Prevalidation: Explained

The following table describes Prevalidation rules for tasks and resource assignments.

Level

Rule

Lowest-level tasks

One labor and multiple expense resources are allowed for a lowest-level task.Remove other resources.

Summary tasks

Only one labor resource with zero allocation is allowed for a summary task.Remove all other resources.

Milestone tasks

No subtasks are allowed under milestone tasks. Milestones must be lowest-level tasks.

Milestone tasks

Milestone tasks must have zero duration.

Milestone tasks

Only one labor resource, with zero effort, is allowed for a milestone task.Remove all other resources.

When exporting milestone tasks, ensure that the tasks:

Are lowest-levels task with zero duration, that is, the same start and finish dates.

Have only one labor resource assignment with zero effort.

Have percent work complete values of 0 or 100 percent. Any other values are set to zero before export.

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

The precedence order that is used by the system for labor schedules to distribute payroll cost is Assignment > Assignment Element > Element. This means that the system first looks for a labor schedule that is assigned to the employee assignment, then for a labor schedule that is assigned to the payroll element of the employee assignment, and finally for a labor schedule that is assigned to the payroll element itself. The system uses the first labor schedule that it finds in this order to distribute the payroll cost to projects and tasks based on the hours and rates defined in the schedule. Reference:

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