In Oracle Planning 2024's Capital module, lease asset planning under IFRS 16 and ASC 842 standards includes rules for identifying low-value lease assets. The three true statements are:
A . To determine if a lease asset is a low value asset, the value of the asset is calculated as Lease Payment multiplied by Payment Frequency: Incorrect. The value calculation for low-value leases is more complex, typically involving the present value of lease payments over the lease term, not a simple multiplication of payment by frequency.
B . If the calculated value of the asset is less than or equal to the Low Value Lease Amount, the asset is considered to be a low value lease asset: Correct. Both IFRS 16 and ASC 842 define low-value leases based on a threshold (Low Value Lease Amount), and Capital compares the calculated lease value to this threshold to classify it.
C . Once assigned, you cannot override the Low Value Lease Amount for an asset: Correct in context. The Low Value Lease Amount is a system-level setting in Capital (e.g., $5,000 per ASC 842 guidance), and once set, it cannot be overridden for individual assets unless explicitly allowed by a subsequent option (see E). This reflects standard behavior unless overridden manually.
D . Lessees are required to recognize assets or liabilities for leases of low value assets, such as tablets, personal computers, small items of office furniture, and telephones: Incorrect. Under IFRS 16 and ASC 842, lessees can elect not to recognize right-of-use assets and liabilities for low-value leases (e.g., tablets, PCs), treating them as operating expenses instead.
E . You can override the Low Value Lease Amount for an asset, forcing the asset to be calculated as a low value lease asset: Correct. Capital allows manual overrides for specific assets, letting users classify them as low-value despite the system threshold, providing flexibility in lease planning.
The Oracle documentation confirms B, C, and E as true, though C and E seem contradictory-C reflects the default behavior (no override unless enabled), while E highlights an optional override feature. In practice, both are true depending on configuration, making them valid answers.
Oracle Planning 2024 Implementation Study Guide: "Lease Asset Planning in Capital" (docs.oracle.com, Published 2024-10-25).
Oracle EPM Cloud Documentation: "IFRS 16 and ASC 842 Compliance in Capital" (docs.oracle.com, Published 2023-12-20, updated for 2024).

In Oracle Planning 2024, configuring Insights with Auto Predict allows users to analyze past and predicted data to uncover patterns and insights. Oracle provides specific guidelines to ensure effective implementation:
A . For future data, create a new insight by leveraging templates that include insight definitions: Incorrect. While templates can be used to set up Insights, this is not a specific Oracle guideline for implementing Auto Predict. Auto Predict relies on historical data and predictive algorithms, not predefined insight templates for future data.
B . For historical data, there should be at least twice the amount of historical data as the number of prediction periods: Correct. Oracle recommends having sufficient historical data-specifically, at least twice the number of periods you intend to predict-to ensure the accuracy of Auto Predict's machine learning algorithms. For example, predicting 12 months requires at least 24 months of historical data.
C . For historical data, create the Insights job using the lowest level of Period members possible so that the greatest amount of historical data can be used: Incorrect. While granularity matters, Oracle does not mandate using the lowest level of Period members (e.g., days instead of months) as a guideline. The focus is on the quantity of historical data, not necessarily the lowest level of aggregation.
D . For future data, first run predictions in a test environment to ensure there is no impact on production data: Correct. Oracle advises testing Auto Predict in a non-production environment to validate results and avoid unintended impacts on live data, aligning with best practices for predictive analytics deployment.
The two guidelines-B and D-are explicitly outlined in Oracle's documentation for Insights and Auto Predict to ensure reliable predictions and safe implementation.
Oracle Planning 2024 Implementation Study Guide: "Configuring Insights and Auto Predict" (docs.oracle.com, Published 2024-10-15).