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

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

The workflows in Project Financial Management are business processes that automatethe approval and notification tasks for various project transactions and events. Two of the workflows in Project Financial Management are:

Project Status Change: This workflow manages the approval and notification tasks for changing the status of a project or task from one value to another. For example, when a project or task is submitted for approval, this workflow routes the request to the appropriate approvers and notifies them of the action required.

Expenditure Item Adjustment: This workflow manages the approval and notification tasks for adjusting expenditure items that have been charged to a project or task. For example, when an expenditure item is adjusted by a project manager or a cost accountant, this workflow routes the adjustment to the appropriate approvers and notifies them of the action required. Capital Interest Calculation, Burden Cost Recalculation, and Asset Line Generation are not workflows in Project Financial Management, but processes that perform various calculations and transactions for project costs and assets. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-financial-management.html#OAPFM2356161

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.

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

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.

Referencehttps://docs.oracle.com/en/cloud/saas/applications-common/r13-update17d/faser /implementing-security-in-oracle-fusion-project-portfolio-management.html#FASER1722595

Ref to “Securing Project Financial Management and Grants Management Applications”

Table lists predefined enterprise roles and the type of security that grants the role access to data in a work area or dashboard.

Enterprise Role

Work Area or Dashboard

Data Security Based On

Project Accountant

Asset

Project business unit

Project Accountant

Costs

Project expenditure business unit

Project Accountant

Revenue

Contract business unit

Project Administrator

Project Financial Management

Project business unit

Project organization

Project Billing Specialist

Invoices

Contract business unit

Project Creator

Project Financial Management

Project business unit

Project organization

Project Management Duty

Project Management Infolet Dashboard

Project assignment

Project Management Duty

Project Performance Dashboard

Project assignment

Project Manager

Project Management Infolet Dashboard

Project assignment

Project Manager

Project Performance Dashboard

Project assignment

Project Manager

Project Management

Project assignment

Project Manager

Project Manager Dashboard

Project assignment

Project Team Member

Project Financial Management

Project assignment

Grants Accountant

Invoices

Contract business unit

Grants Accountant

Revenue

Contract business unit

Grants Administrator

Awards

Contract business unit

Grants Administrator

Contracts

Contract business unit

Grants Administrator

Project Financial Management

Project business unit

Principal Investigator

Awards

Award assignment

Principal Investigator

Contracts

Award assignment

Principal Investigator

Project Financial Management

Project assignment