Free 1Z0-1057-23 Exam Dumps Preview

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/applications-common/r13-update17d/faser/implementing-security-in-oracle-fusion-project-portfolio-management.html#FASER1840867

Reference
https://fusionhelp.oracle.com/helpPortal/topic/TopicId_P_988B43C997365159E040D30A68
813832
https://docs.oracle.com/cd/E48434_01/fusionapps.1118/e49622/F1125377AN61D92.htm

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 types for use on projects owned by a project unit, assign the set associated with the Project Transaction Types reference data object to those entities

Reference
https://fusionhelp.oracle.com/helpPortal/topic/TopicId_P_87F467307D50416BE040D30A68
816855
Spread curves let you distribute quantity, cost, and revenue amounts automatically across accounting or project accounting periods. You assign a spread curve to each resource class. Planning resources (in the planning resource breakdown structure) inherit the spread curve setting from the associated resource class. You can change the spread curve for the planning resource and for any corresponding task assignments, or budget or forecast lines.

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

Reference
https://docs.oracle.com/cloud/latest/projectcs_gs/OAPFM/OAPFM1125357.htm#OAPFM11
25357
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.
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 balance maintenance or reconciliation and reporting requirements.

When you use Create Tree or Create Tree Version in the action menu, you create a new organization tree or a new version of an existing tree, respectively. These actions result in an Inactive status for the organization tree, until you activate it. When you use View Tree Version or select the Edit icon or click the name of the tree, you open an existing organization tree that has an Active status.
References:
https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-organizations.html#OAPFM2355921

Ref:
https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapfm/project-foundation-configuration-define-project-resource-breakdown-structures.html#OAPFM180158_2Whycan'tIfindpersonsinthelistofresourceswhenIenterteammembers,planningresources,orpersonrateschedules?
You can't find persons in the list of resources when you enter team members, planning resources, or person rate schedules in the following situations: The administrator didn't assign a department while creating users. Persons must have an active assignment and be assigned to a department in Oracle Fusion Human Capital Management before they can be added as team members or entered as resources on the planning resource breakdown structure or person rate schedule.
The resource isn't active in Oracle Fusion Human Capital Management because the current date is before the effective date of the resource. If you want to include persons who will start in the future, select the Include people with future-dated effective start dates option when you search for the person. Persons assigned as project managers aren't active as of the project start date. The assignment of the person is terminated, and an appropriate value isn't set for the number of days to display people with terminated assignments. You can set the profile value appropriately at the site profile level using the Specify Number of Days to Display People with Terminated Assignments task in the Setup and Maintenance work area.

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

Ref:
https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapjc/process-project-cost-transactions.html#OAPJC284872What'saborrowedandlentprocessingmethod?
A method of processing cross-charge transactions that generates accounting entries to share revenue or transfer costs from the provider organization to the receiver organization within a legal entity. An internal invoice isn't created but costs or revenue are shared based on the transfer price rules. This method provides a financial view of the performance of an organization.

Ref:
https://docs.oracle.com/cd/E83857_01/saas/applications-common/18b/oaext/page-modification.html#OAEXT1640891

Reference
https://docs.oracle.com/cloud/latest/projectcs_gs/FAPFM/FAPFM1225328.htm

The borrowed and lent cross charge method is a method that allows you to process cross charge transactions between provider and receiver organizations that belong to different legal entities within the same primary ledger. This method does not generate internal invoices or intercompany accounting entries for cross charge transactions. Instead, this method creates accounting entries that move an amount equal to the transfer price between the provider and receiver organizations using borrowed and lent accounts.
Two statements that are true about this method are: Internal Invoice is not generated with this method. This method does not create internal invoices for cross charge transactions, as these transactions are accounted within the same primary ledger using borrowed and lent accounts. This method allows you to process cross charge transactions across legal entities. This method allows you to process cross charge transactions between provider and receiver organizations that belong to different legal entities within the same primary ledger, as long as they share the same chart of accounts, calendar, currency, and subledger accounting method.

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

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

The workflows in Project Financial Management are business processes that automate the 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.
References:
https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-financial-management.html#OAPFM2356161

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