Oracle 1z0-1057-24 Oracle Project Management Cloud 2024 Implementation Professional Exam Practice Test

Referencehttps://docs.oracle.com/en/cloud/saas/applications-common/19b/facia/define-enterprise-structures.html#FACIA462453

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.

Ref:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/fapfm/implementing-pr 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.

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

Referencehttps://docs.oracle.com/ cloud/latest/projectcs_gs/OAPFM/OAPFM1125357.htm#OAPFM1125357

Assignment of Supporting References

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

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

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.

Referencehttp://www.oracle.com/us/products/applications/fusion/fusion-proj-port-mang- solut-brief-173079.pdf

(Page 2)Flexible Contract-Based Billing

Traditional contract and billing systems enforce a rigid relationship between a project and a funding agreement, which can constrain project setup and execution.Oracle Fusion Project Portfolio Management provides a highly flexible approachto project contract-based billing via a non-exclusive

relationship between multiple projects and tasks with contracts and contract lines.This means that you will have full control over defining contracts, rates and limits, and when and how to recognize revenue and generate invoices while segregating the planning and execution of your projects.

 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

Ref:https://docs.oracle.com/cd/E17904_01/doc.1111/e14431/managing.htm#APMAG3333

Fusion Middleware Administrator's Guide for Authorization Policy Manager

Managing Security Artifacts

This chapter describes the procedures an administrator follows to manage application-specific security artifacts, view the external role hierarchy, manage the application role hierarchy, andmanage the many-to-many mapping of application roles to external roles from both the application and the external role point of view.

This chapter is divided into the following sections:

Managing Application Security Artifacts

Viewing the External Role Hierarchy

Managing the Application Role Hierarchy

Mapping Application Roles to an External Role

Mapping External Roles to an Application Role

Role Mapping Policy

A Role Mapping Policy is used to determinewhat external subjects(users, groups orExternal Roles) are assigned to the applicable Application Role. The Application Role, when referenced in an Authorization Policy, defines the principals affected by the Authorization Policy. Role Mapping Policies may also include conditions

Oracle Identity Manager –Not used for mapping application roles to external roles

How do Users Interact with Oracle Identity Manager?

Oracle Identity Manager provides an end-user interface, called the Identity Self Service console, and a system administrator interface, called the Identity System Administration console. Both end-users and system administrators use the web browser to log on to Oracle Identity Manager. Oracle Identity Manager (OIM)

OIM provision users, roles, and defines what a user can do in Oracle Cloud

Duty Roles are mapped to jobs and assigned access privileges (Data Security)

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

Ref: Implementing-Project-Financial-Management-and-Grants-Management.pdf

Chapter 3 – Define Project Organizations Page # 12

Topic – Selecting Organization Hierarchies for the Business Unit

The following conditions are required for an organization to be eligible to be a project expenditure organization:

You must assign the Project Expenditure Organization classification to the organization.

The organization must belong to the hierarchy that you specify in the project implementation options for the business unit.

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

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

Ref: Implementing-Project-Financial-Management-and-Grants-Management.pdf (19A Part # F11256-01)

Chapter 3 – Define Project Organizations

Topic - Set Assignments and Project Data – How They Work Together (Page 29)

Business Unit as Set Determinant

Business units enable you to control and report on financial transactions, usually for specific geographical entities within the enterprise. For project management purposes, assign the Project Accounting business function to the business unit.

Business unit is a set determinant for the project-related reference data objects described in the following table.

Ref Data Object

Entities

Project Accounting Definition

Project Types

Project Rates

Project rate schedules

Project Unit as Set Determinant

Use project units to enforce consistent project management practices across your enterprise. Project unit is a set determinant for the reference data objects described in the following table.

Ref Data Object

Entities

Project Definition

Class codes, financial plan types, project plan types and project roles

Project Transaction Types

Expenditure types and work types

You can only select class codes, plan types, roles, expenditure types and work types that are assigned to the same set as the project unit. To enable expenditure types and work typesfor use on projects owned by a project unit, assign the set associated with the Project Transaction Types reference data object to those entities

According to Oracle sources1, the inheritance between requirements, tasks, and deliverables works as follows:

You can associate a deliverable with a task independent of associating a requirement with a task. You can also associate a deliverable with a requirement independent of associating a task with a requirement1.

A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. You must manually associate the deliverable with the tasks that produce it1.

Therefore, the correct answer is B and D.

1: Can deliverables for projects and tasks be inherited from associated requirements? - docs.oracle.com (index 1)

In Oracle Project Management, you can define requirements, tasks, and deliverables for your project based on your project methodology and lifecycle. Requirements are statements of needs or expectations that must be met by the project outcome. Tasks are units of work that must be performed to complete the project. Deliverables are products or services that are produced or provided as part of a task or requirement. Two correct statements about how the inheritance between requirements, tasks, and deliverables works are:

You associate a deliverable with a task independent of associating a requirement with a task. This means that you can create a deliverable for a task regardless of whether the task is linked to a requirement or not.

A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. This means that you have to manually associate a deliverable with a task even if both the deliverable and the task are linked to the same requirement.

Ref:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/fapfm/im plementing-project-execution-management-applications.html#FAPFM1718570

Topic -Manage Maintenance Conditions for Project Enterprise Labor Resource

When a project invoice is transferred or created in Receivables, the project sends only the invoice header and invoice line description to Receivables, not the invoice distributions. The invoice distributions contain the detailed information such as quantity, unit price, and line total. Therefore, the Receivables invoice does not show these details, but only shows a quantity of 1 and a unit price equal to the line total.Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-invoices.html#OAPFM2355931

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

Ref:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapfm/project-control-configuration-manage-spread-curves.html#OAPFM79760

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

Referencehttps://docs.oracle.com/cd/E60665_ 01/common/OAFSM/OAFSM1166430.htm#OAFSM1166426

Ref:https://docs.oracle.com/en/cloud/saas/project-portfolio-manag ement/19a/oapfm/project-foundation-configuration-manage-project-types.html#OAPFM220111

Topic – Asset Cost Allocation Methods: Explained

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

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/19b/oapfm/project- billing-configuration-define-transfer-pricing.html#OAPFM3094619

Referencehttps://docs.oracle.com/cd/E51367_01/projectop_gs/OAPJC/F1071488AN1004C.htm

To import and process third-party transactions that are costed and accounted, you need to set the Transaction Source Options for the transaction source that you use to import the transactions. The Transaction Source Options allow you to specify whether the transactions are costed and accounted by the source system or by Oracle Fusion Cost Management. You can also specify whether to validate and transfer costs and accounting entries to projects and general ledger.Reference:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-costs.html#OAPFM2355941

Rapid Implementation for Project Financial Management Applications allows you to configure some common setups for project costing and billing using predefined templates and spreadsheets. Some of the setups that can be configured using Rapid Implementation are expenditure types, project templates, and project types. Work types and project class categories are not part of Rapid Implementation.Reference:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/implement-project-financial-management-applications.html#OAPFM2355871

Ref:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapjs/update-project-perfor mance-data-and-generate-kpis.html#OAPJS16654

Performance Status Indicator

Performance status indicators give an immediate picture of the status of a project, such as critical, at risk, and on track. Each distinct icon indicates the status and severity of performance. During KPI definition, you first associate status indicators with performance statuses:

Critical

Severe

At risk

On track

Ahead

You then associate these statuses with threshold levels. When KPI values are generated for a project, each value is compared to the defined thresholds and the corresponding status indicator for the KPI appears on project performance reports.

A status can identify negative performance so that you can take the appropriate actions to prevent or quickly resolve problems. Conversely, a status can identify positive performance to help you track expected or excellent performance.

https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/fapfm/implementing-project-financial-managemen t-applications.html#FAPFM975706

Create Key Performance Indicators

Create key performance indicators (KPI) to measure how well your organization performs an operational, tactical, or strategic activity that is critical for the current and future success of the organization.

Note: To create KPIs you must enable a project unit to track key performance indicators.

Use the Threshold Levels section to specify thresholds to indicate the health status of a KPI. Select one of the following options:

Multiple threshold levels

Single threshold level value

Single threshold level range

Ref:https://do 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

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/19a/faopm/subjectareas.h 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.

Reference https://docs.oracle.com/cloud/latest/projectcs_gs/OAPFM/OAPFM1125361.htm#OAPFM1125277 (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.

The Project Integration Specialist role should be assigned to a user for using the rapid implementation feature to set up the Project Financial Management offering by populating and uploading a Microsoft Excel workbook. This role allows the user to access the Functional Setup Manager and perform the common setups for project costing and billing using predefined templates and spreadsheets. The user can also monitor and validate the setup data using reports and dashboards. Reference:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/implement-project-financial-management-applications.html#OAPFM2356151

The Cost Collection Flexfield is a descriptive flexfield that captures additional information about project costs. It has three core attributes that are required for every cost transaction:Billable Flag, Expenditure Type, and Capitalizable Flag. These attributes can be derived during import if not explicitly entered in a transaction document, based on various rules and sources such as expenditure type defaults, project type defaults, transaction source defaults, etc. Funding Source and Work Type are not core attributes of the Cost Collection Flexfield, but context-sensitive segments that can be optionally enabled for certain transaction sources or business units. These segments capture additional information about how the costs are funded or what type of work is performed. Reference:https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-costs.html#OAPFM2356141

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

Referencehttps://docs.oracle.com/cloud/latest/projectcs_gs/FAPFM/FAPFM1192914.htm

Topic – Creating Calendars for Projects and Resources: Procedure

Project Schedules are used as a base for project and resource calendars in Project Execution Management applications. The smallest scheduling unit is a day. For example, you can define the number of hours in a day but, you can't schedule work for a specific time of the day.

The following are the elements of a schedule:

Shifts

Workday patterns

Exceptions

Application Composer is a tool that allows you to configure standard objects or create custom objects to include business specific attributes for Project Execution Management. Four of the standard objects that you can configure using Application Composer are:

Project Gates: These are checkpoints that mark the completion of a phase or stage in a project lifecycle.

Project Issues: These are problems or risks that affect the progress or outcome of a project.

Project Milestones: These are significant events or achievements that indicate the status or completion of a project or task.

Project Deliverables: These are products or services that are produced or provided as part of a project or task. Project Resource Request and Project Resource Assignment are not standard objects that you can configure using Application Composer. These are features that allow you to request and assign resources for projects and tasks based on various criteria such as availability, qualifications, preferences, etc. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-execution.html#OAPFM2356201

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

Project gate statuses are values that indicate the progress or completion of a project gate. A project gate is a checkpoint that marks the end of a phase or stage in a project lifecycle. Three of the project gate statuses are:

Open: This status indicates that the project gate is not yet ready for review or approval.

In Review: This status indicates that the project gate is under review or approval by the gate reviewers or approvers.

Closed: This status indicates that the project gate has been reviewed or approved and the project can move to the next phase or stage. Approve and Draft are not project gate statuses, but actions that can be performed on a project gate. Approve is an action that allows a gate approver to approve a project gate and change its status to Closed. Draft is an action that allows a gate owner to create or edit a project gate and change its status to Open. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-execution.html#OAPFM2356251