Oracle 1Z0-456 - Questions & Answers

A territory becomes invalid if its boundaries go beyond the boundaries of its parent territory.

Note: When you create or edit a territory proposal, you can include active territories. When you activate your proposal, all territory definitions in the proposal are validated, and the proposal fails if any defined territories are invalid.
References:
Oracle Fusion Applications Sales Guide. Invalid Territories: Explained

The object or attribute cannot be set to inactive if there is a mapping or rule defined using the object or attribute.

Note:
When the assignment object inactive box is checked the selected work or candidate assignment object is not available for assignment processing. When the assignment attribute inactive box is checked the selected work or candidate object attribute is not available for assignment processing.

References:
Oracle Fusion Applications Sales Implementation Guide, What happens if I mark an
assignment object or one of its attributes as inactive?

Note: Most validation issues are recorded as errors, with the exception of Customer Data Management duplicates found during the Matching Configuration process. In this case, matched records are only considered as errors if:
* Customer Management Duplicates option is set to Do Not Import for the Import Activity and the main object of the Import Activity is a consumer, customer, or legal entity object

Note 2: Customer Data Management Duplicates
Consumer, customer, and legal entity objects imported by themselves or as components of another object are subject to duplicate verification. The duplicates are determined using the following matching configurations:
* Batch Location Basic Duplicate Identification
* Batch Person Basic Duplicate Identification
* Batch Organization Basic Duplicate Identification
You can select from one of the following:

* Do Not Import Duplicate Records
If the main object of the Import Activity is a consumer, customer, or a legal entity object, rows that are matched to existing records will not be imported. These duplicates records are reported in the Exception and Error reports.

If the Customer Data Management objects are components of another object and one or more matches are found, the existing duplicate records are evaluated to determine the most recent record. The most recent record will be associated with the main object being imported.

For example, when importing a marketing response object, the consumer object is also a component of the response. If the consumer is matched to an existing record, the consumer in the interface tables is not imported. However, the response object will import and the most recent existing consumer record will be 100% Real Q&As | 100% Real Pass

associated to the response.

* Import Duplicate Records
The Customer Data Management objects will be imported even if matched records exist.

*Import Duplicate Records and Create Resolution Request The Customer Data Management objects will be imported even if matched records exist. In addition, a duplicate resolution request is created and displayed in the Customer Data Management, Duplicate Resolution work area.

References:
Oracle Fusion Applications Customer Data Management Implementation Guide, Interface
Table Data Validation and Error Counts

B: The administrator must enable nonrevenue forecasting.

Note: Nonrevenue forecasts are optional, but if an organization chooses to enable the feature, typically at some level of management some users can submit both revenue and nonrevenue forecasts, and in this case there is often an expected ratio of revenue to nonrevenue dollars. The ratio could be 1 revenue dollar to 1 nonrevenue dollar or 1 revenue dollar to 9 nonrevenue dollars, but any major discrepancy is cause for further analysis. The nonrevenue forecast is based on the nonrevenue credit split within the opportunity, and is closely associated with the nonrevenue quota goals set on the territory.

C: Nonrevenue forecasts allow overlay resources who are not the owners of the primary territory to submit a forecast on the same revenue as the primary sales resource. The primary sales resource submits a revenue forecast, and the amount should be counted only once for the revenue forecast. The nonrevenue forecast allows the same revenue to be forecasted a second time.

If there are multiple overlay resources who forecasted the same deal, then the same revenue amount can be added to the nonrevenue forecast many times. A primary resource for one territory can submit a nonrevenue forecast for another territory, so the context of the territory determines if a user is submitting a revenue or nonrevenue forecast.

References:
Oracle Fusion Applications Sales Implementation Guide, Nonrevenue Forecasting:
Explained