Ref:https://docs.oracle.com/en/cloud/saas/project-portfoli 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

Referencehttps://docs.oracle.com/cloud/farel8/projectcs_ gs/OAPEX/F1082603AN23E61.htm

Manage Project Enterprise Labor Resource Maintenance Conditions

Project Enterprise Labor Resources: How They Are Automatically Created and Maintained

Run the Maintain Project Enterprise Labor Resources process to create resources, remove resource availability for staffing, and maintain the resource search index.

Settings That Affect the Maintain Project Enterprise Labor Resources Process

Create and maintain project enterprise labor resources by defining a set of conditions that specify the employees and contingent workers in Oracle Fusion Human Capital Management (HCM) to create as resources in Oracle Fusion Project Portfolio Management. Define the resource attribute values, such as the resource calendar and primary project role, to assign to the new resources.

The following table lists the criteria that you define for selecting HCM persons to create as project enterprise labor resources.

Selection Criteria

Description

Person type

Select the HCM person type for the process to use as criteria when selecting HCM persons to create as resources. Available person types are employees, contingent workers, orboth employees and contingent workers.

Option to select people based on job

Select this option for the process to create resources for HCM persons with specific jobs.

CautionIf you do not select job criteria for this condition, the process will create resources for all eligible people based only on the person type.

Jobs

If you selected the option to select people based on job, then select the jobs for the process to use as HCM person selection criteria.

The following table lists the attributes for which you specify values to assign to resources that are created for the condition.

Resource Attribute

Description

Option to manage resource availability and staffing

Select this option for resource managers to manage the availability and project staffing of resources who are created based on the condition. Resources who are managed in Oracle Fusion Project Resource Management are eligible to fulfill project resource requests.

Calendar

Select the resource calendar for resources that are created based on the condition. The resource calendar defines the work schedule for project enterprise labor resources, and includes working days and hours and any exceptions, such as holidays.

Primary project role

Select the primary project role for resources that are created based on the condition. Project roles are maintained in Oracle Fusion Project Management.

Cost rate and currency

Enter the cost rate and currency for resources that are created based on the condition.

Bill rate and currency

Enter the bill rate and currency for resources that are created based on the condition.

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

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

Ref:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/18c/oapfm/project-costing-configuration-define-project-costing-integrations.html#OAPFM174886

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.

Referencehttps://docs.oracle.com/cloud/latest/common/FASCC/FASCC1124283.htm

Topic -Contract Actions and Status Changes: Explained

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

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