Oracle 1Z0-1057-24 Exam Dumps

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oefpp/overview.html#External_Data_Integration_Services_for_Oracle_Cloud_Overview

Assignment of Supporting Reference:

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

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

https://docs.oracle.com/en/cloud/saas/sales/18c/oscus/setting-up-applications-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 theForgot Passwordlink 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.

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.